This post is more than 5 years old
1 Rookie
•
47 Posts
0
1703
August 10th, 2010 19:00
Celerra interface configuration.
Folks,
I am trying to configure interfaces for a brand new celerra. Few questions:
1) I figured how to assign IP to cge0, cge1, cge2 & cge3 on primary DM, how would i configure IP for cge0, cge1, cge2 & cge3 on Standby DM?
2) we have two core switches to connect these ports to, how should we connect them?. Do i connect all the ports (cge0-cge3) from primary DM to one switch and all the ports (cge0-cge3) from standby DM to second switch?
3) How do i configure trunking and FSN so that failover and failback happens successfully. What are the best practices?
Thanks
No Events found!
nandas
4 Operator
•
1.5K Posts
0
August 10th, 2010 19:00
Please go through the document "dynamox" had suggested. Howeve, here are some summary answers -
> 1) I figured how to assign IP to cge0, cge1, cge2 & cge3 on primary DM, how would i configure IP for cge0, cge1, cge2 & cge3 on Standby DM?
You can not configure the Networking on the standby DM - this is not needed as well. The standby DM will get the configuration of the active Data Mover which is failing over to the standby DM. That's why it is important to connect the standby data mover same as your active data mover, If you are using any LACP or Etherchannel trunk, the same needs to be configured on the Network switch where the standby data movers ports are connected. In other words, the physical and switch configuration should be the same for Active data mover and Standby data mover in order to Data Mover failover to work properly.
> 2) we have two core switches to connect these ports to, how should we connect them?. Do i connect all the ports (cge0-cge3) from primary DM to one switch and all the ports (cge0-cge3) from standby DM to second switch?
It entirely depends on your need and requirement and network infrastructure. You may configure Trunking (LACP is preferred) and/or Fail safe network. Trunking provide you high availability as well as aggregate bandwidth. FSN provides switch level redundancy. However, if your Network switch supports configuring channeling (trunking) across multiple switches, then you can build the switch level redundancy using channeling with two switches. Please refer to the Doc dynamox mentioned to get more details and clarifications.
If you have multiple protocols requirement, you may configure one channel for CIFS/NFS, another channel for iSCSI - any combination of individual device, trunking or FSN is allowed - except the fact that etherchanneling requires 2 or 4 or 8 ports.
You may also use VLAN tagging - if you want to use multiple VLAN for different purpose. One logical device (etherchannel or FSN) can have multiple Interfaces configured on it and VLAN tagging on the interfaces allows to use multiple VLANs on the same device for different subnets or purpose. For VLAN tagging, please ensure that the ports on the Ethernet Switch are configured as VLAN Trunk port allowing all the required VLANs.
3) How do i configure trunking and FSN so that failover and failback happens successfully. What are the best practices?
Already provided enough details on point 2.
However, please note that, the Interface (IP Address) can only be configured on the top level device - that means, if there is no Trunking or FSN configured, you can configure IP Addresses on the individual devices (cge0, 1, etc) -but if you configure logical devices like Trunk or FSN, the IP address can only be configured on the top level of the logical device - the member devices are no longer available for configuring IP Addresses.
My 2 cents
Thanks,
Sandip
dynamox
9 Legend
•
20.4K Posts
0
August 10th, 2010 19:00
A lot of your questions are answered in this paper, search for it on powerlink
“Configuring and Managing EMC Celerra Network High Availability 5.6”
dynamox
9 Legend
•
20.4K Posts
0
August 10th, 2010 19:00
A lot of your questions are answered in this paper