1: Ping the gateway IP of management vlan 192.168.40.1 from the client ,it is reachable;
2: Check whether the MGMT port of the active and standby MM910 were connected to network: NO
3: Connect to the serial port of the MM910 and check what is the outportmode of MM910: 0
That means the management network of MM910 will come out from the Switch Module of slot 2X and 3X,so can't connect the MGNT of MM910 to network;
4: Ping the gateway IP of management vlan 192.168.40.1 from MM910 CLI,it is reachable;
That means the internal connection between MM910 and 2x,3x switch module is OK,
Two GE ports 2/19/1 and 2/19/2 of 2x and 3x used to connect to two MM910s respectively.
They are used to communicate with the eth0 and eth2 in the internal MM910.
2/19/1 and 3/19/1 connect to SMM1 internal LAN-Switch ,2/19/2 and 3/19/2 connect to SMM internal LAN-Switch .
The three internal network ports of the CPU are described as follows:
: connects to the MGMT ports and switch modules over the LAN switch and maps to the static IP address (eth0) and floating IP address (eth0:0) of the MM910.
: connects to the other MM910 in one chassis over the midplane and is used to synchronize data between the active and standby MM910s.
: connects to the midplane over the LAN switch to communicate with the baseboard management controller (BMC) of each component
5: Run the command ifconfig to check the IP setting of active MM910
We can find the IP of eth2 is 192.168.1.165,it is in the same segment of the client PC IP;In this case,when the MM910 ping the client IP,the package will be send to eth2,not to it's gateway 192.168.40.1,so we can't access the MM910 management IP from the client.