Problem

Testing VCS LLT Interface-to-Interface Continuity with DLPI-PING

Description:

Like ICMP Ping (IP related) you can troubleshoot network continuity with an LLT ping called DLPI Ping. A dlpiping server must be configured on one of the NICs to be tested. This server will reflect packets sent by other DLPI devices attached to the network and configured in client mode.


1. On one node in the cluster, perform the following steps to configure a dlpiping server:

Use the getmac command to display the MAC address of the device on which the dlpiping server will be configured. Record this address for use in steps performed on the client systems. The getmac command takes the form of getmac :

# /opt/VRTSllt/getmac /dev/qfe:0
/dev/qfe:0 08:00:20:E7:DE:B2

Configure the dlpiping server on this interface with the dlpiping command. This command takes the form of dlpiping -s  -v :. Note that this server will run in the foreground (no prompt will be returned). Once testing is completed, use ^C to stop the server process. The -v option is a verbose mode and will give more information. 

# /opt/VRTSllt/dlpiping -s -v /dev/qfe:0

At this point, you can configure other nodes in the cluster as dlpiping clients.

2. Use the MAC address obtained in step 1 above, perform the following on all nodes to test:

Configure the dlpiping client to send packets to the dlpiping server configured above. If communication is successful, you will receive a message indicating that the MAC address specified is alive:

# /opt/VRTSllt/dlpiping -c -v  /dev/qfe:0 08:00:20:E7:DE:B2
08:00:20:E7:DE:B2 is alive

If communication is NOT successful, you will receive output indicating there was no response from the specified MAC address:

# /opt/VRTSllt/dlpiping -c /dev/hme:1 08:00:20:E7:DE:B2 no response from 08:00:20:E7:DE:B2

If there is no response, there is most likely a problem with your hardware configuration. For example, you may be using the wrong type of cables for your environment (i.e., standard ethernet cables as opposed to crossover cables) or you may have the server configured on the wrong Network Interface Card (NIC) (i.e., /dev/qfe:0 instead of /dev/qfe:1). Identify possible configuration errors, and repeat the steps above.