Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...
Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ... Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...
60Picture Perfect 4.6 Enterprise EditionUser ManualAlarmsThe Picture Perfect Enterprise configuration provides the following alarms on the nethost:• Host to Host Comm Fail: Occurs when the network connection between the nethost and asubhost is broken, or when a host goes down.• Remote Database Connect Error: Occurs when the remote Informix databases cannot bereached.All alarms that are routed to the Alarm Monitor on each of the subhosts are also automaticallyforwarded to the nethost’s Alarm Monitor. Therefore the nethost’s Alarm Monitor displays all activeand pending alarms for the entire system.Enterprise Replication introduces four pre-defined logical alarms and associated input groups:• Sequence Object 90% full• Aborted Transaction (conflicts) reported• ER Server stopped or suspended• Server clock out of syncFor more information about these alarms, see Which new alarms are introduced and howdo I proceed if those alarms display in the Alarm Monitor? on page 113The alarm for exceeding 90% of database space now includes a check for the ER database spaces(entrepdbs and entrepsbs).Database scheduled jobs (tasks/sensor), cron jobs, or the database itself catch these conditions andtrigger the alarms. The new alarms and input_group data are added to the system during netlanand subhost installation.These alarms do not have a reset state because it is not possible to detect a "resolved" state versusa "normal good" state. Once the alarmed issue has been resolved, the operator has to respond tothe alarm and/or delete the alarm manually.
Chapter 4Managing your network database61Network alarm monitorThe Network Alarm Monitor feature allows the operator to view and respond to local and remotealarms on the nethost. The Network Alarm Monitor does not require any type of specialconfiguration. All the subhosts that are in the network must be defined in the Hosts table of PicturePerfect and in the /etc/hosts file. See Enterprise system software installation on page 7 fordetails.All alarms that are routed to the Alarm Monitor on each of the subhosts are forwarded automaticallyto the nethost. An operator on the nethost can respond to remote alarms as well as to local alarms.For remote alarms, the Network Alarm Monitor obtains the alarm instructions and responses from thesubhosts.Notes: To view Alarm Instructions, for alarms originated at a subhost, the operator must be defined as anoperator on the subhost as well. Alarms are filtered to the display based on facilities. For furtherinformation on Alarm Filtering, refer to the Picture Perfect 4.6 User Manual, System Parameters Form.The Network Alarm Monitor indicates that the operator is responding to a remote alarm, and theRSVP button can be used to respond. All responses entered on the nethost are sent to the subhostwhere the alarm originated. Remote responses are logged to alarm history on the subhost.All alarm history from all subhosts is uploaded to the nethost alarm history after a predetermined timeinterval. This is accomplished using subhost polling (see Refreshing database history tables onpage 51 for more information).If any subhost is not online with the nethost, its alarms are not reflected on the Network AlarmMonitor as they occur. When the subhost is restarted and is back online with the nethost, all subhostalarms are forwarded to the Network Alarm Monitor. When the nethost recovers from acommunications failure, it queries the subhosts for their alarms and displays them on the NetworkAlarm Monitor.Notes: Define each subhost’s alarms with a description of the alarm origin on the Network Alarm Monitor.Alarm instructions and responses should be defined for subhost operators and nethost operators.Figure 5. Remote Alarm-Response Window
- Page 17 and 18: Chapter 2Installing the Picture Per
- Page 19 and 20: Chapter 2Installing the Picture Per
- Page 21 and 22: Chapter 2Installing the Picture Per
- Page 23 and 24: Chapter 2Installing the Picture Per
- Page 25 and 26: Chapter 2Installing the Picture Per
- Page 27 and 28: Chapter 2Installing the Picture Per
- Page 29 and 30: Chapter 2Installing the Picture Per
- Page 31 and 32: Chapter 2Installing the Picture Per
- Page 34 and 35: 26Picture Perfect 4.6 Enterprise Ed
- Page 36 and 37: 28Picture Perfect 4.6 Enterprise Ed
- Page 38 and 39: 30Picture Perfect 4.6 Enterprise Ed
- Page 40 and 41: 32Picture Perfect 4.6 Enterprise Ed
- Page 42 and 43: 34Picture Perfect 4.6 Enterprise Ed
- Page 44 and 45: 36Picture Perfect 4.6 Enterprise Ed
- Page 46 and 47: 38Picture Perfect 4.6 Enterprise Ed
- Page 48 and 49: 40Picture Perfect 4.6 Enterprise Ed
- Page 50 and 51: 42Picture Perfect 4.6 Enterprise Ed
- Page 52 and 53: 44Picture Perfect 4.6 Enterprise Ed
- Page 54 and 55: 46Picture Perfect 4.6 Enterprise Ed
- Page 56 and 57: 48Picture Perfect 4.6 Enterprise Ed
- Page 58 and 59: 50Picture Perfect 4.6 Enterprise Ed
- Page 60 and 61: 52Picture Perfect 4.6 Enterprise Ed
- Page 62 and 63: 54Picture Perfect 4.6 Enterprise Ed
- Page 64 and 65: 56Picture Perfect 4.6 Enterprise Ed
- Page 66 and 67: 58Picture Perfect 4.6 Enterprise Ed
- Page 70 and 71: 62Picture Perfect 4.6 Enterprise Ed
- Page 72 and 73: 64Picture Perfect 4.6 Enterprise Ed
- Page 74 and 75: 66Picture Perfect 4.6 Enterprise Ed
- Page 76 and 77: 68Picture Perfect 4.6 Enterprise Ed
- Page 78 and 79: 70Picture Perfect 4.6 Enterprise Ed
- Page 80 and 81: 72Picture Perfect 4.6 Enterprise Ed
- Page 82 and 83: 74Picture Perfect 4.6 Enterprise Ed
- Page 84 and 85: 76Picture Perfect 4.6 Enterprise Ed
- Page 86 and 87: 78Picture Perfect 4.6 Enterprise Ed
- Page 88 and 89: 80Picture Perfect 4.6 Enterprise Ed
- Page 90 and 91: 82Picture Perfect 4.6 Enterprise Ed
- Page 92 and 93: 84Picture Perfect 4.6 Enterprise Ed
- Page 94 and 95: 86Picture Perfect 4.6 Enterprise Ed
- Page 96 and 97: 88Picture Perfect 4.6 Enterprise Ed
- Page 98 and 99: 90Picture Perfect 4.6 Enterprise Ed
- Page 100 and 101: 92Picture Perfect 4.6 Enterprise Ed
- Page 102 and 103: 94Picture Perfect 4.6 Enterprise Ed
- Page 104 and 105: 96Picture Perfect 4.6 Enterprise Ed
- Page 106 and 107: 98Picture Perfect 4.6 Enterprise Ed
- Page 108 and 109: 100Picture Perfect 4.6 Enterprise E
- Page 110 and 111: 102Picture Perfect 4.6 Enterprise E
- Page 112 and 113: 104Picture Perfect 4.6 Enterprise E
- Page 114 and 115: 106Picture Perfect 4.6 Enterprise E
- Page 116 and 117: 108Picture Perfect 4.6 Enterprise E
60<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong><strong>User</strong> <strong>Manual</strong>AlarmsThe <strong>Picture</strong> <strong>Perfect</strong> <strong>Enterprise</strong> configuration provides the following alarms on the nethost:• Host to Host Comm Fail: Occurs when the network connection between the nethost and asubhost is broken, or when a host goes down.• Remote Database Connect Error: Occurs when the remote Informix databases cannot bereached.All alarms that are routed to the Alarm Monitor on each of the subhosts are also automaticallyforwarded to the nethost’s Alarm Monitor. Therefore the nethost’s Alarm Monitor displays all activeand pending alarms for the entire system.<strong>Enterprise</strong> Replication introduces four pre-defined logical alarms and associated input groups:• Sequence Object 90% full• Aborted Transaction (conflicts) reported• ER Server stopped or suspended• Server clock out of syncFor more information about these alarms, see Which new alarms are introduced and howdo I proceed if those alarms display in the Alarm Monitor? on page 113The alarm for exceeding 90% of database space now includes a check for the ER database spaces(entrepdbs and entrepsbs).Database scheduled jobs (tasks/sensor), cron jobs, or the database itself catch these conditions andtrigger the alarms. The new alarms and input_group data are added to the system during netlanand subhost installation.These alarms do not have a reset state because it is not possible to detect a "resolved" state versusa "normal good" state. Once the alarmed issue has been resolved, the operator has to respond tothe alarm and/or delete the alarm manually.
Change language