z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


EZZ7912I

z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM)
SC27-3657-01

EZZ7912I
No FSM match, interface interface, state state, event event

Explanation

The specified event occurred while an interface was in the specified state. This occurrence is not covered by the interface Finite State Machine. This often occurs because of harmless timing windows. For example, a hello timer pops for a neighbor with whom adjacency was already lost.

state is the Interface State Code. The Interface State Codes are described in RFC 2328. See Related protocol specifications for directions to get a copy of the RFC. The Interface State Codes can be one of the following:
1
Down
1*
Suspend. This state is not described in RFC2328. The interface is suspended for one of the following reasons:
  • You issued a MODIFY command.
  • After the interface exceeded the futile neighbor state loop threshold (DR_Max_adj_Attempt), the interface was unable to establish an adjacency with a neighboring designated router.

See the network design considerations with z/OS® Communications Server information in z/OS Communications Server: IP Configuration Guide for more information about futile neighbor state loops.

2
Backup. This state is not described in RFC 2328. When more than one OSPF interface is defined to the same subnet, only one of the interfaces can be primary, meaning that it will be the interface to carry the OSPF protocol traffic between OMPROUTE and the subnet. All other interfaces to the same subnet will be in this state. Failure of the primary interface will result in automatic switching of OSPF traffic to one of the backup interfaces.
4
Loopback
8
Waiting
16
Point-to-point
32
DROther
64
DRBackup
128
DR

event is the Interface Event Code. The Interface Event Codes are described in RFC 2328. See Related protocol specifications for directions to get a copy of the RFC. The Interface Event Codes can be one of the following:

1
InterfaceUp
2
WaitTimer
3
BackupSeen
4
NeighborChange
5
LoopInd
6
UnloopInd
7
InterfaceDown
8
BackupUp. This state is not described in RFC 2328. Lower-level protocols have indicated that the network interface is operational. This interface is one of multiple OSPF interfaces defined to the same subnet and it is not the primary interface (the interface to carry the OSPF protocol traffic between OMPROUTE and the subnet). The interface will transition to Backup state.
9
InterfaceSuspend. This event is not described in RFC2328. The interface is suspended for one of the following reasons:
  • You issued a MODIFY command.
  • After the interface exceeded the futile neighbor state loop threshold (DR_Max_adj_Attempt), the interface was unable to establish an adjacency with a neighboring designated router.

See the network design considerations with z/OS Communications Server information in z/OS Communications Server: IP Configuration Guide for more information about futile neighbor state loops.

10
InterfaceActivate. This event is not described in RFC2328. The interface is activated for one of the following reasons:
  • You issued a MODIFY command.
  • The interface can now establish adjacency with a neighboring designated router.
The interface will transition to one of the states other than 1 (Down).

See the network design considerations with z/OS Communications Server information in z/OS Communications Server: IP Configuration Guide for more information about futile neighbor state loops.

System action

The event is ignored.

Operator response

None.

System programmer response

None

Module

SPFIFC, EZA6RSFF

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014