Hey guys.
I have seperated my service console in a vlan wich i can not access. Therefore i have set up a vmware infrastructure server with 2 nics, nice 1 on vlan 50, nic 2 on default vlan. Whenevery i need to change something in my enviorement i access the infrastructure server to nic 2, and then nic 1 have the access to the servers. BUT i have one problem, whenever i want to see the colsone in the servers, it seems as my vmware client tries to connect directly the the servvice console on the host, and that is on the net witch i do not have access to.
Is there any way to connect to the console via the infrastructure server ?
(here is the setup)
Infrastructure server. Nic 1 (vlan 50) 192.168.5.1 / Nic 2 (default vlan 0) 192.168.0.230 <- this is the net my pc is directly connected to. but when i want to see console my vsphere client fails and says it can not connect to ex. 192.168.5.20 (vsphere esx host. Can i bypass this someway ?
The console connection is a direct connection from the vSphere client to the SC over port 903.
With your configuration, you have two options to access the VM's consoles.
1.) Connect to the vCenter Server via RDP and run the vSphere Client on the server.
2.) Connect to the VMs using RDP, VNC or any other protocol.
André
currently i am connectiong to my infrastructure server via rdp, but i was hoping for a fix that could make the the infrastructure server show the console to me without connectiong via rdp...
You might be able to connect directly from the client to the service console if you:
enable routing in the network configuration of the infrastructure server
Add a route the 192.168.5.0 network on the client that uses 192.168.0.230 as a gateway:
route ADD 192.168.5.0 MASK 255.255.255.0 192.168.0.230 -p
Regards, Robert
Maybe this is a dumb question. How do i enable routing on the infrastructure server ? (server 2008)
The route i should add, is that on the infrastructure server, or on the esx hosts ?
You can enable routing on the infrastructure server with the "Routing and Remote Access" snap-in of mmc.exe:
Start
Run...
mmc
File
Add/Remove Snap-in...
Select "Routing and Remote Access"
Add >
OK
Select "Routing and Remote Access"
Action
Add Server
This Computer
OK
Select your computer
Action
Configure and Enaqble Routing and Remote Access
Next
Secure connection between two private networks
No
Next
Finish
Maybe you have to do more. But I don't have a server with nic's in two different subnets. So I'm not able to test this.
The route was intended to be added to your client computer. So not to the infrastructure server and not to the ESX hosts. You might have to add a route to the ESX servers also. They must of course go the other way round. Unix uses a slightly different syntax:
route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.5.1
Regards, Robert
Do you have access to the physical router? U can always make these changes there as well.