ISE post-2.4 upgrade instance loses network connectivity

[bperciac]

I recently ran an update on an ISE 2.3 instance, and after the upgrade, IP connectivity is lost.  It looks like a routing issue, but the IP information is identical pre- and post-upgrade.  I have replicated this twice.  Any suggestions on where to start looking for the cause?

Pre-upgrade:

PING 10.3.66.123 (10.3.66.123) 56(84) bytes of data.
64 bytes from 10.3.66.123: icmp_seq=1 ttl=64 time=0.547 ms
64 bytes from 10.3.66.123: icmp_seq=2 ttl=64 time=0.572 ms
64 bytes from 10.3.66.123: icmp_seq=3 ttl=64 time=0.615 ms
^C
--- 10.3.66.123 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.547/0.578/0.615/0.028 ms

Post-upgrade:

root@lamp ~# ping 10.3.66.123
PING 10.3.66.123 (10.3.66.123) 56(84) bytes of data.
^C
--- 10.3.66.123 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

root@lamp ~#

IP Configuration (unchanged between pre- and post-upgrade)

Route table (also unchanged)

VMWare Profile:

[hslai]

If not already done, please check the interface status. Perhaps, we may get together to take a look.

[bperciac]

I am in SJC this week for the VT, if you are free to get together - let me know!

Bob

[bperciac]

I am re-running the upgrade, and I am capturing the ADE.log for the exact step where things cause connections to stop.  Will chare that once I have it gathered.