Hmm...
See, to me, "the Breakfast of Champions" brings to mind one of two
things: a pack of Twinkies, a pickled sausage and a bottle of ginger
beer, or a Coke and a snack-machine Rice Krispies Treat.
(The snack machine here at Livingston has Rice Krispies Treats, which
is SO unfair. Why don't they just sell little packets of smack for 55
cents?)
> Now for the useful question, I saw several mentions of late to 3.3.1c1,
> but I don't see anything listed at the livingston site, and I apparently
> missed the official announcement here, where can I find it, and where
> are it's release notes (I've been scanning the livingston WWW site for
> the past 20 minutes looking for it)
More information on ComOS 3.3.1c1 is included below.
--G.
-- Benjamin D. Hutchins gryphon@livingston.com | ACHTUNG! Alle Servicearbeiten A Minion of Livingston Enterprises Texaport | sollten vom dazu qualifizierten BellNet 800-458-9966 -><- FAX 510-426-8951 | Servicepersonal ausgefuehrt www.livingston.com <*> Ride the Wild Rhino | werden.---cut---
============================ ComOS 3.3.1c1 ============================
Behind door number one we have ComOS 3.3.1c1. This release is for the PM-2 series *only*. If you are running a PM-2 series unit we strongly recommend upgrading to this release, if you have a PM-2eR we *extremely* strongly recommend it. We'd require it but we can't force it after all...
It is ComOS 3.3.1 with two changes:
1. The *big* one you've all been waiting for - THE WAN PORT BUG FIX! Yes, that's right, after many months of toil we have produced a fix for the WAN port driver. This fix is for the problem a number of users have encountered, where the WAN port stops sending data despite continuing to send LMI updates. This required manual resetting of the port to clear in most cases, in some it would clear up by itself after some period of time.
It should be noted that this is not a panacea, in our investigations we found that by far most WAN port problems turned out to be problems with the CSU/DSU, the telco, cabling, etc - a small percentage actually had this bug. We solved the rest of the cases, and then focused on the few we had left. We eventually located a bug in the WAN port driver code. A few tests sites have been running this release for nearly a month now and they have been delighted with the performance of the 2eR units. Release 3.3.1c1 definitively fixes this problem.
If you have a PM-2eR and are experiencing any problems with the WAN port, you should upgrade to this release immediately before attempting to do any debugging.
2. Many people have been reporting problems with disconnects. Up until now it has been hard to debug because it is nigh-impossible to catch one in the act. Well, 3.3.1c1 helps in this area - the RADIUS value for 'Acct-Terminate-Cause' has been implemented. So now RADIUS Accounting will log the reason for disconnect for each session. In addition the reason for disconnect will be displayed on the !root console and sent to syslog if 'set degbug term on' is set. The full set of Terminate values is listed in the release notes for our other release, just below in the next section.
If you are experiencing any problems with disconnects, we strongly recommend upgrading to 3.3.1c1 to aid in debugging efforts.
ComOS 3.3.1c1 may be found in <ftp://ftp.livingston.com/pub/ts/pm2_3.3.1c1>
If you do not have the ability to upgrade locally, we will do the upgrade for you over the nets if you call support during our business hours.