With ComOS 3.8.* and earlier, there is a nice little 'feature' that when a
connection to port 1643 is closed, then the file descriptor to the file
system is closed as well regardless of whether that particular connection
owned the file descriptor. So here are some scenarios:
User A is using PMVision to monitor users on a PortMaster 3. User B is
upgrading the same PortMaster. User A exits PMVision, therefore the file
descriptor is closed. The upgrade from User B fails because the file
descriptor is no longer valid.
Another scenario:
User A is using tftp from the ComOS command line to upgrade the PortMaster
3. This PortMaster 3 is using ChoiceNet for its filters. A user dials
into the PortMaster 3 who requires a filter. The PortMaster 3 requests the
filter from its ChoiceNet server. The ChoiceNet server opens a connection
on port 1643 to download the filter onto the PortMaster 3. Once the filter
is downloaded, ChoiceNet closes the connection and the file descriptor is
closed. The tftp running on the PortMaster 3 fails because the file
descriptor was closed.
This problem has been fixed in ComOS 3.9, 4.0, 4.1, ...
This problem was described in the PMVision 1.3 release notes.
Hope this info helps everyone.
D. Scott Gardner sgardner@livingston.com
925.737.2217
Lucent Technologies, Remote Access Business Unit
4464 Willow Road
Pleasanton, CA 94588-8519
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>