Environment:vcenter 6.0;Web client; Lenovo Flex System Enterprise Chassis blade server;
Login Blade Server Remote Control interface, login ESXi to view the connection status of the physical NIC ,
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/E0/wKiom1cwVJ6Dlhy6AABLrO2WqcY849.png "title=" Image001.png "alt=" Wkiom1cwvj6dlhy6aablro2wqcy849.png "/>
Figure 1
1, Lenovo Blade Server, Blade of the physical network card with the blade switch internal connection relationship
The Blade switch has 2 put, the first 1 The port of the blade switch is as follows:
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7F/DD/wKioL1cwVffCEGuuAABMIYgPD9M252.png "title=" Image003.png "alt=" Wkiol1cwvffceguuaabmiygpd9m252.png "/>
Figure 2
Note: This Lenovo knife frame can be inserted into the insert , each blade on the 4 physical network card, the normal correspondence is:
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/E0/wKiom1cwVnKjzbN3AAD8lVFoYqs855.jpg "title=" Image030.jpg "alt=" Wkiom1cwvnkjzbn3aad8lvfoyqs855.jpg "/>
Figure 3
As can be seen from the above Figure 2 and Figure 3 , this cutter frame is connected to a total of ten blades and started, because the switch a1-a10,b1-b10 is in the UP State;
But during the actual operation, Mac mac for the first 1 Insert the blade of section 1 physical NIC) is through Intb1 port learned, description section 1 Inb1 port, as shown in Figure 3 Inta1 Port learned to
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/7F/E0/wKiom1cwVr_jsHC7AAAWp0CYdCY963.png "title=" Image005.png "alt=" Wkiom1cwvr_jshc7aaawp0cydcy963.png "/>
Figure 4
to verify the true internal port connection, shutdown the switch1 INA1 Port , and the Vmnic2 in Figure 1 shows Dis connnected", confirms a1-vmnic2,b1-vmnic0(this kind of connection does not conform to the normal logic, Inconsistent with Fujitsu and Dell Blade servers)
3, Blade 1 on the creation of virtual machine,Centos-zabbix, select a network, add a NIC,5 network adapter 2, of course, you can also use the network adapter 1 (There are other effects, do not introduce here), remember the Mac address of network adapter 2
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/7F/DD/wKioL1cwV8ayJ-dfAABtj6v7COE732.png "title=" Image007.png "alt=" Wkiol1cwv8ayj-dfaabtj6v7coe732.png "/>
Figure 5
4.log in to the console of the virtual machine, modify the address, confirm the Mac address for the added network adapter 2
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7F/E0/wKiom1cwVyDQsISIAAAUy_P8xss636.jpg "title=" Image010.jpg "alt=" Wkiom1cwvydqsisiaaauy_p8xss636.jpg "/>
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/7F/E0/wKiom1cwVzPyIYvVAAA38XucH5c125.png "title=" Image011.png "alt=" Wkiom1cwvzpyiyvvaaa38xuch5c125.png "/>
Figure 6
6 , create a virtual switch on the host, see Figure 9 (Choose here Vmnic2 , not because it was created), the port group is created after the creation is complete VM Network2
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/7F/DD/wKioL1cwWGLR2AwGAACRKYlxJSM276.png "style=" float: none; "title=" Image013.png "alt=" Wkiol1cwwglr2awgaacrkylxjsm276.png "/>
Figure 7
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/7F/E0/wKiom1cwV4bi7fbyAAB438MlYaA634.png "style=" float: none; "title=" Image015.png "alt=" Wkiom1cwv4bi7fbyaab438mlyaa634.png "/>
Figure 8
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/7F/E0/wKiom1cwV4bjgvzfAACSxC6gNi4020.png "style=" float: none; "title=" Image017.png "alt=" Wkiom1cwv4bjgvzfaacsxc6gni4020.png "/>
Figure 9
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/E0/wKiom1cwXA-BZA41AAAjYKIYJrM129.jpg "title=" Image020.jpg "alt=" Wkiom1cwxa-bza41aaajykiyjrm129.jpg "/>
Figure 10
7 , assign this virtual switch vlan18 , and point the NIC for this virtual machine to VM Network2 Port Group
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/7F/E0/wKiom1cwV_Hig6FwAACF1u1aE7Q714.png "title=" Image021.png "alt=" Wkiom1cwv_hig6fwaacf1u1ae7q714.png "/>
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7F/DD/wKioL1cwWPTiX5CvAAAx72TZ7HU291.png "title=" Image023.png "alt=" Wkiol1cwwptix5cvaaax72tz7hu291.png "/>
8, the 1 Blade switch is configured as follows (only the first switch is used)
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/E0/wKiom1cwWEGR02LOAAAYINRm3N4121.png "style=" float: none; "title=" Image027.png "alt=" Wkiom1cwwegr02loaaayinrm3n4121.png "/>
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7F/DD/wKioL1cwWR7gHSasAAAF5p593p4212.png "style=" float: none; "title=" Image025.png "alt=" Wkiol1cwwr7ghsasaaaf5p593p4212.png "/>
9, the overall communication process is as follows:
virtual machine NIC (Network adapter2)----virtual switches such as (VM NETWORK2Port Group,Vlan18, you must configure it hereVlan18, in Dell and Fujitsu do not need configuration, because what is unclear)----Virtual Switch out (the blade3block physical NIC,Vmnic2)---Blade Switch (INA1Ports,Vlan18)---Blade Switch (EXT1Port)----Other physical switches
Note: In this example, the redundant link is not used in the blade switch out port, only the EXT1.
Web client6.0 setting Blade server virtual Machine Network