Alcatel-Lucent 6850-48 Reference Guide
CMM Commands
OmniSwitch CLI Reference Guide
September 2009
page 1-17
-> show running-directory
CONFIGURATION STATUS
Running CMM : PRIMARY,
CMM Mode : DUAL CMMs,
Current CMM Slot : 1,
Running configuration : WORKING,
Certify/Restore Status : CERTIFY NEEDED
SYNCHRONIZATION STATUS
Flash Between CMMs : SYNCHRONIZED,
Running Configuration : NOT AVAILABLE,
Stacks Reload on Takeover: ALL STACKs (SW Activation)
output definitions
Running CMM
The CMM currently controlling the switch, either PRIMARY or
SECONDARY.
SECONDARY.
CMM Mode
Displays whether the primary and secondary CMMs are synchronized.
In the case that there is no secondary CMM, MONO-CMM-CHASSIS
is shown.
In the case that there is no secondary CMM, MONO-CMM-CHASSIS
is shown.
Current CMM Slot
The slot number of the primary CMM.
Running Configuration
Where the switch is running from, either WORKING or CERTIFIED.
A switch running from the certified directory will not be able to manip-
ulate files in the directory structure.
A switch running from the certified directory will not be able to manip-
ulate files in the directory structure.
Certify/Restore Status
Indicates if the CM has been certified (i.e., the Working directory
matches the Certified directory).
matches the Certified directory).
Flash Between CMMs
Displays whether the Working and Certified directories are the same.
NIs Reload On Takeover
Stacks Reload on Takeover
Stacks Reload on Takeover
Displays how many Network Interface (NI) modules or switches in a
stack will be reloaded in the event of a management module takeover.
Options include NONE, ALL, or a list of specific NIs.
If there are no unsaved configuration changes and the flash directories
on both the primary and secondary management modules have been
synchronized via the
stack will be reloaded in the event of a management module takeover.
Options include NONE, ALL, or a list of specific NIs.
If there are no unsaved configuration changes and the flash directories
on both the primary and secondary management modules have been
synchronized via the
reloaded if a management module takeover occurs. As a result, data
flow is not interrupted on the NIs during the takeover.
If a configuration change is made to one or more NI modules (e.g., a
VLAN is configured on several different interfaces), and the changes
are not saved via the
flow is not interrupted on the NIs during the takeover.
If a configuration change is made to one or more NI modules (e.g., a
VLAN is configured on several different interfaces), and the changes
are not saved via the
command, the corresponding NIs
will automatically reload if a management module takeover occurs.
Data flow on the affected NIs will be interrupted until the reload is
complete. Note that the NIs will reload whether or not the flash syn-
chronization status shows SYNCHRONIZED. This is because the
unsaved changes have occurred in the running configuration
(i.e., RAM), and have not been written to the flash directory’s configu-
ration file. In this case, a list of only the affected NIs displays in the
table output (e.g., 1 6 9 12).
If the flash directories on the primary and secondary management mod-
ules are not synchronized (e.g., a
Data flow on the affected NIs will be interrupted until the reload is
complete. Note that the NIs will reload whether or not the flash syn-
chronization status shows SYNCHRONIZED. This is because the
unsaved changes have occurred in the running configuration
(i.e., RAM), and have not been written to the flash directory’s configu-
ration file. In this case, a list of only the affected NIs displays in the
table output (e.g., 1 6 9 12).
If the flash directories on the primary and secondary management mod-
ules are not synchronized (e.g., a
been issued recently), all NIs will be reloaded automatically if a man-
agement module takeover occurs. Data flow will be interrupted on all
NIs until the reload is complete.
agement module takeover occurs. Data flow will be interrupted on all
NIs until the reload is complete.