Interpreting traps and errors – Sun Microsystems 1.0 User Manual

Page 140

Advertising
background image

114

SunFDDI/P 1.0 Adapter User’s GuideMay 1997

9

Interpreting Traps and Errors

One of the most important functions of the SunNet Manager agent for
SunFDDI/P is to signal the occurrence of faults or errors on the network.
Traps are sent to the consoles that you specified when you ran the

pf_install_agents

script to install the agents on the client machine. See “To

Install the FDDI Schemas on a Client” on page 105 for detailed instructions.

When a cable or station fault occurs, it is signaled by the neighboring station
and not by the station implicated by the fault; however, the information
provided in the trap report sent to the console allows you to identify the
probable source of the problem. Faults often generate a series of trap events
that are caused when the ring reconfigures itself automatically.

The reason for repeated errors and lost frames is more difficult to identify
because the fault is signaled by the first system to receive the error frame,
which is not necessarily the station closest to the problem.

The trap report in Figure 9-6 was generated by the upstream neighbor
after the cable between a single-attached station and a concentrator was
disconnected. All MAC addresses are displayed in ring format.

Figure 9-6

Single-Attached Station Disconnected

SRF_Source=rully

TransitionTimeStamp: Parameter_Type=0x1034

Transition_TimeStamp.Hi=101

Transition_TimeStamp.Lo=3640570640

MAC Neighbor Change Event: Parameter_Type=0x208f

Mac_Index=1

Multiple_Occurrence=0

NA_Condition=2

Old_UNA=0-1-1b-8-10-92

New_UNA=arbois

Old_DNA=europe

New_DNA=10-0-4-b8-6e-ab

Current_path=3

SMT_Address=rully

Source of trap report ------>
(neighbor to fault)

Trap indicates change
of neighbor ----------------->

Station disconnected ------
>
addr of new neighbor ------>

Advertising