you are very close [IMAGE]  1) connect cge0,1,2 to switch 1. Create portchannel on the switch side that consists of the 3 ports (tag for VLAN id you will need), then create trunk on the Celerra side. 2) connect cge3 to swtich2 (tag for VLAN id you will need). 3) create fail-safe-network (FSN) devices that consists of trunk created in step1 and cge3 devices. When you create FSN device you will specify which device is the active one, in this case you would want your trunk to be the active device and cge3 standby. 4) create interfaces on Celerra and specify VLAN ID that you want to use for that interface. Like you said, you could have interface named "vmware" with VLAN ID 30 and then another interface named "cifs" with VLAN ID 40.  in order for server_3 to work correctly in failover situation it needs to be cabled and configured identically from switch perspective, you don't have to do any logical configuration from Celerra side because when server_2 fails over to server_3 it will assume its identity (MAC address, IP ..etc)
Currently our Celerra is connected to one Cisco 3750G 24 port switch.  Our VMWare (3) servers are also connected to this.  There's 3 VLANs, 1 LAN 10 SAN 20 DMZ  This switch is trunked to the core.  Now we added a second switch.  Any best practices how to make it redundant, so if one switch goes down?  on both sides in the back of the celerra there's cge0, cge1, cge2, cge3        -        cge0, cge1, cge2, cge3   Any link to documents would be helpful.  Storage traffic is on its on vlan.  The VMWare ESX hosts have interfaces on the storage vlan to talk to the celerra via NFS.
redundancy for celerra connection to network