From: Scott Morris (swm@emanon.com)
Date: Thu Nov 24 2005 - 01:23:27 GMT-3
If you can't form a peering relationship, sending communities won't help you
any!!!
Have you run any debug commands to see what's going on?
Try some simple things. You having "router bgp 5" already does what you're
trying to do with the local-as part. So that's not the issue (although
debugs would have helped you there too).
My guess is that it's something very simple. Setting your router-id is nice
for informational purposes, but it doesn't automagically make your packets
get sourced by that IP address. Try using a neighbor command with the
"update-source" option to match whatever the other guy is setting your
neighbor IP to.
Again... Look at debugs. They'll tell you what IS indeed happening so you
can figure out what is NOT happening (providing you get what is supposed to
happen!)!!!
Cheers,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
jnkmail4eva@yahoo.com
Sent: Wednesday, November 23, 2005 8:32 PM
To: ccielab@groupstudy.com
Subject: BGP peering
I have tried couple of things so far, but I have been unsuccessfull.
Router 1 - AS # 5
Router 2 - AS # 6
Router 1 peers with router 2,
I have no control over router 2's bgp configuration.
I need to inform router 2 of my locas-as # ..
router1
route bgp 5
bgp router id 1.1.1.1
neighbor 2.2.2.2 remote-as 6
neighbor 2.2.2.2 ebgp-multihop 10
I tried using the following command
neigbor 2.2.2.2 local-as 5
I get an error.
Other possible solution I can think of is send-community ..
Any thoughts before the turkey is sliced ..
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:07 GMT-3