Troubleshooting
535-0045-00 Rev 02
Violin 6000 Series Memory Array Installation Guide
47
Troubleshooting
This section provides troubleshooting tips, should you have problems configuring or accessing a
Memory Gateway. The following topics are covered:
• Determining IP Addresses of Internal Memory Gateways (One Known, One Unknown) on
page 47
• Determining IP Addresses of Internal Memory Gateways (Both Unknown) on page 48
• Error Messages When Logging in to Memory Gateways on page 49
Determining IP Addresses of Internal Memory
Gateways (One Known, One Unknown)
If the IP address for one internal Memory Gateway is known (and verified via a direct ping) and the
other Gateway’s address is unknown, you can use the following procedure to determine the
unknown IP address.
1. Verify each Memory Gateway is powered and drawing current by examining the output of the
show array modules type mg detail command.
2. Perform a broadcast ping to 169.254.255.255 from the ACM CLI, similar to this example:
3. Examine the output of the above command and determine the IP address that is not
169.254.1.10 (acm-a), 169.254.1.11 (acm-b) or the known IP address of the other Memory
Gateway. The remaining IP address is the Memory Gateway’s unknown IP address.
4. Set up the host definition for the appropriate Memory Gateway (“mg-a” or “mg-b”) and the
newly discovered IP address using the following commands:
no ip host <mg-a|mg-b> <tab>
ip host <mg-a|mg-b> <ip address>
Note: Pressing the Tab key after the first command auto completes the command with any
existing IP address assigned to that host. If none is present, the first command is unnecessary.
5. Verify the host definition by pinging the Memory Gateway directly using its hostname:
ping mg-a or ping mg-b
violin-acma [violin: master] # ping -b -w1 169.254.255.255
WARNING: pinging broadcast address
PING 169.254.255.255 (169.254.255.255) 56(84) bytes of data.
64 bytes from 169.254.1.10: icmp_seq=1 ttl=64 time=0.061 ms
64 bytes from 169.254.1.11: icmp_seq=1 ttl=64 time=0.102 ms (DUP!)
64 bytes from 169.254.42.198: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)
64 bytes from 169.254.87.114: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)
64 bytes from 169.254.1.10: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 169.254.1.11: icmp_seq=2 ttl=64 time=0.058 ms (DUP!)
64 bytes from 169.254.42.198: icmp_seq=2 ttl=64 time=0.099 ms (DUP!)
64 bytes from 169.254.87.114: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)