From: dfredrick@gmail.com
Date: Wed Jun 21 2006 - 10:57:22 ART
Hello,
I just finish an online lab. I had trouble with getting an eBGP neighbor to come up. It was a BB router, so I didn't have access to see the config. Any who... I was recieving RIP updates for it. It was directly connected, on the same vlan, and I could ping it.
I tried the following and still didn't work...
- used the ebgp 255 (just incase it was further than I thought)
- used the update loopback0 (just incase it was peering to my loopback)
- and stripped it down to just basics on the router...
(meaning, didn't have any confederations or anything... just the AS it was going to peer with)
Then I turned on all debugging for BGP...
The only message I could get was "connection refused from remote" or something like that...
Then I turned on debug ip packet detail... to see if I was recieving any packets via TCP port 179... and I wasn't... all I saw from the backbone router was rip updates via 224.0.0.9.
Then I the only last thing I could think that could prevent updates... was an ACL... I looked at the whole path... no ACLs anywhere...
So what else could prevent eBGP neighbors from forming?
Thanks,
Daniel Fredrick
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:33 ART