Unconfiguring PCI communications adapters
The following is an overview of the process for unconfiguring PCI communications adapters. This includes Ethernet, Token-ring, FDDI, and ATM adapters.
If your application is using TCP/IP protocol, you must remove the TCP/IP interface for the adapter from the network interface list before you can place the adapter in the defined state. Use the netstat command to determine whether your adapter is configured for TCP/IP and to check the active network interfaces on your adapter. For information about the netstat command, see netstat.
An
Ethernet adapter can have two interfaces: Standard Ethernet (enX)
or IEEE 802.3 (etX). X is
the same number in the entX adapter
name. Only one of these interfaces can be using TCP/IP at a time.
For example, Ethernet adapter ent0 can have en0 and
et0 interfaces.
A Token ring adapter can have only one interface:
Token-ring (trX). X is
the same number in the tokX adapter
name. For example, Token-ring adapter tok0 has a
tr0 interface.
An ATM adapter can have only one atm interface:
ATM (atX). X is
the same number in the atmX adapter
name. For example, ATM adapter atm0 has an at0 interface.
However, ATM adapters can have multiple emulated clients running over
a single adapter.
The ifconfig command removes an interface from the network. The rmdev command unconfigures the PCI device while retaining its device definition in the Customized Devices Object Class. Once the adapter is in the defined state, you can use the drslot command to remove the adapter.
pci1 and
all other devices under them while retaining their device definitions
in the Customized Devices object class, type: rmdev -p pci1 rmt0 Defined
hdisk1 Defined
scsi1 Defined
ent0 Defined