Sponsored Content
Operating Systems Solaris list of physical net interfaces Post 302388076 by pupp on Tuesday 19th of January 2010 10:22:15 AM
Old 01-19-2010
dladm show-dev shows nothing?
 

10 More Discussions You Might Find Interesting

1. Programming

C program : how to list interfaces with a valid IP ?

Hi all, I think that the title is explicit enough :) I would like in a C program to list the interfaces with a valid IP. Those that can permit to send something over a network. Thanks ;) (7 Replies)
Discussion started by: brolon
7 Replies

2. Solaris

IPMP on 2 physical interfaces

Hi Community, I've a problem with IPMP: I have 2 physical interfaces, 1 "physical IP" and 1 VirtualIP. My question is: is it possible to have IPMP configuring 2 physical interfaces with the same "physical" IP Address? for example: ce0 10.10.10.10 ce5 10.10.10.10 and VIP... (5 Replies)
Discussion started by: Sunb3
5 Replies

3. Solaris

List all resources on physical host LDOM server

Hello, I have a SUN T5240 running Solaris 10 with Logical Domain Manager (v 1.0.3). You can use the "ldm" command to display current resources on the box. Is there away to display all the "physical resources" on the box(i.e.,used and unused). For example, "ldm ls" will tell me what the... (5 Replies)
Discussion started by: stephanpitts
5 Replies

4. AIX

Maximum Limit of HMC to handle Physical Power Virtualization Physical Machine

Hello All, Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time? Thanks, Jenish (1 Reply)
Discussion started by: jenish_shah
1 Replies

5. Solaris

svc:/network/physical:default: Method "/lib/svc/method/net-physical" failed with exit status 96. [ n

After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks. ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface # ifconfig eg1000g0:2 plumb ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface # ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies

6. Solaris

Interfaces and Virtual-interfaces queries

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)
Discussion started by: satish51392111
1 Replies

7. UNIX for Dummies Questions & Answers

Solaris Logic to transmit traffic to physical interfaces ( eg ce0 and ce1)

Just wanted to understand what is the logic being used by Solaris(kernel) to transmit data/traffic on physical interfaces. I have seen most of the time traffic is being sent to interface ce0 and sometime to ce1. I have removed ip address from below command for some reason. netstat -rn ... (3 Replies)
Discussion started by: nadeemahmed
3 Replies

8. Solaris

[Solved] Solaris list physical volume details

in AIX, we have lspv command to display details of physical volume like below: lspv -l hdisk102 hdisk102: LV NAME LPs PPs DISTRIBUTION MOUNT POINT oradata112lv 1599 1599 320..320..319..320..320 /oracle/oradata11 Can you please tell how to... (2 Replies)
Discussion started by: sendtoshailesh
2 Replies

9. AIX

AIX with 2 Net Interfaces lose connectivity

hi guys We have a AIX Server with TSM installed. This server has en0 for administration purposes and we have en1 for backup stuff. en0 subnet 10.10.10.x en1 subnet 10.10.20.x The issue we are having is all of a sudden the LPARs we are backing up lose connectivity to the AIX-TSM Server.... (23 Replies)
Discussion started by: karlochacon
23 Replies

10. Solaris

How to list physical CPU on primary domain?

How to list physical CPU on primary domain? Sparc SPARC T5-4 psrinfo -p 1 in ILOM I see Processors: 4 / 4 (2 Replies)
Discussion started by: thomasj
2 Replies
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)
All times are GMT -4. The time now is 03:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy