On 1q4t ports (except Gigabit Ethernet), the trust-cos port keyword displays an error message, activates receive queue drop thresholds, and as indicated by the error message does not apply the trust-cos trust state to traffic. You must configure a trust-cos ACL that matches the ingress traffic to apply the trust-cos trust state.
Below is my config on Cat6500
set qos acl mac test1 trust-cos any any
set port qos 4/3 trust trust-cos
set qos acl map test1 4/3
commit qos acl all
Then I do the sh port qos...........
(Attached is the result of sh port qos 4/3)
CatOS> (enable) sh port qos 4/3
QoS is enabled for the switch.
QoS policy source for the switch set to local.
Port Interface Type Interface Type Policy Source Policy Source
Traffic which falls in ACL will have no change of cos .The Access list is only considered and goes according to it and hence the Port can be left as untrusted. If traffic doesn't match ACL on that port cos value will be set to default state(untrusted). This is an expected behavior.
I am not sure if you have seen this document that talks about the limitations. You might want to take a look at this also.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.