[j-nsp] T1 Loopback

Hendrik Kahmann hendrik.kahmann at ewetel.de
Wed Jan 27 13:09:14 EST 2010

Hi Abel,

you should be able to identify a loop by checking incoming and outgoing cells. Do the counters increment equally? This also works to identify a local loop on an Ethernet link. There should also be a flag when checking "show interface x/y/z extensive (have a look at line 4):

user at host> show interfaces extensive ct1-4/2/0:7:1
Physical interface: ct1-4/2/0:4:1, Enabled, Physical link is Up
 Interface index: 305, SNMP ifIndex: 2410, Generation: 640
 Link-level type: Controller, MTU: 1504, Clocking: Internal, Speed: T1,   Loopback: None, FCS: 16,
 Framing: ESF, Parent: coc1-4/2/0:7 (Index 304)
 Device flags   : Present Running
 Interface flags: Point-To-Point SNMP-Traps
 Link flags     : None

Kind regards, 


Am 27.01.2010 um 17:54 schrieb Abel Alejandro:

> Hello,
> Is it possible to know if there is a loopback on a T1 interface on a
> Juniper?
> If we need to verify if there is a loopback we activate a BERT test and
> if the BERT synchronizes
> then we know there is a loopback but I am wondering if there is an
> easier way to verify this.
> Regards,
> Abel.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

More information about the juniper-nsp mailing list