[j-nsp] MX80 ports not recognized?

Johan Borch johan.borch at gmail.com
Wed Jan 30 14:48:48 EST 2013


Has Juniper started to enforce the port restrictions for the MX5-80 in
recent releases?

Johan


On Mon, Jan 28, 2013 at 9:51 PM, Alex Arseniev <alex.arseniev at gmail.com>wrote:

> https://www.juniper.net/**techpubs/en_US/junos11.4/**
> information-products/topic-**collections/release-notes/11.**
> 4/topic-62949.html#jd0e5448<https://www.juniper.net/techpubs/en_US/junos11.4/information-products/topic-collections/release-notes/11.4/topic-62949.html#jd0e5448>
>
> License support to enhance port capacity of MX5, MX10, and MX40 routers-By
> installing additional licenses, you can enhance the port capacity of your
> router without a hardware upgrade. For example, an MX5 router, an MX10
> router, or an MX40 router can have the port capacity of an MX80 router,
> provided the required licenses are installed. These routers use feature
> pack licenses, which provide additional port capacity with the same
> hardware. The soft enforcement policy allows the user to use a port for a
> certain period of time (usually a grace period of 30 days), and reverts if
> the license for that feature is not installed after the grace period.
> During the grace period, a reminder to purchase the license is reported in
> the system logs. Licenses can be upgraded or downgraded. When you downgrade
> the license, the port associated with the license is unusable.
>
> Are you certain You have two MX80 units and not 1 MX80 unit and 1
> MX5/10/40 unit?
>
> HTH
> Thanks
> Alex
>
> ----- Original Message ----- From: "Dave Peters - Terabit Systems" <
> Dave at terabitsystems.com>
> To: <juniper-nsp at puck.nether.net>
> Sent: Monday, January 28, 2013 8:25 PM
> Subject: [j-nsp] MX80 ports not recognized?
>
>
>
>  Hi all-
>>
>> I've got two MX80s that I upgraded from 11.1R1.14 to 11.4R6.5, and after
>> I finished, one unit showed the physical ports no longer available via the
>> CLI.  The xe-x/x/x interfaces are configurable on one unit, but don't show
>> up at all on the other.
>>
>> This seems like a simple problem, but I haven't been able to figure out
>> what I'm doing wrong.  Has anyone else seen this kind of error?  Is there
>> something I'm missing?
>>
>> Thanks in advance.
>>
>> --Dave Peters
>> ______________________________**_________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/**mailman/listinfo/juniper-nsp<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<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>


More information about the juniper-nsp mailing list