Q: 7
A QoS policy on Cisco UCS must meet mese requirements:
No-drop class must be configured
Jumbo frames must be enabled without fragmentation.
Which configuration must be implemented to meet mese conditions?
Options
Discussion
C/D? From what I remember, the QoS system class is used for no-drop configs in UCS, and you need to set MTU to 9216 for true jumbo frames. Option D lines up with that and matches what I've seen on official docs. Think that's the way to go but if anyone disagrees let me know. Official guide plus hands-on lab helps a lot here.
D for sure. Only the QoS system class lets you do no-drop and set MTU 9216 for jumbo frames on UCS.
Its D, A and B are traps since they can't enable no-drop plus 9216 MTU together.
No-drop plus jumbo frames points straight to D. Only a QoS system class lets you set no-drop and an MTU high enough (9216) so fragmentation won't happen. Pretty sure that's the only config that checks both boxes.
Not B, D is it. The slow-drain timers (B) don't set up a no-drop class or guarantee jumbo frames without fragmentation. D is needed since only QoS system classes can do no-drop, and 9216 bytes is the correct MTU for jumbo frames on UCS. Pretty sure, unless I missed something.
Definitely D here. Creating a QoS system class with MTU 9216 bytes covers both no-drop and jumbo frames requirements.
Be respectful. No spam.
