I have net0-net18. All net0-18 are already in an IPMP group...via ipadm. If I...dladm create-vnic -l net18 vnic1, dladm create-vnic -l net16 vnic2.
could I by pass IPMP fully?
Last edited by Scott; 11-08-2013 at 04:27 PM..
Reason: Please use code tags
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed?
2. NTP client and server doesnt work on branded... (11 Replies)
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Hi,
This may have already been raised previously so sorry for the duplication. What I want to achieve is have a physical server using link based IPMP setup in the global zone (not problem doing that) and then create a zone set as Shared-IP so when the servers NIC has an issue the IP will... (0 Replies)
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different.
share -F nfs -o ro,anon=0 /dir
This would really surprise me that you cannot do this.
Thanks (2 Replies)
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL):
And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
LEARN ABOUT OPENSOLARIS
di_walk_minor
di_walk_minor(3DEVINFO) Device Information Library Functions di_walk_minor(3DEVINFO)NAME
di_walk_minor - traverse libdevinfo minor nodes
SYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ]
#include <libdevinfo.h>
int di_walk_minor(di_node_t root, const char *minor_nodetype,
uint_t flag, void *arg, int (*minor_callback)(di_node_t node,
di_minor_t minor, void *arg));
PARAMETERS
arg Pointer to caller- specific user data.
flag Specify 0. Reserved for future use.
minor The minor node visited.
minor_nodetype A character string specifying the minor data type, which may be one of the types defined by the Solaris DDI framework,
for example, DDI_NT_BLOCK. NULL matches all minor_node types. See ddi_create_minor_node(9F).
node The device node with which to the minor node is associated.
root Root of subtree to visit.
DESCRIPTION
The di_walk_minor() function visits all minor nodes attached to device nodes in a subtree rooted at root. For each minor node that matches
minor_nodetype, the caller-supplied function minor_callback() is invoked. The walk terminates immediately when minor_callback() returns
DI_WALK_TERMINATE.
RETURN VALUES
Upon successful completion, di_walk_minor() returns 0. Otherwise, -1 is returned and errno is set to indicate the error.
The minor_callback() function returns one of the following:
DI_WALK_CONTINUE Continue to visit subsequent minor data nodes.
DI_WALK_TERMINATE Terminate the walk immediately.
ERRORS
The di_walk_minor() function will fail if:
EINVAL Invalid argument.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO dladm(1M), di_minor_nodetype(3DEVINFO), dlpi_walk(3DLPI), libdevinfo(3LIB), attributes(5), filesystem(5), ddi_create_minor_node(9F)
Writing Device Drivers
NOTES
The di_walk_minor() function is no longer an accurate method for walking network datalink interfaces on the system. Applications should use
dlpi_walk(3DLPI) instead. It has been common for applications to use di_walk_minor() to walk networking devices by passing in a minor_node-
type of DDI_NT_NET, in most cases to discover the set of DLPI devices on the system. Solaris now makes a layering distinction between net-
working devices (the objects displayed in the DEVICE field by dladm show-phys) and network datalink interfaces (the objects displayed by
dladm show-link). Datalink interfaces are represented as the set of DLPI device nodes that applications can open by using dlpi_open(3DLPI)
or by opening DLPI nodes out of the /dev/net filesystem (see filesystem(5)). The dlpi_walk(3DLPI) function is the proper function to walk
these nodes.
SunOS 5.11 14 Jan 2009 di_walk_minor(3DEVINFO)