[j-nsp] BGP error messages
Erik Haagsman
erik at we-dare.net
Wed Sep 7 16:02:24 EDT 2005
All there is to see in the errors you sent is that the sonet interface
went down, and by the looks of it I'd say because of external problems
(clocking/synch comes to mind) but without more info that's pure
speculation. Where there any SONET alarms prior to the
SNMP_TRAP_LINK_DOWN message...? AIS, LOS, RDI....?
jjsyed at aol.com wrote:
>it has been stable and never seen this message in a log file...
>
>here is the snapshot of my sonet interface:
>
>
>Physical interface: so-1/3/1, Enabled, Physical link is Up
>Interface index: 140, SNMP ifIndex: 33, Generation: 27
>Description: CW-OC3-1588771
>Link-level type: PPP, MTU: 4474, Clocking: External, SONET mode, Speed:
>OC3, Loopback: None, FCS: 32,
>Payload scrambler: Enabled
>Device flags : Present Running
>Interface flags: Point-To-Point SNMP-Traps 16384
>Link flags : Keepalives
>Hold-times : Up 0 ms, Down 0 ms
>Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
>Keepalive statistics:
>Input : 1581828 (last seen 00:00:04 ago)
>Output: 1581204 (last sent 00:00:03 ago)
>LCP state: Opened
>NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
>Not-configured
>CHAP state: Not-configured
>CoS queues : 4 supported
>Last flapped : 2005-08-31 05:54:11 EDT (1w0d 08:55 ago)
>Statistics last cleared: 2005-03-09 10:13:01 EST (26w0d 03:36 ago)
>Traffic statistics:
>Input bytes : 3755481907118 2532128 bps
>Output bytes : 10681527863968 7879024 bps
>Input packets: 41237541599 6750 pps
>Output packets: 30784258562 2583 pps
>Input errors:
>Errors: 142, Drops: 0, Framing errors: 243, Runts: 140, Giants: 2,
>Bucket drops: 0,
>Policed discards: 233, L3 incompletes: 0, L2 channel errors: 0, L2
>mismatch timeouts: 5,
>HS link CRC errors: 0, HS link FIFO overflows: 0
>Output errors:
>Carrier transitions: 4, Errors: 0, Drops: 0, Aged packets: 0, HS link
>FIFO underflows: 0,
>MTU errors: 0
>Queue counters: Queued packets Transmitted packets Dropped
>packets
>0 best-effort 30779844779 30779844779
>0
>1 expedited-fo 0 0
>0
>2 assured-forw 0 0
>0
>3 network-cont 4413775 4413775
>0
>SONET alarms : None
>SONET defects : None
>SONET PHY: Seconds Count State
>PLL Lock 0 0 OK
>PHY Light 0 0 OK
>SONET section:
>BIP-B1 0 0
>SEF 1 1 OK
>LOS 0 0 OK
>LOF 0 0 OK
>ES-S 1
>SES-S 1
>SEFS-S 1
>SONET line:
>BIP-B2 1 56
>REI-L 0 0
>RDI-L 0 0 OK
>AIS-L 0 0 OK
>BERR-SF 0 0 OK
>BERR-SD 0 0 OK
>ES-L 1
>SES-L 1
>UAS-L 0
>ES-LFE 0
>SES-LFE 0
>UAS-LFE 0
>SONET path:
>BIP-B3 5 24
>REI-P 4 45
>LOP-P 0 0 OK
>AIS-P 848 2 OK
>RDI-P 3 1 OK
>UNEQ-P 0 0 OK
>PLM-P 0 0 OK
>ES-P 853
>SES-P 849
>UAS-P 837
>ES-PFE 7
>SES-PFE 3
>UAS-PFE 0
>Received SONET overhead:
>F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0xc0
>S1 : 0x00, C2 : 0x16, C2(cmp) : 0x16, F2 : 0x00
>Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00
>Transmitted SONET overhead:
>F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
>S1 : 0x00, C2 : 0xcf, F2 : 0x00, Z3 : 0x00
>Z4 : 0x00
>UAS-P 837
>ES-PFE 7
>SES-PFE 3
>UAS-PFE 0
>Received SONET overhead:
>F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0xc0
>S1 : 0x00, C2 : 0x16, C2(cmp) : 0x16, F2 : 0x00
>Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00
>Transmitted SONET overhead:
>F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
>S1 : 0x00, C2 : 0xcf, F2 : 0x00, Z3 : 0x00
>Z4 : 0x00
>Received path trace: kar2.nyr so-4/3/0
>6b 61 72 32 2e 6e 79 72 20 73 6f 2d 34 2f 33 2f kar2.nyr so-4/3/
>30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0...............
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a ................
>Transmitted path trace: iny-jisp4 so-1/3/1
>69 6e 79 2d 6a 69 73 70 34 20 73 6f 2d 31 2f 33 iny-jisp4 so-1/3
>2f 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 /1..............
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>HDLC configuration:
>Policing bucket: Disabled
>Shaping bucket : Disabled
>Giant threshold: 4486, Runt threshold: 5
>Packet Forwarding Engine configuration:
>Destination slot: 1, PLP byte: 1 (0x00)
>CoS transmit queue Bandwidth Buffer Priority
>Limit
>% bps % bytes
>0 best-effort 95 147744000 95 0 low
>none
>3 network-control 5 7776000 5 0 low
>none
>Logical interface so-1/3/1.0 (Index 73) (SNMP ifIndex 59) (Generation 11)
>Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
>Protocol inet, MTU: 4470, Generation: 18, Route table: 0
>Flags: None
>Filters: Input: Inet-NewDropsThenPass, Output: port-mirror-to-ge-IDS
>Addresses, Flags: Is-Preferred Is-Primary
>Destination: 208.173.135.188/30, Local: 208.173.135.190, Broadcast:
>208.173.135.191,
>Generation: 20
>
>-----Original Message-----
>From: Matt Yaklin <myaklin at g4.net>
>To: jjsyed at aol.com
>Cc: juniper-nsp at puck.nether.net
>Sent: Wed, 7 Sep 2005 15:47:43 -0400 (EDT)
>Subject: Re: [j-nsp] BGP error messages
>
>
>
>
>On Wed, 7 Sep 2005 jjsyed at aol.com wrote:
>
>
>
>>My router is peering with my provider router and I am seeing error messages
>>
>>
>below and was wondering if somebody can explain if this is something to be
>worried about. It seems like I am receiving notification messages from my peer
>but why it would cause the bgp session to drop?
>
>
>>Aug 31 05:54:11 iny-jisp4 mib2d[2532]: SNMP_TRAP_LINK_DOWN: ifIndex 33,
>>ifAdminStatus up(1), ifOperStatus down(2), ifName so-1/3/1
>>Aug 31 05:54:11 iny-jisp4 rpd[2533]: bgp_ifachange_group: NOTIFICATION sent
>>to 208.173.135.189 (External AS 3561): code 6 (Cease) subcode
>> 6 (Other Configuration Change), Reason: Interface change for the peer-group
>>Sep 5 07:49:48 iny-jisp4 rpd[2533]: bgp_read_v4_update: NOTIFICATION
>>received from 208.173.135.189 (External AS 3561): code 6 (Cease) su
>>bcode 6 (Other Configuration Change)
>>Sep 7 13:03:00 iny-jisp4 rpd[2533]: bgp_read_v4_update: NOTIFICATION
>>received from 208.173.135.189 (External AS 3561): code 6 (Cease) su
>>bcode 6 (Other Configuration Change)
>>
>>
>>
>
>i notice you are using a sonet card. are you sure there are no
>physical errors on the transport side of things?
>
>we just turned up an oc-12 a month or two ago and we could
>not keep a session up for more than a day or two due to physical
>errors on the muxes. MCI ended up replacing a card...
>
>it really burned me up they asked for me to replace my sonet
>card in the juniper before they checked their stuff.
>
>is this a new install that has never been stable yet?
>
>good luck.
>
>m
>
>
>
>
>>TIA
>>
>>JS
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp at puck.nether.net
>>http://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>
--
---
Erik Haagsman
Network Architect
We Dare BV
tel: +31(0)10 750 7008
fax: +31(0)10 750 7005
http://www.we-dare.nl
More information about the juniper-nsp
mailing list