Hi Sno,

I’d love to hear the reasoning behind the IST VLAN ID having to be set to 2. There is no requirement that the IST VLAN be any specific number nor that the MLT ID be any specific number. Actually you can use different MLT IDs on each core switch, obviously you need to use the same VLAN ID on both switches though.

In my experiences VRRP is nice but it causes a lot of scaling issues as the number of VRRP instances grow. Depending on which software release you are running I would suggest that you use RSMLT in place of VRRP. I’ve found that RSMLT is much more behaved and uses a lot less resources than VRRP.

In any event (depending on the software release) you are probably running up against a scaling issue where the VRRP hellos are not being processed fast enough. You could keep VRRP, disable the FAST-ADV feature and use the Backup Master feature. This would provide instantaneous fail-over and also help load-balance the traffic between your VRRP peers.

Good Luck with the VLAN conversion!

We are running fast advertisement enabled on both Passports after a vlan is converted:

e.g. config vlan 1241 ip vrrp 241 fast-adv-enable enable

I am getting a lot of continuous log entries showing a vrrp state change, although a state change is not taking place, based on the vrrp uptime indicator. I am going to turn this feature off to stop the messages. From what I’ve been told from our network architects, the reason for the log entry is because my IST VLAN ID number should be 2, whereas, my Passports IST VLAN ID 301 at this time.

Any comments?

Well from with Java Device Manager just look under IP Routing -> VRRP click on the Interfaces tab and then scroll all the way to the right of the screen and you’ll see the options for Backup Master.

I just checked this against a switch running 6.1.3 software.

Cheers!

Hi Thomas,

It can be fairly complicated to add VRRP and/or HSRP. It’s certainly not something that you should undertake without completely understanding what you are doing. Outside of the commands provided in the above article you can post over in the forums if you have additional questions;
http://forums.networkinfrastructure.info/nortel-ethernet-switching/

Good Luck!

Hopefully that fixed your problem.

Please feel free to post any other questions in the Ethernet Switching forums.

Cheers!

Ryan

Hi Ryan,

You have a mis-configuration between the two VRRP routers. You probably have Fast Advertisement enabled on one but disabled on the other. Assuming that your VRIDs match your VLAN IDs you could issue the following command on both your ERS 8600 switches;

ERS-8610:5# config vlan 8 ip vrrp 8 info

Sub-Context: clear config dump monitor show test trace wsm asfm sam
Current Context:

                      action : none
                     address : IP ADDRESS OF VRRP INTERFACE
                   adver-int : 1
               backup-master : enable
                 critical-ip : 0.0.0.0
          critical-ip-enable : disable
                fast-adv-int : 200
             fast-adv-enable : disable
                      delete : N/A
                 vrrp enable : enable
              holddown-timer : 0
                    priority : 100

The settings should be identical on both ERS 8600 switches. It sounds to me like someone has enabled Fast Advertisement on one of the switches but left it disabled on the other switch. Just go ahead and disable Fast Advertisement (fast-adv-enable) and the error should clear.

Good Luck!

CPU5 [07/28/09 09:41:15] IP ERROR rcIpVrrpIn: Misconfigured Advertisement type (Fast Advtisement) for Vrid 8 on IfIndex 2054, Local type:regular Advertisement

The VRRP is functioning fine, but I am just concerned about this incessant log entrys.
I have tried to find more info on this, to no luck, do you perhaps have any suggestions ?

Would be appreciated.

Ryan

BEGIN { print “Nortel ERS 8600 VRRP ID Script” }
{ print “config vlan “$2″ ip vrrp 1 delete” }
{ print “config vlan “$2” ip vrrp “$2″ address ” $3 }
{ print “config vlan “$2” ip vrrp “$2″ backup-master enable” }
{ print “config vlan “$2” ip vrrp “$2″ enable” }
END { print ” – DONE -” }

You would feed the input from the “show ip vrrp info” command into this AWK script and it would output the commands to delete and then re-create the VRRP instances using the VLAN ID as the VRRP ID. We had about 60+ VLANS to change and only 60 minutes and there was no way we were going to change them all on both switches in 60 minutes (we also wanted to minimize the downtime). So that with the output from that script I cut and pasted sections of the output into both 8600 switches and we were done in about 10 minutes with zero downtime.

Thanks for the comment!

hopefully migrating to rsmlt soon as well…