[j-nsp] VPLS Hardware Not present

[magno]

Hi Keegan,

  Keep in mind that you can only configure the tunnel bandwidth according
with the actual port speed on the DPC. If you have a 10ge dpc you must use a
10g tunnel bandwidth config  (and as Harry mentioned you lose a port) and in
case you have a 1g DPC you must use a 1g tunnel bandwith config and you
won't lose anything.

After committing this config, look for a 'vt' interface... moreover check
you are using the correct encapsulation for VPLS (either ethernet-vpls or
vlan-vpls).

Have you just tried with no-tunnel-service just to see if the instance comes
up? This test would confirm encapsulation on the access facing interface.

Cheers

Magno
Il giorno 30/set/2011 23:07, "Harry Reynolds" <harry at juniper.net> ha
scritto:
> So the fpc restart fixed the issue?
>
> AFAIK, the 1g tunnel is free, 10g burns a port.
>
> Regards
>
>
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:
juniper-nsp-bounces at puck.nether.net] On Behalf Of Keegan Holley
> Sent: Friday, September 30, 2011 1:56 PM
> To: juniper-nsp
> Subject: Re: [j-nsp] VPLS Hardware Not present
>
> We are using the following to dedicate fpc bandwidth instead of disabling
> tunnel services. I've been told it's faster but disables a gig interface
to
> cannibalize the asics. It however requires a fpc restart. I suppose a RTM
> is in order. Thanks all for the input.
>
>
> set chassis fpc 0 pic 0 tunnel-services bandwidth 1g
>
>
> 2011/9/30 Keegan Holley <keegan.holley at sungard.com>
>
>> Ok, I'm stumped. Configuring vpls and everything seems to be working but
>> the local router interfaces. They come up as NP or hardware not present.
>> The DPC and pic are up and working fine and I've tried it with "tunnel
>> bandwidth 1g" configured under the chassis stanza as well as no tunnel
>> services under vpls protocols. I have a pretty good grasp of vpls
>> configuration, but I'm sensing a juniper nuance that I don't remember.
Does
>> this ring any bells for anyone?
>>
>> Thanks,
>>
>> Keegan
>>
>> root at mx480> show vpls connections
>> Layer-2 VPN connections:
>>
>> Legend for connection status (St)
>> EI -- encapsulation invalid NC -- interface encapsulation not
>> CCC/TCC/VPLS
>> EM -- encapsulation mismatch WE -- interface and instance encaps not
>> same
>> VC-Dn -- Virtual circuit down NP -- interface hardware not present
>> CM -- control-word mismatch -> -- only outbound connection is up
>> CN -- circuit not provisioned <- -- only inbound connection is up
>> OR -- out of range Up -- operational
>> OL -- no outgoing label Dn -- down
>> LD -- local site signaled down CF -- call admission control failure
>> RD -- remote site signaled down SC -- local and remote site ID collision
>> LN -- local site not designated LM -- local site ID not minimum
designated
>> RN -- remote site not designated RM -- remote site ID not minimum
>> designated
>> XX -- unknown connection status IL -- no incoming label
>> MM -- MTU mismatch
>>
>> Legend for interface status
>> Up -- operational
>> Dn -- down
>>
>> Instance: vplsA
>> Local site: mx480-vplsA (6)
>> connection-site Type St Time last up # Up trans
>> 5 rmt NP
>> 9 rmt NP
>> 10 rmt NP
>>
>> {master}
>> root at mx480>
>>
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp