[j-nsp] BGP error "no spooling requested"
Paul Goyette
pgoyette at juniper.net
Tue Dec 12 13:30:01 EST 2006
You need to understand the working of the TCP protocol
to interpret the connection details. It is beyond the
scope of an E-mail thread to provide this detail.
If you're still stuck, use tcpdump on both sides to
see which packets are being sent and which are being
received. I would expect that you may have an MTU
problem somewhere (a tunnel with MTU x that traverses
a link with MTU y, and y < x).
If you still can't figure it out, open up a case with
JTAC. :)
Paul Goyette
Juniper Networks Customer Service
JTAC Escalation Engineer and
Security Incident Response Team
PGP Key ID 0x53BA7731 Fingerprint:
FA29 0E3B 35AF E8AE 6651
0786 F758 55DE 53BA 7731
> -----Original Message-----
> From: Jonas Frey [mailto:jf at probe-networks.de]
> Sent: Tuesday, December 12, 2006 10:16 AM
> To: Paul Goyette
> Subject: RE: [j-nsp] BGP error "no spooling requested"
>
> Paul,
>
> how would i spot a problem with the tcp seq nrs?
>
> One interesting thing is that one side does actually get all
> routes from
> the neighbour and the other side stops after sending 2 prefixes for no
> reason. The output below was taken at the same time from both sides:
>
> jonas at ams1-edge> show bgp neighbor 82.96.89.162
> Peer: 82.96.89.162+179 AS 29686 Local: 82.96.89.161+2329 AS 29686
> Type: Internal State: Established (route reflector client)Flags:
> <WriteActive Initializing>
> Last State: OpenConfirm Last Event: RecvKeepAlive
> Last Error: Cease
> Export: [ next-hop-self export-static ] Import: [ blackholefilter ]
> Options: <Preference HoldTime RemovePrivateAS LogUpDown Cluster
> AddressFamily PeerAS LocalAS Refresh>
> Address families configured: inet-unicast
> Holdtime: 300 Preference: 170 Local AS: 29686 Local System AS: 29686
> Number of flaps: 10
> Error: 'Hold Timer Expired Error' Sent: 0 Recv: 6
> Error: 'Cease' Sent: 3 Recv: 1
> Peer ID: 82.96.89.218 Local ID: 82.96.89.233 Active
> Holdtime:
> 300
> Keepalive Interval: 100 Peer index: 1
> NLRI advertised by peer: inet-unicast
> NLRI for this session: inet-unicast
> Peer supports Refresh capability (2)
> Table inet.0 Bit: 10002
> RIB State: BGP restart is complete
> Send state: not in sync
> Active prefixes: 14797
> Received prefixes: 24402
> Suppressed due to damping: 0
> Advertised prefixes: 187651
> Last traffic (seconds): Received 6 Sent 34 Checked 34
> Input messages: Total 76662 Updates 76657 Refreshes 0 Octets
> 8445181
> Output messages: Total 425 Updates 416 Refreshes 0 Octets
> 49401
> Output Queue[0]: 186809
> Write buffered octets: 100
>
>
> As you can see the above is the one having the problem. What sounds
> suspicous to me is that it says "write buffered..." and
> "write active".
> The output Queue never decreases from the above value....
>
> The output below is from the side that actually sends all prefixes but
> only receives 2 prefixes.
>
> Peer: 82.96.89.161+2329 AS 29686 Local: 82.96.89.162+179 AS 29686
> Type: Internal State: Established (route reflector client)Flags:
> <Sync>
> Last State: OpenConfirm Last Event: RecvKeepAlive
> Last Error: Hold Timer Expired Error
> Export: [ next-hop-self export-static ] Import: [ add-metric-8 ]
> Options: <Preference HoldTime RemovePrivateAS GracefulRestart
> LogUpDown Cluster AddressFamily PeerAS LocalAS Refresh>
> Address families configured: inet-unicast
> Holdtime: 300 Preference: 170 Local AS: 29686 Local System AS: 29686
> Number of flaps: 5
> Error: 'Hold Timer Expired Error' Sent: 4 Recv: 0
> Peer ID: 82.96.89.233 Local ID: 82.96.89.218 Active
> Holdtime:
> 300
> Keepalive Interval: 100 Peer index: 0
> NLRI for restart configured on peer: inet-unicast
> NLRI advertised by peer: inet-unicast
> NLRI for this session: inet-unicast
> Peer supports Refresh capability (2)
> Restart time configured on the peer: 120
> Stale routes from peer are kept for: 300
> Peer does not support Restart capability
> Table inet.0 Bit: 10006
> RIB State: BGP restart is complete
> Send state: in sync
> Active prefixes: 0
> Received prefixes: 2
> Suppressed due to damping: 0
> Advertised prefixes: 192398
> Last traffic (seconds): Received 118 Sent 7 Checked 27
> Input messages: Total 2 Updates 1 Refreshes 0 Octets
> 139
> Output messages: Total 37295 Updates 37292 Refreshes 0 Octets
> 4099214
> Output Queue[0]: 0
>
>
>
> On Tue, 2006-12-12 at 17:56, Paul Goyette wrote:
> > > i've got a problem with getting 2 simple BGP sessions
> running. They
> > > actually open fine, exchange some routes and then die and
> the whole
> > > thing starts again.
> > >
> > > Errors are the same on both ends:
> > >
> > > Dec 12 17:41:41 ams1-edge rpd[2704]: bgp_send: sending
> 19 bytes to
> > > x.x.x.x (Internal AS 29686) blocked (no spooling
> requested): Resource
> > > temporarily unavailable
> > > Dec 12 17:41:41 ams1-edge rpd[2704]: bgp_traffic_timeout:
> > > error sending
> > > KEEPALIVE to x.x.x.x (Internal AS 29686): Resource temporarily
> > > unavailable
> > > Dec 12 17:41:41 ams1-edge rpd[2704]: bgp_event: peer x.x.x.x
> > > (Internal
> > > AS 29686) old state Established event TransportError new
> state Idle
> > >
> > > I havent been able to find a PR matching on anything like
> spooling,
> > > anyone ever observed this error before?
> >
> > Sounds to me like the TCP session is wedged. Take a tcpdump
> > and check out the sequence numbers. Or, look at the output
> > of "show system connections extensive"...
> --
> Mit freundlichen Grüßen / With kind regards,
> Jonas Frey
>
> ----------------------------------------------------------------
> Probe Networks Jonas Frey e-Mail: jf at probe-networks.de
> Provinzialstr. 104 D-66740 Saarlouis
> Tel: +(49) (0) 180 5959723 Fax: +(49) (0) 180 5998480
> Internet: www.probe-networks.de Hotline: 0800 1656531
> VoIP/SIP: info at probe-networks.de
> ----------------------------------------------------------------
>
> Diese E-Mail enthaelt moeglicherweise vertrauliche und/oder rechtlich
> geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind
> oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte
> sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
> Kopieren sowie die unbefugte Weitergabe dieser Mail ist strengstens
> untersagt.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail
> in error) please notify the sender immediately and destroy this
> e-mail. Any unauthorised copying, disclosure or distribution of the
> contents of this e-mail is strictly prohibited.
>
> ----------------------------------------
>
More information about the juniper-nsp
mailing list