Cisco N5K-C5010P-BF Troubleshooting Guide - Page 63

show queuing interface

Page 63 highlights

Chapter 4 Troubleshooting QoS Issues Improper Configurations Send document comments to [email protected]. set cos 1 mtu 9216 class type network-qos Critical set cos 6 mtu 9216 class type network-qos class-default mtu 9216 class-map type queuing Voice match qos-group 5 class-map type queuing Critical match qos-group 3 class-map type queuing Scavenger match qos-group 2 class-map type queuing Video-Signalling match qos-group 4 //The queuing interface will be applied under "system qos" to define the priority queue and how bandwidth is shared among non-priority queues.// policy-map type queuing Queue-5020 class type queuing Scavenger bandwidth percent 1 class type queuing Voice priority class type queuing Critical bandwidth percent 6 class type queuing Video-Signalling bandwidth percent 20 class type queuing class-fcoe bandwidth percent 0 class type queuing class-default bandwidth percent 73 //The input queuing policy determines how bandwidth are shared for FEX uplink in the direction from FEX to N5k. The output queueing policy determines the bandwidth allocation for both N5k interfaces and FEX host interfaces.// system qos service-policy type qos input classify-5020-global service-policy type network-qos NetworkQoS-5020 service-policy type queuing input Queue-5020 service-policy type queuing output Queue-5020 //Apply service-policy type qos under physical interface in order to classify traffic based on DSCP. Please note that for portchannel member the service-policy needs to be configured under interface port-channel.// interface eth1/1-40 service-policy type qos input Classify-5020 interface eth100/1/1-48 service-policy type qos input Classify-5020 The show queuing interface command can be used to ensure that the CoS-to-queue mapping is properly configured under the FEX interfaces. It can also be used to check the bandwidth and MTU configuration. This same command can be used to check the QoS configuration for the Nexus 5000 interfaces. The following is the output from the show queuing interface command for the Nexus 2248 interfaces when the above configrations are applied: switch# sh queuing interface ethernet 100/1/1 Ethernet100/1/1 queuing information: Input buffer allocation: Qos-group: 0 2 3 4 5 (shared) frh: 2 drop-type: drop cos: 0 1 2 3 4 5 6 OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 4-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

Send document comments to [email protected].
4-5
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 4
Troubleshooting QoS Issues
Improper Configurations
set cos 1
mtu 9216
class type network-qos Critical
set cos 6
mtu 9216
class type network-qos class-default
mtu 9216
class-map type queuing Voice
match qos-group 5
class-map type queuing Critical
match qos-group 3
class-map type queuing Scavenger
match qos-group 2
class-map type queuing Video-Signalling
match qos-group 4
//The queuing interface will be applied under “system qos” to define the priority queue
and how bandwidth is shared among non-priority queues.//
policy-map type queuing Queue-5020
class type queuing Scavenger
bandwidth percent 1
class type queuing Voice
priority
class type queuing Critical
bandwidth percent 6
class type queuing Video-Signalling
bandwidth percent 20
class type queuing class-fcoe
bandwidth percent 0
class type queuing class-default
bandwidth percent 73
//The input queuing policy determines how bandwidth are shared for FEX uplink in the
direction from FEX to N5k. The output queueing policy determines the bandwidth allocation
for both N5k interfaces and FEX host interfaces.//
system qos
service-policy type qos input classify-5020-global
service-policy type network-qos NetworkQoS-5020
service-policy type queuing input Queue-5020
service-policy type queuing output Queue-5020
//Apply service-policy type qos under physical interface in order to classify traffic
based on DSCP. Please note that for portchannel member the service-policy needs to be
configured under interface port-channel.//
interface eth1/1-40
service-policy type qos input Classify-5020
interface eth100/1/1-48
service-policy type qos input Classify-5020
The
show queuing interface
command can be used to ensure that the CoS-to-queue mapping is properly
configured under the FEX interfaces. It can also be used to check the bandwidth and MTU configuration.
This same command can be used to check the QoS configuration for the Nexus 5000 interfaces.
The following is the output from the
show queuing interface
command for the Nexus 2248 interfaces
when the above configrations are applied:
switch# sh queuing interface ethernet 100/1/1
Ethernet100/1/1 queuing information:
Input buffer allocation:
Qos-group: 0
2
3
4
5
(shared)
frh: 2
drop-type: drop
cos: 0 1 2 3 4 5 6