EXOS: X670V-48x Link up delay ??

[M_Nees]

We have 2x X670V-48x Stacks (with 2 Switches each) for redundant Servers connections. We use both hardware servers (windows 2008/2012) and virtual servers(vmware 5.5)). The redundancy mechanism is triggered by port Link status ! (All people know that is not best - but it cannot be changed). The regarding Servers are connected via 1GB TP GBICs (original Extreme parts).

We have some trouble during server redundancy tests !
+ If we power down the switches (pulling power cable) - the expected switch over to backup server run fast (4 seconds) - perfect!
+ If we reboot the switch (warmstart via CLI) the server need a lot of more time (nearly 1 minute) to switch over to the backup server!

The problem is that if the switch was rebooted the switching logic is shutting down fast by the software but the port Link is UP (gbic). Only at the end of the switch shutdown process the GBIC lost the LINK Up (= port down). Now the server recognize that the link failed and switch over. At startup the same problem - the switch link up the GBIC first but the switching logic (EXOS processes) are not running for 100%. So the server think that the link is OK and tried to communicate - but this failed because the switch needs time to startup. This behaviour get more worse because the X670V need a lot of time to boot (regarding to X670-G2).

My question is now - can we control the GBIC link state? In my szenario it would be the best if the link (maybe through a delay of x seconds) come up only if the switch is booted completly. And if the switch was rebooted, shutdown the link immediately (not at the end of the shutdown process).

Any ideas or feedback if you are fighting with the same problems ?

[M_Nees]

Generally i think in EXOS we need my originally claim:
"Link up delay of X seconds" OR "a depency to an EMS event"!

[Prashanth_KG]

Hi Mathias,

I was about to test with a script to avoid the link up delay during the boot up. However, I realised from the logs that the switch becomes operational first and then the links come up.

09/24/2015 17:39:40.47 PSU-1 EDPS-300AB A-S7 is present.09/24/2015 17:39:39.36 Port 1 link UP at speed 1 Gbps and full-duplex
09/24/2015 17:39:36.80 Port 1 link down
09/24/2015 17:39:36.42 Media BASET is inserted into Port 3
09/24/2015 17:39:36.42 Media BASET is inserted into Port 1
09/24/2015 17:39:36.00 Port 1 link UP at speed 1 Gbps and full-duplex
09/24/2015 17:39:35.49 Port Mgmt link UP at speed 1 Gbps and full-duplex
09/24/2015 17:39:35.16 Switch is operational
09/24/2015 17:39:30.38 System is stable. Change to warm reset mode
09/24/2015 17:39:27.34 Watchdog enabled

Ofcourse, I tested with X460.. However, I do not expect much change in the behaviour of X670 either. Are we using any additional software features like MLAG/LACP on these ports?

[André_Herkenrat]

Did you think of enabling the ports on the EMS Message "AAA available" ?

[EtherMAN]

I seems you are asking for a option that would be the same for our servers... I can pretty much guarantee if you issue a restart on any server or pc you will see the same results where the hardware layer one link comes up before the software is fully loaded and passing traffic...Switches and routers are the same the OS will always take longer to load then the layer ports coming up...

One thought to help if I recall by default hardware checks are going on as part of the boot up process so not sure if you could trim the time down by killing that... It is on by default if I recall...

seems you only option on planned reboots would be to disable the ports....save... reboot... enable the ports ... save ... This would help you on planned things but not on a random software failure where the switch reboots on it's on.

Good luck

[M_Nees]

Hi Stephen,

the steps you recommend are maybe for the lab not for productive customer environment (if we want that the customer buy extreme switches again ...).

The main problem is that at startup the Link comes up to early (the switch is not fully booted) and at shutdown the link goes down to late (Switching processes are killed, but link is still up ).

So the issue can only be avoid at shutdown with config commands but not at startup !

Any better suggestions. I think i am not the only customer that have this kind of problems !

Regards,
Matthias