06-27-2005
You can try this:
root@sun # cat /etc/path_to_inst | grep -i network
"/pci@1f,0/pci@1,1/network@1,1" 0 "hme"
"/pci@1f,0/pci@1,1/network@3,1" 1 "hme"
this is a server having two hme interfaces...
If it donīt work for you , you can try to enter each possible name:
cat /etc/path_to_inst | grep -i hme
cat /etc/path_to_inst | grep -i qfe
cat /etc/path_to_inst | grep -i eri
cat /etc/path_to_inst | grep -i bge
cat /etc/path_to_inst | grep -i ce
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Our shops server runs SCO Openserver 5 release 5. It has two network cards in it (one on 10.0.0.6 and one on 90.0.0.99). When I run scoadmin and look at the network settings it show both my 3com network cards and a loop back driver http://theentertainer.com/james/untitled.jpg
Can anyone tell... (1 Reply)
Discussion started by: potter
1 Replies
2. Solaris
Hi,
I'm looking for a command to be able to disable a network card under the boot PROM.
I need it to force my Jumpstart to use the Ethernet card of my server (V880) instead of my fiber card (gem0).
Thanks,
Fabien (6 Replies)
Discussion started by: unclefab
6 Replies
3. AIX
The title speaks for itself. I have never attempted this but understand there is a way to use two network cards (en0 and en1) with the same IP address so as to load balance the traffic flow through both cards. Anyone know the answer? (4 Replies)
Discussion started by: johnf
4 Replies
4. Solaris
Hi all,
I have a server running with Solaris and I have 2 Pci cards installed on this server (since a while), 1 with 4 coppers connections output and one with a Fiber network connection output.
Today, this server is using the on board network connection (Ce0).
How can I find the other... (7 Replies)
Discussion started by: unclefab
7 Replies
5. Solaris
Hi All,
Hope you are all doing good.
In MY unix box i have 2 network cards. I want to know what if one network card fails. Does the second one will automatically take all the traffic or how it is supposed to work. Also in my logs i am seeing below errors . Can you throw some light of this qfe... (3 Replies)
Discussion started by: Krrishv
3 Replies
6. Solaris
Hi all
I hate networking, I hate everything to do with it. Its something I do in anger in one contract, then forget. This is more of a question / than a problem.
So, on a solaris 10 server, using older qfe cards, Ive got a sun truck with 4 nics (qfe0,3,4,7), and a ipmp pair (hemo0,qfe1).... (2 Replies)
Discussion started by: sbk1972
2 Replies
7. Programming
Hello
I have a problem with retreiving network interface list using IOCTLs. I have 4 interfaces:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope... (1 Reply)
Discussion started by: xyzt
1 Replies
8. Hardware
Hello everybody,
I'm having troubles with Slackware 13.1 and network cards.
I have one on-board Ethernet card (which is recognized and works okay) and a PCI Ethernet card (which is also recognized, but doesn't appear in 'ifconfig -a'). If i run a 'lspci', i can see the kernel recognized the... (5 Replies)
Discussion started by: semash!
5 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
I have just setup a webserver running on a linux box. This server has 2 ethernet cards and only 1 is in used now. eg. 192.168.10.1 is my server IP. All users from 192.168.10.X can access my webserver. However, users from another LAN 10.10.10.X are not able to access my webserver. They... (0 Replies)
Discussion started by: jackma
0 Replies
10. Solaris
Hello All
I am trying to get a list of process or applications runninging on the network only. I should emphasize that im not interested in the application or process if its not using the network.
I tried the good old netstat comand, but im not able to figure out how to list the running... (8 Replies)
Discussion started by: busi386
8 Replies
LEARN ABOUT HPUX
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device.
This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1: Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst
SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future
release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.10 2 Nov 1995 path_to_inst(4)