Network Management

last person joined: 21 hours ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

AirWave Serial Number retrieval via GUI

This thread has been viewed 57 times
  • 1.  AirWave Serial Number retrieval via GUI

    Posted Mar 13, 2019 12:55 AM

    Hello Community,

     

    Is it possible to retrieve the AirWave's serial number via the GUI?

     

    If so, can you please provide the steps on how to access it?

     

    Regards,

    Nathan.



  • 2.  RE: AirWave Serial Number retrieval via GUI

    EMPLOYEE
    Posted Mar 13, 2019 02:25 AM

    Hello Nathan,

     

    You should be able to see the serial number on the license by Navigating to the Airwave GUI, Home --> License tab, by clicking on the license.  or I see that you have tagged Airwave version 8.2.5, so i assume, you are on Airwave 8.2.5 version, you could also go to the Airwave CLI, login as  ampadmin, select option 11 to Enter commands, then type-in the command

    $ license

    This should also print the license output, which should have serial number.

     

    If you do not find the Serial number in your license, please call support 1800 WIFI LAN, they should help you to find it. Hope this helps.

     

    ---



  • 3.  RE: AirWave Serial Number retrieval via GUI

    MVP
    Posted Jan 30, 2020 10:26 AM

    For our environment, our server was deployed 5+ years ago with an enterprise license which does not appear to include our Serial Number. In order to find ours, if you log into the CLI with the ampadmin account and use option 11, use the following command:

     

    dmidecode - Display serial number of the server

     

    It will provide an output similar to:

     

    System Information
    Manufacturer: HP
    Product Name: ProLiant DL360p Gen8
    Version: Not Specified
    Serial Number: XXXXXXXXX
    UUID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX
    Wake-up Type: Power Switch
    SKU Number: XXXXXX-XXX
    Family: ProLiant

     

    Just make sure you are logging the CLI session as it will generate a long string of data and you will likely need to go back to where  you issued the command, this is the second thing it provides. I had to go back to the log in order to scroll back enough to find it.