I recently installed Solaris 10 1/13 and proprietary TCP PEP software on a new hard drive within an old Sun v210. When the PEP software starts, the Sun's CE0 interface loses its "ether" address, according to "ifconfig -a".
Here's the output before the software starts:
ce0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 inet 0.0.0.0 netmask 0 ether 0:14:4f:33:82:a1
Here's the output after the software starts:
ce0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 inet 0.0.0.0 netmask 0
The IP address, netmask, and flags are all displaying the expected values. It's just the vanishing MAC address which is a problem. The interface will not pass any data, despite the link being "UP" according to the switch. The server is also using two BGE interfaces which experience no problems whatsoever.
I couldn't find other instances of this issue online, but it could be that it's difficult to phrase the question in a sufficiently specific way to get useful search results. Has anyone else seen this problem in the past? We've used this PEP software on hundreds of v210s over the better part of a decade, and I can find no suggestion that his issue has occurred in the past.
The only thing different about this instance, is the fact that I'm using Solaris 10 1/13; the v210s usually use older releases of Solaris 10, but 1/13 is the only one available from Oracle anymore. Other than rolling back the CE interface driver to match a known-good version, is there anything else related to this interface which may need to be rolled back which could cause these symptoms?
I know this question is probably made more difficult by the inclusion of our proprietary software into the mix, but I appreciate any advice anyone can offer.