External Jumpserver Access

[paul_xtravirt]

So I have a fully deployed VCF9 management stack via Holodeck using default configuration.

I have an external VM called VMA - If I give this VM a secondary nic attached to the same external network as the Holorouter and add a static route (its a windows server) to 10.1.1.0/24 I can now ping ESXi hosts on the 10.1.1.0 network (e.g. 10.1.1.101). However, whatever I do, i cannot get DNS to resolve; e.g. use the holorouter internal DNS server. I have tried adding the 10.1.1.1 address in (as this appears to also be the DNS server) but this doesnt work. Is there any additional configuraton in the holorouter that needs to be done? Has anyone else managed to get this working?

-------------------------------------------

[Dhruv Tyagi]

This is what I've done for my Windows JH to access the nested VCF setup deployed via Holodeck. Assuming you deployed the default CIDR (10.1.0.0/20):

Add a route on your Windows JH to point 10.1.0.0/20 to the Holorouter management IP.

Then I added a secondary eth on my Windows JH and assigned it an IP of 10.1.10.220/25 (could be any unused IP in the Untagged-HoL subnet, you can get a list of subnets by running Get-HoloDeckSubnet -Site a | ft -AutoSize in Holorouter when the config is loaded). I also added the subnet's DNS server 10.1.10.129 as the DNS server on that interface in my Windows JH. 

-------------------------------------------

[paul_xtravirt]

Thanks Druv - that indeed works

-------------------------------------------

[Carlos Rua]

Hi Paul, Dhruv,

I have a left over holoconsole vm from previous holodeck version 5.2. I have added its nic to the internal portgroup that the holorouter v9 is connected to. I assigned a static ip of 10.1.10.220 like Dhruv suggested above. What route add command string did you guys use?

-------------------------------------------

[Dhruv Tyagi]

Hi Carlos,

This is the route command I add from my Windows JH to reach the nested VCF network:

route ADD 10.1.0.0/20 10.160.205.15 -p

Replace 10.160.205.15 with the management IP of holorouter

-------------------------------------------