Forum Discussion
Puli
Nimbostratus
NimbostratusCannot connect to BigIP set up UI.
Hi,
i've installed vmware workstation 30 day trian.
Opened and powered on BigIP LT VE vm.
ran b mgmt. It give me ip address 192.168.1.245. Accepted the default, get ip from DHCP.
I try https://192.168.1.245 but cannot connect.
ipconfig from the host.
-------------------------------------------
Windows IP Configuration Host Name . . . . . . . . . . . . : jmeter02
Primary Dns Suffix . . . . . . . : abc.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : abc.com
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No IP
Address. . . . . . . . . . . . : 192.168.80.1 S
ubnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.202.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : Ethernet adapter Local Area Connection: Connection-specific
DNS Suffix . : abc.com Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont roller
Physical Address. . . . . . . . . : 00-13-72-6F-C6-36 Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 139.185.72.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 139.185.72.1
Can somebody please help.
Appreciate any solutions.
qe_102628
Overall, it sounds like the network that the VE-Trial's Managment Port exists on isn't mapped to the networks that you're using.
1) First, DHCP. If the VE-trial is getting a 192.168.1.245 address, that means it's not getting a valid DHCP response from it's DHCP queries. So, either the DHCP server isn't functioning or the network interface for the management port of the VE-Trial isn't mapped to the appropriate network.
2) None of your Adapters are showing a 192.168.1.x address. VMnet8 is 192.168.80.0/24, VMnet1 is 192.168.202.0/24, Ethernet (bridged) is showing 129.185.72.0/23. This is the technical reason as to why you can't reach 192.168.1.245 from your workstation - the addressing doesn't line up.
3) You can setup the management port's IP address by using the config script (after you're logged into the VE-Trial's Console as root, run "config")
Alternatively, you can use these commands for TMSH:
tmsh create sys management-ip x.x.x.x/y
tmsh modify sys global-settings mgmt-dhcp disabled
tmsh create sys management-route default gateway z.z.z.z
tmsh save / sys config
WHERE:
x.x.x.x is the IP that you want to set the management port to
y is the subnet mask size in significant bits - some might call this the CIDR size. /24, etc.
z.z.z.z is the IP of the gateway - it probably resembles x.x.x.x
so, in example form for a VE-Trial with a bridged interface for the management network:
(Where, in theory, one would ping 139.185.72.172 before setting it, so as to make sure that that address is free before use - in addition to doing the usual checks through any IP subscription databases or spreadsheets)
tmsh create sys management-ip 139.185.72.172/23
tmsh modify sys global-settings mgmt-dhcp disabled
tmsh create sys management-route default gateway 139.185.72.1
tmsh save / sys config
I hope that works for ya!