Implementing VMware Server Virtualization on Juniper Networks ...
Implementing VMware Server Virtualization on Juniper Networks ...
Implementing VMware Server Virtualization on Juniper Networks ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IMPLEMENTATION GUIDE - <str<strong>on</strong>g>Implementing</str<strong>on</strong>g> <str<strong>on</strong>g>VMware</str<strong>on</strong>g> <str<strong>on</strong>g>Server</str<strong>on</strong>g> <str<strong>on</strong>g>Virtualizati<strong>on</strong></str<strong>on</strong>g> <strong>on</strong> <strong>Juniper</strong> <strong>Networks</strong> Infrastructure<br />
Data Center Access Layer and Core Layer C<strong>on</strong>necti<strong>on</strong> Recommendati<strong>on</strong>s<br />
As an example, Figure 15 illustrates the c<strong>on</strong>necti<strong>on</strong> principles for c<strong>on</strong>necting an EX4200 Virtual Chassis c<strong>on</strong>figurati<strong>on</strong> to an<br />
EX8200 switch or MX960 router. The EX8200/MX960 c<strong>on</strong>nects to two Virtual Chassis clusters with the EX8200/MX960<br />
acting as the hub between the two Virtual Chassis c<strong>on</strong>figurati<strong>on</strong>s. If communicati<strong>on</strong> is required between the two Virtual<br />
Chassis c<strong>on</strong>figurati<strong>on</strong>s, then the traffic will traverse the EX8200/MX960.<br />
MX960 (or EX8200)<br />
irb.71: 172.16.56.2<br />
irb.72: 172.16.57.2<br />
irb.73: 172.16.58.2<br />
irb.71: 172.16.56.3<br />
irb.72: 172.16.57.3<br />
irb.73: 172.16.58.3<br />
MX960 (or EX8200)<br />
Iperf Client<br />
172.16.59.5<br />
Vlan71, 72, 73<br />
ge-0/0/5<br />
xe-10/0/0<br />
xe-10/1/0<br />
VIP:<br />
172.16.56.1<br />
172.16.57.1<br />
172.16.58.1<br />
xe-10/0/0<br />
ge-0/0/5<br />
xe-10/1/0<br />
Vlan71: 172.16.56.0/24<br />
Vlan72: 172.16.57.0/24<br />
Vlan73: 172.16.58.0/24<br />
Vlan71: 172.16.56.0/24<br />
Vlan72: 172.16.57.0/24<br />
Vlan73: 172.16.58.0/24<br />
EX4200-C<br />
192.168.6.90<br />
xe-0/1/0<br />
EX4200-D<br />
192.168.6.91<br />
xe-0/1/0<br />
EX4200-E<br />
192.168.6.92<br />
EX4200-F<br />
192.168.6.93<br />
Virtual Chassis<br />
Virtual Chassis<br />
ge-0/0/12<br />
ge-0/0/1<br />
ge-0/0/12<br />
ge-0/0/1 ge-0/0/12 ge-0/0/12<br />
Vlan71, 72, 73<br />
Vlan73<br />
Vlan73<br />
Vlan71, 72, 73 Vlan71, 72, 73<br />
E4<br />
E2<br />
E3<br />
E3<br />
E2<br />
E4<br />
Vlan71: 172.16.56.5<br />
Vlan72: 172.16.57.5<br />
Vlan71: 172.16.56.6<br />
Vlan72: 172.16.57.6<br />
VM<str<strong>on</strong>g>Server</str<strong>on</strong>g>-J<br />
OBM: 190.168.3.60<br />
VMoti<strong>on</strong>: 172.16.58.60<br />
VM<str<strong>on</strong>g>Server</str<strong>on</strong>g>-K<br />
OBM: 192.168.3.61<br />
VMoti<strong>on</strong>: 172.16.58.61<br />
Payload: VLAN 71, VLAN 72<br />
VMoti<strong>on</strong>: VLAN 73<br />
Client: VLAN 75<br />
EX Series switch mgmt: 192.168.6.0/24<br />
<str<strong>on</strong>g>VMware</str<strong>on</strong>g> server mgmt: 192.168.3.0/24<br />
Figure 15: C<strong>on</strong>necting <str<strong>on</strong>g>VMware</str<strong>on</strong>g> ESX server to access and core layer<br />
The following bulleted list represents the VLAN and IP addresses that <strong>Juniper</strong> <strong>Networks</strong> deployed in the soluti<strong>on</strong>s engineering<br />
lab, represented in Figure 15.<br />
• Virtual Machine Traffic: VLAN 71, VLAN 72 (Virtual Switch Tagging)<br />
• VMoti<strong>on</strong> Traffic: VLAN 73 (EX Series Switch Tagging)<br />
• Iperf Client: VLAN 75<br />
• <str<strong>on</strong>g>VMware</str<strong>on</strong>g> ESX server management network: 192.168.3.0/24<br />
• EX4200 switch management network: 192.168.6.0/24<br />
16 Copyright © 2009, <strong>Juniper</strong> <strong>Networks</strong>, Inc.
Change language