Cannot ping device on network

[cobrajdm]

Hello,

I am fairly new to Proxmox and have an issue. I am unable to ping a NAS storage device on my network. My network is fairly simple it has a modem, router and switch with one subnet. Every other device on my network can ping and get to my NAS. I use my NAS to backup Proxmox by adding a smb\cifs share in the storag area of Proxmox Datacenter. This use do work and now it don't matter how many times I rebuild proxmox it just don't work. I am using the latest download of Proxmox 8.3. I thought maybe the arp cache had something to do with it but when I run "arp -a' in the shell it says "-bash: arp: command not found". I believe it is something in Proxmox that is confused. Where do I start to verify the correct record is configured in Proxmox, to resolve and ping an IP, using shell? Or is there another terminal and command I have to use to trouble shoot the host?

Under the host all containers and VM's follow suite, they cannot ping or resolve the NAS.
I also tried to create a hosts entry int he hosts for the NAS but still cannot ping the NAS.

 

[gfngfn256]

I assume you cannot ping that NAS device even while using its' numeric IP address so this is not purely a DNS problem.

Can you ping other devices on your NW from the Proxmox host?
Can you ping the NW GW from the Proxmox host?
Can other devices on the NW ping the Proxmox host?
Can the NAS device ping the Proxmox host?

Could you provide output for the following from the Proxmox host:

ip a

cat /etc/hosts

cat /etc/hostname

cat /etc/network/interfaces

Could you also provide if possible the following from the NAS device:

ip a

PLEASE PROVIDE ALL OUTPUT IN CODE-LINE-EDITOR BY CHOOSING THE </> FROM THE FORMATTING BAR & PASTING OUTPUT

when I run "arp -a' in the shell it says "-bash: arp: command not found"

arp is included in net-tools but is not installed by default:

# apt list | grep net-tools

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ddnet-tools/stable 16.4-1.1 amd64
net-tools/stable 2.10-0.1 amd64

You could install it with:

apt-get install net-tools

 

[aabraham]

@cobrajdm I would add to what @gfngfn256 suggested and also check the output of the following command:
ping -Ov 1.1.1.1

 

[cobrajdm]

Ok, long string

Can you ping other devices on your NW from the Proxmox host? Yes
Can you ping the NW GW from the Proxmox host? Yes
Can other devices on the NW ping the Proxmox host? Yes
Can the NAS device ping the Proxmox host? No

Output of ip a on proxmox
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp59s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 54:bf:64:0d:b3:4e brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 94:b8:6d:f3:0a:11 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 54:bf:64:0d:b3:4e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::56bf:64ff:fe0d:b34e/64 scope link
valid_lft forever preferred_lft forever

Output of cat /etc/hosts on proxmox
127.0.0.1 localhost.localdomain localhost
192.168.1.10 cobrajdmproxmox02.local cobrajdmproxmox02

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Output of hostname
cobrajdmproxmox02

Output of cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp59s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.10/24
gateway 192.168.1.1
bridge-ports enp59s0
bridge-stp off
bridge-fd 0

iface wlp0s20f3 inet manual


