Here's one that should be easy. I have an NS80 with a 10GbE interface (fxg0) and several 1GbE copper ports (cge0-cge4). I have an FSN configured with the 10GbE port as 'active' and two 1GbE ports in a link aggregation as 'standby':
[nasadmin@NS80-CS0 ~]$ server_sysconfig server_2 -virtual -info DM2_FS1
server_2 :
*** FSN DM2_FS1: Link is Up ***
active=fxg0 primary=fxg0 standby=DM2_LA1
[nasadmin@NS80-CS0 ~]$ server_sysconfig server_2 -virtual -info DM2_LA1
server_2 :
*** Trunk DM2_LA1: Link is Up***
*** Trunk DM2_LA1: Timeout is Short ***
*** Trunk DM2_LA1: Statistical Load Balancing is IP ***
Device Local Grp Remote Grp Link LACP Duplex Speed
------------------------------------------------------------------------
cge0 10000 770 Up Up Full 1000 Mbs
cge1 10000 770 Up Up Full 1000 Mbs
My network administrator replaced a switch and would like to give more 1GbE ports for the link aggregation. Is it possible modify my link aggregation (DM2_LA1 shown above) without making any changes to the FSN? Is my only recourse to delete the link aggregation and recreate it?
As I know, there is no such option to re-configure FSN and Link Aggregation devices without deleting them. Unfortunately you have to take downtime for this reconfiguration.
You 'll have to delete the Interfaces (IP Addresses) which are configured on the FSN, before you can delete the FSN. Similarly this will affect the CIFS servers as well - as the interfaces are used by the CIFS server. So, the steps may be like this -
1) Delete the CIFS servers which are using the IP Addresses configured on the FSN (no need to unjoin them from the Domain) 2) Delete all Interfaces on the FSN 3) Delete FSN, 4) Delete Link Aggregation device, 5) Re-create Link Aggregation with more ports, 6) Re-create FSN. 7) Re-create all Interfaces on the FSN - keeping the same names and IP Addresses 8) Re-create the CIFS servers with same Name and using the same Interfaces as used before. (by that way, the CIFS servers will still remain in the AD)
Also, if there is any Celerra Replication or any other configuration that is affected by the deletion of IP Addresses, need to be considered (paused or stopped etc).
Hope this helps. Other may provide more valuable comments and suggestions. Regards, Sandip
My absolute pleasure to be of any help. However, you may open a case with EMC Celerra Support and run it by them once, if they can help you out with any internal way of editing files or database - may be you can avoid the delete and re-create steps with a reboot or so. However, none of us except the experienced Celerra Support personnel are aware of those - so it may not be a bad idea to check it out. Or else, you have the plan in your hand
The PER was opened several years ago. No responses ever came back to my TC while I was with another employer, so I doubt anything ever happened. Even on a new VNX 5700 we purhcased, I still had the same limitation as on my old NS80. Ahh, well!
nandas
6 Operator
•
1473 Posts
1308
0
Posted March 23rd, 2009 19:00
You 'll have to delete the Interfaces (IP Addresses) which are configured on the FSN, before you can delete the FSN. Similarly this will affect the CIFS servers as well - as the interfaces are used by the CIFS server. So, the steps may be like this -
1) Delete the CIFS servers which are using the IP Addresses configured on the FSN (no need to unjoin them from the Domain)
2) Delete all Interfaces on the FSN
3) Delete FSN,
4) Delete Link Aggregation device,
5) Re-create Link Aggregation with more ports,
6) Re-create FSN.
7) Re-create all Interfaces on the FSN - keeping the same names and IP Addresses
8) Re-create the CIFS servers with same Name and using the same Interfaces as used before. (by that way, the CIFS servers will still remain in the AD)
Also, if there is any Celerra Replication or any other configuration that is affected by the deletion of IP Addresses, need to be considered (paused or stopped etc).
Hope this helps. Other may provide more valuable comments and suggestions.
Regards,
Sandip