Table of Contents
Advertisement
Configuration
A change in revision level causes any remote autoframes to follow the revision if they are version
X.10 and up and the originating autoframe is also X.10 and up:
While you are changing revision types, entering a Control-C (<Ctrl-C>) is ignored until execution
of the change is complete. This avoids problems that may occur when writing to non-volatile
memory and aborting a command in mid-execution.
To change the firmware revision level, proceed as follows:
a. From the Configuration Menu, select:
CHANGE REVISION LEVEL
b. The prompt,
SWITCH TO REVISION 2.XX, 3.XX, 4.XX or A1XX (2/3/4/A)?"
Select 2, 3, 4 or A. The number represented by "XX" is dependent on the
firmware that your system has:
c. The following prompt displays
THIS WILL ALSO CLEAR CONFIGURATION MEMORY, ARE YOU SURE? (Y/N)
d. Selecting "Y" enters the selected revision level and the status line flashes
CLEARING CONFIGURATION MEMORY
until such time as the configuration memory is completely cleared.
e. The changed revision level is now saved in memory and displays on the Main Menu.
f.Reconfigure the system using the configuration routines.
In software version X.10 through X.20, if a master is powered up and detects that the slave's re-
vision type is mismatched, the master will send a revision change command to the slave's autof-
rame in an attempt to match the revision levels. If the slave has time-of-day enabled and is not an
X.OX type, then the master assumes the slave's revision type. When a slave is powered up, it as-
sumes the masters multiplexer type if the master is not an X.OX type. A master will attempt to
make a slave its multiplexer type upon resuming operation after a link interruption. In X.21 and
up, 4.00 and up, there is no restriction as to what version the other end must be for the local end
to assume the remote's revision type.
AUTO FRAME Redundancy
The user can now select whether the AUTO FRAME modules are redundant or nonredundant at
Node M or Node S. Whenever a node is configured as nonredundant, the out-of-service AUTO
FRAME alarm is squelched and the out-of-service AUTO FRAME (located on the status screen
update technique display) is blanked. The user selected state of redundancy is also used to help
determine if the local or remote out-of-service update method will be used (in 3.20 and up). In
cases where both ends are configured as nonredundant, then no updating is necessary at all and
the AUTO FRAME status screen update technique display is blanked.
Conversely, setting a node's Autoframes as redundant will assure that the out-of-service card is
properly updated. Use the arrow keys to change the Redundant/Nonredundant setting.
NOTE
The software selection of redundancy does not control the
hardware. The MEGAMUX PLUS Redundancy Control Card must
still be strapped for either redundant or nonredundant operation.
5-3
036R660-000, Issue 10
Advertisement
Table of Contents
