NBU 5230 3.2 MR1 - issue with ping
Hello
Recently I did upgrade NBU on this box to 3.2 and than did apply Maintenance Release 1 pack. after few days I did notice I am unable to ping one of its clients. NBU appliance as well this client is in the same subnet - so no routing involved, but still pings does not work. I did open a case with VRTS and waiting for their inputs...
NBU app is having a bond in 802.3ad mode made from two 10 Gbps NICs ... on top of that I laid down vlan 10.
vlan10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.60.208.47 netmask 255.255.255.0 broadcast 10.60.208.255
inet6 fe80::21e:67ff:fef2:cbd5 prefixlen 64 scopeid 0x20<link>
ether 00:1e:67:f2:cb:d5 txqueuelen 1000 (Ethernet)
routing table
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.60.208.1 0.0.0.0 UG 0 0 0 vlan10
10.60.208.0 0.0.0.0 255.255.255.0 U 0 0 0 vlan10
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 vlan10
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 vlan20
192.168.229.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
I am able to ping GW
ping 10.60.208.1
PING 10.60.208.1 (10.60.208.1) 56(84) bytes of data.
64 bytes from 10.60.208.1: icmp_seq=1 ttl=255 time=1.29 ms
^C
--- 10.60.208.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.290/1.290/1.290/0.000 ms
but I am unable to ping 10.60.208.5
PING 10.60.208.5 (10.60.208.5) 56(84) bytes of data.
^C
--- 10.60.208.5 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms
Below is client config
Windows IP Configuration
Ethernet adapter Live Network Connection:
Connection-specific DNS Suffix . : some.com
IPv4 Address. . . . . . . . . . . : 10.60.208.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.60.208.1
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.60.208.1 10.60.208.5 271
10.60.208.0 255.255.255.0 On-link 10.60.208.5 271
10.60.208.5 255.255.255.255 On-link 10.60.208.5 271
10.60.208.255 255.255.255.255 On-link 10.60.208.5 271
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.60.208.5 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.60.208.5 271
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 10.60.208.1 Default
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
1 331 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
There is no Firewall on this client - it is a VM running windows server 2016...
I can't see the NBU app IP in arp -a outcome - not sure what to do .... do you have any idea?
Today I started to map what VMs are residing on which ESXi and was pinging these. It turned out I can ping few and few from the same subnet from the same ESXi can't.
I forced network team to verify LACP status on their end, and it turned out that one of the ports in this port channel was suspended (down) while NBU appliance was showing for both UP status.
So I did elevate to CLI and run ifdown bond0 followed by ifup bond0
Than I had to add again default gw
And everything is working back fine…
I am just wondering why appliance did not notice the remote port being in down state.
Nonetheless thank you for your assistance.

