Help with FAS2020 multistore config

[draft_support]

Hi all.

We had a technician here in the company which did the first multistore config, vfilers etc...

Yesterday i was planning to upgrade to the latest firmware version, which includes a reboot, and checking the actual ifconfig -a result:

e0a: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500

        ether 02:a0:98:28:0f:3c (auto-1000t-fd-up) flowcontrol full

        trunked vif1

e0b: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500

        ether 02:a0:98:28:0f:3c (auto-1000t-fd-up) flowcontrol full

        trunked vif1

lo: flags=0x1948049<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)

vif1: flags=0xa2d08863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500

        ether 02:a0:98:28:0f:3c (Enabled virtual interface)

vif1-1: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

        inet 192.168.11.70 netmask 0xffffff00 broadcast 192.168.11.255

        inet 192.168.11.32 netmask 0xffffff00 broadcast 192.168.11.255

        partner vif1-1 (not in use)

        ether 02:a0:98:28:0f:3c (Enabled virtual interface)

vif1-15: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

        inet 192.168.15.70 netmask 0xffffff00 broadcast 192.168.15.255

        partner vif1-15 (not in use)

        ether 02:a0:98:28:0f:3c (Enabled virtual interface)

vif1-5: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

        inet 192.168.5.32 netmask 0xffffff00 broadcast 192.168.5.255

        ether 02:a0:98:28:0f:3c (Enabled virtual interface)

i noticed 3 vlans, on vif1 (vif-1, vif1-15 and vif1-5)

And x-checking with the /etc/rc:

hostname san1

vif create lacp vif1 -b ip e0a e0b

ifconfig vif1 `hostname`-vif1 mediatype auto

ifconfig vif1 down

vlan create vif1 1

vlan add vif1 15

ifconfig vif1-1 192.168.11.70 netmask 255.255.255.0 partner vif1-1 mtusize 1500 trusted

ifconfig vif1-15 192.168.15.70 netmask 255.255.255.0 partner vif1-15 mtusize 1500 trusted

ifconfig vif1-1 alias 192.168.11.32 netmask 255.255.255.0

route add default 192.168.11.1 1

routed on

options dns.domainname draft.local

options dns.enable on

options nis.enable off

savecore

i noticed that there is not a line for vif1-5 in the RC file, this is probably a problem right?

Could someone shed some light if am i correct ? or this might be in another config file?

Thanks in advance.

[ismopuuronen]

Hi,

If you reboot the filer, vif1-5 goes down.
Looks like vif1-5 has been configured UP, by using CLI and >ifconfig command and >vlan command.
RC file is not updated automatically by using those commands, you have to edit the RC file separately.
So yes, you should add the vlan ID to the RC files vlan add line, and new ifconfig line as well.

Basically RC file is a list of commands, which filer reads from up to down during boot.

Br.
Ismo.

[draft_support]

can you tell me exactly what should i add to the etc/rc?

[ismopuuronen]

Hi,

You have these two lines in your /etc/rc file:

ifconfig vif1 `hostname`-vif1 mediatype auto

ifconfig vif1 down

In a first line, you should not specify mediatype for vif. Mediatype is specified only for physical interfaces

In a secondline you actually configure vif1 down? if you don't want to do that, you should remove this line.
You can see the IP address assigned to vif1 in this case from /etc/hosts file. Maybe this is for management purpose or something.

vlan lines:

vlan create vif1 1

vlan add vif1 15
In your ifconfig -a output we are able to see ifconfig line where is vlan id 5 in vif1. I don't know your configurations but just make sure the vlan id is correct and it should be added to vif1.
Then rc files vlan line could be:
vlan create vif1 1 5 15

Ifconfig lines:

ifconfig vif1-1 192.168.11.70 netmask 255.255.255.0 partner vif1-1 mtusize 1500 trusted

ifconfig vif1-15 192.168.15.70 netmask 255.255.255.0 partner vif1-15 mtusize 1500 trusted

ifconfig vif1-1 alias 192.168.11.32 netmask 255.255.255.0
Just add one line in this section:
ifconfig vif1-5 <ipaddress> netmask <netmask> partner vif1-5 mtusize 1500 trusted

When you do these changes you also have to edit partner nodes rc file to match, so everything will work in event of failover.
If there is no need for interface vif1-5 in partner node, then the ifconfig line in partners rc file could be simple as:

ifconfig vif1-5 partner vif1-5
So then it's only for failover purpose.

Br.
Ismo.

[draft_support]

great, i will backup my system do the tests and post the results!

amazing!

[ismopuuronen]

Yep, before editing the rc file, it should be copied to somewhere else, so you can go back if necessary.
Remeber that commands in rc file is "issued" during boot, so just modifying rc file doesen't actually change anything in that time.
And if you don't want to boot the filer, you can use command >source etc/rc

But ofcourse you should test failover capabilites, so takeover would be the correct way to test new rc file.

Br.
Ismo.

[draft_support]

Worked as a charm!

Thanks