03-01-2016 07:05 AM
Just wanted to ask a question around port flags:
portFlags: PRESENT ACTIVE F_PORT G_PORT U_PORT NPIV LOGICAL_ONLINE LOGIN NOELP ACCEPT AOQ AOQ_AG
I have been unable to find information regarding the AOQ and AOQ_AG port flags....
These flags have appeared since an unknown issue caused some devices connected via an access gateway mode switch failed to pass through WWN's properly causing a drop in storage to these devices (also fabric login issues with the devices connected to the access gateway mode switch (reboot clears the issue)).
Since the blip 'AoQ' appears in a switchshow:
Port 1 example
1 1 0d0100 id N8 Online FC F-Port 1 N Port + 13 NPIV public (AoQ)
Port 2 example
4 4 0d0400 id N4 Online FC F-Port 1 N Port + 9 NPIV public
Any info on these port flags would be helpful.
03-02-2016 07:40 AM
From what I know, AoQ stands for "application oriented quality of service". When the term appeared some time ago, I've seen a whitepaper on it, and it was about doing some end-to-end QoS down to the virtual machines. You had to run 8G and/or 16G switches with "server application optimization" and "adaptive networking" licenses, and you had to have brocade HBAs in your virtualization servers running in NPIV mode. All this looked too complicated, especially together with the talks that Brocade is going to sell the HBA business soon. I hope you would still be able to find some more details on this now that you know how to decode the abbreviation.
03-10-2017 03:45 AM
Both side of the link support QoS and during the login process (ELP) have agreed to support QoS.
If you check the port on the switch side with "portcfgshow" or "portcfgqos" and that QoS is ON.
The device on the other end, HBA or AG, also supports QoS and have it enabled.
From the FOS 7.4 command reference manual for switchshow at http://www.brocade.com/content/html/en/command-ref
"AoQ Application-oriented QoS; indicates that an F_Port or N_Port has negotiated a link that is capable of quality of service (QoS). Both sides of the link have QoS capability and agreed on the protocol. The link could be between an HBA and an Access Gateway, between an Access Gateway and an edge switch, or between an HBA and an edge switch."
03-10-2017 08:13 AM
03-16-2017 05:38 AM
I do not think the AoQ will tie in your problem - it around the QoS applicabe between the switch and VC.
How does your problem manifest itself on the switch and on the VC?
From the provided example the VC clearly logs into the fabric but the hosts do not?
Pending your FOS level, have you looked at the output from to see if the host triedo to login or not?
portloginshow <port> -history
And NS entries with to see what if any activities on the VC ports
nsdevlog --show port <port>