-
- Novice
- Posts: 5
- Liked: never
- Joined: Aug 17, 2016 8:34 am
- Contact:
Help on Virtual Lab configuration, thanks.
Hi, all
I have this VL set up,
Lab name:Virtual Lab 1
ESX name:192.168.210.36
Datastore:SATA Datastore 1
Appliance:
Name:Virtual_Lab_1
Pool name:Virtual Lab 1
Production network name:VM Network
IP: 192.168.210.220
Subnet mask: 255.255.255.0
Default gateway: 192.168.210.1
DNS:
Preferred:192.168.210.94
Alternate:...
Network configuration type:advanced single-host
Network options:
Isolated network: Virtual Lab 1 VM Network
Masquerade IP: 192.168.211.0
Appliance IP: 192.168.210.1
DHCP: enabled
Network mapping:
VM Network --> Virtual Lab 1 VM Network
Static mapping:
192.168.210.230 --> 192.168.210.226
but I can not ping the server inside the VL from production network using 192.168.211.xxx or static IP 210.226.
anything wrong?
I have this VL set up,
Lab name:Virtual Lab 1
ESX name:192.168.210.36
Datastore:SATA Datastore 1
Appliance:
Name:Virtual_Lab_1
Pool name:Virtual Lab 1
Production network name:VM Network
IP: 192.168.210.220
Subnet mask: 255.255.255.0
Default gateway: 192.168.210.1
DNS:
Preferred:192.168.210.94
Alternate:...
Network configuration type:advanced single-host
Network options:
Isolated network: Virtual Lab 1 VM Network
Masquerade IP: 192.168.211.0
Appliance IP: 192.168.210.1
DHCP: enabled
Network mapping:
VM Network --> Virtual Lab 1 VM Network
Static mapping:
192.168.210.230 --> 192.168.210.226
but I can not ping the server inside the VL from production network using 192.168.211.xxx or static IP 210.226.
anything wrong?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Is there any firewall enabled inside the guest (for example, Windows firewall could block pings from public networks)?
-
- Novice
- Posts: 5
- Liked: never
- Joined: Aug 17, 2016 8:34 am
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Thanks, I have turn off all the firewalls.
Now I am able to ping through the static mapping (192.168.210.230 --> 192.168.210.226)
But still can not ping through 192.168.211.230.
Now I am able to ping through the static mapping (192.168.210.230 --> 192.168.210.226)
But still can not ping through 192.168.211.230.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Aug 17, 2016 8:34 am
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Can anyone help? Thanks.
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Are you pinging from the Veeam B&R server? By default, routing rules are added on the backup server only, if you want to be able to reach them from other machines in production network, you need to configure routing for that.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Aug 17, 2016 8:34 am
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Yes, I am pinging from the Veeam B&R server, but still failed.
Also, can explain how to "configure routing"?
Also, can explain how to "configure routing"?
-
- Novice
- Posts: 5
- Liked: never
- Joined: Aug 17, 2016 8:34 am
- Contact:
Re: Help on Virtual Lab configuration, thanks.
Does it matter if the observed range of the VM network adapter is from 192.168.210.1 - 192.168.210.254?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Help on Virtual Lab configuration, thanks.
You need to ensure that masquerade addresses are routed to the appliance (since only appliance knows where to forward these requests further in the isolated network).
Who is online
Users browsing this forum: Amazon [Bot] and 16 guests