After this issue happens, as a temporary workaround when the VDX interface fails to come back up, applying "shutdown" and "no shutdown" to the VDX interface settings will allow it to come back up temporarily.
This is not a permanent solution. The same issue will reoccur if the next upgrade is also ISSU. The issue can also theoretically reoccur if there is a HA failover after a triggering ISSU. For a permanent solution after the issue has happened, either a coldboot upgrade or "reload system" must be performed.
To avoid this issue completely, ISSU must not be used when upgrading from NOS 6.0.1 or NOS 6.0.1a to any NOS 6.0.2x release or when upgrading from 6.0.1 to 6.0.1a. Coldboot must be used instead.
This issue is acknowledged and documented in release notes with the following note that appears in 6.0.2x release notes such as nos6.0.2_releasenotes_v1.0.pdf under the section "6.0.2 Caveats":
"After ISSU upgrade from 6.0.1 to 6.0.1a, if the peer port (40G/Breakout/1G) goes down for any reason then the local port may go down and not come up. To recover, it is required to perform shut/no shut on the local port."
At the time that caveat was written, the possibility of consecutive ISSU without reloads or HA failover after ISSU was not considered. With those possibilities, the only safe method of preventing this issue from reoccurring is to avoid ISSU and use coldboot when NOS 6.0.1 or 6.0.1a is involved.