vnets not recovered on Guest Domain after Control or Service Domain reboots

(Doc ID 1625145.1)

Last updated on SEPTEMBER 25, 2016

Applies to:

Solaris Operating System - Version 11.1 to 11.1 [Release 11.0]
Solaris Operating System - Version 10 1/13 U11 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.

Symptoms

 vnets  not recovered on Guest Domain after Control or Service Domain reboots i.e vnet link does not come up once the control or service domain is up after reboot.

/var/adm/messages

********************************

Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 215189 daemon.error] The link has gone down on net1
Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 968981 daemon.error] IP interface failure detected on net1 of group oob0
Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 215189 daemon.error] The link has gone down on net3
Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 968981 daemon.error] IP interface failure detected on net3 of group backup0
Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 215189 daemon.error] The link has gone down on net5
Jan 14 09:28:46 Hostname in.mpathd[108]: [ID 968981 daemon.error] IP interface failure detected on net5 of group prod0
Jan 14 09:30:06 Hostname vnet: [ID 920994 kern.warning] WARNING: vnet1: exceeded number of permitted handshake attempts (5) on channel 2
Jan 14 09:30:06 Hostname vnet: [ID 920994 kern.warning] WARNING: vnet5: exceeded number of permitted handshake attempts (5) on channel 10

***********************************

The vnet in guest can be restored using 'ipadm disable-if' and 'ipadm enable-if' on the guest. (Or rebooting the guest.)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms