Functions Of The Management Module Reset Button - Aruba 6400 Series Installation And Getting Started Manual

Faulty or loose cables. Look for loose or faulty connections. If they appear to be OK, make sure that the
n
connections are snug. If that does not correct the problem, try a different cable.
Non standard cables. Non standard and mis-wired cables may cause network collisions and other
n
network problems, and can seriously impair network performance. Use a new, correctly wired cable. For
pinouts and correctly wired cable, compare your cable to the cable information in the latest version of the
ArubaOS-Switch and ArubaOS Transceiver Guide at https://asp.arubanetworks.com/downloads. A category
5 cable tester is a recommended tool for every 1000Base-T network installation.
Improper Network Topologies. It is important to ensure that you have a valid network topology.
n
Common topology faults include excessive cable length and excessive repeater delays between end nodes.
If you have network problems after recent changes to the network, change back to the previous topology.
If you no longer experience the problems, the new topology is likely at fault. In addition, make sure that
your network topology contains no data path loops. Between any two end nodes, there must be only one
active cabling path at any time. Data path loops cause broadcast storms that severely impact your network
performance. Building redundant paths between important nodes in your network provides some fault
tolerance. Before opening redundant paths, enable Spanning Tree Protocol support on the switch.
Spanning tree ensures that only one of the redundant paths is active at any time, thus avoiding data path
loops. Spanning Tree can be enabled through the switch console or the web browser interface. The 6400
switches also support Trunking (link aggregation), which allows using multiple network cables for a single
network connection without causing a data path loop. For more information, go to
https://asp.arubanetworks.com/downloads
Spanning Tree: Layer 2 Bridging Guide
l
Trunking: Link Aggregation Guide
l
Using event and debug logs, show tech, and run-time diagnostics. These built-in features can help
n
to isolate the sources of problems. For more information, see the Diagnostics and Supportability Guide at
https://asp.arubanetworks.com/downloads.

Functions of the Management Module Reset Button

Use a hard reset on a management module only if other methods to recover from a loss of control have
failed. Using a hard reset can result in corrupting the file system on the management module SSD (solid
state drive). In this case, reformatting the management module SSD is required to recover.
Module Soft reset: Press Reset button for less
than five seconds
Module "A"
Resets management module "A"
n
Active
after a 5-10 second delay for orderly
shutdown.
Failover occurs. Module "A"
n
becomes the Standby after it comes
back up.
Module "B" (the former Standby
n
management module) becomes the
new Active management module and
maintains switch operation
If there is no Standby management
n
module installed, or if the installed
Standby module is inoperative, then
the switch goes down while module "A"
and see these publications:
Hard reset: Press Reset button for five
seconds or more
Immediately resets management
n
module "A". There is no shutdown
process. This action can result in a loss
of data that was currently being
processed in module "A".
Management module "B" does not
n
reset; becomes the new Active
management module.
If there is no second module
n
installed, or if the installed second
module is inoperative, then the switch
goes down while management module
"A" completes the reset process and
resumes operation.
Troubleshooting | 85