vss + dual active fast hello is not working

[vinodjad1234]

HI ,

I have configured the ethernet port in both the chassis for dual active fast hello but once i remove the VSL links manually , i am getting service restored ....

only active switch will go in recovery mode but i am not able to ping any IP address .

how can i make sure that dual active fast hello is working fine.

[Reza Sharifi]

Hi,

use  command "switch virtual dual-active summary"

To configure on interface for fast-hello

interface fastethernet x/x/xx
dual-active fast-hello

no switchport
no ip address

Also, It is normal for first chassis to go to recovery mode when you disconnect both VSL links, but you should be able to ping the backup chassis's IP.  Check your configs.

[vinodjad1234]

Hi,

Thanks for your prompt response .

I have already configured the same as your mentioned

interface GigabitEthernet1/3/1
no switchport
no ip address
dual-active fast-hello

interface GigabitEthernet2/3/1
no switchport
no ip address
dual-active fast-hello

, please find the complete configuration of VSS switch in attachment.

I am not too sure that , whether i am cross verifying the dual-active fast hello properly or not ?

I would like to brief the same.... please find below method to check the dual active test . which i have carried over.

I have switch 1 and switch 2

switch 1  is active as of now

I have connected the PC to one of the port to switch 1 and try to ping directly connected ( from VSS switch )  l2 switch management IP from PC .

before removing the the VSL , it was pinging continously but once I remove both the links, I was not able to ping the IP and current active gone to recovery mode as it should be ...

but even after waiting for more than 30 min. i was unable to get ping response.

I have attached the error  as well which i was getting while testing the same.

Am I testing the dual-active scenario in correct manner ?

please suggest me for the same .

As i understood , might be 10-15 Request timed out is acceptable but i should get ping response afterword atleast.

please find all the attachement for more details :