Gary,
Sorry, I misled you there, while talking to Mike, I changed the npconfig
entry to just the bare-bones and took out the SMNP_ENABLED=FALSE to try and
get some more info.
Tracy Johnson also suggested PJL_SUPPORTED=FALSE JAM_RECOVERY=FALSE which I
had in the original entry.
I like your suggestions of
poll_interval_max = 120 # Poll_interval decays to 2
min.
data_timeout = 20 # Allow for busy network.
snmp_timeout = 20 # Same network, same timeout.
snmp_max_retries = 1 # Only give it one chance.
message_interval = 1
and will try various combinations to see if anything works.
Thank you guys for all your help. This is not as straight-forward a job as
I had first imagined. :o(
Cheers,
John
On 16 August 2012 16:19, <[log in to unmask]> wrote:
> Hi John,
>
> Sorry, I see that you already have SNMP_ENABLED=FALSE...
>
> What OS version are you on? The spooler is supposed to NOT make the
> SNMP device check if snmp_enabled = FALSE, but perhaps that is in a
> later version of the spooler code than what is on your system...
>
> ---- John Dunlop <[log in to unmask]> wrote:
> > Progress so far :
> >
> > Having talked to Mike Ranft who very kindly took some time to try and
> help
> > me, we determined that the HP3000 is talking to the Canon Copier and
> Telnet
> > does communicate with it and the port is set up on the HP3000 correctly.
> >
> > However, when sending a spoolfile to the copier (ldev 207), the spoolfile
> > shows ACTIVE but nothing prints and the following mesasages came up on
> the
> > console :
> >
> > 15:04/85/Output spooler, LDEV #207: SNMP error SNMP_ResponseTimeout
> > reported
> > while retrieving printer status.
> > Native Mode Spooler message 9656
> > 15:04/85/Output spooler, LDEV #207: Cannot communicate with network
> > printer.
> > Check network xport config, NPCONFIG.PUB.SYS, xport and links started
> > status,
> > intermediate network, and printer status.
> > Native Mode Spooler message 9662
> >
> > I'm not sure if anyone can interpret much of this but I get the
> impression
> > that the copier is not sending back a status that the HP3000 can
> understand
> > hence the timeout.
> >
> > Can anyone add anything that might shed more light on this?
> >
> > Cheers,
> > John
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|