[Wedge100BF-series] Management Port failure Follow

Purpose:

This is the troubleshooting guide for Management Port failure on Wedge100BF-series.

Model:

Wedge100BF-32X/65X/32QS

Procedure:

Caution: The management port can only link up at 1G.

Step 1. Make sure the problem is not cause by physical cable

Try another cable that already ensure it can work well.

Step 2. Ping test on management port

Method 1. Ping test in BMC

Configure the Management Port "eth0" an IP address.

Make sure the IP address is in same subnet as target IP and connected physically.

Then ping the target IP, it can be stop by ctrl+c.

root@bmc:~# ifconfig eth0 188.188.97.171
root@bmc:~# ping 188.188.99.1
PING 188.188.99.1 (188.188.99.1): 56 data bytes
64 bytes from 188.188.99.1: seq=0 ttl=64 time=0.551 ms
64 bytes from 188.188.99.1: seq=1 ttl=64 time=0.476 ms
64 bytes from 188.188.99.1: seq=2 ttl=64 time=0.513 ms
64 bytes from 188.188.99.1: seq=3 ttl=64 time=0.553 ms
64 bytes from 188.188.99.1: seq=4 ttl=64 time=0.553 ms
64 bytes from 188.188.99.1: seq=5 ttl=64 time=0.457 ms
^C
--- 188.188.99.1 ping statistics ---
11 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 0.387/0.486/0.555 ms
root@bmc:~#

Method 2. Login Diag mode to test

To login Diag, please refer to the article: Install and start up Accton Diag

Choose item 7 to test management interface.

Note: This test requires another object(like PC) connect to management port directly with port IP setting 192.168.1.99, switch will force to configure the management IP as 192.168.1.1 automatically.

*********************************************************
(...omitted)
7 The ICMP ECHO test for CPU management interface
(...omitted)
*********************************************************
Please enter your choice (0 to quit): 7
enp2s0 Link encap:Ethernet HWaddr 00:90:fb:5f:9b:1c
PING 192.168.1.99 (192.168.1.99): 56 data bytes

(...omitted)

Item (7) test result: PASSED/FAILED

If the result is PASSED but still can't contact with internet through MGMT port, please check your network environment and configuration again.

If tries several times and the results are FAILED , collect the log to us for RMA.