[j-nsp] Resource Temporarily Unavailable - Juniper MX

[Derick Winkworth]

Scratch that, it was bigger tx/rx buffers for sockets...  internal sockets.
 
Derick Winkworth
CCIE #15672 (RS, SP), JNCIE-M #721
http://packetpushers.net/author/dwinkworth/


________________________________
 From: Derick Winkworth <dwinkworth at att.net>
To: "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net> 
Sent: Tuesday, December 6, 2011 7:45 AM
Subject: Re: [j-nsp] Resource Temporarily Unavailable - Juniper MX
 
FWIW, some socket related changes were made in 10.4 (I believe)...  Bigger windows by default.  I haven't verified with Wireshark, but this is what I've heard.


 
Derick Winkworth
CCIE #15672 (RS, SP), JNCIE-M #721
http://packetpushers.net/author/dwinkworth/


________________________________
From: Paul Stewart <paul at paulstewart.org>
To: 'Alexandre Snarskii' <snar at snar.spb.ru> 
Cc: juniper-nsp at puck.nether.net 
Sent: Monday, December 5, 2011 9:23 AM
Subject: Re: [j-nsp] Resource Temporarily Unavailable - Juniper MX

Thanks - that actually makes a lot of sense ;)  We don't see any load to
speak of on our side but it does typically occur when a BGP session is reset
and we're sending out a full table to a customer...

Appreciate it,

Paul


-----Original Message-----
From: Alexandre Snarskii [mailto:snar at snar.spb.ru] 
Sent: Monday, December 05, 2011 10:09 AM
To: Paul Stewart
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Resource Temporarily Unavailable - Juniper MX

On Mon, Dec 05, 2011 at 07:48:22AM -0500, Paul Stewart wrote:
> Can anyone shed some light on these log messages?
> 
>  
> 
> Nov 30 04:48:21  core2.toronto1 rpd[1359]: bgp_send: sending 19 bytes 
> to
> xx.xxx.52.50 (External AS xxxxx) blocked (no spooling requested): 
> Resource temporarily unavailable
> 
> We get these every so often .. Presuming it has to due with load on 
> the system for a short period of time?

More possibly it's caused by remote system load (or link congestion or
whatever other reason for remote system not able to receive updates fast
enough). Then, when socket buffer is full with unacknowledged data, your
system tries to send another update/keepalive message and it results in
write(2) syscall returning EAGAIN error (actually, not an error, just and
indication of 'no data sent, try again later'), which translates to
"Resource temporarily unavailable" message. 

> 
> Platform is Juniper MX boxes running 10.0R3.10
> 
>  
> 
> Thanks,
> 
>  
> 
> Paul
> 
>  
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp

--
In theory, there is no difference between theory and practice. 
But, in practice, there is. 


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp