We recently installed a P2P T3 circuit between two offices. We are getting a large number of input errors, CRC, overruns and carrier transitions INTO one of the sites. At the site the connection is coming from, our provider is testing clean to the handoff to the LEC. The LEC claims their network is clean and that there is an issue between the demarc and CPE.
Our extension is RG59 Coax with a length of 478 feet from demarc to router.
My question is: I have read teh limits for this cable for T3 is 450 feet. Is this true? Could this be the problem? Does anyone have any insight into what direction to go with this?
It could be a number of things, but the very first that I would look at based on previous experiences is the clocking.
If it's a P2P you will likely need to specify your own clocking, and are probably seeing slips on your t3 controller interface. If this is the case, try setting a clock source on one side as Internal, and on the other side as Line.
Thanks again. I had read somewhere 450 feet for this setup? Does this sound right? We are looking at our distance at around 480 feet. What would you think the best option be at the point? Repeater/booster, low loss cable, fiber converter?
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.