Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Network Availability Technologies Chapter 3 Medianet Availability Design Considerations Switch(config-if)# channel-group 16 mode active Cisco Virtual Switching System However, note that PAgP and LACP do not interoperate with each other; ports configured to use PAgP cannot form EtherChannels with ports configured to use LACP, nor can ports configured to use LACP form EtherChannels with ports configured to use PAgP. EtherChannel plays a critical role in provisioning network link redundancy, especially at the campus distribution and core layers. Furthermore, an evolution of EtherChannel technology plays a key role in Cisco VSS, which is discussed in the following section. The Cisco Catalyst 6500 Virtual Switching System (VSS) represents a major leap forward in device and network availability technologies, by combining many of the technologies that have been discussed thus far into a single, integrated system. VSS allows for the combination of two switches into a single, logical network entity from the network control plane and management perspectives. To the neighboring devices, the VSS appears as a single, logical switch or router. Within the VSS, one chassis is designated as the active virtual switch and the other is designated as the standby virtual switch. All control plane functions, Layer 2 protocols, Layer 3 protocols, and software data path are centrally managed by the active supervisor engine of the active virtual switch chassis. The supervisor engine on the active virtual switch is also responsible for programming the hardware forwarding information onto all the distributed forwarding cards (DFCs) across the entire Cisco VSS as well as the policy feature card (PFC) on the standby virtual switch supervisor engine. From the data plane and traffic forwarding perspectives, both switches in the VSS actively forward traffic. The PFC on the active virtual switch supervisor engine performs central forwarding lookups for all traffic that ingresses the active virtual switch, whereas the PFC on the standby virtual switch supervisor engine performs central forwarding lookups for all traffic that ingresses the standby virtual switch. The first step in creating a VSS is to define a new logical entity called the virtual switch domain, which represents both switches as a single unit. Because switches can belong to one or more switch virtual domains, a unique number must be used to define each switch virtual domain, as Example 3-3 demonstrates. Example 3-3 VSS Virtual Domain Configuration VSS-sw1(config)#switch virtual domain 100 Domain ID 100 config will take effect only after the exec command `switch convert mode virtual' is issued VSS-sw1(config-vs-domain)#switch 1 Note A corresponding set of commands must be configured on the second switch, with the difference being that switch 1 becomes switch 2. However, the switch virtual domain number must be identical (in this example, 100). Additionally, to bond the two chassis together into a single, logical node, special signaling and control information must be exchanged between the two chassis in a timely manner. To facilitate this information exchange, a special link is needed to transfer both data and control traffic between the peer chassis. This link is referred to as the virtual switch link (VSL). The VSL, formed as an EtherChannel interface, can comprise links ranging from one to eight physical member ports, as shown by Example 3-4. 3-18 Medianet Reference Guide OL-22201-01
Chapter 3 Medianet Availability Design Considerations Network Availability Technologies Example 3-4 VSL Configuration and VSS Conversion VSS-sw1(config)#interface port-channel 1 VSS-sw1(config-if)#switch virtual link 1 VSS-sw1(config-if)#no shut VSS-sw1(config-if)#exit VSS-sw1(config)#interface range tenGigabitEthernet 5/4 - 5 VSS-sw1(config-if-range)#channel-group 1 mode on VSS-sw1(config-if-range)#no shut VSS-sw1(config-if-range)#exit VSS-sw1(config)#exit VSS-sw1#switch convert mode virtual This command converts all interface names to naming convention interface-type switch-number/slot/port, saves the running configuration to the startup configuration, and reloads the switch. Do you want to proceed? [yes/no]: yes Converting interface names Building configuration... [OK] Saving converted configurations to bootflash ... [OK] Note As previously discussed, a corresponding set of commands must be configured on the second switch, with the difference being that switch virtual link 1 becomes switch virtual link 2. Additionally, port-channel 1 becomes port-channel 2. VSL links carry two types of traffic: the VSS control traffic and normal data traffic. Figure 3-15 illustrates the virtual switch domain and the VSL. Figure 3-15 Virtual Switch Domain and Virtual Switch Link Virtual Switch Domain Virtual Switch Link Virtual Switch Active Active Control Plane Active Data Plane Virtual Switch Standby Hot-Standby Control Plane Active Data Plane 228676 Furthermore, VSS allows for an additional addition to EtherChannel technology: multi-chassis EtherChannel (MEC). Before VSS, EtherChannels were restricted to reside within the same physical switch. However, in a VSS environment, the two physical switches form a single logical network entity, and therefore EtherChannels can be extended across the two physical chassis, forming an MEC. Thus, MEC allows for an EtherChannel bundle to be created across two separate physical chassis (although these two physical chassis are operating as a single, logical entity), as shown in Figure 3-16. OL-22201-01 Medianet Reference Guide 3-19
Page 1 and 2:
Medianet Reference Guide Last Updat
Page 3:
About the Authors Solution Authors
Page 6 and 7:
Contents Application Intelligence a
Page 8 and 9:
Contents The Globalization of the W
Page 10 and 11:
Contents NetFlow Collector Consider
Page 12 and 13:
Contents viii Medianet Reference Gu
Page 14 and 15:
Business Drivers for Media Applicat
Page 16 and 17:
Business Drivers for Media Applicat
Page 18 and 19:
Challenges of Medianets Chapter 1 M
Page 20 and 21:
Challenges of Medianets Chapter 1 M
Page 22 and 23:
Solution Chapter 1 Medianet Archite
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43: Solution Chapter 1 Medianet Archite
Page 44 and 45: Solution Chapter 1 Medianet Archite
Page 46 and 47: Conclusions Chapter 1 Medianet Arch
Page 48 and 49: Related Documents Chapter 1 Mediane
Page 50 and 51: Related Documents Chapter 1 Mediane
Page 52 and 53: Measuring Bandwidth Chapter 2 Media
Page 54 and 55: Packet Flow Malleability Chapter 2
Page 56 and 57: Shapers Chapter 2 Medianet Bandwidt
Page 58 and 59: Shapers versus Policers Chapter 2 M
Page 60 and 61: Shapers versus Policers Chapter 2 M
Page 62 and 63: Converged Video Chapter 2 Medianet
Page 64 and 65: Bandwidth Over Subscription Chapter
Page 66 and 67: Capacity Planning Chapter 2 Mediane
Page 68 and 69: Load Balancing Chapter 2 Medianet B
Page 70 and 71: EtherChannel Chapter 2 Medianet Ban
Page 72 and 73: Bandwidth Conservation Chapter 2 Me
Page 74 and 75: Summary Chapter 2 Medianet Bandwidt
Page 76 and 77: Network Availability Chapter 3 Medi
Page 78 and 79: Network Availability Chapter 3 Medi
Page 80 and 81: Device Availability Technologies Ch
Page 82 and 83: Device Availability Technologies Ch
Page 84 and 85: Network Availability Technologies C
Page 104 and 105: Operational Availability Technologi
Page 106 and 107: Summary Chapter 3 Medianet Availabi
Page 108 and 109: Drivers for QoS Design Evolution Ch
Page 122 and 123: Cisco QoS Toolset Chapter 4 Mediane
Page 136 and 137: Enterprise Medianet Strategic QoS R
Page 142 and 143:
Enterprise Medianet Strategic QoS R
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
References Chapter 4 Medianet QoS D
Page 154 and 155:
References Chapter 4 Medianet QoS D
Page 156 and 157:
An Introduction to Securing a Media
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Medianet Security Reference Documen
Page 168 and 169:
Medianet Security Reference Documen
Page 170 and 171:
Network-Embedded Management Functio
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Cisco Network Analysis Module Chapt
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Application-Specific Management Fun
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Summary Chapter 6 Medianet Manageme
Page 252 and 253:
Auto Smartports Chapter 7 Medianet
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Location Services Chapter 7 Mediane
Page 278 and 279:
Summary Chapter 7 Medianet Auto Con
Page 280:
References Chapter 7 Medianet Auto
show all

Medianet Reference Guide - Cisco

Create successful ePaper yourself

Delete template?

Save as template?