How are you using nvpage? As a straight numeric dial or did you invent a
dummy paging service entry in the nv.carriers file? It sounds like you
did the latter and said Protocol: UNKNOWN or used something other than the
standard TAP.
I don't know what it means to say you "simulated a paging service". We
expect the default paging service to implement TAP protocol, the US
standard for these things, which means that after the dial we get back a
message which says "<modem speed> CONNECTED". You can specify an
alternative protocol but then you must define it in the nvpaging.protocol
file.
If you have further problems, I suggest a call to Support so that someone
can look at your NetView pager config files
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Randy Pelle (DSN)" <Randy.Pelle@DSN.ERICSSON.SE> on 09/24/98 06:25:28 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: getting nvpage to work
We are trying to use nvpage (on Netview 5 AIX) to issue alerts to our
network administrators. At the moment we can't get it to work properly.
To simulate a pager service we've set up a laptop with a modem using our
internal comm. network. The nvpagerd daemon manages to get a connection
with the laptop, but the 7 digits which identify the right pager never
arrive. According the log file of nvpagerd (as shown below) the 7
numbers are sent as a string, but then the daemon returns with the
message "Protocol not recognized: NOTKNOWN" and tries to resends them
again. If we try a manual connection with ATE it works perfectly (also
with the actual paging service), so I assume the modem configuration is
correct.
Can anyone advise on how to solve for this problem.
I've an open mind to any suggestions.
Thanks in advance!
a part of the nvpagerd.alog logging:
modem[0604] do_alpha[1412] calling modem_init()
modem[0832] modem_init[0612] calling PUTS(4)
txd->ATS11=80S0=0E1H0M1Q0V1X0L1&D2< (sent)
modem[0925] modem_init[0612] calling PUTC(4) txd-><CR><
(sent)
modem[1193] modem_init[0614] calling GET
rxd->ATS11=80S0=0E1H0M1Q0V1X0L1&D2<CR><CR><LF>< (30 bytes)
modem[1193] modem_init[0619] calling GET
rxd->OK<CR><LF>< (3 bytes)
modem[1019] do_alpha[1428] calling modem_dial(6070)
modem[0832] modem_dial[1029] calling PUTS(4) txd->ATDT<
(sent)
modem[0832] modem_dial[1029] calling PUTS(4) txd->6070<
(sent)
modem[0925] modem_dial[1029] calling PUTC(4) txd-><CR><
(sent)
modem[1193] modem_dial[1034] calling GET
rxd->ATDT6070<CR><CR><LF>< (9 bytes)
modem[1193] modem_dial[1043] calling GET
rxd->CONNECT<CR><LF>< (8 bytes)
modem[0832] do_logon[1140] calling PUTS(4) txd->1234567<
(sent)
modem[0925] do_logon[1145] calling PUTC(4) txd-><CR><
(sent)
Protocol not recognized: NOTKNOWN
modem[0832] do_logon[1140] calling PUTS(4) txd->1234567<
(sent)
modem[0925] do_logon[1145] calling PUTC(4) txd-><CR><
(sent)
Protocol not recognized: NOTKNOWN
note: a login prompt isn't required in the simulation (we've tried it
and the system does respond properly)
Ericsson Data Netherlands B.V. (DSN) l
Randy Pelle
Email: Randy.Pelle@dsn.ericsson.se
|