Celerra management vlan

Hi StorageGuy,

The Celerra's management interface (the one going to the Control Station) and the data interfaces (the ones going to your Data Mover(s)) are physically separate. You'd just connect the Celerra's management interface to the new VLAN, and change its IP address (and default gateway and other IP settings) appropriately.

Does your network not have routing between the management and the data VLANs, though?

Ian, thanks for the quick reply. I've never managed a Celerra box before but I'm a unix/linux guy so do I just ssh in and then change the IP address of eth3 and bounce the interface? I'm assuming this won't cause the standby Celerra to take over?

Also, physically I see the management interfaces connect to a small EMC supplied 10/100 switch which also has a cable going into the Clariion. What's that connection for on the Clariion?

Our data vlan is non-routable by design for security reasons

Here's some info from the Celerras (server_2 and server_3):

$ server_ifconfig server_2 -a
server_2 :
iSCSI1.16 protocol=IP device=fsn01
inet=192.168.228.15 netmask=255.255.255.0 broadcast=192.168.228.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:a:14:34
iSCSI2.17 protocol=IP device=fsn02
inet=192.168.228.90 netmask=255.255.255.0 broadcast=192.168.228.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:a:14:35
loop protocol=IP device=loop
inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255
UP, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost
el30 protocol=IP device=fxp0
inet=10.1.10.2 netmask=255.255.255.0 broadcast=10.1.10.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:9:79:0 netname=localhost
el31 protocol=IP device=fxp0
inet=10.1.20.2 netmask=255.255.255.0 broadcast=10.1.20.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:9:79:0 netname=localhost

$ server_ifconfig server_3 -a
server_3 :
loop protocol=IP device=loop
inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255
UP, loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost
el30 protocol=IP device=fxp0
inet=10.1.10.3 netmask=255.255.255.0 broadcast=10.1.10.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:9:78:e3 netname=localhost
el31 protocol=IP device=fxp0
inet=10.1.20.3 netmask=255.255.255.0 broadcast=10.1.20.255
UP, ethernet, mtu=1500, vlan=0, macaddr=0:60:16:9:78:e3 netname=localhost


$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:02:B3:EA:0B:45
inet addr:10.1.10.100 Bcast:10.1.10.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3642925117 errors:0 dropped:0 overruns:0 frame:0
TX packets:1884136580 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:948715141 (904.7 Mb) TX bytes:535769124 (510.9 Mb)

eth0:0 Link encap:Ethernet HWaddr 00:02:B3:EA:0B:45
inet addr:10.1.20.100 Bcast:10.1.20.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1

eth1 Link encap:Ethernet HWaddr 00:02:B3:EA:0B:44
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xac00 Memory:fc4e0000-fc500000

eth2 Link encap:Ethernet HWaddr 00:0E:0C:5E:2A:CB
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xbc00 Memory:fc5e0000-fc600000

eth3 Link encap:Ethernet HWaddr 00:0E:0C:5E:2A:CA
inet addr:192.168.228.10 Bcast:192.168.228.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:643832293 errors:0 dropped:0 overruns:0 frame:0
TX packets:440367698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1921737182 (1832.7 Mb) TX bytes:3836320484 (3658.6 Mb)
Base address:0xb800 Memory:fc5c0000-fc5e0000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:172153553 errors:0 dropped:0 overruns:0 frame:0
TX packets:172153553 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9050280 (8.6 Mb) TX bytes:9050280 (8.6 Mb)
.

StorageGuy,

Before you make any changes, make sure you understand all the different components in your system, what they're for, and how everything's supposed to be cabled - otherwise you may have some serious problems. For example, don't disconnect anything from that internal switch. =)

If you have Ethernet cables running from the two Clariion SPs to the internal 100Mbps Ethernet switch on the Celerra, then it sounds like you have what's called an Integrated system. This is where the Clariion is reserved exclusively for the Celerra, and not intended to be used as storage for other hosts. In this case, the Clariion talks to the Celerra over a private, internal network (what that switch is used for), and not through any "public" network. On your system, this is the 10.1.10.x and 10.1.20.x IP addresses that you see configured.

In this situation, the Celerra talks to the Clariion ONLY through this private network, and not through the "external" IP addresses that you assign to them.

In any case, it sounds like you still want to move the Celerra Control Station's management IP into the subnet of your management VLAN, and that's fine. And yes, you're right, you can just change the IP on the interface to do this (no need to bounce the interface). Of course, once you change the IP of eth3 you'll lose access to the Celerra's management interface until you actually move it into new VLAN.

If you end up having problems (you find you can't talk to the Control Station (management interface) anymore), you can connect a serial cable to the Control station, and talk to it with Hyperterminal or some other term program. Then just log in like normal. (This is similar to most other Linux systems)


As far as "standby taking over", keep in mind that the Celerra's made of of two main parts: 1) The Control Station (management server) that you're ssh'ing into. It's the little 1U server with the CD drive. If you have two of these (I doubt you do), then you have one "active" and one "standby", but changing the IP on the "active" one won't cause failover (and even if it did, that won't interrupt production, since this is only the management station). 2) The Data Mover(s). These are the systems that actually do the file serving. It looks like you have two of these, one active and one standby. When you say "cause the standby to take over", I'm assuming that this is the standby you mean. If so, changing the IP of the management station also won't cause failover of this.

The easiest way to change the ControlStations management interface is actually thru the GUI.
Just open Celerra Manager and login as root (not nasadmin) - then you can change it on
the Controlstation properties tab.

As Ian said, its always a good idea to have a serial cable around when playing with the interface you're using

Thanks guys, I was able to move the vlan without any issues!