I have an E3 line that i have started to test, but it seems to be impossible to make it work, here is the config:
ip address x.x.x.x 255.255.255.252
no ip route-cache distributed
dsu bandwidth 34010
(I have tried to get clock source from internal or line with the same result)
The encapsulation is HDLC with CRC16.
The problem is that the interface is up, but line protocol is down. And sometimes along 10 or 20 seconds line protocol comes up(i can ping the other side!) but after that time lapso line protocol comes down again. The line´s carrier says that in his side everything is fine.
I dont know about routers, but based on my knowledge about the DSU configuration in my card I'm explaining this.
The problem could be due to the DSU setting. Depending on the DSU type you are using, the E3 framing could change. A standard E3 frame has 12 overhead bits and 1524 data bits (may also be called as clear mode)
If you are using it Digital link DSU DL3100E mode, then the E3 frame could be set as 16 overhead bits and 1520 data bits. If you set the line to some subrate (i.e less than 34.368), then the number of data bits would vary.
If you are using it ADC Kentrox mode, then the E3 frame would have 12 overhead bits and the number of data bits would depend on the subrate you use.
If you use the fullrate, then it same as the clear mode i.e 12 ovh bits and 1524 data bits. So, if the other end is not using any DSU, then try using the clear mode.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...