cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5650
Views
0
Helpful
5
Replies

"auto qos voip cisco-phone" command not working on switch

Tracy La Rue
Level 1
Level 1

Hi All,

Have a 4510 switch that I found 2 ints not configured in our standard format like most all of the other ints on the switch.

When I tried to configure them with our standard config got the error message below after the "auto qos voip cisco-phone" command:

NRI-USTXWDL01-SW4510(config-if)# auto qos voip cisco-phone

AutoQoS Error: the following generated command was not properly applied:

service-policy input AutoQos-VoIP-Input-Cos-Policy

AutoQoS Error while generating commands on Gi8/9.

 

What does this mean? All of the other ints were configured with this command when switch was first configured last September.

Here's an example of one:

interface GigabitEthernet1/7
 switchport access vlan 30
 switchport mode access
 switchport voice vlan 20
 switchport port-security maximum 3
 switchport port-security aging time 2
 switchport port-security violation restrict
 switchport port-security aging type inactivity
 auto qos voip cisco-phone
 qos trust device cisco-phone
 spanning-tree portfast
 spanning-tree bpduguard enable
 service-policy input AutoQos-4.0-Cisco-Phone-Input-Policy
 service-policy output AutoQos-4.0-Output-Policy

 

Thanks for your help.

Tracy

1 Accepted Solution

Accepted Solutions

Terry Cheema
VIP Alumni
VIP Alumni

Tracy,

Whats the IOS version on the switch? Was it recently upgraded?

Can you share the interface configuration that gives this error? Is the error you have pasted complete or does it give any further output for any reason etc. why it is unable to apply the auto qos?

Can you also try to default the interface: "default int GX/Y"

Copy all the config to a notepad prior to that and paste the config back, first apply just the base config vlan etc. and try to apply auto qos config and see how yo go.

-Terry

Please rate all helpful posts.

View solution in original post

5 Replies 5

Terry Cheema
VIP Alumni
VIP Alumni

Tracy,

Whats the IOS version on the switch? Was it recently upgraded?

Can you share the interface configuration that gives this error? Is the error you have pasted complete or does it give any further output for any reason etc. why it is unable to apply the auto qos?

Can you also try to default the interface: "default int GX/Y"

Copy all the config to a notepad prior to that and paste the config back, first apply just the base config vlan etc. and try to apply auto qos config and see how yo go.

-Terry

Please rate all helpful posts.

Hi Terry,

I just didn't think it would work but I gave it a go anyway.

I defaulted the ints again and added in this order:

 switchport access vlan 30
 switchport mode access
 switchport voice vlan 20
 auto qos voip cisco-phone

And it worked! No error message.

NRI-USTXWDL01-SW4510-A1A#config t
Enter configuration commands, one per line.  End with CNTL/Z.
NRI-USTXWDL01-SW4510(config)#interface GigabitEthernet8/9
NRI-USTXWDL01-SW4510(config-if)#switchport access vlan 30
NRI-USTXWDL01-SW4510(config-if)# switchport mode access
NRI-USTXWDL01-SW4510(config-if)# switchport voice vlan 20
NRI-USTXWDL01-SW4510(config-if)#auto qos voip cisco-phone
NRI-USTXWDL01-SW4510(config-if)# switchport port-security maximum 3
NRI-USTXWDL01-SW4510(config-if)# switchport port-security aging time 2
NRI-USTXWDL01-SW4510(config-if)# switchport port-security violation restrict
NRI-USTXWDL01-SW4510(config-if)# switchport port-security aging type inactivity
NRI-USTXWDL01-SW4510(config-if)# spanning-tree portfast

Thanks Terry!

Not a prob Tracy, glad that helped! From experience when switch ports are not behaving as they should for no apparent reason - defaulting and reconfiguring solves the issue most of times :)

Anyways good to see your issue is resolved.

See you around.

-Terry

Hi Tracy La Rue,

 if you recently upgrade your switch, then you should remove all the 'auto qos' commands and insert it again.

 

Hope this helps.

Hi Marcelo,

Thanks for your reply to my post. The issue was resolved thru Terry's post.