AOS-CX Switch Simulator

 View Only
Expand all | Collapse all

ArubaOS-CX Troubleshooting Techniques

This thread has been viewed 135 times
  • 1.  ArubaOS-CX Troubleshooting Techniques

    Posted Apr 20, 2021 11:01 PM

    ArubaOS-CX Troubleshooting Techniques
    This post is about the different troubleshooting techniques available in ArubaOS-CX switches.
    This might come handy either in your simulation lab or in real production network troubleshooting.

    Useful show Commands:

    show interface physical

    To check the Physical interface state

    show interface link-status

    To review the link status

    show interface transceiver detail

    To check the Transceiver details

    show interface statistics

    Review the interface statistics

    show interface statistics non-zero

    Review the interface statistics of the interfaces that have non-zero statistics

    clear interface statistics

    To clear the statistics. Only clears statistics for the current session

     

    Support Logs:

    To Copy support files for all features. Useful for Aruba TAC.

    copy support-files all tftp://<IP address>/filename.tar.gz

     

    Accounting Logs:

    If you make any configuration changes, you should find this change in the accounting logs.

    Accounting logs includes configuration and show commands, as well as HTTP call made using the REST API.

    show accounting log last 10

     

    Event Logs:

    Each event is logged by a daemon (process) on the switch, and the daemon name is included after the hostname. To see the event log in reverse order.,

    show events -r -n 10

    show events -d <process name> -r -n 10


    Terminal Monitor:

    To get live logging of events on terminal (Only supported in a SSH session).

    show terminal-monitor

    To check terminal-monitor severity options

    terminal-monitor

    Enable terminal monitor

    terminal-monitor severity info

    To change the severity level in terminal-monitor

    no terminal-monitor

    Disable terminal-monitor

     

    Diagnostic tools:

    Useful to explore dropped frames due to Jumbo frames, VLAN mismatch

    diag                                                                 //Enable diagnostics mode

    diag interface 1/1/1 statistics                    //diagnostic statistics

     

    Debugging options:

    To check the default logging and logging destinations.

    show debug

    Check debug status

    show debug destination

    Check debug destination (default debug destination is buffer)

    debug <module> <sub-module>

     Enable debugging on a particular process/daemon.

    show debug buffer module <module-name> lines 40

    viewing debug messages.

    clear debug buffer

    To clear the debug buffer

    no debug all

    Disable all debugging

     

    Traffic Mirroring and Packet Captures:

    show mirror                     //To review existing mirrors.

    show mirror 1                  //To review the mirror configured.

    Configuration required:


    Dataplane mirroring can be done to 3 destinations.

    1. Local mirror

    destination interface 1/1/1

     

    1. Remote mirror over GRE tunnel

    destination tunnel <IP address of PC running Wireshark> source <in-band IP address in switch>)

    Note:

    • It is not possible to configure the GRE tunnel over the OOBM network.
    • Since the PC does not have a real tunnel endpoint, the PC complains that the GRE packet cannot be handled.
    • Use display filter in Wireshark. (Eg: To check icmp ping between two switches)

    !ip.src == <IP address of PC running Wireshark> and gre and icmp

     

    1. Mirror to CPU (can be live or to pcap file)

    destination cpu

    Note:

    Launch the diagnostic utility "tshark" to have the live view of the packets.

    diagnostics

    diag utilities tshark

     

    Launch the diagnostic utility "tshark" with the "file" option to save the packets in a pcap file.

    diag utilities tshark delete-file

    clear any existing pcap files.

    diag utilities tshark file

    Save to file.pcap

    copy tshark-pcap tftp://<PC IP address>/file.pcap

    copy tshark file from switch to PC.

     

     

    Control plane analysis – TCPDUMP:

    Control and Management plane protocol can be monitored using "TCPDUMP" that operates on the software of the AOS-CX device.

    diagnostics

    diag utilities tcpdump host-port 1812 vrf default count 10                           //tcpdump on port 1812 that is used for RADIUS communication.



    ------------------------------
    Kapildev Erampu
    PreSales Consultant
    Aruba, a Hewlett Packard Enterprise company
    Sydney, Australia.
    Any opinions expressed here are solely my own and not necessarily that of HPE
    ------------------------------


  • 2.  RE: ArubaOS-CX Troubleshooting Techniques

    Posted Apr 21, 2021 12:56 AM
    In addition to this awesome list of commands, another helpful debug one that I use quite frequently when troubleshooting is the reverse command for debug buffer output:


    Comes in handy especially if debugging client access and trying to find the last client that has authenticated and if there were any issues with something like user role application.

    ------------------------------
    Justin Noonan
    ------------------------------