Got a MC32S on rls 6.0 and is joined to my UCM network, problem is I cant get the card to work at 100 meg, works fine at 10 meg. When connected at 100mg I get one way talk path and lots of errors, any ideas?
Your data switch port should be set to auto/auto. If it's not, then you'll have issues. Set the MC32S to auto/auto also. It will negotiate at 100/full.
depending what type of switch its in, if it's an OLD IPE shelf then you have to put in a filter to go 100mbps and /or replace the backplane cable to the amphenol connector.
also, i had an issue with the connector once, bad connection inside the connector (the silver one with the DB9 and two Rj45 connections)
__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
Well - we have had issues with auto even negotiating properly (algorythm from the Cisco/Foundry/etc. switch) so you may have to hard set it at 100 full on both sides. But yes, it should auto set properly.
The hard/fast rule - when in doubt (if auto-neg is really working properly) hard set it.
At least I have seen my fair share of network equipment operating with VoIP that required hardset before it worked properly.
It is really just drilled into data guy heads to always use auto and drilled into VoIP guy heads to hardset when needed
Guys thank you for your great advice. This IPE is less than a year old an was new when I upgraded to 6.0. I have also work with my customers IT tech and have tried several different configurations on the Cisco 3750 switch. I do have the filter connector installed and have all my patches up to date. I was told by another co worker that the cable from the backplane to the IPE IO my need to be changed but this is a new IPE shelf and cant imagine that be the problem. If I lower my speed all is great and when I go to 100meg it fails.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.