Important note regarding product identification: When the full part number
of a Point System device is abbreviated for use in catalogs and marketing literature,
the first set of numeric digits in the string is dropped and replaced by the last.
In most Point System products, the first set of numeric digits in the full part
number is the same as the last, so this process is transparent. In the case of Management
Modules, this is not true. The full part number of the CPSMM100 Base Management
Module is CPSMM100-200, and it is referred to in catalogs and marketing literature
as CPSMM200.
This document describes the following Point System topics:
Focal Point - Base Management Module Details Screen
Redundant Management: What is a "Primary" Management Module? (back to top)It is possible to install several Base Management Modules in a Point System stack.
One of these modules, known as the "Primary" Management Module, controls the flow
of management data within the Point System. The others are known as "Standby" Management
Modules. The Primary Management Module is responsible for scanning the stack, collecting
and distributing status and configuration information. The Standby modules listen
in on conversations to and from the Primary. You can read configuration or status
information from any of the Base Management Modules, but the Primary Base Management
Module is the only one that is able to accept configuration changes, since
it is the only one that has the means to distribute the information to the destination
device in the stack. Therefore, it is strongly recommended that you always direct
the Focal Point application to the Primary Management Module. When multiple Base Management Modules are installed in a Point System stack, they
negotiate to determine which will be the Primary. The winner of this negotiation
sets its IsPrimary indication to "Yes," and all of the others
set theirs to "No" and stop scanning the stack. Every Base Management Module must make a decision as to whether or not it is the
Primary module based on the conditions in the stack. The criteria are as follows:
- If the module is ineligible to be the Primary, it drops out of the negotiations.
A module is ineligible to be the Primary if it is unable to communicate over the
Ethernet, either because link is down or because its IP configuration is invalid.
See "CanPrimary" described below.
- If the module is not configured by the user to "want" to be the Primary and
it sees that any other eligible module is, it drops out of the negotiaions. See
"WantPrimary" described below.
- The modules that remain "negotiate" by yeilding Primary status to any other
eligible module that is installed in a cabinet with a lower serial number, or
in a lower (further left) slot if the cabinet serial numbers are the same.
What is the ICIF? (back to top)ICIF stands for Inter-Cabinet Communications Interface. Multiple Point System cabinets can be interconnected via cables that plug in to
the front of Base and Expansion Management Modules. In order to avoid loops that
would disrupt inter-cabinet communications, each cabinet must have exactly one Base
or Expansion Management Module that serves as a gateway between the local cabinet
and remote cabinets. When there are multiple Management Modules installed in a cabinet, care must be
taken to ensure that each end of each cable is plugged into the ICIF rather than
any other module, which will have isolated its ICIF cables from the Cabinet. The ICIF also is solely responsible for communicating configuration changes to
the Cabinet hardware. This includes the Cabinet's description and slot power enable/disable
states. Which Management Module is the ICIF?There is always one ICIF for each Cabinet in the stack. The Base Management Module
that is installed in the slot to the left of all of the others of will be the ICIF.
If there are no Base Management Modules, then the leftmost Expansion Managment Module
in the selected. No influence can be exerted over this selection process. The "ICIF"
MIB variable indicates whether or not a particular Management Module has been selected
as the gateway.
Base Management Module SNMP MIB Variables (back to top)Note that a few of the configurable options for the Base Management Module have
no effect unless/until that Base Management Module is/becomes the Primary Management
Module. These options are indicated with a '*' below.
The following manageable features are available for the Base Management Module:
- BiaIndex - (Integer, read only) "Burned In Address." This is the serial
number of the cabinet into which this Base Management Module is installed.
- SlotIndex - (Integer, read only) The cabinet slot into which this Base
Management Module is installed.
- Groups - (String, read/write) This is the Device Group String for this
Base Management Module. For more information on Device Group Strings, see the
help for Configuration Management.
- Reset - (Integer, write only) When the Reset button is clicked, the Base
Management Module reboots.
- SaveConfig - (Integer, write only) Unlike other devices, changes sent
to a Base Management Module via an "Apply" button are placed in temporary storage
(RAM) and will be lost at the next reboot unless they are permanently saved via
SaveConfig. Click the SaveConfig button to make the current Base Management Module
configuration permanent.
- HwRevision - (String, read only) The Hardware Revision of this Base Management
Module.
- SwRevision - (String, read only) The revision of the Firmware running
on this Base Management Module.
- IPAddress - (IP, read/write) The IP address of the Ethernet interface
of this Base Management Module.
- SubnetMask - (IP, read/write) The Subnet Mask of the Ethernet interface
of this Base Management Module.
- Gateway - (IP, read/write) The Gateway Address (or default IP route) of
the Ethernet interface of this Base Management Module.
- IsPrimary - (Integer, read only) When this Base
Management Module is the "Primary" Management Module, the
value of this variable is yes(1).
- WantPrimary - (Integer, read/write) This variable can be changed by the
user to make a Base Management Module "want" to be the Primary
Management Module and thus gain priority during negotiaions. If multiple Base
Management Module modules have their WantPrimary variables set, then these modules
negotiate with each other as equals. See also: Redundant Management:
What is a "Primary" Management Module?
- CanPrimary - (Integer, read only) This indicator shows whether or not
a Base Management Module is qualified to be the Primary
Management Module.
- EthernetLink - (Integer, read only) This indicator shows whether or not
the Base Management Module's Ethernet port has link.
- TntRIP - (IP, read-write) Telnet Remote IP. This security control field
(in conjunction with the TntRIPMask) controls which stations are permitted to
access the Base Management Module via Telnet. Incoming connection requests that
do not match this IP address are rejected.
- TntRIPMask - (IP, read-write) Telnet Remote IP Mask. This field modifies
the TntRIP field in much the same way that a subnet mask modifies an IP address:
For every bit position in the TntRIPMask that contains a '1', the corresponding
bits are compared between the IP in the incoming connection request and the TntRIP.
If any mismatch occurs, the connection request is ignored. Note that a subnet
mask requires a single block of '0' bits on the right and a single block of '1'
bits on the left. The TntRIPMask does not have this restriction.
- SNMPTrapMgr* - (IP, read-write) The IP address to which this Base Management
Module will send its SNMP traps.
- SNMPTrapInterval* - (Integer, read-write) The minimum interval, in seconds,
at which traps are transmitted.
- SysUpTime - (TimeTicks, read only) This Base Management Module's "local"
copy of mib-2.system.SysUpTime. This makes it possible for the Primary Management
Module to make changes to mib-2.system variables in a Standby Management Module.
- SysContact - (String, read-write) This Base Management Module's "local"
copy of mib-2.system.SysContact. This makes it possible for the Primary Management
Module to make changes to mib-2.system variables in a Standby Management Module.
- SysName - (String, read-write) This Base Management Module's "local" copy
of mib-2.system.SysName. This makes it possible for the Primary Management Module
to make changes to mib-2.system variables in a Standby Management Module.
- SysLocation - (String, read-write) This Base Management Module's "local"
copy of mib-2.system.SySLocation. This makes it possible for the Primary Management
Module to make changes to mib-2.system variables in a Standby Management Module.
- CfgMatch - (Integer, read only) This value indicates whether or not this
particular Base Management Module is selected to receive configuration changes.
For more information, see the help for Configuration Management.
- SerialNumber - (Integer, read only) The serial number for this Base Management
Module
- ICIF - (Integer, read only) This Base Management Module is currently the
Inter-Cabinet Communications Interface.
- MRevision - (Integer, read only) This is the marketing revision level
of the device. It is the last three digits of the part number. The CPSMM100-200
Base Management Module has a MRevision of 200, and is generally referred to as
a CPSMM200.
(back to top)
|
