Header Only - DO NOT REMOVE - Extreme Networks

ping doping on software-controlled redundant


software-controlled redundant losing one ping how to fix that what is best way to enable redundant path

6 replies

Userlevel 7
Hi, you mean on a failover?

when you are setting up your redundant port, you have the option of configuring "link on". This helps speed up the failover (port negotiation is already performed and port is logically blocked - led is up). If you already had link on configured, there's little you can do.
hi thanks for your reply ..

actually im new to exos extreme switches, i'm not able to understand how STP works. i find out that stp is disable.

i have 2 core switches DB8900 series and i have few edge switches summit X450, i need to have one up link from each edge switches to core switches. . what i fond out is its making loop so i used software-controlled redundant but software-controlled redundant works good. its taking few seconds to establish the link

what is best way to do that.
Userlevel 7
Sounds like you might prefer to have both link active, configured in a LAG at the edge, and using MLAG at the Core so that you do not have a loop.

http://documentation.extremenetworks.com/exos/16.1/EXOS_User_Guide_16_1.pdf

page 279
ok.. ill try that. and update you .. i enable inter-vlan routing but i my host cant ping to different vlan but i can ping in my core switch, i try to ping one ip to from anther one.. so confusing. my host can ping its default IP.

CSW1 # ping 172.17.0.3 from 172.19.0.2Ping(ICMP) 172.17.0.3: 4 packets, 8 data bytes, interval 1 second(s).
16 bytes from 172.17.0.3: icmp_seq=0 ttl=64 time=15 ms
16 bytes from 172.17.0.3: icmp_seq=1 ttl=64 time=4.494 ms
16 bytes from 172.17.0.3: icmp_seq=2 ttl=64 time=5.224 ms
16 bytes from 172.17.0.3: icmp_seq=3 ttl=64 time=4.265 ms
Userlevel 7
Have a look at those documents, they should help you understand the basis of EXOS configuration:

http://documentation.extremenetworks.com/PDFs/EXOS/EXOS_Quick_Guide.pdf
http://learn.extremenetworks.com/rs/extreme/images/Extreme-Networks-Deployment-Jumpstart.pdf

To avoid mistakes on your network, I'd also recommend you to try all of that on the VM before :

https://github.com/extremenetworks/Virtual_EXOS
hi.. Grosjen,

thank you for your suppot, problem is solved without loop

Reply