Okay, i tried with "number-of-ports" on pic-level instead. But
unfortunately, "number-of-sub-ports 2" is ignored now
fpc 5 {
pic 0 {
pic-mode 100G;
}
pic 1 {
number-of-ports 5;
port 1 {
number-of-sub-ports 2;
}
}
}
Are 100g ports only recognised with a transceiver plugged in ? I am
missing the 100g ports in the output of "show int terse"
router# show interfaces terse | match "xe-5/1|et-5/1" | except 16386 |
except "\.0"
xe-5/1/0:0 up down
xe-5/1/0:1 up down
xe-5/1/0:2 up down
xe-5/1/0:3 up down
xe-5/1/1:0 up down
xe-5/1/1:1 up down
xe-5/1/1:2 up down
xe-5/1/1:3 up down
xe-5/1/2:0 up down
xe-5/1/2:1 up down
xe-5/1/2:2 up down
xe-5/1/2:3 up down
xe-5/1/3:0 up up
xe-5/1/3:1 up up
xe-5/1/3:2 up up
xe-5/1/3:3 up up
xe-5/1/4:0 up down
xe-5/1/4:1 up down
xe-5/1/4:2 up down
xe-5/1/4:3 up down
>You can't oversubscribe the capacity of the MPC7 card.
Yes, i know. In my setup, i would use 14x 10G + 2x100G on pic 1 in
maximum which sums up to 240G, means no oversubscription.
Regards,
Alex
we have some MX-Routers (MX480 and MX960) with MPC7E-MRATE
linecards. As
far as i know, one PFE supports 240G each. Is it possible to use both
100G ports and in addititon 14x 10G ports on a single PFE ?
With the following configuration, i got an error "FPC 5 PIC 1 Invalid
port profile configuration":
You can't oversubscribe the capacity of the MPC7 card. See
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/preventing-oversubscription-active-physical-ports.html#id-supported-active-physical-ports-for-configuring-rate-selectability-to-prevent
for permitted port configurations. Note "Oversubscription of Packet
Forwarding Engine capacity is not supported."
Steinar Haug, Nethelp consulting, sth...@nethelp.no
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
