Red Hat NETSCAPE MANAGEMENT SYSTEM 4.5 User Manual download pdf (Page 220)

Networking

220

www.vmware.com

The VMkernel Network Card Locator

When network interface cards are assigned to the VMkernel, sometimes it is difficult to

map from the name of the VMkernel device to the physical network adapter on the

machine.

For example, if there are four Intel EEPro cards in a machine and all are dedicated to

the VMkernel, these four cards are called vmnic0, vmnic1, vmnic2 and vmnic3.

The name of a card is based on its order in the PCI bus/slot hierarchy on the machine

— the lower the bus and slot, the lower the number at the end of the name.

If you know the bus and slot order of the adapters, you can figure out which adapter

has which name. However, if you don’t, you can use the findnic program to help

you make the proper association of network adapter to name.

The format of the command is

findnic <options> <nic-name> <local-ip> <remote-ip>

The findnic program takes a VMkernel network device name, an IP address to give

the device on the local machine and an IP address that findnic should try to ping.

When you issue the command, findnic pings the remote IP address.

This allows you to determine which adapter is which by looking at the LEDs on the

cards to see which one has flashing lights or by seeing if the ping itself is successful.

Options

-f

Do a flood ping.

-i <seconds>

Interval in seconds between pings.

Examples

findnic vmnic0 10.2.0.5 10.2.0.4

Binds VMkernel device vmnic0 to IP address 10.2.0.5 and then tries to ping the

remote machine with the IP address 10.2.0.4.

findnic -f vmnic1 10.2.0.5 10.2.0.4

Binds VMkernel device vmnic1 to IP address 10.2.0.5 and then tries to flood ping the

remote machine with the IP address 10.2.0.4.

1 2 ... 215 216 217 218 219 220 221 222 223 224 225 ... 285 286

No comments

Red Hat NETSCAPE MANAGEMENT SYSTEM 4.5 User Manual Page 220