Hello,
which network interface i must sellect during the solaris9 installation le0 or hme0 ?
this system is part of the network, it is a standalone system
and is not on any domain.
thanks for your help,
em (1 Reply)
Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1)
will not failover?
Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
I got second IOU in my M5000 but not able bring internal network interfcae .. ike i don't get link on those 2 interfaces .. and the same network cable plugged in PCI network card it works like a charm Is there any special way to enable the internal IOU interfaces or i have bad nics ? (8 Replies)
Hello,
can someone please suggest if is possible to use different net interfaces
for non global zones ?
for example ,
bash-3.00# uname -srv
SunOS 5.10 Generic_137137-09
bash-3.00# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
... (6 Replies)
i need a one liner command that writes in /var/log/net.log the date when i connect to the network and when i disconect ..i know that i need to write somethin in /etc/network/interfaces but idk what ! please help (1 Reply)
Hi friends,
I am abit confused regarding these interfaces, hope you could clearify everything, and differentiate between them, with examples?
1. Graphical User Interface(GUI)
2. Text User Interface(TUI)
3. Character User Interface(CUI)
4. Commandline Interface(CLI)
5. Text-based User... (1 Reply)
Hi Al,
In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified.
1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
So after getting a Nagios plugin up and running that checks certain things including network interfaces, I get an error off the one box I built (as opposed to all of the others that were built by a former employee). The error complains of the "NIC logical group" failing.
All the boxes are HP... (7 Replies)
Discussion started by: xdawg
7 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)