Well, I am guessing here because I haven't seen anything quite like this before,
but the error message indicates that we are having trouble opening the the tty
port with the parameters given (that's the file error). I notice that your
tip command (not familiar with it), uses a bunch of defaults from somewhere,
while nvpager is going to try to use what is in nvpager.config. So the natural
question is, Do they match? Does tip open with 8 data bits, 1stop bit, No
parity, and speed of 38400? And why is that port speed so high? I have never
seen a pager company accept a speed greater than 9600 and most use a lot less.
I would drop that to about 2400 and see if you have better luck. Perhaps
Solaris won't accept a port speed that high on ttyb.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Clay David (rti1dwc)" <rti1dwc@ISMD.UPS.COM> on 11/16/99 09:38:52 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: Modem Configuration For Paging
James,
I tried what you suggested but it still didn't work. Here a trace of what I
am seeing. Thanks for your help.
nms (csh)# tip /dev/ttyb
connected
at
OK
~
[EOT]
nms (csh)# nvpage 18009763308 911
ID(s): 18009763308(2)
Message sent successfully.
nms (csh)#
***** nvpagerd.alog ******
(C) Copyright IBM Corporation 1990, 1993, All Rights Reserved.
11/16/99 08:51:43 - START /usr/OV/bin/nvpagerd as PID 1501
IpcKey: 0x6e005e56
Warm start information is being checked, but will not be used...
Warm start file "/usr/OV/conf/nvpager.warm" has data that is not being used.
Service nvpagerd using TCP socket 1671.
nvpagerd[1000] calling page_q_enq(): Pri(3) Person(18009763308) Mesg(911)
page_q[0589] page_q_enq(): ID(2) added as only item on the queue
Error: Too many consecutive child errors.
Problem with child. 411/16/99 08:52:04 - Error: select() failed. : Bad file
number
page_q_deq(): ID(2) Pri(3) Person(18009763308) Mesg(911)
11/16/99 08:52:10 - STOP /usr/OV/bin/nvpagerd as PID 1501
****** nvpagerd.errlog ******
Error(/usr/OV/bin/nvpagerd): Too many consecutive child errors.
11/15/99 15:37:18 - Error(/usr/OV/bin/nvpagerd): select() failed. : Bad file
number
Error(/usr/OV/bin/nvpagerd): Too many consecutive child errors.
11/15/99 15:41:41 - Error(/usr/OV/bin/nvpagerd): select() failed. : Bad file
number
Error(/usr/OV/bin/nvpagerd): Too many consecutive child errors.
11/16/99 08:43:25 - Error(/usr/OV/bin/nvpagerd): select() failed. : Bad file
number
Error(/usr/OV/bin/nvpagerd): Too many consecutive child errors.
11/16/99 08:52:04 - Error(/usr/OV/bin/nvpagerd): select() failed. : Bad file
number
***** nvpage.conf *******
#
# GSC Paging configuration file
#
# Outside Line # (p=Pause): 9p
# This is any dialing that needs to be done for the attached modem to
# get an outside dial tone. Numeric pager numbers as well as carrier
# phone number should NOT include this. This will be dialed each time
# a call is made by the modem.
# Valid characters: 0123456789p
Outside Line (p=Pause): 9p
# Default Modem File: newhayes.modem
# This is the modem information file that describes the initialization
# needed for the attached modem and other control information specific
# to each type of modem.
#Default Modem File: ibm5853.modem
Default Modem File: newhayes.modem
# Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 300
# This is the baud rate between the computer and modem when direct-dial
# numeric pagers are contacted and when the carrier's direct-dial DTMF
# number is used for numeric pagers.
# Valid values: 300,1200,2400,4800,9600,19200,38400
Default Baud Rate (300,1200,2400,4800,9600,19200,38400): 38400
# Default Data Bits (7,8): 7
# This is the number of data bits between the computer and modem when
# direct-dial numeric pagers are contacted and when the carrier's direct-
# dial DTMF number is used for numeric pagers.
# Valid values: 7,8
#Default Data Bits (7,8): 7
Default Data Bits (7,8): 8
# Default Parity (N,E,O): E
# This is the parity between the computer and modem when direct-dial
numeric
# pagers are contacted and when the carrier's direct-dial DTMF number is
# used for numeric pagers.
# Valid values: N,E,O
#Default Parity (N,E,O): E
Default Parity (N,E,O): N
# Default Stop Bits (1,2): 1
# This is the number of stop bits between the computer and modem when
# direct-dial numeric pagers are contacted and when the carrier's direct-
# dial DTMF number is used for numeric pagers.
# Valid values: 1,2
Default Stop Bits (1,2): 1
# Default Device: tty1
# This is the device that the modem is attached to. It must be in the
/dev
# directory. If your modem is attached to another tty port, this must be
# changed.
#Default Device: tty0
Default Device: ttyb
Thanks,
Dave Clay UPS
-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Monday, November 15, 1999 5:10 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: Modem Configuration For Paging
First, check /usr/OV/log/nvpagerd.alog and errlog for error messages. That
number 8008797632 should have a "1" in front of it, shouldn't it? If you
see
no error messages, then check that nvpagerd is still running. Do you have
the
right tty specified in nvpager.conf?
You can trace what the pager does by adding -d in the ovsuf file. You can
do
that more permanently by editting the lrf file and using ovdelobj and then
ovaddobj, or by using the Framework configuration menu. You can even ovstop
nvpagerd, and run him in a separate window with just " /usr/OV/bin/nvpagerd
-d"
and issue your pages in another window. The logs will still fill with trace
messages.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Clay David (rti1dwc)" <rti1dwc@ISMD.UPS.COM> on 11/15/99 04:14:53 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Modem Configuration For Paging
I am using Netview v5.1 and trying to get the paging services working
properly. I setup a USRobotics 56.k modem on my ultra 10 running Solaris 2.6
and tested it's functionality using the 'tip' command. This all worked fine.
When I try to test paging functions with Netview, it doesn't work. I am
using the command 'nvpage' for testing purposes. I also configured
nvpager.conf to use the following ::newhayes.modem, 8,1,N. When I execute
the command 'nvpage 8008797632 911' I get the message that it was queued. I
never see the modem go off hook and I never get a page. Does anyone have any
ideas as to what the problem could be? Any suggestions would be greatly
appreciated.
Thanks,
Dave Clay UPS
|