ALTERPATH-PM
FAMILY RELEASES
This document brings all new features and bug fixes regarding
PM8/8i/10/10i/20/20i
versions (Including BETA versions which have a letter after the version
number).
V_1.7.0 Sep/15/05
: (official
release;
upgrade from V_1.6.0)
a) New features
b) Bug fixes
-
Status command with formatting problem in the Users field (missing a TAB)
-
Unassign command shows now the outlets out of the first IPDU being unassigned
-
Executing alarm command to set a given threshold followed by restore command would not recover the
threshold saved in flash
c) Change Log
- Outlet names now allow only alphabetic characters
d) PM User Documentation
- PM manual (Installation, Administration, and User’s Guide) has
been updated. Please go to
ftp://ftp.cyclades.com/pub/cyclades/alterpath/pm/doc/ and download the
current PM manual (pm_install_admin_user_v170_091905.pdf).
V_1.6.0 Jul/28/05
: (official
release;
upgrade from V_1.5.0)
a) New features
-
Support to PM10i 32A, PM20i 32A, PM8iR 16A and PM10DC 10A.
-
Support to outlet names with 16 characters long
b) Bug fixes
-
Interval time was not accurate (bigger than it should be) affecting on, off and cycle commands
-
currentprotection command ignores parameters different from on/off
-
factory_defaults will turn ON all outlets w/o turning them OFF first
c) Change Log
- PM10DC does not support the commands: alarm, current,
currentprotection and buzzer
- cycle command has changed to OFF all outlets of one IPDU then ON
all outlets of this same IPDU and then passes the command along to the
next IPDU
- special cycle command for PM10DC model (cycle = off/on/off or
on/off/on depending on the state of the outlet)
- If PM10DC in chain with other PM models it should be placed last
in the chain
- status all had a change in the layout (users placed in the last
column)
- WARNING: configuration from boxes running V_1.0.0 or V_1.1.0 will
be lost when upgrading to this FW version. Boxes running V_1.2.0 up to
V_1.5.0 will have their configuration preserved when upgrading to this
FW version.
V_1.5.0 Oct/25/04
: (official
release;
upgrade from V_1.4.0)
a) New features
b) Bug fixes
c) Change Log
V_1.4.0 Oct/04/04
: (official
release;
upgrade from V_1.3.0)
a) New features
b) Bug fixes
-
Can't remove an outlet name by using command 'name' for a given outlet #(s)
-
List command doesn't show some of the outlets on the console
- Separating commas are not deleted when users are deleted
-
"not V_1.2.0/1 or V_1.1.0 compatible" when executing 'restore' from pmCommand with a certain type of name being set for the outlets.
-
typo in 'deluser' help info
- Delete a user gives four output of 'Username Deleted'
- Outlet name 8 chars long ending with a number, are not saved to
flash after a save command.
- As a regular user, type 'reboot' or 'assign' doesn't echo
"Privileged Command" at the prompt.
c) Change Log
V_1.3.0 Mar/12/04 : (official
release;
upgrade from V_1.2.2)
a) New features
b) Bug fixes
c) Change Log
V_1.2.2 Feb/23/04 : (official
release;
upgrade from V_1.2.1)
a) New features
b) Bug fixes
-
When registering one user's password greater than 8 characters the admin user would be deleted. Only powering off and back on would recover the unit.
-
Current reading for PM10 30A, outlets 5-10, was wrong
- Daisy chain is not broken anymore when there's a session timeout
c) Change Log
- Command upgrade uncommented
d) Known problems
- When rebooting the unit (warm boot) the maxCurrent MAY present a
wrong value. In that case, a "current reset" command would clear the
wrong value. This problem does not appear in a cold boot.
V_1.2.1 Feb/17/04 :
(official
release;
upgrade from V_1.2.0)
a) New features
b) Bug fixes
-
Upgrading from 1.1.0i to 1.2.0 could present problems in the outlet names, users and maxCurrent.
-
Buzzer could go off when upgrading to 1.2.0
- Configuration was not preserved when upgrading from 1.1.0o to
1.2.0
- Commands like status or off all could make the unit hang after an
upgrade to 1.2.0
c) Change Log
d) Known problems
- When rebooting the unit (warm boot) the maxCurrent MAY present a
wrong value. In that case, a "current reset" command would clear the
wrong value. This problem does not appear in a cold boot.