You could set the port down on the network switch, which would trigger a FSN failover to your other switch.  With regards to a command on the Celerra, I don't see a command I can provide to do it.

There is no customer facing command to do that directly.

You can try to ifconfig down the physical interface and see if that does the trick

support should also be able to help you with some debug commands

Please open a product enhancement request (PER) via Powerlink if you have a minute

Rainer

ifconfig does not work on physical interfaces, support and I have tried that when we had another issue where DART stopped working on a physical interfaces, while network switch was still showing good connectivity. I'll open a PER (not holding my breath, it's been 4 years now that i filed a PER for Celerra commands exit status to be published, ridiculous !)

Kevin,

i don't have access to network switching infrastructure so have to do it from Celerra side.

Thanks

Hi,

there are maintenance commands to shutdown an specific device ( cgex, fgex, fgxy, etc...), but unfortunately they are not customer facing.

If you open a service request, the tech support, or your local field support can assist you.

Gustavo Barreto.

Hi dynamox,

sorry – I keep forgetting that you can only shutdown an interface but not a device with server_ifconfig.

There are maintenance commands to look at and manipulate a FSN which support should be able to help you with.

Rainer

It MAY be possible using the server_sysconfig command if you do the following:

1 - Hardcode your switch to the desired speed (ex: 1000FD)

2 - Use the server_syconfig command to hardcode the primary ports of the FSN to a different speed other than auto/auto: server_syconfig server_2 -p cge0 -o "speed=100,duplex=full"

This should cause your primay links to go down,  and therefore cause the others to failover.

Let me know if this helps.

- Sebby Robles

Thanks for the tip.  I'm hoping for a solution that's "hands off" on the switch side, and I think this is a good start.  I have no physical access or contact with the folks responsible for the switches connected to an NS42G that I'm supporting - it's another department's Celerra (their admin is out on maternity leave).  Nobody in that group can even tell me who to call about the switch gear.  Even since the Force10 switches have had this (buggy?) code loaded, I get flapping errors.  I wanted to failover to the old Cisco switch on the standby side of the FSN.  This is a good idea, so thanks much for suggesting it!  I will try it the next time I see more errors from the Force10.

Thanks much!

Karl

i don't know about Celerra but on a server side (HP Blades with broadcom cards) if i have duplex/port mismatch, the link never goes down it simply stops working so i am not sure that would trigger FSN failover. I will be installing new ProCurve and NS120 in a few weeks so will test it out. In my main datacenter i don't have access to switch gear so i will not always be able to verify port settings on the switch side.

Karl

It is best practice to have the switch and Datamovers hard coded to the same speed, so chances are the switch is already set to 1000FD.  If you have a flapping  issue, this is most likely due to a speed/duplex mismatch.

Set your ports to auto/auto, and then verify what speed they are connecting at.

Let me know if this helps.

- Sebby Robles