Recent content by Bhupinder

These are resolved ONLY the Kernel issue is persisting I am getting this on checking the readiness for upgrade Checking for package updates.. PASS: all packages up-to-date Checking proxmox-ve package version.. PASS: already upgraded to Proxmox VE 8 Checking running kernel version.. WARN...

Hi, While checking the prerequisites for update from proxmox 7.4.18 to Proxmox 8 I am getting the following WARNING: ``` WARNING: updates for the following packages are available: dpkg, fontconfig, telnet, inetutils-telnet, reportbug, libnetfilter-conntrack3, librados2...

I get this block message on running nmap -r

Hi Folks, I am badly stuck. My second subnet is not pinging the Switch PING 172.20.124.1 (172.20.124.1) 56(84) bytes of data. --- 172.20.124.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2025ms. I shall appreciate a pointer to debug and move forward. Direct...

Still not working Unable to ping switch. Should I remove the bridge VMBR3 and add the gateway to the Bond?

@beisser Thanks for the response and guidance: Checked I had corrected it the corrected values are: auto bond1 iface bond1 inet manual bond-slaves ens4f0np0 ens4f1np1 bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy layer2+3 I have added a separate gateway for this in...

Thxs Shall update and revert

The TCP Dump File is attached Ran it just now.

I look for support and guidance around where I am going wrong in a PROXMOX environment that I am setting up. I have one server that is connected and working for the Test Environment. It is running on the 172.16.0.15/16 network. We have three more servers that we have set up in cluster. The...

Needed help and forward guidance of the august community on best practice for a potential deployment. SUMMARY: We have the need for deployment of a Hybrid micro services application. Each single instance deployment has 10 VMs that communicate with each other that is on a separate VLAN. CRITCAL...

We believe we have identified the bottle neck Till try to resolve and update Thanks for your time and guidance

Checked again Changed to "virtio" instead of "e1000". i.e, please edit the 153 VM and set the Network Model as a "virtio", you can edit the VM from PVE Web UI -> Datacenter->activewellnessserver->153->Hardware->Network Device. From proxmox VM1 to VM2: root@CEPHNode-3-Beta:~# iperf -c 172.16.0.90...

The outputs are attached

Enabled queues=2 in those vms

OK