[f-nsp] BGP between XMRs (or from XMR to Juniper)
David Ball
davidtball at gmail.com
Thu Apr 3 15:38:49 EDT 2008
I'm brand new to Foundry devices and thought I was doing well, but
somehow I'm stumbling at getting something as simple as BGP running
(iBGP), and I can't afford to tear much more hair out.
Is much else needed just to establish a session besides:
-ip connectivity (PtP and loopback IPs seen on both sides, all pingable)
-an IGP (or static routes) to advertise loopback IPs (using OSPF)
-local-as
-neighbor statement specifying a neighbor IP and remote-as
I know there are dozens of other settings I can (and will) employ,
but just to get a session up, should it require much more ?
When trying to establish a session to a Juniper m10 with full
traceoptions enabled, the m10 indicated:
Apr 3 10:30:20.868934 bgp_recv: peer 172.16.0.4 (Internal AS 64555):
received unexpected EOF
where 172.16.0.4 is the XMR. I (apparently) have full logging
enabled on the XMR, but it's telling me nothing (unless I'm not asking
it properly). The following shows logging enabled, but I see nothing
about BGP:
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 32 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Any thoughts or nudges in the right direction would be appreciated.
Of all the things I plan to configure on the XMRs, I figured BGP would
be the easiest, but clearly I'm missing something. Thanks in advance.
David
More information about the foundry-nsp
mailing list