Huawei ensp works with Wmware virtual machine Openstack platform to implement Vlan network mode

Huawei ensp cooperates with Wmware virtual machine Openstack platform to realize external Vlan network mode (solution)

Reserve of theoretical knowledge
https://blog.csdn.net/u013201439/article/details/51491746
https://blog.csdn.net/weixin_34208185/article/details/93725119
https://blog.csdn.net/tjcwt2011/article /details/78659242
https://blog.csdn.net/qq_42796807/article/details/103367120

Here, the vlan mode is implemented in the virtual machine openstack, and it is eager to realize the solution of the communication between the cloud virtual machine generated by the openstack platform and the (wmware virtual machine) and the physical machine. There may also be an easier way to welcome everyone to communicate.

openstack platform network environment

Insert picture description here

I was lazy when I created it here. I used 1 for the segment ID. Of course, you can define other segment IDs yourself, but the corresponding virtual network card segment ID needs to be changed.
Network type: vlan
physical network: provider
Segment ID: 1
Subnet gateway: 192.168. 200.2 Same as Wmware virtual network card

Insert picture description here
Insert picture description here
Insert picture description here

Note: The next step is very important, which is to turn on the vlan ID of the VMnet8 network card. This is consistent with the vlan segment ID created by the openstack platform. Here I write 1
Insert picture description here

Platform routing

Insert picture description here
Insert picture description here

Create a cloud host here, the floating ip is 192.168.200.8

Insert picture description here

Virtual machine environment

Here the control node and the computing node are three network cards
ens32 192.168.100.0/24 gateway 192.168.100.1 host only (VMnet1)
ens33 192.168.200.0/24 gateway 192.168.200.2 nat mode (VMnet8)
ens35 192.168.10.0/24 gateway 192.168. 10.1
Description of host only (VMnet2) : Why three network cards are used here, because when ensp is started later, he will preempt ens32 and ens33, causing tools such as CRT to fail to connect to the virtual machine and the cloud through these two (virtual network cards VMnet1, VMnet8) network cards The host, so it depends on the third network card ens35 to achieve.

Insert picture description here

ensp environment

By the way, there can actually be simpler topologies (methods), but I only think of this one at the moment. If you have a simpler method, you can communicate with me.

Insert picture description here

Insert picture description here

Insert picture description here

LSW2 related configuration

vlan batch  10 20 
interface Vlanif1
 ip address 192.168.200.2 255.255.255.0
#
interface Vlanif20
 ip address 192.168.20.20 255.255.255.0
#
interface GigabitEthernet0/0/1
 port link-type access
#
interface GigabitEthernet0/0/2
 port hybrid pvid vlan 20
 port hybrid untagged vlan 10 20
#
ospf 1
 area 0.0.0.0
  network 192.168.200.0 0.0.0.255
  network 192.168.20.0 0.0.0.255
##下面两条可以不加
  network 192.168.100.0 0.0.0.255   
  network 192.168.10.0 0.0.0.255

AR2 related configuration

vlan batch 10 20
#
interface GigabitEthernet0/0/0
 ip address 192.168.20.10 255.255.255.0 
#
interface GigabitEthernet0/0/1
 ip address 192.168.10.20 255.255.255.0 
#
ospf 1 
 area 0.0.0.0 
  network 192.168.10.0 0.0.0.255 
  network 192.168.20.0 0.0.0.255 
  network 192.168.100.0 0.0.0.255 
  network 192.168.200.0 0.0.0.255 

LSW3 related configuration


vlan batch 10 20
#
interface Vlanif1
 ip address 192.168.100.1 255.255.255.0
#
interface Vlanif10
 ip address 192.168.10.10 255.255.255.0
#
interface GigabitEthernet0/0/1
 port link-type access
#
interface GigabitEthernet0/0/2
 port hybrid pvid vlan 10
 port hybrid untagged vlan 10 20
#
ospf 1
 area 0.0.0.0
  network 192.168.100.0 0.0.0.255
  network 192.168.10.0 0.0.0.255
  network 192.168.200.0 0.0.0.255
  network 192.168.20.0 0.0.0.255

Test connectivity

Switch LSW3 can ping VMnet8 network card and openstack platform virtual machine

Insert picture description here
Insert picture description here

Switch LSW2 can ping VMnet1 network card and WMware virtual machine

Insert picture description here
Insert picture description here

Use CRT to connect to the third network card to test

Due to the preemption of the network card, the CRT cannot connect to the openstack cloud virtual machine and the control node of the 192.168.100.0 network segment, so we can use the third network card to enter the cloud virtual machine or control node through ssh. Here we can also see With the help of ensp, our cloud virtual machine can also communicate with control nodes and computing nodes.

Insert picture description here
Insert picture description here

Do some configuration of ansible, you can use ansible normally.

Insert picture description here

related resources

Link: First call ansible to deploy openstack.zip .

Link: Huawei ensp links Wmware virtual machine Openstack platform to realize Vlan network mode topology.zip .

Guess you like

Origin blog.csdn.net/weixin_43663238/article/details/114449811