[nsp] HSSI on Cisco 7513/6509 and Adtran TSU 3800
Kashif.Khawaja at Broadwing.com
Kashif.Khawaja at Broadwing.com
Sun Dec 21 12:58:46 EST 2003
Hi Everyone,
I was wondering if anyone was aware of the issues between the HSSI interface on a Cisco
7513 or a Cat. 6509 and the Adtran (TSU 300s) where:
If the network side on the Adtran TSU 3800 takes errors or bounces and then comes back up
the Ciscoswitch side keeps bouncing between up/up and up/down (almost like it looses
timing and cannot recover it). The DSU usually has to be reset to stablize the ckt.
Is there any special/recommended setting on the Cisco (or even Adtran if somebody happens
to know a gotcha there) side for a HSSI interface that should be used to have a stable
circuit?
A higher level picture of the layout is:
6509 --- HSSI --- Adtran 3800 --------- [[[[[[[[ A lot of layer 1 equipment
]]]]]]]]-------- Adtran 3800 --- HSSI --- 7513
Cisco 6509:
LINE CLOCKING
interface Hssi9/0/0
bandwidth 45000
ip address 1.1.1.1 255.255.255.252
ip mask-reply
ip ospf cost 3
ipx delay 3
ipx network 1234
ipx output-sap-filter 1001
ipx update interval rip 300
ipx update interval sap 300
7513 side:
INTERNAL CLOCKING
interface Hssi11/0/0
bandwidth 45000
ip address 1.1.1.2 255.255.255.252
ip mask-reply
no ip directed-broadcast
no ip route-cache distributed
ipx delay 3
ipx network xxxxxx
ipx output-sap-filter 1001
ipx update interval rip 300
ipx update interval sap 300
Checking to see why the clocking set as internal is not showing in sh run (assuming it is
not the default; default seems to be line on my lab router). For this argument's sake
let's consider it is.
I would really really appreciate any help or pointers on this.
-Kashif
+++The information transmitted is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender and destroy any copies of this
document.+++
More information about the cisco-nsp
mailing list