Project

General

Profile

Bug #2128

network/physical in maintenance on virtual interface

Added by Anil Jangity over 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
2012-02-14
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

SunOS oi 5.11 oi_151a2 i86pc i386 i86pc

I have a crossbow virtual interface on the global zone called "oi0" assigned to a non-global zone called "oi":

root@sjc3:~# dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID
oi0 igb0 1000 2:8:20:f:23:dc random 0
root@sjc3:~#

After upgrading to OI 151a2, the zone is not able to boot up. The "svc:/network/physical:default" is in maintenance. The logs show:

[ Feb 14 12:57:29 Leaving maintenance because clear requested. ]
[ Feb 14 12:57:29 Enabled. ]
[ Feb 14 12:57:29 Executing start method ("/lib/svc/method/net-physical"). ]
[ Feb 14 12:57:29 Timeout override by svc.startd. Using infinite timeout. ]
ifconfig: cannot plumb oi0: Interface already exists
ipadm: Could not enable oi0 : Object not found
configuring IPv4 interfaces:ifconfig: error: oi0: no such interface
/lib/svc/method/net-physical571: ![[: not found [No such file or directory]
/lib/svc/method/net-physical571: ==: not found [No such file or directory]
oi0.
add net default: gateway 208.64.61.62: Network is unreachable
di_init: No such file or directory
[ Feb 14 12:57:29 Method "start" exited with status 96. ]

root@oi:~# ipadm show-if
IFNAME STATE CURRENT PERSISTENT
lo0 ok m-v------46 --
oi0 down bm-------Z4- ---
root@oi:~#

History

#1

Updated by Anil Jangity over 7 years ago

It turns out this is happening because I had
"allowed-address" defined in my net configuration of the zone.
I've tried using A.B.C.D as we as A.B.C.D/32 ... neither of them work. It's not documented but I believe this feature should be there.

#2

Updated by Ken Mays over 6 years ago

  • Assignee set to OI illumos

Also available in: Atom PDF