Team -
I was on a call today and somebody from VZ told me that "Juniper routers are
not supported on Verizon's IDA network" and that's the reason why our
customer's T1 and NxT1 interfaces (using F/R and MLFR encap) regularly "flap."
I called B.S. but was wondering if anyone else had heard them throw out this
kind of excuse.
Typical config on our single T1 sites:
bkessler@US-ISCRA-RTR01> show configuration interfaces t1-2/0/0
description "VZB IDA Site ID:Uxxxxxx - LEC CktID:12/HCGS/xxxxxx//PA - Verizon
Support Phone # 800-900-0241";
per-unit-scheduler;
clocking external;
encapsulation frame-relay;
lmi {
lmi-type ansi;
}
t1-options {
remote-loopback-respond;
}
unit 0 {
description "VZB IDA Site ID:Uxxxxxx - LEC CktID:12/HCGS/xxxxxx//PA";
dlci 500;
family inet {
filter {
input Internet-ISCRA-In;
}
address x.x.x.x/30;
}
}
NxT1 example:
bkessler@US-ICHIN-RTR01> show configuration interfaces ls-0/0/0:0
description "Verizon Master SiteID:Uxxxxxx - Verizon Support Phone Number:
800-900-0241";
encapsulation multilink-frame-relay-uni-nni;
mlfr-uni-nni-bundle-options {
yellow-differential-delay 150;
red-differential-delay 250;
lmi-type ansi;
}
unit 0 {
dlci 500;
family inet {
filter {
input Internet-ICHIN-In;
}
address x.x.x.x/30;
}
}
bkessler@US-ICHIN-RTR01> show configuration interfaces t1-2/0/0
description "VZB CktID:Uxxxxxx - CktID:/HCGS/xxxxxx//LB";
clocking external;
encapsulation multilink-frame-relay-uni-nni;
t1-options {
remote-loopback-respond;
}
unit 0 {
description "VZB CktID:Uxxxxxx - CktID:/HCGS/xxxxxx//LB";
family mlfr-uni-nni {
bundle ls-0/0/0:0;
}
}
bkessler@US-ICHIN-RTR01> show configuration interfaces t1-2/0/1
description "VZB CktID:Uxxxxxx - CktID:/HCGS/xxxxxx//LB";
clocking external;
encapsulation multilink-frame-relay-uni-nni;
t1-options {
remote-loopback-respond;
}
unit 0 {
description "VZB CktID:Uxxxxxx - CktID:/HCGS/xxxxxx//LB";
family mlfr-uni-nni {
bundle ls-0/0/0:0;
}
}
Example log messages:
bkessler@US-ISCRA-RTR01> show log messages | match t1-2/0/0 | match LINK
Jan 13 23:43:06 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_DOWN: ifIndex 134,
ifAdminStatus up(1), ifOperStatus down(2), ifName t1-2/0/0
Jan 13 23:43:07 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 134,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0
Jan 13 23:43:07 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 149,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0.0
Jan 14 00:21:50 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_DOWN: ifIndex 134,
ifAdminStatus up(1), ifOperStatus down(2), ifName t1-2/0/0
Jan 14 00:21:52 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 134,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0
Jan 14 00:21:52 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 149,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0.0
Jan 14 01:21:22 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_DOWN: ifIndex 134,
ifAdminStatus up(1), ifOperStatus down(2), ifName t1-2/0/0
Jan 14 01:21:24 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 134,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0
Jan 14 01:21:24 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 149,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0.0
Jan 14 01:41:11 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_DOWN: ifIndex 134,
ifAdminStatus up(1), ifOperStatus down(2), ifName t1-2/0/0
Jan 14 01:41:13 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 134,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0
Jan 14 01:41:13 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 149,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0.0
Jan 14 01:41:14 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_DOWN: ifIndex 134,
ifAdminStatus up(1), ifOperStatus down(2), ifName t1-2/0/0
Jan 14 01:41:20 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 134,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0
Jan 14 01:41:20 US-ISCRA-RTR01 mib2d[923]: SNMP_TRAP_LINK_UP: ifIndex 149,
ifAdminStatus up(1), ifOperStatus up(1), ifName t1-2/0/0.0
Here's what show interface extensive has for errors/alarms:
Input errors:
Errors: 2, Drops: 0, Framing errors: 0, Policed discards: 0, L3
incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 206, Errors: 0, Drops: 0, Aged packets: 0, MTU errors:
0, Resource errors: 0
DS1 alarms : None
DS1 defects : None
T1 media: Seconds Count State
SEF 0 0 OK
BEE 78 75 OK
AIS 7914 16 OK
LOF 7927 161 OK
LOS 0 0 OK
YELLOW 28 19 OK
BPV 0 0
EXZ 0 0
LCV 10 10
PCV 0 0
CS 0 0
LES 7
ES 18
SES 18
SEFS 18
BES 0
UAS 8003
Could this be something as simple as clock slip? Our customer's CPE is
generally Juniper J6350s and J2320s running 9.3S10 code
Thanks in advance for any suggestions,
Ben
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
