Hello - I'm trying to install Proxmox on a UCSC-C220 chassis (vSphere replacement). I was able to install the ISO image and it boots properly - showing me the ip to access the web gui. The issue I'm having is with the ethernet port. I can't seem to ping anything - even via a direct connection. The ethernet port is up and I've tried using all of the ports but no luck. Not sure if anyone else has installed on a UCSC-C220 and has seen the same issue. Thanks in advance...B
Can you login to the Proxmox host console and show (using a readable photo) the output of
ip a and cat /etc/network/interfaces?
can you ping the gateway (10.10.19.1)?
IF YES- can you ping inbound from wherever you're trying to use for webui?
IF YES- please post output of
systemctl status pveproxy
systemctl status pvestatd
/etc/hosts
IF NO for either of the above, you're still experiencing network issues that need to be resolved.
IF YES- can you ping inbound from wherever you're trying to use for webui?
IF YES- please post output of
systemctl status pveproxy
systemctl status pvestatd
/etc/hosts
IF NO for either of the above, you're still experiencing network issues that need to be resolved.
Hmm, why the
Are you sure that ens1f0 is not the IPMI interface, otherwise use one of the other network device shows by
Is your gateway/router at 10.10.19.1? Is the static addres 10.10.19.77 outside the DHCP range of the router?
What is the output of
auto ens1f0? The virtual bridge will bring up the bridge-ports automatically.Are you sure that ens1f0 is not the IPMI interface, otherwise use one of the other network device shows by
ip a.Is your gateway/router at 10.10.19.1? Is the static addres 10.10.19.77 outside the DHCP range of the router?
What is the output of
ping -w3 10.10.19.1 and ping -w3 1.1.1.1/ICODE]?
Sounds like a router issue. Are you sure the static IP 10.10.19.77 is outside of the DHCP range of the router? Otherwise, please choose an IP address outside of the DHCP range.
EDIT:
Okay, never mind then. Apologies for suggesting any routing issue or overlap with the DHCP range.
Last edited:
Those two things are in conflict. you MOST DEFINATELY have a networking issue, albeit maybe not routing specific. This is not specific to your hardware.
Most likely, either you are attempting to map a port that isnt plugged in, or using an out-of-subnet address as @leesteken was explaining.
Assuming there is an ethernet cable connected to an ethernet port on the back of your chassis that ISNT the BMC dedicated port, and that in turn is connected to your router that is serving dhcp:
type dhclient
note what port(s) (if any) now have an ip address. thats what you should be using for your bridge.