Specifications

Chapter 2 Provisioning
21
For an example of configuration for Alarm #2, press '5' (five).
Alarm#2 Mode:
<0>: Disable -- ignore all alarm conditions
<1>: By Fans -- active if any fan fails
<2>: By User#2 -- active if any user#2 definition is met
<3>: Active -- for manual testing
<ESC>: Go to previous menu. Please select an item.
0 : This will completely disable Alarm #2. The relay dry contact will not close and the NMC ALM2 red LED will not light.
1 : This is the factory default setting. This alarm will only be off when one or both fans fail or are removed.
2 : This setting will take the user parameters and set the alarm according to failures in any parameters set under items 6,7,8.
3 : This selection will set the alarm for testing purposes. The ALM2 LED will light and dry contact for Alarm 2 will close.
User Alarm Definitions
Chassis [X]Power#1 [X]Power#2 [X]Fan#1 [X]Fan#2
Local [X]UTP_Link_Down [X]FX_Link_Down
[X]FEF_Detect [X]Remote_Power_Fail
Remote [X]UTP_Link_Down [X]FX_Link_Down
When alarm mode is set to "User", these definitions may be added to either User#1 or User#2. Any selected
item that fails will cause alarm activation. For chassis activated alarms, the user may select individual power or fan
combinations. For locally generated alarms, any copper, fiber, Far End Fault or Remote Power Failure can be
selected (only for cards that support dying gasp), in any combination to generate an alarm on failure from installed
cards. For any remotely connected in-band converters, any copper, fiber, or Far End Fault may be used to trigger
the alarm relay (only for OAM managed converters).
Below is an example of user settings where Alarm#1 will be triggered by any chassis component failure (power
or fan). At the same time, Alarm#2 will be triggered if any local copper or fiber link, Far End Fault or remote power
has failure. The system is designed to allow very flexible use of the two dry contact alarms through customized
monitoring schemes.
****************************************
*** CTC UNION TECHNOLOGIES CO., LTD. ***
*** FRM220 NMC VER. 1.95 ***
****************************************
This Chassis ID:[00] Cascaded:[Yes] Monitored Chassis ID:[00]
SLOT #01 > NMC and Chassis [ Ver:1.00-1.95 #12314 ]
Power#1 Type:[Empty ] Status:[----] Fan#1 RPM:[2910] Status:[OK ]
Power#2 Type:[AC90-250V] Status:[OK ] Fan#2 RPM:[2940] Status:[OK ]
Alarm#1 Status:[Inactive] Alarm#2 Status:[Inactive]
<1>: Alarm#1 Mode: [User#1 ]
<2>: User#1: Chassis [X]Power#1 [X]Power#2 [X]Fan#1 [X]Fan#2
<3>: Local [ ]UTP_Link_Down [ ]FX_Link_Down
[ ]FEF_Detect [ ]Remote_Power_Fail
<4>: Remote [ ]UTP_Link_Down [ ]FX_Link_Down **
<5>: Alarm#2 Mode: [User#2 ]
<6>: User#2: Chassis [ ]Power#1 [ ]Power#2 [ ]Fan#1 [ ]Fan#2
<7>: Local [X]UTP_Link_Down [X]FX_Link_Down
[X]FEF_Detected [X]Remote_Power_Fail
<8>: Remote [ ]UTP_Link_Down [ ]FX_Link_Down **
(** for 2 OAM units only)
<R>: Redundance Mode:[Disable] (10/100I Series only.)
<ESC>: Go to previous menu. Please select an item.
Note: When receiving traps via SNMP management, Alarm1 is seen as “Major Alarm” while Alarm2 is seen as “Minor
Alarm”.
Note: Do not enable redundancy mode for 10/100i unless you know exactly what you are doing. This mode is discussed in
detail in Chapter 3 under Web Management.