HP 3000 Manuals HP 3000 Manuals
Using NMDUMP for the SNA Links The NMS utility NMDUMP can be used to format tracing and logging records for the SNA links. Described below are the tracing and logging formats produced for the SNA links by NMDUMP. Note that NMDUMP is described in more detail in Using the Node Management Services Utilities [32022-61005]. If you are not familiar with NMDUMP, you should read that manual before running NMDUMP. As stated earlier in this chapter, link trace logging information is written to the system log file, which your Hewlett-Packard support contact formats by using the DUI. So, no description of that file's format is given below. SNA Transport Output Formats For SNA Transport, NMDUMP formats tracing records and logging records. When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for SNA Transport: 1. Then, proceed normally with NMDUMP. The format for each type of record is described below. Tracing Records. Figure 5-1 below is a partial example of the format of a tracing record for SNA Transport.
NOTE All numeric values in the SNA Transport trace are given in hexadecimal.
******************************************************************************** HP | EVENT : snasendexpedited call FEB 29, 1992, 8:27:43.022 HP | LU NAME : INDLU1 ROLE: Pri Session Type: LU-LU IND HP | Open ID : Not Used SIDH: nil SIDL: nil ODAI: nil HP | RESULT : Good Complete RU Length: 0020 HP | TH: SNF: 0001 Send ID: Not Used HP | RH: REQ SC FI.....BCI.ECI.DR1........................................ HP | RU: BIND 31 00 13 07 b0 b0 50 | ......& HP | BUFFER: 31 00 13 07 b0 b0 50 b1 03 00 85 89 80 03 | ......&...ei.. HP | BUFFER: 06 02 00 00 00 00 00 00 00 00 00 00 00 00 | .............. HP | BUFFER: 00 00 00 00 | .... ******************************************************************************** . . . ******************************************************************************** HP | EVENT : snarcv call FEB 29, 1992, 8:27:43.036 HP | LU NAME : INDLU1 ROLE: Pri Session Type: LU-LU IND HP | Open ID : Not Used SIDH: 02 SIDL: 00 ODAI: 01 HP | RESULT : Good Complete ******************************************************************************** . . . ******************************************************************************** IBM| EVENT : receive completion FEB 29, 1992, 8:27:43.046 IBM| LU NAME : INDLU1 ROLE: Pri Session Type: LU-LU IND IBM| Open ID : Not Used SIDH: 02 SIDL: 00 ODAI: 01 IBM| RESULT : RU Length: 0001 IBM| TH: Whole Expedited SNF: 0002 Send ID: Not Used IBM| RH: +Rsp SC FI.....BCI.ECI.DR1........................................ IBM| RU: UNBIND 32 | . IBM| BUFFER: 2f 00 02 00 00 02 eb 80 00 32 | .......... ******************************************************************************** Figure 5-1. SNA Transport Trace Format Example Logging Records. Figure 5-2 is a partial example of the format for SNA Transport logging information. SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Node PFAPU ready for activation by host SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Open user granted on node PFAPU SIDH = 0 ,SIDL = 0 ,ODAI = 0 LUNAME IS XPORTPU SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Open user granted on node PFAPU SIDH = 0 ,SIDL = 2 ,ODAI = 0 LUNAME IS XPORTLU SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Open user granted on node PFAPU SIDH = 0 ,SIDL = 3 ,ODAI = 0 LUNAME IS XPORTLU SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Open user granted on node PFAPU SIDH = 0 ,SIDL = 4 ,ODAI = 0 LUNAME IS XPORTLU . . . SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Session terminated on node PFAPU SIDH = 0 ,SIDL = 0 ,ODAI = 0 HP IS SECONDARY LU LUNAME IS XPORTPU SNA/TRANSPORT Logging SAT, FEB 29,1992, 4:49 PM Close user granted on node PFAPU SIDH = 0 ,SIDL = 6 ,ODAI = 0 LUNAME IS XPORTLU Figure 5-2. SNA Transport Logging Format Example SDLC Link Output Formats For the SDLC link, NMDUMP formats tracing records and logging records. When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for SDLC Link: 27. Then, proceed normally with NMDUMP. The format of the tracing records is shown below. Tracing Records. Figure 5-3 is a partial example of the format of a tracing record for the SDLC link. ref = 1.1 08:44:38:591 Start of Trace diff = 9999:999 SAT, FEB 29, 1992 $0000: 00 00 00 02 C0 00 00 00 00 00 00 00 FC 08 00 00 ................ $0010: 00 1D 7C 9F F7 6B 64 45 00 00 00 00 00 00 00 00 ..|..kdE........ $0020: 00 02 02 08 80 00 00 00 00 00 00 00 FC 08 00 00 ................4 $0030: 57 41 4E 5F 53 44 4C 43 5F 44 52 49 56 45 52 20 WAN_SDLC_DRIVER $0040: 20 20 20 20 20 20 20 20 41 30 30 31 30 30 36 33 A0020063 $0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ $0060: 00 00 00 00 00 00 00 D8 20 20 20 20 20 20 20 20 ........ $0070: 00 00 00 07 4E 45 57 59 4F 52 4B 33 20 20 20 20 ....NEWYORK3 $0080: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 $0090: 20 20 20 20 FF FF FF C5 00 00 00 00 00 00 00 00 ............ $00A0 SAME BYTE $00: TO $00C0-1 NOT SHOWN: #32 $00C0: 00 00 00 00 00 00 00 00 00 00 00 00 02 AE A5 40 ...............@ $00D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ $00E0 SAME BYTE $00: TO $013C-1 NOT SHOWN: #92 ref = 1.2.6 08:44:41:530 Receive from Remote diff = 0:797 SAT, FEB 29, 1992 SNRM (P) Addr=$C1 len = 2 $0000: C1 93 Al ref = 1.77 08:44:41:530+ Driver Mid-plane State-Change diff = 0:000 SAT, FEB 29, 1992 $0000: 00 00 00 00 Figure 5-3. SDLC Link Tracing Record Format Example Logging Records. Figure 5-4 is a partial example of the format for SDLC link logging information. SAT, Feb 29, 1992, 11:02:16.6 AM SDLC Link (27) Linkname = SDLC24 Event Type = Kill Module Log Class = Informational KM Version = A004005D SAT, Feb 29, 1992, 11:03:05.2 AM SDLC Link (27) Linkname = SDLC24 Event Type = Module Config Log Class = Informational Path = 24 MC Version = A004005D SAT, Feb 29, 1992, 11:03:07.3 AM SDLC Link (27) Linkname = SDLC24 Event Type = Driver Startup Log Class = Informational Driver Version = A004006A Driver PDA Ptr = 0000000A.C2CC02C0 . . . SAT, Feb 29, 1992, 11:31:58.7 AM SDLC Link (27) Linkname = SDLC24 Event Type = Kill Module Error Log Class = Error Path = 20 Error Num = #56 Status = CC9000D8 SAT, Feb 29, 1992, 11:33:09.4 AM SDLC Link (27) Linkname = SDLC24 Event Type = Driver Error Log Class = Error Location = $FF93 Sublocation = $0004 Error Code = #1016 Status = $9C9300D9 Cause Status = $9C9300D8 Error Actions = $000F SAT, Feb 29, 1992, 11:33:44.8 AM SDLC Link (27) Linkname = SDLC24 Event Type = Module Config Error Log Class = Error Path = 20 Error Num = #16 Status = $9C9300D8 Figure 5-4. SDLC Link Logging Format Example X.25 Link Output Formats For the X.25 link, NMDUMP formats tracing records. (Logging information is contained within the SNA Transport logging information.) When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for X.25 Link: 38. Then, proceed normally with NMDUMP. The format of the tracing records is shown below. Tracing Records. Figure 5-5 is a partial example of the format of a tracing record for the X.25 link. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HP | EVENT: Snax25_module_config Call FEB 29, 1992, 3:47:47.033 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HP | EVENT: QLLC Initialization Begins FEB 29, 1992, 3:47:48.040 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HP | EVENT: IPCCREATE Call FEB 29, 1992, 3:47:48.045 HP | RESULT: GOOD COMPLETE HP | DESC: X 0000000A !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HP | EVENT: IPCDEST Call FEB 29, 1992, 3:47:48.053 HP | RESULT: GOOD COMPLETE HP | DESC: X FFFFFFFF !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! HP | EVENT: IPCCONNECT Call FEB 29, 1992, 3:47:49.010 HP | RESULT: GOOD COMPLETE HP | CALL DESC: X 0000000A HP | VC DESC: X 0000000B HP | DEST DESC: X FFFFFFFF !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Figure 5-5. X.25 Link Tracing Record Format Example Logging Records. As stated earlier in this chapter, X.25 link logging information is contained within the SNA Transport logging information. Token Ring Link Output Formats For the Token Ring link, NMDUMP formats tracing records and logging records. When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for Token Ring Link: 61. Then, proceed normally with NMDUMP. The format of the tracing records is shown below. Tracing Records. Figure 5-6 is a partial example of the format of a tracing record for the Token Ring link. 13:06:13:082 (+9999.999) Start of Trace ref = 1.1 TUE, SEP 29, 1992 Trace level = Partial Subqueue mask = $FBFC80000 Driver status = $00000000 Load info = $4 Firmware partnu = ............ Firmware date = .... Firmware svers = $00005F80 Driver vers = A0045054 Driver name = HP_LANCON_DVR Startup time = TUE, SEP 29, 1992 13:06:13:082 $0000: 00 00 00 01 C0 00 00 00 FB FC 80 00 00 51 99 E9 .............Q.. $0010: EF 87 D3 B0 00 00 00 00 00 00 00 00 00 02 02 00 ................ $0020: 40 00 00 00 00 20 00 00 00 00 00 04 48 50 5F 4C @...........HP_L $0030: 41 4E 43 4F 4E 5F 44 56 52 20 20 20 20 20 20 20 ANCON_DVR $0040: 20 20 20 20 41 30 30 34 35 30 35 34 00 00 00 00 A0045054.... $0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5F 80 .............._. $0060: 00 00 00 00 00 00 00 D8 00 00 00 00 00 00 00 00 ................ $0070: SAME BYTE $00: TO $00F0-1 NOT SHOWN: #128 $00F0: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ $0100: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF C1 ................ $0110: 00 00 00 00 10 00 90 90 C8 16 FE EC ............ 13:06:02.793 (+ 10.289) Driver received a message ref = 1.2.2 TUE, SEP 29, 1992 Do_Bind_Req_Msg len = 72 $0000: 00 03 FC 18 00 00 AB 58 FF FF FE FC 15 00 00 0B $0010: FF FF FE F3 FF FB E0 07 FF FA C0 00 FF F6 00 00 $0020: 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 $0030: C0 00 00 00 C0 00 00 00 00 38 C0 A4 00 39 00 11 $0040: 00 50 93 04 0D 00 00 00 Figure 5-6. TR Link Tracing Record Format Example Logging Records. Figure 5-7 is a partial example of the format for token ring link logging information NOV 11, 1992, 3:51:34.6 PM IEEE 802.5 Token Ring LAN Linkname = T2REG2 Event type = Module config call Log Class = Informational Path = 48 MC Version = A0045019 Subsystem opened link T2REG2 (LANINFO 1) NOV 11, 1992 4:06:04.9 PM IEEE 802.5 Token Ring LAN Linkname = T2REG2 Event type = Driver error Log Class = Warning Location = $00000044 Sublocation = $0000001E Status = $011602E4 Actions = $00000008 Cause = $E8000840 Token Ring adapter detected lobe cable fault on T2REG2 (LANWARN 2105) Cause: An open or short circuit was detected in the lobe cable. Action: Verify that this station is properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network. NOV 11, 1992 4:06:34.8 PM IEEE 802.5 Token Ring LAN Linkname = T2REG2 Event type = Driver error Log Class = Warning Location = $00000044 Sublocation = $0000001E Status = $011502E4 Actions = $00000008 Cause = $011502E4 Token Ring adapter detected signal loss on T2REG2 (LANWARN 2101) Cause: The station has detected a loss of signal on the ring. Action: Verify that this station is properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network. Figure 5-7. Token Ring Link Logging Format Example