White Papers
Diagnostics VRTX Chassis
ping
The ping command is used to check the connectivity between systems in the network. When a Web
connectivity is unable to connect to the VRTX Server on the Internet or LAN, the cause is often,
because the Web server is not functioning, or it may be a network-related issue which hinders from
connecting the host system. Therefore, the first step in diagnosing the problem is to test if the
network connection is working. The ping command can be used in this situation without requiring a
Web server. In the diagnostic console "ping" followed by the URL or IP address of the host you want to
test. Ping6 is the equivalent command to IPV6 networks. For example, ping < IP Address or
Hostname>
The following is the sample command and response: $ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.1 ms
--- 127.0.0.1 ping statistics ---
1 packets transmitted, 1 packets received, 0 percent packet loss
From the above command, the delay time and the packet loss can be diagnosed.
ifconfig
ifconfig –(Interface configurator) is widely used to initialize the network interface and to enable or
disable the interfaces. In the VRTX Chassis ifconfig command, when issued on the Diagnostic
console, displays the configuration of the active interface on the chassis to the external network.
This helps to diagnose any issues on the VRTX chassis interface settings.
For Instance: ifconfig
eth0 Link encap:Ethernet HWaddr 78:45:C4:FA:31:90
inet addr:10.36.0.26 Bcast:10.36.1.255 Mask:255.255.254.0
inet6 addr: fe80::7a45:c4ff:fefa:3190/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13180720 errors:0 dropped:0 overruns:0 frame:0
TX packets:489876 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1687604342 (1609.4 Mb) TX bytes:54119040 (51.6 Mb)
Where eth0 is the interface
inet addr is the IP address.
Mask is the subnet mask.
HWaddr is the MAC Address of the device.
gettracelog
The gettracelog command gives access to logs which can help troubleshoot the issues on any settings
or abnormal activities on the chassis, apart from the chassis log and SEL log. The gettracelog
response helps identify the failure more in detail than the Chassis log and SEL log.