What version of Netiron are you running on each and do they both have the
adv license key enabled?  do show license it should show:
[image: image.png]

Erich Kaiser
The Fusion Network
er...@gotfusion.net
Office: 815-570-3101





On Wed, Nov 13, 2019 at 2:54 PM Fawcett, Nick via NANOG <nanog@nanog.org>
wrote:

> All mpls-interfaces are listed and policy is just traffic-eng ospf.
>
>
>
> Nick
>
>
>
> *From:* James Cornman <ja...@atlanticmetro.net>
> *Sent:* Wednesday, November 13, 2019 2:43 PM
> *To:* Fawcett, Nick <nfawc...@corp.mtco.com>
> *Cc:* nanog@nanog.org
> *Subject:* Re: Brocade CER MPLS
>
>
>
> Ensure that 'mpls-interface xxx' is on for all of the interfaces, and also
> ensure that any traffic-engineering options match on both sides.  "show
> mpls lsp detail" should show some other info that may be helpful here.
>
>
>
> On Wed, Nov 13, 2019 at 3:24 PM Fawcett, Nick via NANOG <nanog@nanog.org>
> wrote:
>
> I have one CER (let’s call him Charlie) that is not able to build an LSP
> tunnel to another CER.  Shows “Currently found no route. Will schedule for
> retry”.  Both CER’s can ping and traceroute each other.  When I had the LSP
> to the destination router (Snoopy) it adds the LSP and shows UP in status
> field.  Both have the same number of routes in their ospf table.  Charlie
> has other LSP’s built to other CER’s on the network with productive VLL’s
> and VPLS’s.  I have removed both lsp’s from both Charlie and Snoopy and
> re-added them and only one Snoopy’s LSP comes up.  Any ideas?
>
>
>
> Nick
>
> --
>
> Checked by SOPHOS http://www.sophos.com
>
>
>
> --
>
> *James Cornman*
>
>
> *Chief Technology Officer *jcorn...@atlanticmetro.net
> 212.792.9950 - ext 101
>
> * Atlantic Metro Communications*
>
> *4 Century Drive, Parsippany NJ  07054*
>
>
> *Cloud Hosting • Colocation • 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
>
>
>
> --
>
> Checked by SOPHOS http://www.sophos.com
>
>

Reply via email to