ITEM: AY2363L
Service Director return code=101-Modem Configuration for SD/6000
ENVIRONMENT:
Service Director/6000 version 2.0, 7015-R30, AIX 4.1.4, Hayes Acura 28.8
modem.
.DESCRIPTION:
Standalone host configuration for Service Director.
.Customer has installed the new version (v. 2) of Service Director, but
is getting a return code of 101 when he attempts to register the machine.
The modem is attached to native serial port S1, and is configured as tty1.
.When customer dials in to the machine, he's getting a clean login prompt.
.The modem does not appear to be dialing out, but customer believes he saw
one of the lights on the modem change, as if it had been contacted, but
no commands were received. The modem in question is a Hayes Acura 28.8
modem. Customer used the modem string from the Appendix of the Service
Director User's Guide and eliminated the commands that did not work in cu.
.ACTION:
.1. VERIFY THAT THE MODEM IS CONFIGURED CORRECTLY:
Examined configuration of tty1 in SMIT:
Baud rate: 9600
Parity: none
Data Bits: 8
Stop Bits: 1
Handshaking: RTS
Enable Login: DISABLED
. We then examined /etc/uucp/Devices
Direct tty1 - 9600 direct
. ***************************************************************
* The baud rate listed in the SMIT ttyX configuration, in the *
* /etc/uucp/Devices file, and in the Service Director config- *
* uration must be the same! *
***************************************************************
Reinitialize the modem:
cu -dml tty1
at
ok
AT&FE0&D2&C1S0=1&W
~.\
(the above sequence exits the cu session)
.
2. VERIFY MODEM CONFIGURATION IN SERVICE DIRECTOR
SMIT
Problem Determination
Service Director
Service Director Registration Session
(go through introduction screens)
Main Menu
Build/Update List of Machines for Registration
Update machine(s) in the current machine list
(this displayed GUMBY, the only host in customer's setup)
Select GUMBY
\<\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^>
\< BUILD LIST OF MACHINES FOR REGISTRATION (BUILD2) >
\< >
\< 1. uname -m xxxxyyyyzzzz >
\< 2. Type: 7015 >
\< 3. Serial: 0012345 >
\< *** don't use leading '26' ***
\ 4. Hostname: GUMBY
\ 5. Is this a Reporting Server? (y/n): y
\ *** This field should always *
\ * be set to yes if you want *
\ * this machine's errors to be * >
\< * reported to IBM. *** >
\< >
\< 6 through 14. Contact Data >
\< >
\< o. CHANGE configuration data, for this machine >
\< s. SAVE this machine's data, move to next machine
\ c. CANCEL this entry, do not save it, return to calling menu
\
\ Please enter menu selection: o
\_______________________________________________________________________
.\\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^
\ BUILD LIST OF MACHINES FOR REGISTRATION (BUILD3)
\
\ For Machine with Type: 7015 Serial: xxxxyyyyzzzz Hostname: GUMBY
\
\ *** Field Values Suggested for Standalone SD/6000 Machines ***
\ 1. Host reports problems? (N/Y) Y
\ 2. Host forwards problems? (N/Y) Y
\ 3. Comm. method (RPC or TTY) TTY
\ 4. File containing RPC target: /usr/lib/ras/callhomehost
\ 5. TTY device: tty1 *** name of modem device ***
\
\ Fields 6 through 12 are not implemented at this time and may be left
\ blank
\
\ d. SCROLL DOWN, for other values
\ s. SAVE these values (may replace default configuration, too)
\ c. CANCEL, discard any changed values
\ h. SHOW explanations for data fields (uses pg command)
\
\ Please enter menu selection: d
\_______________________________________________________________________
.\\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^
\ BUILD LIST OF MACHINES FOR REGISTRATION (BUILD4)
\
\ For Machine with Type: 7015 Serial: xxxxyyyyzzzz Hostname: GUMBY
\
\ *** Field Values Suggested for Standalone SD/6000 Machines ***
\ 13. File containing RPC clients: /usr/lib/ras/probrephosts
\ 14. Modem file name: /usr/lpp/servdir/modem.setup.hayes288
\ *** use the absolute pathname for the modem file name ***
\ 15. Remote latency delay: 0
\ 16. Remote timeout: 300
\ 17. Retry count: 2
\ 18. Response timeout: 600
\ 19. TTY retry timeout: 86400
\ 20. BAUD rate: 9600 *** same value as SMIT ***
\ *** tty definition and ***
\ *** uucp devices direct ***
\ *** line baud rate! ***
\ 21. Dial out phone number: 99-1-800-830-1041
\ *** This customer had to dial ***
\ *** 99 to get outside line. ***
\ *** Use dashes, not commas. ***
\ 22. Phone number to call back to: 000-000-0000
\ 23. Local operator voice phone: 000-000-0000
\ 24. Hub phone:
\ 25. Duplicate problem timeout: 86400
\ 26. Dial tone, P(ulse), T(one): T
\
\ u. SCROLL UP, for other values
\ s. SAVE these values (may replace default configuration, too)
\ c. CANCEL, discard any changed values
\ h. SHOW explanations for data fields (uses pg command)
\
\ Please enter menu selection: s
\_______________________________________________________________________
. This took us to another screen that asked if we wanted to override
the default configuration data. The default configuration data is
used for other clients in the configuration. The only time that
you would want to say Yes to this option would be if you had other
machines in the Service Director configuration that would be using
the same data in these fields.
. No, do not override default configuration.
.\\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^\^
\ BUILD LIST OF MACHINES FOR REGISTRATION (BUILD2)
\
\ 1. uname -m: xxxxyyyyzzzz
\ 2. Type: 7015
\ 3. Serial: 0012345
\ 4. Hostname: GUMBY
\ 5. Is this a Reporting Server? (y/n): y
\ 6. through 14. (Customer Contact Information)
\
\ o. CHANGE configuration data, for this machine
\ s. SAVE this machine's data, move to next machine >
\< c. CANCEL this entry, do not save it, return to calling menu >
\< >
\< Please enter menu selection: s >
\<_______________________________________________________________________>
. **************************************************************
* PLEASE NOTE THAT THE 'SAVE' OPTION HAS TO BE CHOSEN TWICE! *
**************************************************************
. Since there was only one machine in the list of customer's
machines for Service Director, this took us back to the parent
menu.
.3. REGISTER MACHINES WITH SERVICE DIRECTOR
Choose option '2' from the main menu
(All machines registered OK)
.4. COMPLETE THE SERVICE DIRECTOR REGISTRATION
Choose option '3' from the main menu; Build Reporting Topology Files
* Choose 'yes' for creating RPC files. Although there is only one
machine in the configuration now, it won't hurt.
* Choose 'no' for changing the crontab information. This can be modi-
fied later if you discover you need to.
* No other changes.
. Choose option '4' from the main menu; Distribute Registration Files
* Yes, this will still need to be done, even if you only have one
machine!
. Option '5' in the main menu; Service Director Code Distribution, does
not need to be done in a standalone configuration. If you had client
machines in your configuration, this would provide a convenient way to
install the code on all of your machines at once.
.5. VERIFY THAT SERVICE DIRECTOR IS FUNCTIONAL
Go back to the 'Service Director' entry in SMIT.
Invoke Service Director User Interface
SERVICE DIRECTOR - MAIN MENU
Utilities
Test Communications Path
(This will attempt to place a call to IBM)
. Checked the crontab entry to verify that Service Director is
enabled:
crontab -l
servdir.timer entry? Yes
.
Recommended that customer print out a copy of the User's Guide
for Service Director (it's in the same directory as a README).
Support Line: Service Director return code=101-Modem Configuration for SD/6000 ITEM: AY2363L
Dated: October 1996 Category: N/A
This HTML file was generated 99/06/24~13:30:24
Comments or suggestions?
Contact us