we have two sites that are primarily connected to an MPLS Provider. Each site has an 1841.
Site A is connected to the MPLS provider on a VWIC-2MFT-T1
Site B is connected to the MPLS provider on a VWIC2-1MFT-T1/E1
The two sites are also connected together with a point to point t1. Site A utilizes a second VWIC-2MFT-T1 and site B uses a WIC-1DSU-T1-V2 for the point to point connection
The issue is at Site B we are seeing a lot of path code violiations on the point to point circuit. Telco states they've tested clean both ways, but are seeing timing slips coming from site A. I have swapped the timing on the P2P T1 back and forth (Site A clock source internal, site B clock source line) and vice versa.
i'm wondering if there is any architectual issues with the 1841 that doesn't truly provide independant clocking on these VWICS.
COuld the clocking across the two T1's at site B be skewing every once in a while and causing the input errors?
If you're seeing slips, then you're definitely looking in the right direction with clocking. Have you asked the provider if their providing clock? Perhaps you can have them ensure they are, and and set both sides of your P2P to line as the source.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...