Re: OpenBGP Setup Question

2005-05-20 Thread j knight 
Manon Goo wrote:
Hi,
I have setup openbgp on two routers (Config below). I am connecting to
two uplink routers at my ISP.
My ISP Complains that one of the his sessions allways is idle. (He is
running a cisco
12000 IOS 12.0.something) and this is filling his logs.
Might this be because of the state of your carp interfaces? (carp1124 
and carp1146)

From bgpd.conf(5):
depend on interface
  The neighbor session will be kept in state IDLE as long as
  interface reports no link.  For carp(4) interfaces, no link means
  that the interface is currently backup.  This is primarily in-
  tended to be used with carp(4) to reduce failover times.
  The state of the network interfaces on the system can be viewed
  using the show interfaces command to bgpctl(8).

.joel

OpenBGP Setup Question

2005-05-19 Thread Manon Goo 
Hi,

I have setup openbgp on two routers (Config below). I am connecting to
two uplink routers at my ISP.

My ISP Complains that one of the his sessions allways is idle. (He is
running a cisco
12000 IOS 12.0.something) and this is filling his logs.

He asked me to accept the bgp session on both routers and
only anounce my network on one of them.

Is this something taht can be done with openBGPD ?

Thanks in advance for any hints.


Manon


# CFG Router 1
peer_mesh_edge1_dus1=xx.xx.213.17
peer_mesh_edge2_dus1=xx.xx.213.25

# global configuration
#AS 65001
AS 65112
router-id xx.xx.152.246
log updates
network xx.xx.213.32/27

# neighbors and peers
group peering ASN25074 {
remote-as 25074
neighbor $peer_mesh_edge1_dus1 {
descr   Primary Peer Mesh
local-address xx.xx.213.19
announce self
depend on carp1124
tcp md5sig password XX
}
neighbor $peer_mesh_edge2_dus1 {
descr Secondary Peer Mesh
local-address 213.203.213.27
announce self
depend on carp1146
tcp md5sig password XX
}
}

# CFG Router 2
peer_mesh_edge1_dus1=xx.xx.213.17
peer_mesh_edge2_dus1=xx.xx.213.25

# global configuration
#AS 65001
AS 65111
router-id xx.xx.152.245
log updates
network xx.xx.213.32/27

# neighbors and peers
group peering ASN25074 {
remote-as 25074
neighbor $peer_mesh_edge1_dus1 {
descr   Primary Peer Mesh
local-address xx.xx.213.18
announce self
depend on carp1124
tcp md5sig password Y
}
neighbor $peer_mesh_edge2_dus1 {
descr Secondary Peer Mesh
local-address xx.xx.213.26
announce self
depend on carp1146
tcp md5sig password YYYX
}
}

[demime 1.01d removed an attachment of type application/pgp-signature]