noted is that this offering is basic and has limited redundancy that relies on port aggregation and trunk failover.
7.6.1 Layer 2 configuration with 802.1Q tagging and trunk failover
Figure 7-3 illustrates the first basic Layer 2 topology.
|
|
|
|
| 9.0.0.0 |
|
|
|
|
|
|
|
|
|
| G0/24 |
| G0/24 |
|
|
|
| |
Cisco 3560G |
| G0/23 | G0/23 | Cisco 3560G | |||||||
|
| Core 1 |
|
|
|
| Core 2 |
|
| ||
| G0/1 |
| G0/2 | Port Channel |
|
| G0/1 |
| G0/2 | Port Channel | |
|
|
| VLAN10, 20, 99 |
|
|
|
| VLAN10, 20, 99 | |||
| Ext1 |
| Ext2 | Trunk |
|
|
| Ext1 |
| Ext2 | Trunk |
10.99.0.243 | GbESM_1 |
|
|
|
| GbESM_2 | 10.99.0. 244 | ||||
|
|
|
|
| Int4 |
| Int1 |
|
|
|
|
|
| Int1 | Int2 | Int3 |
| Int2 | Int3 | Int4 |
|
| |
|
|
|
|
|
| ||||||
M |
|
|
|
|
|
|
|
|
|
|
|
M |
|
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
|
|
Management |
|
|
|
|
|
|
|
|
|
|
|
Network | 1 | 2 |
| 1 | 2 | 1 | 2 | 1 | 2 |
| |
|
|
| |||||||||
M | Team |
| Team |
|
|
|
|
|
| ||
M |
|
|
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
|
|
| Blade |
| Blade | Blade | Blade |
|
| ||||
| Server |
| Server | Server | Server |
| |||||
Management |
| 1 |
|
| 2 |
| 3 |
| 4 |
|
|
10.20.0.1 | 10.10.0.2 | 10.10.0.3 | 10.99.0.4 |
| |||||||
Workstation |
| ||||||||||
|
|
|
| 10.20.0.2 | 10.20.0.3 |
|
| BladeCenter | |||
|
|
|
|
|
|
|
|
|
| ||
| Links between Management Modules and GbESMs not shown |
|
Figure 7-3 Basic Layer 2 topology with 802.1Q tagging and trunk failover
70Nortel Networks L2/3 Ethernet Switch Module for IBM Eserver BladeCenter