19 messages in net.nether.puck.cisco-nsp[c-nsp] Source address on BGP peering...
FromSent OnAttachments
PiltrafillaJan 14, 2005 8:13 am 
Mark TinkaJan 14, 2005 8:46 am 
McCallum, RobertJan 14, 2005 9:00 am 
Daniel GinsburgJan 14, 2005 9:04 am 
Erdem SenerJan 14, 2005 9:09 am 
Marko MilivojevicJan 14, 2005 9:17 am 
Mark TinkaJan 14, 2005 9:19 am 
Rick CosseyJan 14, 2005 9:52 am 
Jared MauchJan 14, 2005 10:02 am 
Stephen J. WilcoxJan 14, 2005 10:34 am 
PiltrafillaJan 17, 2005 11:27 am 
Brian FeenyJan 17, 2005 11:37 am 
PiltrafillaJan 17, 2005 6:59 pm 
Brian FeenyJan 17, 2005 7:18 pm 
Michael K. SmithJan 17, 2005 10:30 pm 
PiltrafillaJan 18, 2005 3:33 am 
PiltrafillaJan 18, 2005 4:49 am 
Michael K. SmithJan 18, 2005 11:52 am 
PiltrafillaJan 24, 2005 8:01 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Source address on BGP peering set upActions...
From:Daniel Ginsburg (dgin@gmail.com)
Date:Jan 14, 2005 9:04:15 am
List:net.nether.puck.cisco-nsp

On Fri, 14 Jan 2005 15:45:30 +0200, Mark Tinka <mti@africaonline.co.sz>

Without manually specifying your source interface, BGP will find and use the Loopback interface with the highest IP address. Failing that, it will take the next highest IP address configured on the router (regardless of interface).

This can become a problem, especially if you keep adding/removing IP addresses on your router (customers, new routers, new segments, e.t.c.), hence the elegance of 'update-source'.

You confused source address of BGP session with router ID. They don't serve the same purpose nor have to be equal.

-- dg