|
|
This chapter describes the Maps event notification messages. The APPN and DLSw Maps applications send event notification messages to the workstation network management system (NMS) when changes in network status occur. Currently, the event notification messages are sent as traps to the NMS. Event notification is controlled by the event values that are kept in the cwbinit file. For more information, see the section "Using the cwbinit Preferences File" in the "Using the DLSw Application" chapter, and the section "Using the cwbinit Preferences File" in the "Using the APPN Application" chapter.
Each notification message has an 8-character message ID followed by a text string. The message ID has the syntax shown in Figure 8-1.
Where:
Severity indicates the severity of the problem that caused the message to be issued.
Message number is a three-digit message identification number.
Protocol is a two-character protocol ID that indicates to which protocol the event notification message applies:
Program is a two-character program ID that indicates which program issued the message:
This section lists the messages in numerical order, by their message IDs. The messages are listed in the following sections:
The following messages are issued by either runappn or runappnpoller.
dlur_node is the DLUR node.
dlus_node is the DLUS node.
Explanation
An APPN DLUR node (dlur_node) has established a CPSVRMGR session with the DLUS node (dlus_node), and the eventgen_dlur event value in the cwbinit file is set to ON.
dlur_node is the DLUR node.
dlus_node is the DLUS node.
Explanation
An APPN DLUR node (dlur_node) has lost a CPSVRMGR session with the DLUS node (dlus_node), and the eventgen_dlur event value in the cwbinit file is set to ON.
dlur_node is the DLUR node.
dlus_node is the DLUS node.
dlur_node is the DLUR node.
dlus_node is the DLUS node.
Explanation
The definition of an APPN DLUR node (dlur_node) has been deleted to the DLUS node (dlus_node), and the eventgen_dlur event value in the cwbinit file is set to ON.
tg_number is the TG number.
cp_name_1 is the CP name of the first node.
cp_name_2 is the CP name of the second node.
Explanation
An APPN network CP-CP transmission group (tg_number) from the node identified as cp_name_1 to the node identified as cp_name_2 has become operational, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
cp_name_1 is the CP name of the first node.
cp_name_2 is the CP name of the second node.
Explanation
An APPN network CP-CP transmission group (tg_number) from the node identified as cp_name_1 to the node identified as cp_name_2 has become inactive, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
cp_name_1 is the CP name of the first node.
cp_name_2 is the CP name of the second node.
Explanation
An APPN endpoint CP-CP transmission group (tg_number) from the node identified as cp_name_1 to the node identified as cp_name_2 has become operational, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
cp_name_1 is the CP name of the first node.
cp_name_2 is the CP name of the second node.
Explanation
An APPN endpoint CP-CP transmission group (tg_number) from the node identified as cp_name_1 to the node identified as cp_name_2 has become inactive, and the eventgen_tg event value in the cwbinit file is set to ON.
node_name is the APPN node.
clink_name is the link name.
Explanation
On an APPN node (node_name), a link (link_name) has become active, and the eventgen_link event value in the cwbinit file is set to ON.
nnode_name is the APPN node.
clink_name is the link name.
Explanation On an APPN node (node_name), a link (link_name) has become inactive, and the eventgen_link event value in the cwbinit file is set to ON.
node_name is the APPN node.
clink_name is the link name.
Explanation On an APPN node (node_name), a link (link_name) has been deleted, and the eventgen_link event value in the cwbinit file is set to ON.
node_name is the APPN node.
port_name is the port name.
Explanation On an APPN node (node_name), a port (port_name) has become active, and the eventgen_port event value in the cwbinit file is set to ON.
node_name is the APPN node.
port_name is the port name.
node_name is the APPN node.
port_name is the port name.
Explanation On an APPN node (node_name), a port (port_name) has become inactive, and the eventgen_port event value in the cwbinit file is set to ON.
node_name is the APPN node.
port_id is the port ID.
Explanation On an APPN node (node_name), a port (port_id) has been deleted, and the eventgen_port event value in the cwbinit file is set to ON.
tg_number is the TG number.
node_name_1 is the name of the first node.
node_name_2 is the name of the second node.
Explanation An APPN network transmission group without CP-CP sessions (tg_number), from node_name_1 to node_name_2 has become operational, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
node_name_1 is the name of the first node.
node_name_2 is the name of the second node.
Explanation An APPN network transmission group without CP-CP sessions (tg_number), from node_name_1 to node_name_2 has become inactive, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
node_name_1 is the name of the first node.
node_name_2 is the name of the second node.
Explanation An APPN endpoint transmission group without CP-CP sessions (tg_number), from node_name1 to node_name2 has become operational, and the eventgen_tg event value in the cwbinit file is set to ON.
tg_number is the TG number.
node_name_1 is the name of the first node.
node_name_2 is the name of the second node.
Explanation An APPN endpoint transmission group without CP-CP sessions (tg_number), from node_name1 to node_name2 has become inactive, and the eventgen_tg event value in the cwbinit file is set to ON.
The following messages are issued by either APPN or DLSw.
router is a router name or IP address.
Explanation An APPN or DLSw router has stopped responding to an SNMP network management poll, and the eventgen_device event value in the cwbinit file is set to ON.
router is a router name or IP address.
Explanation
An APPN or DLSw router (router is the host name or IP address of a router) has started responding to an SNMP network management poll, and the eventgen_device event value in the cwbinit file is set to ON.
The following messages are issued by cwbdlswpollerd, which is started by the rundlsw script. You can also start cwbdlswpollerd from the command prompt, as described in the appendix "CiscoWorks Blue Maps Daemons and Processes."
router1 is the host name or IP address of the first router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation A DLSw router (router1 ) has established a new peer connection with another DLSw router (router2), and the eventgen_dlswpeercxn event value in the cwbinit file is set to ON.
router1 is the host name or IP address of the first router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation A DLSw router (router1) has lost a peer connection with another DLSw router (router2), and the eventgen_dlswpeercxn event value in the cwbinit file is set to ON.
router1 is the host name or IP address of the first router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation A DLSw router (router1 ) recovered a broken peer connection with another DLSw router (router2), and the eventgen_dlswpeercxn event value in the cwbinit file is set to ON.
router1 is the host name or IP address of the first router.
local_mac is the MAC of the local router.
local_sap is the SAP of the local router.
remote_mac is the MAC of the remote router.
remote_sap is the SAP of the remote router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation
A DLSw router (router1) has established a new DLSw circuit with another DLSw router (router2). The circuit is specified by the local_mac, local_sap, remote_mac, and remote_sap. The eventgen_dlswcircuit event value in the cwbinit file is set to ON.
router1 is the host name or IP address of the first router.
local_mac is the MAC of the local router.
local_sap is the SAP of the local router.
remote_mac is the MAC of the remote router.
remote_sap is the SAP of the remote router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation
A DLSw router (router1) has lost a DLSw circuit with another DLSw router (router2). The circuit is specified by the local_mac, local_sap, remote_mac, and remote_sap. The eventgen_dlswcircuit event value in the cwbinit file is set to ON.
router1 is the host name or IP address of the first router.
local_mac is the MAC of the local router.
local_sap is the SAP of the local router.
remote_mac is the MAC of the remote router.
remote_sap is the SAP of the remote router.
router2 is the host name or IP address of the second router. This value can also be ? if the second router's IP address is 0.
Explanation
A DLSw router (router1) has recovered a DLSw circuit with another DLSw router (router2). The circuit is specified by the local_mac, local_sap, remote_mac, and remote_sap. The eventgen_dlswcircuit event value in the cwbinit file is set to O N.
pu_name is the name of a PU.
value is the hexadecimal IDBLK/IDNUM value.
Explanation
SNA View found a PU (pu_name) whose hexadecimal IDBLK/IDNUM value is already in the database for another PU name. This could happen if you changes the VTAM definitions of the PUs, or it can happen if there is a problem with the VTAM definition for one of these PUs.
Posted: Thu Aug 19 11:01:26 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.