Monitoring SMT Frames
The pf_smtmon(1M) or nf_smtmon(1M) utility is an active monitor that displays the SMT frames received by the local station. It is particularly useful for diagnosing communication problems with the SunNet Manager proxy agent.
This command must be executed as root (or superuser) and has the general form:
# <basedir>/pf_smtmon [-i pf<inst>] [--x] [--h] [<frameclass>]
-i pf<inst> specifies the SunFDDI interface
-x displays the received SMT frames in hexadecimal
-h displays help information, including a list of valid frame classes
<frameclass> specifies one or more SMT frame classes (used to filter output)
If you do not specify an interface, pf_smtmon(1M) or nf_smtmon(1M) returns the SMT frames received by pf0. If you do not specify a frame type, pf_smtmon displays all the SMT frames that it receives. Use Ctrl-C to stop pf_smtmon(1M) or nf_smtmon(1M).
To display the encoded SMT frames received by interface pf1, type:
# <basedir>/pf_smtmon -i pf1 pf1: nif_request v=0x1 t=0xfc03e781 s=10-0-4-48-6f-a5 i=0x28 pf1: nif_response v=0x1 t=0xfc03e781 s=10-0-4-8-24-5c i=0x28 pf1: nif_request v=0x1 t=0xfc00dec6 s=10-0-4-b8-6e-ab i=0x28 pf1: nif_request v=0x1 t=0xfc03e787 s=10-0-4-48-6f-a5 i=0x28 pf1: nif_response v=0x1 t=0xfc03e787 s=10-0-4-8-24-5c i=0x28
The elements of the SMT frames are defined as follows:
Table 2-5 Elements of the SMT Frames| Element | Definition |
|
class_type |
Identifies the SMT frame class and type (see "SMT Frame Classes and Types") |
|
v |
Version ID; identifies the structure of the SMT information field |
|
t |
Transaction ID; used to pair SMT response and request frames |
|
s |
Station ID; uniquely identifies the station transmitting the frame |
|
i |
InfoField Length; defines the length of the SMT information field |
-
To display the SMT frames received by interface pf1 in hexadecimal format, type:
# <basedir>/pf_smtmon -i pf1 -x pf1: nif_request v=0x1 t=0x170 s=10-0-4-8-24-5c i=0x28 004DC000 0000004F FFFFFFFF FFFF1000 0408245C 01020001 00000170 00001000 0408245C 00000028 00010008 00001000 04B86EAB 00020004 00010100 00030004 00002100 200B0008 00000001 00000001 76C467A0 pf1: nif_request v=0x1 t=0x5e0f s=10-0-d4-78-42-4d i=0x28 004D0000 0000004F FFFFFFFF FFFF1000 D478424D 01020001 00005E0F 00001000 D478424D 00000028 00010008 00001000 0408245C 00020004 01010208 00030004 00001200 200B0008 0000000B 00000002 A522BBA1 pf1: nif_response v=0x1 t=0xfc00d94a s=10-0-4-8-24-5c i=0x28 004D0000 00000041 100004B8 6EAB1000 0408245C 01030001 FC00D94A 00001000 0408245C 00000028 00010008 00001000 04B86EAB 00020004 00010100 00030004 00002100 200B0008 00000001 00000001 865549E2 0049C020 F0154E4F FFFFFFFF FFFF1000 04B86EAB 01020001 FC00D94A 00001000 04B86EAB 00000028 00010008 00001000 D478424D 00020004 00010100 00030004 00002000 200B0008 00000001 00000001 pf1: nif_request v=0x1 t=0x5e13 s=10-0-d4-78-42-4d i=0x28 004D0000 0000004F FFFFFFFF FFFF1000 D478424D 01020001 00005E13 00001000 D478424D 00000028 00010008 00001000 0408245C 00020004 01010208 00030004 00001200 200B0008 0000000B 00000002 4AD75A79 pf1: nif_request v=0x1 t=0x5e17 s=10-0-d4-78-42-4d i=0x28 004D0000 0000004F FFFFFFFF FFFF1000 D478424D 01020001 00005E17 00001000 D478424D 00000028 00010008 00001000 0408245C 00020004 01010208 00030004 00001200 200B0008 0000000B 00000002 DCEBADA2 pf1: nif_request v=0x1 t=0x171 s=10-0-4-8-24-5c i=0x28 004DC000 0000004F FFFFFFFF FFFF1000 0408245C 01020001 00000171 00001000 0408245C 00000028 00010008 00001000 04B86EAB 00020004 00010100 00030004 00002100 200B0008 00000001 00000001 127B1D3B pf1: nif_request v=0x1 t=0x5e1b s=10-0-d4-78-42-4d i=0x28 004D0000 0000004F FFFFFFFF FFFF1000 D478424D 01020001 00005E1B 00001000 D478424D 00000028 00010008 00001000 0408245C 00020004 01010208 00030004 00001200 200B0008 0000000B 00000002 626FA878
SMT Frame Classes and Types
SMT frames are used for peer-to-peer (station-to-station) management. They are divided into classes, which define the function of the frame. Each class is then divided into up to three types, which define whether the frame is an announcement (information only), a request for service, or a response to a request. Refer to the ANSI/FDDI Station Management (SMT) X3.299 R7.3 Specification for a detailed description of SMT frames and their functions.
The pf_smtmon(1M) or nf_smtmon(1M) utility is used to monitor the following SMT frame classes:
NIF (Neighbor Information Frames)
These are the most common frames displayed when you run pf_smtmon(1M) or nf_smtmon(1M). As the name suggests, they carry information about a neighboring station (for example, address, description, state, MAC capabilities) and are used as keep-alive notifications that a station is still attached to the ring and functioning. An NIF frame can be an announcement, a request, or a response.
SIF (Status Information Frames)
These frames carry more detailed information about a station. SIF configuration frames describe the station configuration (for example, number of ports, number of MAC entities, connection policy). SIF operation frames describe the current status of the station. A SIF frame can be either a request or a response.
ECF (Echo Frames)
These frames are equivalent to ICMP ping packets and are used to test connectivity between stations. An ECF frame can be either a request or a response.
RDF (Request Denied Frame)
These frames are used to indicate that the request is rejected. If an SMT agent (such as the SunNet Manager proxy agent delivered with SunFDDI) receives an unsupported or unrecognized request, it issues an RDF frame to indicate that the request is rejected. An RDF frame is always a response.
ESF (Extended Service Frame)
These frames are implementation dependent. An ESF frame can be an announcement, a request, or a response.
PMF (Parameter Management Frame)
These frames are used to access remote station attributes. The Parameter Management Protocol supports both get (display) and set (modify) functions. However, the pf_smtmon(1M) or nf_smtmon(1M) utility can display only PMF_get frames. A PMF_get frame can be either a request or a response.
- © 2010, Oracle Corporation and/or its affiliates