-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear List, does anyone know what ird> show protocol R123 name proto table state since info R123 BGP Ttablename start 2010-04-16 09:36:35 Idle Socket: Broken pipe mean? Rgds, Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLyDouAAoJEJDQtqadNP/lrqQH/A1KAe2opON2YY4dsrd5p+Jv 6pa4x+q10EGFf/f/podPpr3qK8UcvQu2ynRpYSKE6+ypHm5kQjcvCZptk6l637fF VQnGXC7eiO0IU7fxAG/78A5Oy+5skFEzZxiLfgqapgDZ8E6d1oVD1LdB94AHsKhs S4/fFd/bLCD9bFHBcBvko6tttf9a4n7ovnfCNkm25KULggod3uiOafkIE108Hwyx BkNbQtvWk3oyPZWb2LxfihgPIp/nsAA9Tq7WrvnXukQZFM+AgGGTbYmcJxUBFpnY YbdcuvfVJrI7y48HeduwAPGblLjK5oU3RNAhDgbhmKHTCfB23qEOksjfZ9+kpns= =Wpr+ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 16.04.2010 12:21, schrieb Stefan Jakob:
ird> show protocol R123 name proto table state since info R123 BGP Ttablename start 2010-04-16 09:36:35 Idle Socket: Broken pipe
restart R123 removed the Broke pipe state - Still not sure, what kind of impact this might have had. Rgds, Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLyD5LAAoJEJDQtqadNP/l3S4H/1XJTr9khC3gWoGYR4ZouDZ4 93Xja4G3f6iRzLy9SDw4WOcyTHQpGUVMVBbsgumrw4Rsn4+66VCAI51nXMINoNIN bZJ0ZdygWYbGcJ07f15pNpLBtGRFDjbnPGuK22VzVfQwjuVKGOI2AIZHjtRBXAHe TlNArB/qr0hz3AqC3gguWzmuce5mqGYqCPeUpMQIFWFk+uHEZR608z14XyMheVCY 3nJtLSAi2ITZCO/sEzrlyalj72w7d/bzfVwJ64aYwz7irClmUY/XReuB0VCGFuiN XP9gbkprZOS3NqomglN4CeFiArWbtOMj5tg0d+G6lrAZBJPBD8YTmF5qxggU7Wo= =Teow -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Version Info: Bird 1.2.1 + 1.2.2 pre-patches Debian Lenny 64 Rgds, Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLyGO+AAoJEJDQtqadNP/l1q8IAIlnAG9qgGPkPGhu/gyRB42E XLNpbs5SxvRIm0sfrTmNXXiX98v4tyMvaL4Z4AHKIkpATwbdZ3cuGbUJr630YDe3 ymFSDtxnXifr7d4SlBNjQCrAeP0p53poE0frqOSwXwHD0iCPeekTz/5AI5DuQSUY e+XdVtWgpvc4LNvDIAa3f7OkCYT8gg+rACc8QkqHfRmmrxl/iMc53/5HhkDb7aK3 4x0bqoDqEI9eYfW7RpaJQi098y/Xp8VijLpZvv2IfR8o/Qq3Dpb9sOixE9xX4mZp 4AsbBgDZhkjp/1c+vw3a7IoW/htN64kmsFcXuh/lo95k1cQPhKn9fq+vvEhYzTc= =IcCG -----END PGP SIGNATURE-----
On Fri, Apr 16, 2010 at 12:39:07PM +0200, Stefan Jakob wrote:
Am 16.04.2010 12:21, schrieb Stefan Jakob:
ird> show protocol R123 name proto table state since info R123 BGP Ttablename start 2010-04-16 09:36:35 Idle Socket: Broken pipe
restart R123
removed the Broke pipe state - Still not sure, what kind of impact this might have had.
'Broken pipe' is an system error signalizing that the other end of (BGP) connection closed it when we are trying to write to it. We should handle it better as a normal connection close, but it shouldn't cause any impact. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Ondrej Zajicek -
Stefan Jakob