Subscribe

Network Interface e0a and e0b cannot be reached.

[ Edited ]

HI, 

I just want to ask what is the reason why e0a and e0b cannot be ping from the network or is there any reason for this issue? The solution I did is to down the port and up it for it to be ping and reach in the LAN. 

Is there any reason why this happend?

Thank you!


Re: Network Interface e0a and e0b cannot be reached.

Hi,

 

Can you list the output of the command "ifconfig -a"

 

Thanks

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Network Interface e0a and e0b cannot be reached.

netapp1> ifconfig -a
e0a: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 192.168.100.91 netmask 0xffffe000 broadcast 192.168.127.255
partner inet 192.168.100.93 (not in use)
ether 00:a0:98:3b:fe:78 (auto-1000t-fd-up) flowcontrol full
e0b: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 192.168.100.92 netmask 0xffffe000 broadcast 192.168.127.255
partner inet 192.168.100.94 (not in use)
ether 00:a0:98:3b:fe:79 (auto-1000t-fd-up) flowcontrol full
e0c: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:a0:98:3b:fe:7a (auto-unknown-down) flowcontrol full
e0d: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:a0:98:3b:fe:7b (auto-unknown-down) flowcontrol full
e0M: flags=0x2b0c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT> mtu 1500
ether 00:a0:98:3b:fe:7d (auto-100tx-fd-up) flowcontrol full
e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT> mtu 1500
inet 192.168.3.34 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
ether 00:a0:98:3b:fe:7c (auto-100tx-fd-up) flowcontrol full
lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
ether 00:00:00:00:00:00 (VIA Provider)
losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188
inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1