HSRP (Hot Standby Routing Protocol)

[lagapidis (Lazarus Agapidis)]

Hello Daniel

@dlais1987

For the configuration examples in the HSRP page under SW1 there is no ip sla set? Shouldn’t we set the ip sla for interfaces on each MLS?

Not necessarily. In this particular case, SW2 has a priority of 150, so it is the active router. The IP SLA configuration will make the priority drop by 60 in the event the IP SLA goes down. This will result in SW1 having the higher priority, and thus will become active. Once the SLA is restored, the priority of SW2 will go back up and it will become the active gateway. So this can be done with an IP SLA config on only one switch.

@dlais1987

can you just use the command:
standby 1 track gi0/2 without the “line-protocol” part? What does the extra 1 after track signify in the lesson because on packet tracer the command standby 1 track 1 the “1” isnt allowed?

The command requires the tracked object number to be specified asfter the keyword track. Take a look at the following:

SW1(config-if)#standby 1 track ?
  <1-1000>  Tracked object number

SW1(config-if)#standby 1 track 

That 1 signifies the SLA that you have created. Packet tracer doesn’t support all of the commands available on real IOS devices, so you may run into some such situations.

@dlais1987

Would the commands be different for ip sla if instead of 1 mutual vlan we were working intervlans or a physical interface what should the command output look like for those instead of the below:

Tracking should use the same syntax regardless of whether you are using an SVI or a physical interface. The track feature always requires a tracked object number after the keyword track, at least on the IOS and platforms I am using. It may be the case that some other platforms use slightly different syntax, like the one you state in your post, where you indicate the interface directly.

I hope this has been helpful!

Laz