Subscribe

rc file configuration after new network connection

[ Edited ]

Hi all,

 

last week we add a new network adapter to the netapp filers fas 2240 with HA Pair ( OnTap 8.2.3 P4) on e1a (10g). I do this on both filer.

 

e0a: flags=0x9f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:36:7e (auto-1000t-fd-up) flowcontrol full
        trunked vif_lan
e0b: flags=0x9f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:36:7e (auto-1000t-fd-up) flowcontrol full
        trunked vif_lan
e0c: flags=0x9f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:36:7f (auto-1000t-fd-up) flowcontrol full
        trunked vif_san
e0d: flags=0x9f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:36:7f (auto-1000t-fd-up) flowcontrol full
        trunked vif_san
e1a: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
        inet 192.168.10.229 netmask 0xffffff00 broadcast 192.168.10.255
        ether 00:a0:98:56:ff:5e (auto-10g_sr-fd-up) flowcontrol full
e1b: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
        ether 00:a0:98:56:ff:5f (auto-unknown-down) flowcontrol full
e0M: flags=0x2b0c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT> mtu 1500
        ether 00:a0:98:53:36:83 (auto-100tx-fd-up) flowcontrol full
e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT> mtu 1500 PRIVATE
        inet 192.168.0.248 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
        ether 00:a0:98:53:36:82 (auto-100tx-fd-up) flowcontrol full
lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 9188
        inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188
        inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1
vif_lan: flags=0x22f4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        inet 192.168.4.231 netmask 0xffffff00 broadcast 192.168.4.255
        partner vif_lan (not in use)
        ether 02:a0:98:53:36:7e (Enabled interface groups)
vif_san: flags=0x26f4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
        inet 192.168.10.231 netmask 0xffffff00 broadcast 192.168.10.255
        partner vif_san (not in use)
        ether 02:a0:98:53:36:7f (Enabled interface groups)

partner

 

e0a: flags=0x9f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:2b:4e (auto-1000t-fd-up) flowcontrol full
        trunked vif_lan
e0b: flags=0x9f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:2b:4e (auto-1000t-fd-up) flowcontrol full
        trunked vif_lan
e0c: flags=0x9f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:2b:4f (auto-1000t-fd-up) flowcontrol full
        trunked vif_san
e0d: flags=0x9f0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:53:2b:4f (auto-1000t-fd-up) flowcontrol full
        trunked vif_san
e1a: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
        inet 192.168.10.230 netmask 0xffffff00 broadcast 192.168.10.255
        ether 00:a0:98:56:ca:3c (auto-10g_sr-fd-up) flowcontrol full
e1b: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
        ether 00:a0:98:56:ca:3d (auto-unknown-down) flowcontrol full
e0M: flags=0x2b0c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT> mtu 1500
        ether 00:a0:98:53:2b:53 (auto-100tx-fd-up) flowcontrol full
e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT> mtu 1500 PRIVATE
        inet 192.168.3.25 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
        ether 00:a0:98:53:2b:52 (auto-100tx-fd-up) flowcontrol full
lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 9188
        inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188
        inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1
vif_lan: flags=0x22f4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        inet 192.168.4.232 netmask 0xffffff00 broadcast 192.168.4.255
        partner vif_lan (not in use)
        ether 02:a0:98:53:2b:4e (Enabled interface groups)
vif_san: flags=0x26f4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
        inet 192.168.10.232 netmask 0xffffff00 broadcast 192.168.10.255
        partner vif_san (not in use)
        ether 02:a0:98:53:2b:4f (Enabled interface groups)

Now the netapp support side shows me a risk:

 

Missconfigured ifconfig entries in /etc/rc 
The partner in rc is missing from the configuration of the acitve interface for e1a.

 

There is a kb with this risk:

 

https://kb.netapp.com/support/index?page=content&id=2011411&actp=LIST_RECENT&viewlocale=en_US&searchid=1411062323461

 

Now i will configure the e1a for the rc file:

 

netapp03> rdfile /etc/rc
hostname netapp03
vif create multi vif_lan e0a e0b
vif create multi vif_san e0c e0d
ifconfig vif_lan `hostname`-vif_lan netmask 255.255.255.0 mtusize 1500 partner vif_lan
ifconfig vif_san `hostname`-vif_san netmask 255.255.255.0 mtusize 1500 -wins partner vif_san
route add default 192.168.4.1 1
routed on
savecore

 

ifconfig e1a `hostname`-e1a netmask 255.255.255.0 trusted -wins partner e1a

 

but now i have the messge:

 

netapp03-e1a: bad value
netapp03-e1a: not found.

 

Can anyone help me to unterstand this error?

 

Greetings

Stefan

 

 

Re: rc file configuration after new network connection

 

Stephan -

 

Do you have an entry in /etc/hosts for netapp03-e1a ?


I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, IT Learning Solutions http://sg.itls.asia/netapp
(P.S. I appreciate 'kudos' on any helpful posts.)

Re: rc file configuration after new network connection

Hi Eugene,

 

thank you for help, your are right. That was my mistake.

 

The rc file must manuell configure after the shell comand so at next boot the settings are correct?

 

Greetings

Stefan

Re: rc file configuration after new network connection

Yes.

 

Each line in the /etc/rc will be executed during the node boots.