Documenting adjacency failures
The following documentation should be available for initial
diagnosis of adjacency failures:
- MVS™ system log
- SYSLOGD
- The data set containing OMPROUTE trace and debug information, unless trace and debug information is being redirected to the OMPROUTE CTRACE internal buffer, which is automatically included in a dump of the OMPROUTE address space. For details, see OMPROUTE traces and debug information.
- TCP/IP and OMPROUTE CTRACE. For information about generating an OMPROUTE Component Trace, see TCP/IP services component trace for OMPROUTE.
- Output from appropriate OMPROUTE DISPLAY commands as described
in z/OS Communications Server: IP System Administrator's Commands.
Use the DISPLAY TCPIP,,OMROUTE,OPTIONS command to display the global configuration options.
If using IPv4, use the following commands to display OSPF configuration, interfaces, neighbors, and routing table:- DISPLAY TCPIP,,OMPROUTE,OSPF,LIST,ALL
- DISPLAY TCPIP,,OMPROUTE,OSPF, INTERFACES
- DISPLAY TCPIP,,OMPROUTE,OSPF, INTERFACE,NAME=if_name
- DISPLAY TCPIP,,OMPROUTE,OSPF,NEIGHBOR
- DISPLAY TCPIP,,OMPROUTE,OSPF,NEIGHBOR,IPADDR=ip-addr
- DISPLAY TCPIP,,OMPROUTE,RTTABLE
If using IPv6, use the following commands to display OSPF configuration, interfaces, and neighbors, and routing table:- DISPLAY TCPIP,,OMPROUTE,IPV6OSPF,ALL
- DISPLAY TCPIP,,OMPROUTE,IPV6OSPF, INTERFACES
- DISPLAY TCPIP,,OMPROUTE,IPV6OSPF, INTERFACE,NAME=if_name [Note: ID=if-id can be used instead of NAME parameter]
- DISPLAY TCPIP,,OMPROUTE,IPV6OSPF,NEIGHBOR
- DISPLAY TCPIP,,OMPROUTE,IPV6,NEIGHBOR,ID=router-id [Note: IFNAME=if_name can be used instead of ID parameter]
- DISPLAY TCPIP,,OMPROUTE,RT6TABLE
- When applicable, the dumps of TCPIP and VTAM® address spaces. A SLIP on OMPROUTE adjacency failing message (for example, EZZ7921I ) may be used to capture the OMPROUTE trace and debug information as well as the dumps of TCPIP and VTAM address spaces at the time of the error.