network --troubleshoot [--links] [--gateway] [--ntp] [--dns] [--active_domain] [--nis] [--clients] [--port_mapper] [--network_config] [--show_active <NFS|CIFS|OST|NDMP|ISCSI|RDS>] [--interface <bondN | ethN>]
Description
Note: When entering the
network --troubleshoot command string, the DR Series system checks and displays the current state for all of the
--troubleshoot options. To limit the type of network troubleshooting check you want to display, 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]).
Syntax
network --troubleshoot
Result
*** Checking link status for each interface
bond0 : Link detected: yes
eth0 : Link detected: yes
eth1 : Link detected: yes
eth2 : Link detected: yes
eth3 : Link detected: yes
lo : Link detected: yes
*** Getting local IP addresses
bond0 addr:10.25.20.23 Mask:255.255.245.0
*** Getting bond information
Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)
Bonding Mode: transmit load balancing
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:50:56:93:59:7a
Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:50:56:93:59:7b
Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:50:56:93:59:7c
Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:50:56:93:59:7d
*** Getting Gateway status
Gateway IP address is 10.25.20.1
Route to the gateway is up and uses bond0 interface.
Pinging gateway 10.25.20.1
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 0.332/1.612/3.742/1.274 ms
*** Checking NTP configuration
Network time is enabled.
System is configured with following NTP servers:
0.centos.pool.ntp.org
1.centos.pool.ntp.org
2.centos.pool.ntp.org
Checking if NTP servers are reachable...
Pinging 0.centos.pool.ntp.org
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 75.696/76.042/76.541/0.506 ms
Pinging 1.centos.pool.ntp.org
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 49.150/50.098/52.292/1.212 ms
Pinging 2.centos.pool.ntp.org
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 77.854/77.999/78.075/0.085 ms
*** Checking DNS configuration
DNS Suffix: storage.local
Primary Nameserver: 10.25.19.5
Secondary Nameserver: 10.25.19.6
Pinging 10.25.19.5
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 0.253/0.451/1.123/0.336 ms
Pinging 10.25.19.6
Ping successful. No packet loss.
RTT timings min/avg/max/mdev = 0.239/0.537/1.149/0.326 ms
*** Checking Active Directory configuration
AD configuration: This node has not joined any domain.
*** Checking NIS configuration
NIS domain configuration not found.
*** Checking NFS and CIFS clients configured for various containers
NFS/CIFS clients configured for containers:
-no specific clients-
*** Checking if there is another host with same name
Local system name: acme-01.storage.local
Local system IP: 10.25.20.23
Pinging acme-01.storage.local 3 times
Got IP address as 10.25.20.23
Got IP address as 10.25.20.23
Got IP address as 10.25.20.23
No duplicate hostname found on the network.
*** Checking portmapper
portmap (pid 3716) is running
Checking ports currently being used by portmapper
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
