network --troubleshoot [--links] [--gateway] [--ntp] [--dns] [--active_domain] [--nis] [--clients] [--port_mapper] [--network_config] [--show_active ]Isolates a variety of networking issues that you might encounter while running a DR Series system. When you canisolate a problem or issue to a specific cause, you can better understand and resolve it. The DR Series system CLInetwork --troubleshoot command and its options allow you to perform basic troubleshooting checks on the state of a DRSeries system.DescriptionNOTE: When entering the network --troubleshoot command string, the DR Series system checks and displays thecurrent state for all of the --troubleshoot options. To limit the type of network troubleshooting check you want todisplay, define the command string to a specified check (or checks). For example, using network --troubleshoot --gateway, displays the status of the gateway for a DR Series system (for details, see network --troubleshoot [--gateway]).Syntaxnetwork --troubleshootResult*** Checking link status for each interfacebond0 : Link detected: yeseth0 : Link detected: yeseth1 : Link detected: yeseth2 : Link detected: yeseth3 : Link detected: yeslo : Link detected: yes*** Getting local IP addressesbond0 addr:10.25.20.23 Mask:255.255.245.0*** Getting bond informationEthernet Channel Bonding Driver: v3.4.0 (October 7, 2008)Bonding Mode: transmit load balancingPrimary Slave: NoneCurrently Active Slave: eth0MII Status: upMII Polling Interval (ms): 100Up Delay (ms): 0Down Delay (ms): 0Slave Interface: eth0MII Status: upLink Failure Count: 0Permanent HW addr: 00:50:56:93:59:7aSlave Interface: eth1MII Status: upLink Failure Count: 0Permanent HW addr: 00:50:56:93:59:7bSlave Interface: eth2MII Status: upLink Failure Count: 0Permanent HW addr: 00:50:56:93:59:7c40
