Cisco NME-X-23ES-1G User Guide - Page 108

Voice Traffic and VVID, Configuring a Single Subnet for Voice and Data

Page 108 highlights

Configuration Tasks 16- and 36-Port Ethernet Switch Module for Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Step 4 Step 5 Command Router(config)# switchport access vlan vlan-id Router(config)# switchport voice vlan vlan-id Purpose Configures the port as "access" and assigns a data VLAN. Configures the voice port with a VVID that will be used exclusively for voice traffic. Voice Traffic and VVID The Ethernet switch network module can automatically configure voice VLAN. This capability overcomes the management complexity of overlaying a voice topology onto a data network while maintaining the quality of voice traffic. With the automatically configured voice VLAN feature, network administrators can segment phones into separate logical networks, even though the data and voice infrastructure is physically the same. The voice VLAN feature places the phones into their own VLANs without the need for end-user intervention. A user can plug the phone into the switch, and the switch provides the phone with the necessary VLAN information. Configuring a Single Subnet for Voice and Data For network designs with incremental IP telephony deployment, network managers can configure the Ethernet switch network module so that the voice and data traffic coexist on the same subnet. This might be necessary when it is impractical either to allocate an additional IP subnet for IP phones or to divide the existing IP address space into an additional subnet at the remote branch, it might be necessary to use a single IP address space for branch offices. (This is one of the simpler ways to deploy IP telephony.) When this is the case, you must still prioritize voice above data at both Layer 2 and Layer 3. Layer 3 classification is already handled because the phone sets the Type of Service (ToS) bits in all media streams to an IP Precedence value of 5. (With Cisco CallManager Release 3.0(5), this marking changed to a Differentiated Services Code Point ([DSCP]) value of EF.) However, to ensure that there is Layer 2 classification for admission to the multiple queues in the branch office switches, the phone must also use the User Priority bits in the Layer 2 802.1p header to provide Class of Service (CoS) marking. Setting the bits to provide marking can be done by having the switch look for 802.1p headers on the native VLAN. This configuration approach must address two key considerations: • Network managers should ensure that existing subnets have enough available IP addresses for the new Cisco IP phones, each of which requires a unique IP address. • Administering a network with a mix of IP phones and workstations on the same subnet might pose a challenge. To automatically configure Cisco IP phones to send voice and data traffic on the same VLAN, use the following commands beginning in privileged EXEC mode: Step 1 Step 2 Command Router# configure terminal Router(config)# interface interface Purpose Enters global configuration mode. Enters the interface configuration mode and the port to be configured (e.g., interface fa5/1). 108 Cisco IOS Release 12.2(2)XT, 12.2(8)T, and 12.2(15)ZJ

  • 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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

16- and 36-Port Ethernet Switch Module for Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series
Configuration Tasks
108
Cisco IOS Release 12.2(2)XT, 12.2(8)T, and 12.2(15)ZJ
Voice Traffic and VVID
The Ethernet switch network module can automatically configure voice VLAN. This capability
overcomes the management complexity of overlaying a voice topology onto a data network while
maintaining the quality of voice traffic. With the automatically configured voice VLAN feature, network
administrators can segment phones into separate logical networks, even though the data and voice
infrastructure is physically the same. The voice VLAN feature places the phones into their own VLANs
without the need for end-user intervention. A user can plug the phone into the switch, and the switch
provides the phone with the necessary VLAN information.
Configuring a Single Subnet for Voice and Data
For network designs with incremental IP telephony deployment, network managers can configure the
Ethernet switch network module so that the voice and data traffic coexist on the same subnet. This might
be necessary when it is impractical either to allocate an additional IP subnet for IP phones or to divide
the existing IP address space into an additional subnet at the remote branch, it might be necessary to use
a single IP address space for branch offices. (This is one of the simpler ways to deploy IP telephony.)
When this is the case, you must still prioritize voice above data at both Layer 2 and Layer 3.
Layer 3 classification is already handled because the phone sets the Type of Service (ToS) bits in all
media streams to an IP Precedence value of 5. (With Cisco CallManager Release 3.0(5), this marking
changed to a Differentiated Services Code Point ([DSCP]) value of EF.) However, to ensure that there is
Layer 2 classification for admission to the multiple queues in the branch office switches, the phone must
also use the User Priority bits in the Layer 2 802.1p header to provide Class of Service (CoS) marking.
Setting the bits to provide marking can be done by having the switch look for 802.1p headers on the
native VLAN.
This configuration approach must address two key considerations:
Network managers should ensure that existing subnets have enough available IP addresses for the
new Cisco IP phones, each of which requires a unique IP address.
Administering a network with a mix of IP phones and workstations on the same subnet might pose
a challenge.
To automatically configure Cisco IP phones to send voice and data traffic on the same VLAN, use the
following commands beginning in privileged EXEC mode:
Step 4
Router(config)#
switchport access vlan
vlan-id
Configures the port as “access” and assigns a data VLAN.
Step 5
Router(config)#
switchport voice vlan
vlan-id
Configures the voice port with a VVID that will be used
exclusively for voice traffic.
Command
Purpose
Command
Purpose
Step 1
Router#
configure terminal
Enters global configuration mode.
Step 2
Router(config)#
interface
interface
Enters the interface configuration mode and the port to be
configured (e.g., interface fa5/1).