I just power on my new FAS2020A, and try to configure network properties.
So, FAS2020A had two controllers, i named it A and B.
How many IP should i have to manager my FAS ? One, Two ?
I have configured in CLI a virtual interface on the first controller A, and create a virtual interface named TRUNK-A, with IP 192.168.1.15 255.255.255.0 using e0a and e0b.
This virtual interface is up and ping successfully.
My problem, is on the second controller.
Under CLI, when i type SETUP command, and begin to configure the controller, i try to create a virtual interface, system tell me e0a and e0b are already in use ...
So i cannot had ip address on my second controller !
All my licenses are installed, and when i type CF STATUS command, it tell me CLUSTER enable.
So should i connect a wire directly from controller A to controller B ?
Actually, my two controllers had each of one two wire on two different switch with LACP enable.
So if anyone can explain me how to configure network, it will be plaisant for me.
thanks a lot.
See The Solution
e0a and e0b will be 'in use' if they're part of a VIF that is configured up.
To get this config into your /etc/rc to make it persist:
a. export or CIFS share vol0 and use an editor from your admin host to add your 'vif create' and 'ifconfig' statements.
b. use 'wrfile' to edit localy.
(not! wrfile is a very clumsy editor. I avoid having to use it all I can!)
c. unconfigure the vif so you can run through setup again. You don't need to re-boot, you can 'source /etc/rc' to run the script.
I hope this response has been helpful to you.
At your service,
Eugene KashpureffNetAppU Instructor and Independent Consultant(P.S. I appreciate points for helpful or correct answers.)
View solution in original post
Interfaces can not be added to a VIF if they are configured in an UP state. It seems controller 2 had already been configured at some point.
You need to connect via the console interface and 'ifconfig e0A/B down', then run through setup again to configure the VIF for the second unit.
Ensure that there is a correct ''partner' ifconfig parameter for the VIFs on each controller in the /etc/rc startup file.
Test your configuration with reboot and 'cf takeover' from each side before putting these units into production.
NetAppU Instructor and Independent Consultant
(P.S. I appreciate points for helpful or correct answers.)
Thanks for your answer.
Already ifconfig e0a e0b down.
System said e0a and e0b already in use.
So how to edit the /etc/rc startup file ?
In fact, when the controller as finished to boot, under CLI, if i type this command my interface bring to up.
vif create lacp TRUNK-B e0a e0b
ifconfig TRUNK-B 192.168.1.16 netmask 255.255.255.0 partner TRUNK-A
So when i reboot, this interface was cleared. How to fix it ?
Yeah ! It's working ! Thanks.
It's a little bit strange to tagg native vlan. I always let it as untagged, and tag only vlan i want to communicate.
So, when i modify the RC file, and when i reboot, my configuration is not saved.
Have you an idea ?
I can edit the file by mounting the C$ on the admin computer, and edit the rc file with NOTEPAD++.
NetApp Wins One Silver and One Bronze Stevie® Award in 2022 Stevie Awards for Sales and Customer Service
Live Chat, Watch Parties, and More!
Engage digitally throughout the sales process, from product discovery to conﬁguration, and handle all your post-purchase needs.