[c-nsp] Cisco POS interface compatibility

[Chris Chaundy]

Thanks - all of these matched up.

Things are working now - we found the culprit, some old configuration that
had set the keepalive way down at one end for fast rerouting in a previous
application, so it kept declaring the interface down and resetting it which
caused errors and took the other end of the link down (where the keepalive
was set to default).


On 12/2/08 1:05 PM, "Hyunseog Ryu" <r.hyunseog at ieee.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>  
> Did you check following ?
> 
> - - Clocking : unless transport gear provide it, one side should be
> internal, and other side should be external.
> - - FCS/CRC : 32 bit ? or 16 bit ? Probably 32 bit...
> - - scramble  : Probably off
> - - Fiber mode : SMIR or something else ?
> 
> Hyun
> 
> 
> Chris Chaundy wrote:
> | Is anyone aware of compatibility issues between the current generation POS
> | PA¹s (PA-POS-1OC3 in particular) connected to an old model GSR line card
> | (LC-4OC3/POS-SM, yes, the engine 0 card!)?  We have been trying to
> bring up
> | a new circuit and each interface works fine when looped up to the last
> OFTP
> | before the other router, but when you connect them, the circuit gets B3
> | error threshold exceeded, TC alarm declared syslog messages.  The circuit
> | then drops, the alarm is cleared and it comes back up again to get the
> error
> | again (so it is continuously flapping at a rate of a couple of times a
> | minute).
> |
> | Thanks.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>  
> iD8DBQFHsP7rZkEzJIVS03MRAquuAKC0dZLvgLKPVtVBv2zomOovxR86EgCeJgVE
> LhewgoHJMN105u1zdPgO6D0=
> =zese
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/