PCI Token Ring Administrator's Guide

Configuring Token Ring
Configuration Using SAM
Chapter 250
Driver-specific information will be displayed after the extended
station address and encapsulation. Included in the driver-specific
information are the driver name, which is stored in the hwift name
field, and, for the HP-PB and built-in FDDI interfaces, the
driver-specific major number.
The purpose of displaying the driver name is to distinguish a 100VG
interface from a non-VG interface.
The executables that parse the lanscan output will have to be
changed. See the lanscan manpage for details.
The PPA# is no longer equal to the NMID as it was in 10.20.
Programs that get the NMID from lanscan and expect it to be the
same as PPA# should be changed to get the PPA# instead.
Network management tools and some driver start-up scripts that use
NMID must be changed. Any tool that depends on PPA# to be the
same as NMID needs to be changed. See the -p option for details.
• ifconfig
Another way of finding the interface state is by using ifconfig:
$ ifconfig lan0
lan0: flags=843<UP,BROADCAST,RUNNING,MULTICAST>...
inet 15.13.136.73 netmask fffff800 broadcast 15.13.143.255
$ ifconfig lan1
lan1: flags=842<BROADCAST,RUNNING,MULTICAST>...
inet 0.0.0.0 netmask 0
Interface names. Interface names used for ifconfig commands and
/etc/rc.config.d/netconf statements can have a logical instance
number appended to the card name (for example, lan0:1). The new
syntax is:
name X[: logical_instance ]
where:
name is the class of interface, such as lan (Ethernet LAN, Token
Ring, FDDI, or Fibre Channel links), snap (IEEE802.3 with SNAP
encapsulation), atm (ATM), du (Dial-up), ixe (X.25), and mfe (Frame
Relay).