Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: How to find network cards available ...
Operating Systems Solaris How to find network cards available ... Post 302094570 by unclefab on Monday 30th of October 2006 04:24:16 AM
Old 10-30-2006
Thanks !

Last question, Can we find somewhere a list of interfaceswe can found under Solrais and hardware linked?

I.E :
Ce= Internal copper
Qfe= Pci copper
bge = Fiber ....
eri .....
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO Unix and Two Network Cards

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

Disable Network cards under boot Prom

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. Solaris

How to List all Network cards

Hi, I'm looking for a command to be able to list all my network cards available on my server. With the command "ifconfig - a", I can only see to configured network card(s) Any idea ? :confused: Thanks a lot for your help, Fabien (5 Replies)
Discussion started by: unclefab
5 Replies

4. AIX

Load balancing across network cards

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

5. Solaris

qfe errors and network cards

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

Network cards - Routing

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. Hardware

Slackware 13.1 can't configure two network cards

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

8. UNIX for Dummies Questions & Answers

How to use wild cards to find files beginning with upper and lower case

Im trying to use wild cards to find files that start with either an upper or lower case letter e.g. list files that beginning with b or B, i also want to sort them by the time they were last modified. e.g latest file created first. At the moment i have the following code that ls -d... (3 Replies)
Discussion started by: parker4001
3 Replies

9. UNIX for Dummies Questions & Answers

1 Server with 2 ethernet cards IP on seperate network. Possible?

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

LEARN ABOUT HPUX

vparefiutil

vparefiutil(1M) 														   vparefiutil(1M)

NAME

       vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database

SYNOPSIS

       db_file] hw_path]

DESCRIPTION

       The  command  displays  the  HP-UX  hardware path to EFI path mappings that are stored in the virtual partition database.  Legacy and agile
       hardware paths will be displayed, if available, as provided by HP-UX.  If the virtual partition database is not specified,  then  the  live
       database or by default is used.	It can also be used to update the hw_path to EFI_path mappings from to the database.  The behavior without
       any options is to display the HP-UX hardware path to EFI path mappings.

       This command is not supported on PA-RISC systems.

   Options and Arguments
       recognizes the following command line options and arguments:

       Specifies the alternate database from which the HP-UX hardware path to EFI
	     path mappings need to be displayed, updated, or deleted.  or live is default if this is not specified.

       Updates the database from the info available (from

       Displays the HP-UX hardware path to EFI path mapping in machine readable format.
	     Each mapping is displayed in a separate line as follows:

       Deletes the HP-UX hardware path to EFI path mappings in the database.

	     Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed.

       If this is specified, only the HP-UX hardware paths at or below the given
	     hw_path are displayed, updated, or deleted.

SECURITY RESTRICTIONS

       This command is restricted to processes owned by superuser.

RETURN VALUE

       returns the following values:

	      Successful completion.
	      Error condition occurred.

EXAMPLES

       Display the hw_path to EFI_path mappings from the live database.

       # vparefiutil
       Hardware path - EFI path mapping
       ================================

	Hardware path : 2.0.0.2.0.6.0
		      : 2.0.0.2.0.6.0
	EFI path      : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.0.3.0.6.0
		      : 2.0.0.3.0.6.0
	EFI path      : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/
	HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.0.3.1.2.0
		      : 2.0.0.3.1.2.0
	EFI path      : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.8.1.0.3.4.0.0.1.6
		      : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
	EFI path      : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
	Fibre(WWN50001FE1500339ED,Lun1000000000000)/
	HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.8.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
	HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.10.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.12.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
	HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

       # vparefiutil
       Hardware path - EFI path mapping
       ================================

	Hardware path : 2.0.0.2.0.6.0
		      :
	EFI path      : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.0.3.0.6.0
		      :
	EFI path      : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/
	HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.0.3.1.2.0
		      :
	EFI path      : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.8.1.0.3.4.0.0.1.6
		      : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
	EFI path      : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
	Fibre(WWN50001FE1500339ED,Lun1000000000000)/
	HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
	EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.8.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
	HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.10.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.12.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
	HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

       Display the hw_path to EFI_path mappings from the alternate database in machine readable format.

       # vparefiutil -M -D vpdb_foo

       2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0

       2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/
       Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0

       2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0

       2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
       Fibre(WWN50001FE1500339ED,Lun1000000000000)/
       HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
       EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000

       2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
       HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::

       2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/
       EFIHPUXHPUX.EFI::

       2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
       HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::

       # vparefiutil -M -D vpdb_foo

       2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::

       2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/
       Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::

       2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::

       2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
       Fibre(WWN50001FE1500339ED,Lun1000000000000)/
       HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/
       EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000

       2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
       HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::

       2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/
       Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI::

       2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/
       HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::

       Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar.

       # vparefiutil -d -H 2/0/0/3
       # vparefiutil
       Hardware path - EFI path mapping
       ================================

	Hardware path : 2.0.0.2.0.6.0
		      :
	EFI path      : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.8.1.0.3.4.0.0.1.6
		      : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
	EFI path      : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
	Fibre(WWN50001FE1500339ED,Lun1000000000000)/
	HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.8.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
	HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.10.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/
	EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.12.0
		      :
	EFI path     pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/
	HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

       # vparefiutil -d -H 2/0/0/3
       # vparefiutil
       Hardware path - EFI path mapping
       ================================

	Hardware path : 2.0.0.2.0.6.0
		      :
	EFI path      : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.8.1.0.3.4.0.0.1.6
		      : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000
	EFI path      : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/
	Fibre(WWN50001FE1500339ED,Lun1000000000000)/
	HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.8.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/
	HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.10.0
		      :
	EFI path      : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/
	Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI

	Hardware path : 2.0.12.1.0.4.1.12.0
		      :
	EFI path     pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/
	HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI

       For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path.

	 Hardware path : 0.0.14.0.0.0.0.0.0.2.0
	 EFI path      : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/
	   VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/
	   HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI
	 SAS Address   : 0x500000e01200d3f2

       The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain  the  same.   To  locate  SAS
       devices	in  different  OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware
       path.

WARNING

       The option is provided only to remove the stale HP-UX hardware path to EFI path mappings.  If you remove the valid HP-UX hardware  path	to
       EFI  path mappings, you may not be able to load vpars.  It is always better to follow the operation with a operation to update the database
       with the valid HP-UX hardware path to EFI path mappings available from

AUTHOR

       was developed by the Hewlett-Packard Company.

SEE ALSO

       vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M),  vparenv(1M),  vparextract(1M),  vparmodify(1M),  vparreloc(1M),
       vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5).

							     Itanium(R)-Based Systems						   vparefiutil(1M)
All times are GMT -4. The time now is 09:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy