RE: BGP - Connection refused by remote host

From: Todd, Douglas M. (DTODD@PARTNERS.ORG)
Date: Wed Feb 20 2008 - 19:45:17 ARST


Coonnection refused -

Wrong neighbor configuration
eBGP - missing multihop
eBGP - Using Loopback (and need multihop)
Password on bgp peer

If you are in the wrong as you will get the wrong as message in your logs
without doing a debug.
I don't think this I your problem.

DMT

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Patrick
Galligan
Sent: Tuesday, February 19, 2008 1:10 AM
To: Rookie Ccie
Cc: Cristian Ionescu; Cisco certification
Subject: Re: BGP - Connection refused by remote host

On Feb 18, 2008 12:35 AM, Rookie Ccie <rookie.ccie@gmail.com> wrote:
>
> The problem is how to find this AS number, I have seen several threads
> regarding this but no proper solution. Some say it's the hex number in
> "debug ip bgp" but it does not give what we want.
>
> If some one has a solution please let us know.
>
With V12.4(15)T3 on a 3825, debug ip bgp is all you need.

You will get output in logs such as:

BGP: 203.5.192.1 bad OPEN, remote AS is 65500, expected 100

This occurs 2 lines before the notification with the hex numbers and the "peer
in wrong AS" message

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.8/1289 - Release Date: 2/20/2008 10:26
AM
 

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.8/1289 - Release Date: 2/20/2008 10:26
AM
 

The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.



This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:49 ARST