Subscribe
karim

network management interface

[ Edited ]

‎2016-01-27 07:27 AM - last edited on ‎2016-01-28 09:34 AM by alissa Netapp Alumni

Labels:

hello folks,

 I am managing a fas 2240 and I dont understand some sentance displayed by the filer.

When I display th result of the command ifconfig -a, il appears a sentence at the of 2 interfaces status.

The following is the result of the command and I don't understand the terme "NOT IN USE"....what this mean?

 

primesB> ifconfig -a
e0a: flags=0x89f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 9000
        ether 02:a0:98:53:1f:b2 (auto-1000t-fd-up) flowcontrol full
        trunked vif0
e0b: flags=0x89f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 9000
        ether 02:a0:98:53:1f:b2 (auto-1000t-fd-up) flowcontrol full
        trunked vif0
e0c: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 00:a0:98:53:1f:b4 (auto-unknown-down) flowcontrol full
e0d: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 00:a0:98:53:1f:b5 (auto-unknown-down) flowcontrol full
e0M: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT> mtu 1500
        inet 10.0.4.11 netmask 0xffffff00 broadcast 10.0.4.255 noddns
        ether 00:a0:98:53:1f:b7 (auto-100tx-fd-up) flowcontrol full
e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT> mtu 1500 PRIVATE
        inet 192.168.3.131 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
        ether 00:a0:98:53:1f:b6 (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
vif0: flags=0xa2f0c862<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 9000
        ether 02:a0:98:53:1f:b2 (Enabled interface groups)
vif0-52: flags=0x2b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        inet 10.0.2.252 netmask 0xffffff00 broadcast 10.0.2.255
        partner vif0-52 (not in use)
        ether 02:a0:98:53:1f:b2 (Enabled interface groups)
        nfo enabled
vif0-53: flags=0x2b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000
        inet 10.0.3.252 netmask 0xffffff00 broadcast 10.0.3.255
        partner vif0-53 (not in use)
        ether 02:a0:98:53:1f:b2 (Enabled interface groups)
        nfo enabled

 

Thanks for your comments!

 

Reply
0 Kudos
Renifa
NetApp

Re: network management interface

‎2016-01-27 08:58 PM

Hi,

 

This can be a result of incomplete configuration. When configuring an interface or interface group with the ifconfig command,  nfo needs to be included to have Network FailOver (NFO) enabled for the specific interface. Make sure the information is also included in the RC files of the storage systems.

For example:
ifconfig vif1 `hostname`-vif11 netmask 255.255.255.0 nfo partner vif1 mtusize 1500
If there are VLANs on top of Virtual Interface Groups (VIFs), NFO can be enabled on the VLANs directly or on the main VIF. If NFO is enabled on the main VIF, it has to be assigned with an IP, even if it is a generic one, only for Data ONTAP to notice the UP to DOWN transition. If the main VIF does not have an IP assigned, it is not recognized as UP in ifconfig -A.

 

Refer Kb : https://kb.netapp.com/support/index?page=content&id=2021804&actp=LIST_RECENT&viewlocale=en_US&searchid=1453955837960

 

Hope this helps.

 

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

Re: network management interface

‎2016-01-27 09:54 PM


This can be a result of incomplete configuration. When configuring an interface or interface group with the ifconfig command,  nfo needs to be included to have Network FailOver (NFO) enabled for the specific interface.

Sorry, but that is wrong. "partner XXX not in use" simply means that there was no failover, so partner interface is inactive on this filer. NFO is something rather different and enables failover in case on network connectivity loss. It is unrelated to this question.

Reply
karim

Re: network management interface

[ Edited ]

‎2016-02-09 03:00 AM - edited ‎2016-02-09 03:07 AM

thank you for your help....  my feeling about the sentence " not in use"  means ....No failover for the moment so the partner is no used ....

But it s just a feeling I am not sure!!! thank for your time and attention Renifa,

best Regards

 

Reply
0 Kudos
karim

Re: network management interface

[ Edited ]

‎2016-02-09 03:43 AM - edited ‎2016-02-15 01:29 AM

Again in the same subject  the "network management interface"

I have encountered a behaviour that disturb me.

at the network level  I have implemented a trunk named vif0 based on e0a and e0b ports.

Above this vif0 I have created a vlan id=53 with the following command :" vlan create vif0 53"

From this point I have 2 interfaces.

In front of the filer physical interface I managed the port swtich in order to be a trunked ports. I have the default_vlan and the vlan-53 configured on my swich router. the routing operation is enable on the switch-router.

next are the commands used to configure vif0 and vif0-53 :

 

next is the routing table result :

routing_table.PNG

 

When I execute the ping command "ping -i vif0-53 10.0.3.254" the system responds with the following answer "the host is down"

but the folowing command return a positif response : ping 192.168.1.254

 

The filer was rebooted  thinking it might help but after reboot I did some ping test without positive result.

 

I don't know what I forget to do! So I share my lack og understanding!

Thanks for your attention!

Best regards

Reply
0 Kudos