• Subject: Re: Experince with Perle 494
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 15 Jan 2001 08:43:48 -0800
  • Organization: Pacer International

It sounds to me like some of your virtual devices got varied off.

Perhaps your system is set to disable a device once someone enters
a wrong password.  If someone out there on your WAN kept trying to 
log in, they could of been disabling your devices without realizing it.

Try this:


that is, assuming your virtual devices are the standard QPADEV0001,
QPADEV0002, etc...

Do you see any varied off?  Vary them back on.  See if that fixes the

Another way is just to turn back on your auto create devices for a while.
That would create more devices, but I'm sure you want to vary the disabled
ones back on.


Jim Langston

Date: Sat, 13 Jan 2001 19:59:33 -0600
From: "Roger Vicker, CCP" <rvicker@vicker.com>
Subject: Re: Experince with Perle 494


Sounds reasonable but...

This had been working for along time

The Perle tech specifically said that the only limits was twinax addresses (4
ports * 7 addresses = 28 PCs not sessions), and the QPCSUPP mode limit on
sessions per PC (set at 256 so no problem), and QUTOVRT (500) for total virtual
devices system wide automatically created (all virtual existed prior to problem
and no new ones needed to be created)


Roger Vicker, CCP.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.