From: Scott Morris (swm@xxxxxxxxxx)
Date: Thu Jan 03 2002 - 00:08:07 GMT-3
Well.. Your BGP RID's don't match... On router B, you probably have a BGP
neighbor statement that doesn't match 3.3.3.3 (which is who the other router
says it is), and likewise the other router's neighbor statement doesn't
match the 193.1.1.2 that RouterB says it is....
Use the update-source part of the neighbor command to use a different
interface (like the loopback) for the RID. Otherwise, BGP will default to
use the interface that the IP packets route out of to reach that neighbor as
its RID. It's not like OSPF's router-wide RID selection.
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Wen Jia Yang
Sent: Wednesday, January 02, 2002 9:35 PM
To: ccielab@groupstudy.com
Subject: please explain the following debug output,thanks
RouterB#
01:01:55: BGP: 193.1.1.1 open active, delay 7436ms
RouterB#
01:02:03: BGP: 193.1.1.1 open active, local address 193.1.1.2
01:02:03: BGP: 193.1.1.1 sending OPEN, version 4
RouterB#
01:02:04: BGP: 193.1.1.1 remote close, state CLOSEWAIT
01:02:04: BGP: 193.1.1.1 closing
RouterB#
01:02:24: BGP: 193.1.1.1 open active, delay 8304ms
RouterB#
01:02:31: BGP: 193.1.1.1 passive open
01:02:31: BGP: 193.1.1.1 OPEN rcvd, version 4
01:02:31: BGP: 193.1.1.1 sending OPEN, version 4
01:02:31: BGP: 193.1.1.1 bad OPEN, wrong router identifier 3.3.3.3
01:02:31: BGP: 193.1.1.1 sending NOTIFICATION 2/3 (BGP identifier wrong) 4
bytes
03030303
01:02:31: BGP: 193.1.1.1 local error close after sending NOTIFICATION
01:02:31: BGP: 193.1.1.1 closing
Please list the potential problems and possible solutions,thanks in advance.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:14 GMT-3