ASYDEBUG Commands
Asybdeug - Definition
Asydebug is a tool available with all version of Insight APOGEE to provide information regarding traffic being processed by the Insight Async service.
Syntax of Asydebug
The syntax of Asydebug is asydebug <servername> Debugnumber
where
- x <servername> is the name of the PC where the Async service is currently running. If you do not specify a servername, then asydebug will display data from the PC the command is executed from.
- x DebugNumber an option that displays various data collected by the Insight Async Service.
Syntax Examples
- A system consists of one PC named APOGEEDB. Async service is running on this PC. The syntax to run the command is asydebug DebugNumber . Note that a servername was not specified since the PC the command is being executed from is where the Insight Async Service is running on.
- A system consists of 3 PCs; APOGEEDB is the database server hosting the Insight Async service, and APOGEECLT1 and APOGEECLT2 are two APOGEE clients. You are logged on to APOGEECLT2 PC and want to ldisplay the asydebug data from APOGEEDB PC. The syntax is asydebug APOGEEDB DebugNumber . Note that the APOGEEDB was specified since the command was run from another PC.
- A system consists of 3 PCs; both APOGEEDB and APOGEECNT1 have an ALN attached to them which would mean that the Insight Async service is running on both PCs. APOGEECLT2 is a client PC with no ALNs. Below are several syntax examples for this scenario:
- o Sitting at APOGEDB and requesting Async data from APOGEEDB asydebug <DebugNumber>
- o Sitting at APOGEDB and requesting Async data from APOGEECLT1 asydebug APOGEECLT1 <DebugNumber>
- o
- Sitting at APOGECLT1 and requesting Async data from APOGEEDB asydebug APOGEEDB <DebugNumber>
- o Sitting at APOGECLT1 and requesting Async data from APOGEECLT1
asydebug <DebugNumber>
- o Sitting at APOGECLT2 and requesting Async data from APOGEEDB asydebug APOGEEDB <DebugNumber>
- o Sitting at APOGEECLT2 and requesting Async data from APOGEECLT1 asydebug APOGEECLT1 <DebugNumber>
Asydebug <DebugNumber> options
Below is a list of the available options with the asydebug command
C:\Windows\System32>asydebug Usage:asydebug [<SeruerName>] <DebugNumber> where<SeruerName> is the name of the computer if not there, this computer will be chosen where <DebugNumber> can take one of the ualues: 1=C0Us:points pool + registered applications 2 Alarms:-registered applications 3 Alarms:pending alarm pool Loader Status:-registered applications 5 Loader: pending euents + registered loader 6 = registered applications 了 三 registered applications 8 = Operator Msgs:--registered applications 9 = Statistic:-counters 10 RPC:known applications addresses 11 Global Data Inds:--registered applications 80..89= DebugLeuel:leuel 0 through 9 100 三 190 Tests, call RPC seruer holds RPc for 5 minutes seruer exits !!!! 197 = delay=10 seconds 198 = delay=1 second 199 二 delay=0 200 =XTS statistic:C:\Windows\System32>
The list below is a brief explanation of the options. Subsequent Tech Tips will dive into more details on how to use the data to identify anomalies with the APOGEE system. Please note that not all options are relevant for troubleshooting APOGEE issues. Only the relevant <DebugNumber> will be discussed below:
Asydebug 1
Asydebug 1 lists all points that are currently registered with the Async service to receive COVs along with which application is requesting the COV. Examples of applications that may request COV data are: Graphics, CrossTrunk, OPC, Dynamic Plotter etc. Below is an example out the output of an asyndebug 1 command:
C:\>asydebug 1 Printing async server Cov Reg info (4 covs stored) 1. <MBC87 AI05 1 TEMP> received: 37 distributed: 73 <:> DATA Val = 69.92, COV STATUS OK <:> NORMAL val = 69.92, stat= <:> ENH ALARM enh = pri= 0, dir= -1 <:> IN SVC stat= <:> PT FAIL RET <:> PROOF OFF stat= <:> OUT OF HAND MODE <:> CMD PRI cmdpri= 0 Registered App: \\APoGEE1\1\graphic 2. <MBC87AI05 2 TEMP> received: 12 distributed: 23 <:> DATA Va1 = 69.75, C0V STATUS OK <:> NORMAL val = 69.75, stat= <:> ENH ALARM enh = pri= 0, dir= -1 <：> IN SVC stat= <：> PT FAIL RET <:> PROOF OFF stat= <:> LnO OF HAND MODE <：> CMD PRI cmdpri= 0 Reqistered App:\APoGEEl\1\graphic
Asydebug 2
Asydebug 2 lists all the applications that are currently registered to receive alarms from the Insight Async service. Examples are Alarm, Graphics, Reno, DBCS Server, EventLog etc.
C:\>asydebug 2 Printing async server Alarm Reg info 1: \\APOGEE1\0\EventLogSvc 2:\\APOGEE1\0\DBCSSerVer 3: \\APOGEEl\0\InsiqhtRENOServer 4: \\APOGEE1\0\alarm 5: \APOGEE1\1\alarm 6: \\APOGEE1\1\graphic 7: \\APOGEE1\0\graphic
Asydebug 3
Asydebug 3 lists all the points that are currently in Alarm, Alarm Ack, or Normal but not acknowledged states.
C:\>asydebug 3 = Printing async server Alarm Pool info (125 alarms stored) 1: Alarm Ack, N: BAC 1 AI 1: U: SYS, Ta: 10/06/11 10:08:09 2: *** Alarm Ack, N: BAC 1 EE 2: U: SYS, Ta: 10/06/11 11:39:18 3: *** Alarm Ack, N: BAC 1 EE U: SYS, Ta: 10/06/11 11:39:55 4 *** Alarm Ack, N: BAC 17002 EE 1:, U: ADMN, Ta: 12/14/11 12:20:27 5: *** Alarm Ack, N: BAC EE U: SYS, Ta: 10/26/11 15:55:03 6: *** Alarm Ack, N: BAC 5 EE 1:. U: SYS, Ta: 10/07/11 08:51:29 7： *** Alarm Ack, N: BAC 5 AI 1:, U: SYS, Ta: 10/18/11 09:23:44 8: *** Alarm Ack, N: test lao 01:, U: ADMN, Ta: 05/04/12 08:47:58 9: *** Alarm Ack, N: BAC 7016 EE 0:, U: SYS, Ta: 06/29/12 10:04:28 10: *** Alarm Ack, N: ER14ZT:, U: ADMN, Ta: 01/21/13 14:33:01
Asydebug 9
Asydebug 9 provides statistics on the number of events that Async has processed since the start of the service.
| C:>asydebug | 7759523 | 0 | RPC statistics | ||||
|---|---|---|---|---|---|---|---|
| RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics | RPC packets in 0 out: 0 Event Indications queue statistics |
| Events received | 1181306 0 | (max) : | 70 | ||||
| Alarms received | dist.: | 116 | at 01/31/15 13:50:51 | ||||
| Alarm statistics | Alarm statistics | Alarm statistics | Alarm statistics | Alarm statistics | Alarm statistics | Alarm statistics | Alarm statistics |
| 17 | not dist.: | 0 | |||||
| Ack received | 34 | dist.: | 196 | not dist.: | 0 | ||
| Events in queue (now) Alarms stored | 0 125 | (max) : | 7 | not exec.: | 0 | ||
| cov statistics | cov statistics | cov statistics | cov statistics | cov statistics | cov statistics | cov statistics | cov statistics |
| covs received | dist.: | 145 | not dist.: | 0 | |||
| Events in queue (now) covs stored | 0 4 | (max) : | 4 | not exec.: | 0 | ||
| Loader status statistics | Loader status statistics | Loader status statistics | Loader status statistics | Loader status statistics | Loader status statistics | Loader status statistics | Loader status statistics |
| Ldr status rec. | 297 | dist.: | 297 | not dist.: | 0 | ||
| (now) Registered apps | 0 1 | (max) : | 2 | not exec.: | 0 | ||
| Loader statistics | Loader statistics | Loader statistics | Loader statistics | Loader statistics | Loader statistics | Loader statistics | Loader statistics |
| Loader msgs rec. | dist.: | 6905 | not dist.: | 0 | |||
| Events in queue (now) | (max) : | 5 | not exec.: | 0 | |||
| Registered apps | 1 |
Asydebug 80
Asydebug 80 disables the collection of Insight APOGEE log files by the Async service
Asydebug 89
Asydebug 89 starts the collection of Insight APOGEE log files by the Async service.
Asydebug 100
Asydebug 100 is use to delete all alarms from the Async cache. This command should be used with extreme caution since alarm data is lost when it is cleared.
Asydebug 200
Asydebug 200 is used to display the list of points that are currently being processed by the Cross Trunk service. An example of the output of asydebug 200 is below:
Distr Queue has 0 entries Maximum Cov of Points :2000 Total Number of Points : 2296 Point Name : BAC 360 MI 72 Routing : STCCMSCL, BACNet STRC, 360 Last C0V Received : 5/7/2009 11:13:31 AM AM cov State : Active CoVs Received : 326 COVTYPE DATA val = 1.00, COV STATUS OK COVTYPE NORMAL val = 1.00, stat= COVTYPE IN SVC stat= COVTYPE PT FAIL RET COVTYPE PROOF OFF stat= COVTYPE OUT OF HAND 0MODE COVTYPE_CMD_PRI cmdprio= 0 Last Commanded ： Pending Operation : 1 None Commands Received 1： 0 Commands Executed : 0 Routing : STCCMSCL, SOFTCONTROL HKJC, STCCMSCLI5430 Initial Request : 5/5/2009 10:10:45 AM AM ReadyPending : FALSE NotificationPending : FALSE Point Name : BAC 360 MI 355 Routing : STCCMSCL, BACNet STRC, 360 Last C0V Received : 5/7/2009 11:12:58 AM AM cov State : Active coVs Received : 1110 COVTYPE DATA val = 1.00, COV STATUS OK COVTYPE NORMAL val = 1.00, stat= COVTYPE IN SVC stat= COVTYPE PT FAIL RET COVTYPE PROOF OFF ,stat= COVTYPE OUT OF HAND MODE COVTYPE _CMD_PRI cmdprio= 0 Last Commanded ： Pending Operation : None