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


EZZ8157I

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

EZZ8157I
jobname ipversion OSPF detected futile neighbor state loop with neighbor neighbor on interface interface after threshold_value adjacency attempts

Explanation

This event was generated for the neighboring designated router (specified by the neighbor value), which exceeded the loop threshold for the number of adjacency attempts allowed before reaching full adjacency. This event might be caused by a problem with remote networking hardware. If OMPROUTE finds a redundant parallel interface (primary or backup) that can reach the same neighbor in the LAN, OMPROUTE changes the interface state to SUSPEND and issues message EZZ8158I to indicate that OMPROUTE will attempt to establish an adjacency over the redundant interface. If OMPROUTE does not find a redundant parallel interface, OMPROUTE continues to attempt to establish an adjacency to that neighbor over the same interface. 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.

In the message text:
jobname
The name of the OMPROUTE application.
ipversion
The IP version that OSPF is running. Possible values for ipversion are:
IPv6
OSPF for IPv6
IPv4
OSPF for IPv4
neighbor
neighbor is one of the following:
  • The interface address of the neighboring OSPF router, if the ipversion value is IPv4.
  • The router ID of the neighboring OSPF router, if the ipversion value is IPv6.
interface
The name of the local interface over which OMPROUTE failed to form an adjacency with the specified neighbor.
threshold_value
The neighbor state loop threshold value for the number of adjacency attempts with a specified neighbor.

System action

OMPROUTE continues and tries to establish an adjacency with the neighbor over the same interface or over a redundant parallel interface (primary or backup), if one is available.

Operator response

Contact the system programmer

System programmer response

If connectivity problems persist, investigate the reason that the adjacency could not be established. Inspect the remote networking hardware components, such as routers, switches, or cabling, that might contribute to the problem.

User response

Not applicable.

Problem determination

See the system programmer response.

Source

z/OS Communications Server TCP/IP: OMPROUTE

Module

SPFNBR, EZA6RSPB

Routing code

10

Descriptor code

12

Automation

This message goes to the console or syslog.

Example

For IPv4:
EZZ8157I OMPROUTE IPv4 OSPF detected futile neighbor state loop with  neighbor 10.1.1.2 on 
         interface OSAGBE1 after 10 adjacency attempts 
For IPv6:
EZZ8157I OMPROUTE IPv6 OSPF detected futile neighbor state loop with  neighbor 10.1.1.5 on 
         interface OSAGBE1 after 10 adjacency attempts  

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014