Re: [f-nsp] MLXe BGP Next Hop Not Reachable

Youssef Bengelloun-Zahr <[email protected]>
Newsgroups gmane.network.nsp.foundry
Message-ID <CALHo_yCbfja5BmTF89RoyD57G5StFuRYB6u5J=z+5f89S5oOmg@mail.gmail.com>
Dear James,

Silly question : why a /29 IP interconnect and not a /30 ? Have you tried
changing that ?

Best regards.



2016-08-30 14:10 GMT+02:00 James Cornman <[email protected]>:

> Hello,
>
> Came across a strange issue that I could use a second set of eyes on.
>
> Have an MLXe8 router with 5.6e running.  Customer BGP session is up and
> we're receiving the route they're advertising, but BGP thinks the next-hop
> is unreachable and not accepting the route. Its not even getting to the
> point of processing any prefix-lists or route-maps.
>
>
> SSH@router#show ip bgp neigh 10.60.154.210 received-routes detail
>        There are 1 received routes from neighbor 10.60.154.210
> Searching for matching routes, use ^C to quit...
> Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
>        E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH
> m:NOT-INSTALLED-MULTIPATH
>        S:SUPPRESSED F:FILTERED s:STALE
> 1       Prefix: 10.60.158.0/26,  Status: EF,  Age: 0h0m12s
>          NEXT_HOP: 10.60.154.210, Not Reachable, Learned from Peer:
> 10.60.154.210 (64585)
>           LOCAL_PREF: 100,  MED: 0,  ORIGIN: igp,  Weight: 0
>          AS_PATH: 64585
>
>
> interface ve 170
>  ip address 10.60.154.209/29
> !
>
>  neighbor CUSTOMER-ABC peer-group
>  neighbor CUSTOMER-ABC remote-as 64585
>  neighbor CUSTOMER-ABC soft-reconfiguration inbound
>  neighbor CUSTOMER-ABC default-originate
>  neighbor CUSTOMER-ABC route-map in CUSTOMER-NOEXPORT-in
>  neighbor CUSTOMER-ABC route-map out DEFAULT-ONLY
>  neighbor 10.60.154.210 peer-group CUSTOMER-ABC
>
> Tried the usual suspects of removing the interconnect /29 from the ve and
> re-applying, rebuilding the BGP session, bouncing it many times, etc.
> Session is up..ping communication works fine.
>
>
>
> --
>
> *James Cornman*
>
> [email protected]
> 212.792.9950 - ext 101
>
> *Atlantic Metro Communications*
>
> *4 Century Drive, Parsippany NJ  07054*
>
>
> *Colocation • Cloud Hosting • Network Connectivity • Managed Services*
> Follow us on Twitter: @atlanticmetro <https://twitter.com/atlanticmetro> *•
> Like us on Facebook <https://www.facebook.com/atlanticmetro>*
> www.atlanticmetro.net
>
> _______________________________________________
> foundry-nsp mailing list
> [email protected]
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>



-- 
Youssef BENGELLOUN-ZAHR

_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.