Ethernet Port device path? Post: 302901636

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

determining ethernet port speed in solaris

i purchased, what was labeled as a 4-port fast ethernet sbus card from ebay. i installed it in my ultra1, and it seems to be working fine. how can i determine if the card is infact a fast ethernet card vs. the standard ethernet 4-port card?

2. UNIX for Dummies Questions & Answers

serial port device path

hi. Im trying to install a switch. And the manual says i should type a command including a SerialPortDevicePath. which is the filepath to serial port used for connection. However.. nothing about how to find this info. Could anyone help me where to find this path? thx mr.T

3. Solaris

Reg. Ethernet port

Hi Friends, I am using intel system installed solaris 10, when i check ifconfig -a it doesn't show any thing eg-for HP servers hme0, for sun servers-iprb0. for me it doesn't show any thing, and tell me what files to be modified. Thanks in Advance.

4. Solaris

Ethernet Port Name

I have a new Sun 440 and I am trying to configure it. Non of the Ethernet ports are enabled; when I issue "ifconfig -a" it returns nothing. Is there a way to know the available port name (e.g. ce, bge, etc.) by running a command or so ?

5. Linux

Do linux have a device file for ETHERNET CARD.

Sir, Do linux have device file for ethernet card. Can I use open , read , write , system calls to read data transferred through LAN. Is there any methods to read network datas (with out header and tailor information). Hope anyone can help me out. Thanking you.... ...

6. Red Hat

Oracle RAC -- changing ethernet device name

I have a RAC setup that was configured before I started at my new company. I would like to reconfigure the network devices and change the names. How complex is this regarding the Oracle RAC environment? Does the Oracle RAC rely on the device name or is it only relying on the IP information? ...

7. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ...

8. UNIX for Advanced & Expert Users

Command to see the logical volume path, device mapper path and its corresponding dm device path

Currently I am using this laborious command lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}' Would like to know if there is any shorter method to get this mapping of...

LEARN ABOUT DEBIAN

ibv_uc_pingpong

IBV_UC_PINGPONG(1)						   USER COMMANDS						IBV_UC_PINGPONG(1)

NAME

       ibv_uc_pingpong - simple InfiniBand UC transport test

SYNOPSIS

       ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e] HOSTNAME

       ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e]

DESCRIPTION

       Run a simple ping-pong test over InfiniBand via the reliable connected (RC) transport.

OPTIONS

       -p, --port=PORT
	      use TCP port PORT for initial synchronization (default 18515)

       -d, --ib-dev=DEVICE
	      use IB device DEVICE (default first device found)

       -i, --ib-port=PORT
	      use IB port PORT (default port 1)

       -s, --size=SIZE
	      ping-pong messages of size SIZE (default 4096)

       -r, --rx-depth=DEPTH
	      post DEPTH receives at a time (default 1000)

       -n, --iters=ITERS
	      perform ITERS message exchanges (default 1000)

       -l, --sl=SL
	      use SL as the service level value of the QP (default 0)

       -e, --events
	      sleep while waiting for work completion events (default is to poll for completions)

SEE ALSO

       ibv_rc_pingpong(1), ibv_ud_pingpong(1), ibv_srq_pingpong(1)

AUTHORS

       Roland Dreier
	      <rolandd@cisco.com>

BUGS

       The  network  synchronization between client and server instances is weak, and does not prevent incompatible options from being used on the
       two instances.  The method used for retrieving work completions is not strictly correct, and race conditions may  cause	failures  on  some
       systems.

libibverbs							  August 30, 2005						IBV_UC_PINGPONG(1)