If you have installed the X3522 low
latency network adapter:
- Identify a server on the same subnet as the X3522:
- If you have a link partner that is directly connected, use that server.
- Otherwise, identify another suitable server.
- Confirm that you can ping the X3522 from the server that you have
identified:
$ ping <x3522_ip_address>For example:$ ping 192.168.10.10 PING 192.168.10.10 (192.168.10.10) 56(84) bytes of data. 64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.068 ms 64 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=0.074 ms - Press Ctrl-C to finish and output
statistics:
ping 192.168.10.10 PING 192.168.10.10 (192.168.10.10) 56(84) bytes of data. 64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.068 ms 64 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=0.074 ms 64 bytes from 192.168.10.10: icmp_seq=3 ttl=64 time=0.080 ms 64 bytes from 192.168.10.10: icmp_seq=4 ttl=64 time=0.050 ms 64 bytes from 192.168.10.10: icmp_seq=5 ttl=64 time=0.048 ms 64 bytes from 192.168.10.10: icmp_seq=6 ttl=64 time=0.049 ms 64 bytes from 192.168.10.10: icmp_seq=7 ttl=64 time=0.048 ms 64 bytes from 192.168.10.10: icmp_seq=8 ttl=64 time=0.049 ms 64 bytes from 192.168.10.10: icmp_seq=9 ttl=64 time=0.047 ms 64 bytes from 192.168.10.10: icmp_seq=10 ttl=64 time=0.049 ms ^C --- 192.168.10.10 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 195ms rtt min/avg/max/mdev = 0.047/0.056/0.080/0.012 ms