Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VGMC Errors

Status
Not open for further replies.

Altayan

Technical User
Mar 14, 2008
83
US
Afternoon,
I have a VGMC that is throwing errors when I monitor the Telnet into it. I also get QoS packet loss warning for the card in the 30%+ range. The error message in Telnet is:

VGW: Warning channel 18 open msg in unknown dspMode: reset, tick 35070049

I had another card in our Branch Office switch attached to the 81C of the the card in question doing the same thing. The vendor replaced the card and the problem went away. However, this is the second card to throw odd errors on the 81C in the last week. I find it unlikely that 3 cards in 2 systems have all experinced an identical hardware crash. Any ideas on what might be screwed up? Thanks.
 
So far as I am able to tell it is. Our network tech assures me that it is. However, our Dell switched refer to it as CoS (cost of service) instead of QoS. Could this be a mismatch between the network switches and the Nortel switch?
 
For anyone that might have similar issues:

Rebooting the signaling server, diabling the VGMC's and bringing it all back up did correct my issue for the time being. However, I still have 1 of my 3 VGMC's that is reporting incredibly high (in the hundreds of thousands of miliseconds) jitter. In my case the 3rd card is a backup for the backup but I would still like to know what wen wrong. The card is a replacement for a crad that was doing exactly the same thing. I suspect it is slot/programming related but I haven't found the issue yet. Any input would be greatly appreciated.
 
I suppose you started out with some basic troubleshooting? Checking speed/duplex settings on the card and network switch, verify that the RJ45 cables are good and filters are on each. The fact that resetting the devices cleared the issue seems like there are errors generating from somewhere which will eventually cause the issue to return once it gets to a certain threshold. On the network level,One thing we have done in the past is verify how packets are being tagged and verify the QOS configuration for those packets to the device.
 
We did check the filters and cables, everything good there. I do agree with GTexx that there are errors generating that will crop back up again but I can't for the life of me find the problem.
 
Is there a particular piece(s) of programming that I can paste here that would help in the diagnosis?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top