A REMOTE ALERT CANNOT BE HANDLED ON MTC-NM IF NM LINK IS DOWN
Article ID: 122280
Updated On:
Products
CMDB for z/OS
NetSpy Network Performance
NetMaster Network Automation
SOLVE
NetMaster Network Management for SNA
NetMaster Network Management for TCP/IP
NetMaster File Transfer Management
Issue/Introduction
From a colleague on the field:
There is a problem when MTC-NM has an alert published IF the alert's
origin NM region link with the (NM) MTC-NM region publishing the
alert is dropped or is recycled. The alert is left FROZEN on the
(NM) MTC-NM publishing it.
-
Support note: This happened there with a SEV1 alert--it was reporting
exactly that: The link had come down.
There is a problem when MTC-NM has an alert published IF the alert's
origin NM region link with the (NM) MTC-NM region publishing the
alert is dropped or is recycled. The alert is left FROZEN on the
(NM) MTC-NM publishing it.
-
Support note: This happened there with a SEV1 alert--it was reporting
exactly that: The link had come down.
Environment
OS: z/OS.
Resolution
SE raised SO06141 plus instructions on how to set up $GLBL LINKAL OFF
(on NMINIT) were e-mailed out--and tested successfully.
(on NMINIT) were e-mailed out--and tested successfully.
Feedback
Yes
No
Powered by
