Hi there, That’s not true and you sad it yourself. You have 240G per PIC. With 2x100G ports enabled you can still set one remaining port to 40G on the same pic. And it also works just fine.
Best regards, Vincentz > Am 06.05.2020 um 19:47 schrieb Tobias Heister <li...@tobias-heister.de>: > > On 06.05.2020 18:24, Brian Johnson wrote: >> A wise man once told me… “Just because you can do something, doesn’t mean >> you should”. More specific, “Just because you can do it in the Junos config, >> doesn’t mean it’s supported.” Junipers licensing “honor system” required >> honorable intentions. ;) > > I would say it is supported. Even the documentation has an example where one > port of the group is 100GE and two others are 10GE: > https://www.juniper.net/documentation/en_US/junos/topics/topic-map/rate-selectability-configuring.html#id-configuring-rate-selectability-at-port-level > > Also with MPC7 its not like its honor based to only use 240G per PFE ... its > a hard limit ;) > > If you run in PIC Mode with 100GE set, than in deed the other ports are > disabled: > "For example, if you choose to configure PIC 0 at 100-Gbps speed, only ports > 2 and 5 of PIC 0 operate at 100-Gbps speed, while the other ports of the PIC > are disabled." > https://www.juniper.net/documentation/en_US/junos/topics/topic-map/rate-selectability-configuring.html#id-configuring-rate-selectability-on-mpc7e-multi-rate-to-enable-different-port-speeds > > I mean what else should it do, there are only two 100GE Ports per PFE anyway > ;) > > -- > Kind Regards > Tobias Heister > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
