VRRP cause and type 1

[guygt]

Hi All,
we had a VRRP transition problem between two passports.
does any one has the Cause and Type table?
"CPU5 [05/23/05 10:16:06] SNMP INFO Vrrp State Transition Trap(Port/Vlan=224, Type=3, Cause=5, VrId=224, VrIpAddr=10.5.224.1, Addr=10.5.224.3)<000>"
I really need to know why did it happened.....

You have to dream of being a Pro before you become one !

 

[Googer]

I have heard of one issue where the VRRP can loose connection to its partner do to a problem with Windows XP. XP runs a service called SSDP that conflicts with the VRRP mechanism on the Nortel switches. SSDP dynamically tries to discover routers on the network and my understanding is that if you get enough XP clients (100+) running this service the VRRP partners can loose connection and thus the backup can think it needs to take over as the master.

Good luck,

Googer

 

[ports]

Hi Googer,
Regarding the Win XP SSDP service, is the info true? if so, any workaround.
We are also facing a similar issue. We have 2 Passports working with ISTMLT and every now and then we get logs on VRRP state transition only on one passport. Plus this issue began after we have enbaled Multicasting on the Network.

If you have any docs, reference please do let me know

Thanks

Regards,
FG

 

[Alainv]

type:
vrrpTrapStateTransitionType OBJECT-TYPE
SYNTAX INTEGER {
none(1),
masterToBackup(2),
backupToMaster(3),
initializeToMaster(4),
masterToInitialize(5),
initializeToBackup(6),
backupToInitialize(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Potential types of state transitions.
Used by vrrpTrapStateTransition trap."
::= { vrrpOperations 14 }


And the reason.

vrrpTrapStateTransitionCause OBJECT-TYPE
SYNTAX INTEGER {
none(1),
higherPriorityAdvertizeReceived(2),
shutdownReceived(3),
vrrpAddrAndPhysicalAddrMatch(4),
masterDownInterval(5),
preempted(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Potential types of causes that will
generate a vrrpTrapStateTransition trap."
::= { vrrpOperations 15 }


You can find this in the vrrp mibs.

We had this issue, where the log indicated that the master had changed, but inmediatly the master came back. So no transition was executed.

Reason was the arp table that became to big and by re-arping it, it caused a hickup with vrrp. Although not you didn't noticed it on the network.

 

[ports]

Hi Alan,
Thanks, for the info.
We also had the ARP issue sync issue between the Passports, a reboot solved the problem.

However we still have have the VRRP Transitions and i really need to figure out why.


Regards,
FG

 

[Alainv]

How big is your arp table?

Nortel gave us the advice to use a fwd database timer of 6h +1 second, since the arp timer is 6h by default. I know it is a huge timer but it won't give us problems.

We still do have those transitions (sporadicly), but now minimum 6 hours in between and only @ 1 premesis.

Also we suppressed the topology changes for every userport.

If a user get's connected, this will cause a topo change, and each bridge on the network will flush its content. result is again a lot of arp request, and vrrp has problems.
Those topo changes can be suppressed on the 8600.

We are still running old soft, with the new once you can limit the max amount of open request.
And there are some bugs related with smlt solved.

 

[trblmkr]

What version of code are you running on your 8600's?

 

[ports]

Hi,
We are running 3.5.9.0 Passport 8610co.
How can i supress topology change on the passport?

Anyways we have logged a call with Nortel and waiting for the feedback.

will keep you guys posted.

Regards,
FG

 

[ports]

Hi,
We are running 3.5.9.0 Passport 8610co. we have over 2300 arp entries
How can i supress topology change on the passport?


Anyways we have logged a call with Nortel and waiting for the feedback.

will keep you guys posted.

Regards,
FG