Solved: I How to change the ipspace on the partner filer??

SKC64750 · ‎2012-05-22

hii,

I am setting up a new vfiler on a Filer, the vfiler is on different domain from the filer, so i created a vlan on vif1 having eoa and eob trunked..My question is by mistake i have put the ipspace on the partner different from filer..i typed it as nor2 instead of nor1. so i want to change it to nor1 however it is on source. I know that there is no way to change the IPspace name or change the vfiler ipspace assigned once created as here it is Trunked interface having a vlan created on vif1. But to be noted, there is no vfiler apart from default vfiler on the partner where i created ipspace. so how can i resolve this issue considering the failover process to work fine. It would be a great help.

Thanks,

Srinivas

scottgelb · ‎2012-05-22

For failover, Ipspace names must match with the partner interface in the same Ipspace. If not the same you have to destroy and recreate them.

View solution in original post

scottgelb · ‎2012-05-22

For failover, Ipspace names must match with the partner interface in the same Ipspace. If not the same you have to destroy and recreate them.

SKC64750 · ‎2012-05-22

Thanks scott, you are so quick..But the virtual interface is already assigned to ipspace that i want to destroy..below is what i did on partner

partner filer>vlan create vif1 513

ipspace create nor2

ipspace assign nor2 vif1-513

Now what should i do??

scottgelb · ‎2012-05-22

Bring it back to default then create nor1 and reassign. As long as not in use yet.

ipspace assign default-ipspace vif1-513

ipspace create nor1

ipspace destroy nor2

ipspace assign nor1 vif1-513

Create the vFiler with nor1

ipspace assign nor2 vif1-513

Sent from my iPhone 4S

SKC64750 · ‎2012-05-22

Perfect..Do we need to create vfiler on partner also or not a compulsion??

scottgelb · ‎2012-05-22

Not required. Just the Ipspace and partner. No vFiler needed on the partner. Just interface in the Ipspace

Sent from my iPhone 4S

SKC64750 · ‎2012-05-22

Thanks, I have changed accordingly, it works fine..Also, these are the three steps I want to additionally add to the rc file on both nodes..Do you think its right??

Nas01>

vlan create vif1 513

ifconfig vif1-513 192.168.55.221 netmask 255.255.255.165 mtusize 1500 partner vif1-513

vfiler run nor1 route add default 192.168.55.128 1

Nas02>

vlan create vif1 513

ifconfig vif1-513 192.168.55.221 netmask 255.255.255.165 mtusize 1500 partner vif1-513

vfiler run nor1 route add default 192.168.55.128 1

scottgelb · ‎2012-05-22

The ips are duplicate. On the partner you don't need an ip of no vFiler on that interface...or a different ip if there is. And the vFiler name won't be the same if on the partner do the default route only on the node that owns the vFiler.

Sent from my iPhone 4S

SKC64750 · ‎2012-05-22

True, Ips are duplicate, and I dint get what you meant??..If you don’t mind can you be clear.

scottgelb · ‎2012-05-22

To be more clear... You can't have duplicate ips. Either a different ip or no ip.

Sent from my iPhone 4S

SKC64750 · ‎2012-05-23

I still dint get that scott.

scottgelb · ‎2012-05-23

vif1-513 on nas01 and nas02 each need a unique IP address... or if no vFiler on nas02, then you don't need to specify an ip address at all.

SKC64750 · ‎2012-05-23

Vif1-513 on desti has no Ip assigned, Considering no vfiler on nas02, below is the only change in the green bold required. Correct me if I am wrong.

Nas01>

vlan create vif1 513

ifconfig vif1-513 192.168.55.221 netmask 255.255.255.165 mtusize 1500 partner vif1-513

vfiler run nor1 route add default 192.168.55.128 1

Nas02>

vlan create vif1 513

ifconfig vif1-413 partner vif1-413

vfiler run nor1 route add default 192.168.55.128 1

scottgelb · ‎2012-05-23

Much better. That works.

Sent from my iPhone 4S

SKC64750 · ‎2012-05-23

Thanks a lot..when I created a vlan on existing vif of a filer having two ethernet interfaces trunked. The interfaces got bounced or rebooted for some secs or a minute and got alerts to the server side. Again they got back saying that interfaces are up. I don’t know why it happened, but I think once I created vfiler they got up..Is it right??..IF so in future how to avoid this issue do I need to down the interfaces before creating vlans. Hope you give some insight on this..Thanks in advance.

scottgelb · ‎2012-05-23

The ip address assignment automatically binds to a vFiler when the vFiler starts. It is in the registry to know that when the ip Comes up where to assign it

Sent from my iPhone 4S

SKC64750 · ‎2012-05-23

So do we need to down the vif or do we need to take downtime from the server team for the users accesing that vif before binding happens to the vfiler or what is the best practice??

scottgelb · ‎2012-05-23

When the vfiler starts it is the same as a physical controller…the ip is available if the vfiler is online. Vfiler status –a will show the status

SKC64750 · ‎2012-05-23

From: Chakkirala Karthik

Sent: Wednesday, May 23, 2012 1:31 PM

To: 'xdl-communities@communities.netapp.com'

Subject: RE: - Re: I How to change the ipspace on the partner filer??

That is fine…what I mean is before the vfiler is started..i said the interfaces got rebooted when vlan is assigned to vif, right..so my question is before rebooting what do I need to tell the server team like do I need to take down time from the users who are accessing that interfaces or do I need to just let them that interfaces reboots gonna happen??

From: Scott Gelb

Sent: Wednesday, May 23, 2012 12:43 PM

To: Chakkirala Karthik

Subject: - Re: I How to change the ipspace on the partner filer??

<https://communities.netapp.com/index.jspa>

Re: I How to change the ipspace on the partner filer??

created by Scott Gelb<https://communities.netapp.com/people/scottgelb> in Products & Solutions - View the full discussion<https://communities.netapp.com/message/82315#82315>

The ip address assignment automatically binds to a vFiler when the vFiler starts. It is in the registry to know that when the ip Comes up where to assign it

Sent from my iPhone 4S

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/82315#82315>

Start a new discussion in Products & Solutions by email<mailto:discussions-community-products_and_solutions@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2068>

scottgelb · ‎2012-05-23

Same as a physical controller… if the interface goes down the users go down… if a cluster takeover/giveback then nfs and iscsi can stay persistent but not cifs which has to reconnect.

SKC64750 · ‎2012-05-23

So before rebooting happens for interfaces, what do I need to tell the server team…do I need to take down time from the users who are accessing those interfaces or just let them know that interfaces reboots gonna happen ??