source /etc/network/interfaces.d/*

Output of ping -Ov 1.1.1.1
ING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ident=31994 ttl=56 time=48.3 ms
64 bytes from 1.1.1.1: icmp_seq=2 ident=31994 ttl=56 time=30.0 ms
64 bytes from 1.1.1.1: icmp_seq=3 ident=31994 ttl=56 time=27.4 ms
64 bytes from 1.1.1.1: icmp_seq=4 ident=31994 ttl=56 time=28.9 ms
64 bytes from 1.1.1.1: icmp_seq=5 ident=31994 ttl=56 time=30.4 ms
64 bytes from 1.1.1.1: icmp_seq=6 ident=31994 ttl=56 time=27.0 ms
64 bytes from 1.1.1.1: icmp_seq=7 ident=31994 ttl=56 time=28.4 ms
64 bytes from 1.1.1.1: icmp_seq=8 ident=31994 ttl=56 time=29.8 ms
64 bytes from 1.1.1.1: icmp_seq=9 ident=31994 ttl=56 time=26.9 ms
64 bytes from 1.1.1.1: icmp_seq=10 ident=31994 ttl=56 time=26.9 ms
64 bytes from 1.1.1.1: icmp_seq=11 ident=31994 ttl=56 time=29.4 ms
64 bytes from 1.1.1.1: icmp_seq=12 ident=31994 ttl=56 time=32.7 ms
64 bytes from 1.1.1.1: icmp_seq=13 ident=31994 ttl=56 time=33.3 ms

I installed net tools and here is the out put of arp -a, the NAS I am trying to ping is 192.168.1.17
? (192.168.1.11) at b4:45:06:cd:14:03 [ether] on vmbr0
? (192.168.1.145) at ea:ce:2e:05:e4:8e [ether] on vmbr0
? (192.168.1.1) at c8:9e:43:bc:25:7d [ether] on vmbr0
? (192.168.1.17) at <incomplete> on vmbr0
? (192.168.1.155) at ce:10:da:0f:3e:02 [ether] on vmbr0
? (192.168.1.15) at 04:d4:c4:55:42:d5 [ether] on vmbr0

After seeing the above I deleted ? (192.168.1.17) at <incomplete> on vmbr0 and added a static entry
I ran this arp -s 192.168.1.17 24:5E:BE:2F:C2:26
Output of the above
? (192.168.1.11) at b4:45:06:cd:14:03 [ether] on vmbr0
? (192.168.1.145) at ea:ce:2e:05:e4:8e [ether] on vmbr0
? (192.168.1.1) at c8:9e:43:bc:25:7d [ether] on vmbr0
? (192.168.1.17) at 24:5e:be:2f:c2:26 [ether] PERM on vmbr0
? (192.168.1.155) at ce:10:da:0f:3e:02 [ether] on vmbr0
? (192.168.1.15) at 04:d4:c4:55:42:d5 [ether] on vmbr0

Still could not ping

I ran arp -a on another device on the same network and the arp comes back good and can ping the NAS

 

[gfngfn256]

Could you please provide output for the following:

cat /etc/pve/storage.cfg

pveversion -v

cat /etc/pve/firewall/cluster.fw

cat /etc/pve/nodes/cobrajdmproxmox02/host.fw

 

[cobrajdm]

Output of cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content backup,iso,vztmpl

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

cifs: ProxmoxSrvBackup
path /mnt/pve/ProxmoxSrvBackup
server 192.168.1.15
share ProxmoxSrvBackup
content backup,iso,images
prune-backups keep-all=1
username Proxmox

Output of pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Output of cat /etc/pve/firewall/cluster.fw
cat: /etc/pve/firewall/cluster.fw: No such file or directory

Output of cat /etc/pve/nodes/cobrajdmproxmox02/host.fw
cat: /etc/pve/nodes/cobrajdmproxmox02/host.fw: No such file or directory

 

[cobrajdm]

Do you know if Proxmox supports talking to a LAG Group as the NAS is trunked into a LAG Group? Everything else on the NW has no issues with it.

 

[cobrajdm]

I would assume since it Proxmox itself supports LAG Groups it would support connecting to a LAG Group.

 

[gfngfn256]

cifs: ProxmoxSrvBackup
    path /mnt/pve/ProxmoxSrvBackup
    server 192.168.1.15
    share ProxmoxSrvBackup
    content backup,iso,images
    prune-backups keep-all=1
    username Proxmox

Is this storage device fully working in Proxmox? Where is this 192.168.1.15 device located?

NAS is trunked into a LAG Group

Most likely the cause, since I can't see anything unusual with the PVE side. Maybe try taking out one of the NIC cables of the NAS ( & wait for the NW stack to adjust). Check it is still pingable from other devices on NW & then check from Proxmox server.

You should probably change something on the NAS LAG group config side.

Why only the Proxmox server has a problem - is a good question. Do you have another standalone Debian device to test with? See if that can connect to the NAS.

 

[cobrajdm]

Yep, removed one side of the LAG group and ping came right back, Proxmox can ping the NAS. I will see if I can install Debian to test and narrow the issue down. What version of Debian should I get Trixie Alpha 1?

 

[gfngfn256]

The Proxmox OS is basically Debian on a Ubuntu kernel. Your current machine seems up to date (from your output above) so you'll be on Debian 12.9, so just use that, (current Bookworm stable).

You probably want to check that LAG group/trunk/switch, you'll probably find something that can be changed to correct the issue.