-
- Novice
- Posts: 7
- Liked: 1 time
- Joined: May 30, 2016 5:29 am
- Full Name: Matthias Lang
- Contact:
Virtual Lab Network doesn´t work after upgrade to V10
Hello All,
After the upgrade to V10 i have an problem in Virtual LAB.
Configuration:
VMware Test: vCenter Server 6.7 Update 3b Build 15132721 (Appliance)
VMware Prod: vCenter Server Appliance 6.7 Update 26.7.0.30000 Built 13010631 (Appliance)
Veeam: V10
VLAB: Advanced single-host
Problem:
After the upgrade to V10 the network in my VLAB is not working properly. If I start the Surebackup Job the VLAB Appliance will start without problems and it is pingable after starting.
The VM in the SurebackupJob is also started without problems but the problem is, that I cannot ping the Gateway in the VM and also I cannot ping the VM (the masquerade ip) from the backup server.
The route print on the Backupserver shows me, that the routes were set correctly
10.255.255.224 255.255.255.224 10.2.5.101 10.2.5.99 6
192.1.0.0 255.255.0.0 10.2.5.101 10.2.5.99 6
192.255.3.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.4.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.5.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.6.0 255.255.255.0 10.2.5.101 10.2.5.99 6
Ping doesn´t work:
Pinging 192.255.6.1 with 32 bytes of data:
Reply from 192.255.6.1: Destination host unreachable.
In the Logfile - ViLab.xxxxx_Virtual_Lab_Test.Deployment.log – I can see the following entries which looks suspicious:
Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:48] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:48] <01> Info [SureBackup] =========================================================================================================================================
[22.04.2020 14:34:48] <01> Info [SureBackup] | VM | VM IP | Real IP | Device ID | Power State | VM State | Tools Status | Version Status | Heartbeat |
[22.04.2020 14:34:48] <01> Info [SureBackup] =========================================================================================================================================
[22.04.2020 14:34:48] <01> Info [SureBackup] | xx-VLAB-xx | ???.???.???.??? | ???.???.???.??? | 0 | PowerOn | NotRunning | NotInstalled | NotInstalled | Gray |
[22.04.2020 14:34:53] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:58] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:03] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:08] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:14] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:19] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:19] <01> Info [SureBackup] | XX-VLAB-XX | 10.2.5.101 | 10.2.5.101 | 0 | PowerOn | Running | Ok | Unmanaged | Gray |
[22.04.2020 14:35:24] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
I have now configured an second Virtual Lab with the same Configuration as the one which is not working but it is deployed in our productive vCenter which is running an older Version of vCenter.
The VLAB Appliance and VM starts normal and also the routes on the Backupserver were set correct.
10.255.255.224 255.255.255.224 10.2.5.102 10.2.5.99 6
192.1.0.0 255.255.0.0 10.2.5.102 10.2.5.99 6
192.255.3.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.4.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.5.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.6.0 255.255.255.0 10.2.5.102 10.2.5.99 6
In the Logfile - ViLab.xxxxx_Virtual_Lab_Test.Deployment.log – I can´t see the warnings with the API version and network is working.
The ping on both servers (VM in VLAB and Backupserver) are working.
Ping from Backupserver to VM in VLAB:
Pinging 192.255.6.1 with 32 bytes of data:
Reply from 192.255.6.1: bytes=32 time<1ms TTL=127
Reply from 192.255.6.1: bytes=32 time<1ms TTL=127
Did anyone here in the forum has the same troubles?
I also opend already an case - #04142974 - maybe they can find something..
Best Regards
Matthias
After the upgrade to V10 i have an problem in Virtual LAB.
Configuration:
VMware Test: vCenter Server 6.7 Update 3b Build 15132721 (Appliance)
VMware Prod: vCenter Server Appliance 6.7 Update 26.7.0.30000 Built 13010631 (Appliance)
Veeam: V10
VLAB: Advanced single-host
Problem:
After the upgrade to V10 the network in my VLAB is not working properly. If I start the Surebackup Job the VLAB Appliance will start without problems and it is pingable after starting.
The VM in the SurebackupJob is also started without problems but the problem is, that I cannot ping the Gateway in the VM and also I cannot ping the VM (the masquerade ip) from the backup server.
The route print on the Backupserver shows me, that the routes were set correctly
10.255.255.224 255.255.255.224 10.2.5.101 10.2.5.99 6
192.1.0.0 255.255.0.0 10.2.5.101 10.2.5.99 6
192.255.3.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.4.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.5.0 255.255.255.0 10.2.5.101 10.2.5.99 6
192.255.6.0 255.255.255.0 10.2.5.101 10.2.5.99 6
Ping doesn´t work:
Pinging 192.255.6.1 with 32 bytes of data:
Reply from 192.255.6.1: Destination host unreachable.
In the Logfile - ViLab.xxxxx_Virtual_Lab_Test.Deployment.log – I can see the following entries which looks suspicious:
Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:48] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:48] <01> Info [SureBackup] =========================================================================================================================================
[22.04.2020 14:34:48] <01> Info [SureBackup] | VM | VM IP | Real IP | Device ID | Power State | VM State | Tools Status | Version Status | Heartbeat |
[22.04.2020 14:34:48] <01> Info [SureBackup] =========================================================================================================================================
[22.04.2020 14:34:48] <01> Info [SureBackup] | xx-VLAB-xx | ???.???.???.??? | ???.???.???.??? | 0 | PowerOn | NotRunning | NotInstalled | NotInstalled | Gray |
[22.04.2020 14:34:53] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:34:58] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:03] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:08] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:14] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:19] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
[22.04.2020 14:35:19] <01> Info [SureBackup] | XX-VLAB-XX | 10.2.5.101 | 10.2.5.101 | 0 | PowerOn | Running | Ok | Unmanaged | Gray |
[22.04.2020 14:35:24] <01> Warning [TryOverrideApiVersion] The native API version [6.7.3] was changed to [6.7.2] for VC [vc-xxx.xxx.com]
I have now configured an second Virtual Lab with the same Configuration as the one which is not working but it is deployed in our productive vCenter which is running an older Version of vCenter.
The VLAB Appliance and VM starts normal and also the routes on the Backupserver were set correct.
10.255.255.224 255.255.255.224 10.2.5.102 10.2.5.99 6
192.1.0.0 255.255.0.0 10.2.5.102 10.2.5.99 6
192.255.3.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.4.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.5.0 255.255.255.0 10.2.5.102 10.2.5.99 6
192.255.6.0 255.255.255.0 10.2.5.102 10.2.5.99 6
In the Logfile - ViLab.xxxxx_Virtual_Lab_Test.Deployment.log – I can´t see the warnings with the API version and network is working.
The ping on both servers (VM in VLAB and Backupserver) are working.
Ping from Backupserver to VM in VLAB:
Pinging 192.255.6.1 with 32 bytes of data:
Reply from 192.255.6.1: bytes=32 time<1ms TTL=127
Reply from 192.255.6.1: bytes=32 time<1ms TTL=127
Did anyone here in the forum has the same troubles?
I also opend already an case - #04142974 - maybe they can find something..
Best Regards
Matthias
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 29, 2020 9:43 pm
- Full Name: victor pereira santiago
- Contact:
Re: Virtual Lab Network doesn´t work after upgrade to V10
Same problem here. i´m opening a case.
-
- Product Manager
- Posts: 14839
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Virtual Lab Network doesn´t work after upgrade to V10
Hello,
@victorpsantiago: could you please post your case number? Then we can try to find whether it is the same issue.
As I upgraded my 9.5U4 lab yesterday... there was a warning during upgrade to click through the Virtual Lab wizard again to update the virtual lab appliance... did you both do that?
Best regards,
Hannes
@victorpsantiago: could you please post your case number? Then we can try to find whether it is the same issue.
As I upgraded my 9.5U4 lab yesterday... there was a warning during upgrade to click through the Virtual Lab wizard again to update the virtual lab appliance... did you both do that?
Best regards,
Hannes
-
- Novice
- Posts: 7
- Liked: 1 time
- Joined: May 30, 2016 5:29 am
- Full Name: Matthias Lang
- Contact:
Re: Virtual Lab Network doesn´t work after upgrade to V10
Hi Hannes
I clicked through the Virtaul Lab wizard -> not working; i also deleted the vlab and re-deploy it with the same config but i have the same behaviour.
Best Regards
Matthias
I clicked through the Virtaul Lab wizard -> not working; i also deleted the vlab and re-deploy it with the same config but i have the same behaviour.
Best Regards
Matthias
-
- Product Manager
- Posts: 14839
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Virtual Lab Network doesn´t work after upgrade to V10
Hello Matthias,
I contacted support because the VMware tools version they are currently investigating makes no sense to me.
Also I cannot reproduce it in my lab. Ping with working and SureBackup is running fine for me. I also run VCenter 15132721 which I upgraded some weeks ago from an earlier version (don't remember).
Best regards,
Hannes
I contacted support because the VMware tools version they are currently investigating makes no sense to me.
Also I cannot reproduce it in my lab. Ping with working and SureBackup is running fine for me. I also run VCenter 15132721 which I upgraded some weeks ago from an earlier version (don't remember).
Best regards,
Hannes
-
- Novice
- Posts: 7
- Liked: 1 time
- Joined: May 30, 2016 5:29 am
- Full Name: Matthias Lang
- Contact:
Re: Virtual Lab Network doesn´t work after upgrade to V10
Hi Hannes,
Today i´ve updated my productive vCenter to 15132721 and now I´ve the same behaviour.
I already talked to support and we will have an remote session to check the config,..
I will keep you informed if we can solve this.
Best Regards
Matthias
Today i´ve updated my productive vCenter to 15132721 and now I´ve the same behaviour.
I already talked to support and we will have an remote session to check the config,..
I will keep you informed if we can solve this.
Best Regards
Matthias
Who is online
Users browsing this forum: AlexLeadingEdge, Bing [Bot], tyler.jurgens and 306 guests