Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Are fabric services in VSAN X protected against CPU hogging from VSAN Y? In other words, if an HBA in VSAN Y starts going crazy and does 2000 FLOGIs in a couple of seconds, will the login service in VSAN Y peg the CPU and possibly deny (or severely ...
Are there any holddown timers to guard against "brown" failures? For example, if an HBA goes bad and does 2000 FLOGI's within a couple of seconds, can the switch shut down that port for a specified length of time?
1. I'm pretty sure, but not positive.2. In the ingress port of the source switch, this configuration would mark the frames for the high-priority queue. You are correct that it uses 3 bits in the header for marking. There are actually 4 queues, bu...
Frames are marked per VSAN (or, service policies are assigned per VSAN), but there is not a scheduler for each VSAN as I understand it. The scheduler doesn't know about VSANs - it only knows about its 4 queues.Therefore, a frame marked High in VSAN ...
Yes and no. If you put traffic from Host10 in the High queue, and traffic from Host20 in the Medium queue, the ingress port would prioritize the traffic from Host10 over the traffic from Host20. It would NOT, however, prioritize ALL traffic in VSAN...
