• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 448
  • Last Modified:

BGP - state of ISP2 is not "established"

We are attempting to establish a BGP connection with a second ISP (228) but we could not "establish" the connection.

Any answers as to why (see below config) the ASN 228 state is not "ESTABLISHED?"

ASN 127 is established and working fine.

# show ip route bgp

                                IP Route Entries

  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.
  ------------------ --------------- ---- --------- ---------- ---------- -----  4024 bgp                  1          20

# show ip bgp summ
Peer Information

  Remote Address  Remote-AS Local-AS State         Admin Status
  --------------- --------- -------- ------------- ------------  127     40710    Established   Start  228       40710    Connect      Start


HP procurve 3800 >>

; J9573A Configuration Editor; Created on release #KA.15.10.0009
; Ver #03:03.1f.ef:f0

module 1 type j9573x
no cdp run
ip routing
no ip source-route
interface 25
   name " CrossConnect-2T "
interface 26
   name " CrossConnect-2X "
   speed-duplex 1000-full
router bgp 40710
   bgp router-id
   neighbor remote-as 127
   neighbor remote-as 228
vlan 1
   name "DEFAULT_VLAN"
   no untagged 1-2,6,16,25-26
   untagged 3-5,7-15,17-24
   ip address
vlan 3999
   name "DATA-Internet"
   untagged 1-2,6
   ip address
   ip address
   ip address
vlan 4024
   name "DATA-ISP-4024"
   untagged 25
   ip address
vlan 4047
   name "Data-ISP-4047"
   untagged 16,26
   ip address
no autorun

ALL names, numbers and code has been changed to mask identity.
  • 2
  • 2
1 Solution
Jan SpringerCommented:
debug ip bgp
debug ip tcp transaction
term mon

and optionally log to an external syslog server
Can you ping the IP address of the peer?

If IP connectivity is fine, it is typically a config error - any side has configured the wrong ASN or only one side has configured a password for authentication.
dts3909Author Commented:
We cannot ping directly.  Ping works through ISP#4024 around to ISP#4047 but not through direct connect to ISP#4047.

Config shows transceiver is linked and enabled.

ARP does not show direct attached ISP#4047 MAC address.

We even tried another transceiver on our side...we had same symptoms.

Can the procurve switch be linked and enabled at the layer-3 level but not layer-2?
You probably want to check the other end of that fiber.
Perhaps that ISP have a mix-up with ports at their end.
dts3909Author Commented:
Will check with ISP#4047 today and get back to forum after push-back.

UPDATE:  ISP#4047 was allowing only whitelisted MAC addresses.  Once the ISP tech#3 determined the block and then removed all the above BGP settings worked as planned.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now