Just a quick Sanity check question please:
si interface for l2tp:
show chassis hardware:
FPC 1 REV 08 750-063183 CAJA1580 MPC2E NG HQoS
CPU REV 13 711-045719 CAHM5690 RMPC PMB
MIC 0 REV 31 750-028387 CAHL3541 3D 4x 10GE XFP
PIC 1 BUILTIN BUILTIN 2x 10GE XFP
Xcvr 0 REV 01 740-014279 F174JU02815 XFP-10G-LR
If I am using the above interface for the si - am I right in saying the command for the inline services will be:
set chassis fpc 1 pic 1 tunnel-services bandwidth 10gset chassis fpc 1 pic 1 inline-services bandwidth 10gset chassis fpc 1 pic 1 max-queues-per-interface 8set chassis fpc 1 flexible-queuing-mode
And the si interface is : si-1/1/0
Does the FPC require a reboot for the change?
set chassis fpc 1 flexible-queuing-mode - on commit, this will require a FPC reboot but, why use this knob when your FPC is HQoS?
and set chassis fpc 1 pic 1 inline-services bandwidth 10g / set chassis fpc 1 pic 1 inline-services bandwidth 10g is enough for SI and interface is si-1/1/0. Can verify through show interface terse | match si-1/1/0
Thanks Karan for the sanity check.... Just wanted to confirm... 🙂
The reason for the other setting, I can't remember, but without, something didn't work..... 🙂
To add more info, flexible-queueing-mode is for non-HQoS MPC(s). In terms of subscriber(pppoe/l2tp/dhcp) use case, this knob basically helps to scale subscribers on policy/filters attached to them.
For HQoS MPC, like in your case, its not required.
Ah, probably for either of the following:
IPv6 MSS in the dynamic profile - or - Dynamic CoS settings
I haven't tested ipv6 mss, but for dynamic QoS or say when having multiple service attached per subscriber interface - it certainly helps in those cases when they are large in scale.
Yes. I had to upgrade for the Dynamic MSS settings, but it seems to work well. I had numerous problems with MSS on IPv6 before I applied this and now it seems okay.
Yes, it will be for the Dynamic CoS then..... I don't think it worked at all when we tested from a ppp subscriber on VoiP and then added the command and, bingo, it started queuing correctly and working as per documentation.
Thanks for the Help Karan...