Datacomm Troubleshooting Procedure No. 1 [ HP Predictive Support CE Guide For HP 3000 Series 900 ] MPE/iX 5.0 Documentation
HP Predictive Support CE Guide For HP 3000 Series 900
Datacomm Troubleshooting Procedure No. 1
Probable Cause of File Transfer Failure: Error in modem configuration or
modem set up.
NOTE If an FSERR accompanies the error message in PSRNLOGD, go to "FSERR
Messages" in Appendix F first before proceeding with the
instructions below.
Datacomm Troubleshooting Procedure No. 1
----------------------------------------------------------------------------------------------
| | | |
| Step | What To Do | How To Do It |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 1 | Make sure modem LDEV/device class in | To check/change the modem |
| | psconfig is correct. | LDEV/device class: |
| | | |
| | | |
| | * If correct, go to Step 2, below. | a. Log on as manager.sys,pred. |
| | | |
| | * If incorrect, enter correct number; | b. Type run psconfig |
| | then, go to Step 10. | |
| | | c. Type co tr at the psconfig |
| | | Main Menu |
| | | |
| | | d. Type the item number of the |
| | | field to change and press |
| | | Return. |
| | | |
| | | e. Type the correct value and |
| | | press Return. |
| | | |
| | | f. Type e; save your changes. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 2 | Make the sure modem port is available. | Type showdev nnn, where nnn is the |
| | | modem LDEV or device class, at the |
| | | MPE prompt. |
| | A. If the port is available, go to D, | |
| | below. | |
| | | |
| | B. If the port is not available | |
| | because of another "owner", wait | |
| | until it is free; then, go to Step | To perform an ABORTIO: |
| | 10. | |
| | | |
| | C. If the port is not available | * Type abortio nnn at the MPE |
| | because it is "owned" by "SYS", | prompt, where nnn is the |
| | reset it through ABORTIO and verify | modem LDEV number. |
| | through showdev. | |
| | | * Verify the abortio by typing |
| | If showdev then shows that the port | another showdev. |
| | is AVAIL, go to Step 10; otherwise, | |
| | go to Step 9. If the port | To check for remote console |
| | continues to show that it is | enabling; |
| | "owned" by "Sys", verify that the | |
| | OPENVIEW configuration for "enable | * Enter Ctrl B at the console |
| | Automatic Connection" is set to | (LDEV 20). A flashing |
| | OFF. | message will be displayed: |
| | | "REMOTE: <state>", where |
| | D. Make sure the remote console is not | <state> is either DISABLED, |
| | enabled. Disable it if it is | PENDING, or ENABLED. |
| | ENABLED or PENDING. | |
| | | |
| | | * If the flashing |
| | | message states, |
| | | ENABLED or PENDING, |
| | | type dr (to disable), |
| | | type co to exit, and |
| | | go to Step 10. |
| | | |
| | | * If the flashing |
| | | message states, |
| | | DISABLED, type co to |
| | | exit, and go to Step |
| | | 3. |
| | | |
----------------------------------------------------------------------------------------------
Table E-0. Datacomm Troubleshooting Procedure No. 1 (cont.)
----------------------------------------------------------------------------------------------
| | | |
| Step | What To Do | How To Do It |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| | | |
| 2 | | |
| Cont. | * If showdev shows that the modem | |
| | LDEV does not exist on the system, | |
| | then the LDEV is invalid or the | |
| | system has lost communication with | |
| | the DTC. | |
| | | |
| | * Verify the modem LDEV in | With the system manager, perform the |
| | psconfig, and correct it, if | following, even if the entire |
| | necessary. Go to Step 10. | configuration appears to be correct: |
| | | |
| | NOTE: If the modem LDEV in | |
| | psconfig is CORRECT, the | * For a Host-Based DTC: |
| | system may have lost | |
| | communication with the DTC | |
| | or the DTC may be improperly | * Validate NMMGR; |
| | configured. With the system | cross-validate through |
| | manager, step through every | SYSGEN; restart the |
| | portion of NMMGR, including | system; restart the |
| | the DTC address, DTC port | DTC. |
| | configurations, etc. | |
| | | * For a PC-Based DTC: |
| | If problems still persist, | |
| | contact the HP Response | |
| | Center. | * Validate NMMGR; |
| | | cross-validate through |
| | | SYSGEN; verify |
| | | OPENVIEW; restart the |
| | | system; restart the |
| | | DTC. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 3 | Make sure the modem port is configured | To check/re-configure the DTC port: |
| | correctly. | |
| | | |
| | * If it is, go to Step 4. | * Run nmmgr.pub.sys and check |
| | | the DTS profile for the port, |
| | * If NMMGR is changed, restart the | as discussed in "Phase 8: |
| | system. If the DTC is Host-based, | Checking the Datacomm Port |
| | restart the DTC. Then, go to Step | Configuration" in Chapter 2. |
| | 10. | |
| | | |
| | | * If the DTC is PC-based, also |
| | | check OPENVIEW. |
| | | |
| | | * Go to Appendix D, |
| | | "Configuring the Datacomm |
| | | Port," if changes must be |
| | | made. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 4 | Make sure the modem dialout method in | To check/change modem dialout |
| | psconfig is compatible with the modem | setting in psconfig: |
| | being used. Only supported modems can | |
| | have an AUTODIAL setting in psconfig. All | |
| | other modems must have a MANUAL setting. | * Log on as manager.sys,pred. |
| | | |
| | | * Type run psconfig |
| | * If the modem is properly set, go to | |
| | Step 5. | * Type co tr at the psconfig |
| | | Main Menu |
| | * If the modem is not properly set, | |
| | correct it; then, go to Step 10. | * If the value must be changed, |
| | | type 4 and press Return. |
| | | |
| | | * Type the correct value and |
| | | press Return. |
| | | |
| | | * Type e (to save) and exit. |
| | | |
----------------------------------------------------------------------------------------------
Table E-0. Datacomm Troubleshooting Procedure No. 1 (cont.)
----------------------------------------------------------------------------------------------
| | | |
| Step | What To Do | How To Do It |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 5 | Power the modem off and back on again. | |
| | Attempt a file transfer (see Step 10). If | |
| | the transfer is not successful, go to Step | |
| | 6. | |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 6 | Make sure the modem cable is P/N 92219Q | Modem is NOT cabled through the |
| | and make sure it is properly attached. | Access Port: |
| | | |
| | | * "Dataset" end: attach |
| | * If the cables are securely and | securely to the modem. |
| | properly attached, go to Step 7. | * "Computer" end: attach |
| | | securely to the DTC. |
| | * Otherwise, secure connections and | |
| | go to Step 10. | Modem IS cabled through the Access |
| | | Port: There are two cables. |
| | | |
| | | |
| | | * Cable One: |
| | | |
| | | * "Dataset" end: attach |
| | | securely to the |
| | | "Session Port" access |
| | | port |
| | | * "Computer" end: |
| | | attach securely to the |
| | | DTC |
| | | |
| | | * Cable Two: |
| | | |
| | | * "Dataset" end: attach |
| | | securely to the modem |
| | | * "Computer" end: |
| | | attach securely to the |
| | | "Remote Support Modem" |
| | | access port |
| | | * Modem is cabled |
| | | through remote console |
| | | port: |
| | | |
| | | * Dataset end: |
| | | attach to modem |
| | | |
| | | * Computer end: |
| | | attach to |
| | | remote console |
| | | port |
| | | (typically, |
| | | LDEV 21) |
| | | |
| | | If additional help is required, see |
| | | the appropriate HP 3000 Series 900 |
| | | configuration manual. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 7 | | See Appendix C, "Setting Modem |
| | * Reset the modem option settings | Options," for information on setting |
| | (even if they appear to be set | autodial modems supported by HP |
| | properly). | Predictive Support). |
| | * Power the modem off and then on | |
| | again. | |
| | * Then, go to Step 8. | |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 8 | Attempt a file transfer NORMAL. If | To initiate a transfer normal: |
| | unsuccessful, go to Step 9. | |
| | | |
| | | * Go to the psconfig Main Menu; |
| | | type tr no and press Return. |
| | | |
| | | |
| | | OR |
| | | |
| | | * From the MPE prompt, type the |
| | | following and press Return: |
| | | |
| | | run |
| | | psconfig.pred.sys;info="tr |
| | | no" |
| | | |
----------------------------------------------------------------------------------------------
Table E-0. Datacomm Troubleshooting Procedure No. 1 (cont.)
--------------------------------------------------------------------------------------------------------
| | | |
| Step | What To Do | How To Do It |
| | | |
--------------------------------------------------------------------------------------------------------
| | | |
| 9 | Reset the modem port through TERMDSM (if | Details on resetting the port |
| | Host-based DTC) or OPENVIEW (if PC-based | through TERMDSM and OPENVIEW are |
| | DTC). | given in Datacomm Troubleshooting |
| | | Procedure No. 5. |
| | | |
--------------------------------------------------------------------------------------------------------
| | | |
| 10 | Initiate a file transfer. | To start a transfer normal: |
| | | |
| | | |
| | | * Go to the psconfig Main Menu; |
| | | type tr no and press Return. |
| | | |
| | | |
| | | OR |
| | | |
| | | * From the MPE prompt, type the |
| | | following and press Return: |
| | | |
| | | run psconfig.pred.sys;info="tr no" |
| | | |
--------------------------------------------------------------------------------------------------------
MPE/iX 5.0 Documentation