Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Changing Alarm Settings for the Optics and OTN Interfaces

 

You can modify the configuration settings for alarm settings of optical interfaces using the Preferences page of the Connectivity Services Director application. To open the Preferences page, click the down arrow next to the System button in the Connectivity Services Director banner and select Preferences. The Preferences page opens with User Preferences as the default tab. Click the Fault tab of the Preferences page of the Connectivity Services Director GUI to enable individual alarms, set the retention period for alarms, configure alarm notifications, and to specify the number of events to keep for each alarm. The Fault tab has multiple sections, which you can expand and collapse by clicking the arrow next to the section title:

  • Global Settings, for configuring Faults settings such as global alarm notifications and alarm data retention.

  • Individual Alarms and Threshold Settings, for configuring settings for individual alarms.

This section describes the following tasks that you can perform by using the alarm monitors displayed in Fault mode:

Alarms for Optical Interfaces

The following alarms are applicable for management of the Optics interface.

  • JnxOpticsLocation—Near end or far end

  • jnxOpticsPerformanceMonitoring—{ jnxIfOpticsMib 2 }

  • jnxOpticsAlarm—{ jnxIfOpticsMib 3 }

  • jnxOpticsConfigTable—This table provides information on the optics configuration.

    • jnxOpticsConfigEntry—A conceptual row that contains information about the optics configuration Table.

    • jnxOpticsConfigContainerIndex—The associated jnxContentsContainerIndex, for example, shelf.

    • jnxOpticsConfigL1Index—The level one index associated with this subject, for example, slot.

    • jnxOpticsConfigL2Index—The level two index associated with this subject, for example, port.

    • jnxOpticsConfigL3Index—The level three index associated with this subject, for example, channel.

    • jnxOpticsType

    • jnxLaserEnable—The transmit wavelength of the laser.

    • jnxSpacing—A minimum nominal difference in frequency (GHz) between two adjacent channels.

    • jnxModulation

    • jnxTxOpticalPower—Transmit optical power.

    • jnxModuleTempHighThresh—High module temperature in degree Fahrenheit above which a Threshold Crossing Alert (TCA) should be sent.

    • jnxModuleTempLowThresh—Low module temperature in degree Fahrenheit above which a Threshold Crossing Alert (TCA) should be sent.

    • jnxTxPowerHighThresh—Tx power above which a Threshold Crossing Alert (TCA) should be sent.

    • jnxTxPowerLowThresh—Tx Power below which a Threshold Crossing Alert (TCA) should be sent.

    • jnxRxPowerHighThresh—Rx power above which a Threshold Crossing Alert (TCA) should be sent.

    • jnxRxPowerLowThresh—Rx Power below which a Threshold Crossing Alert (TCA) should be sent.

  • jnxOpticsTraceToneCfgTable—Information about the optics tests.

    • jnxOpticsTraceToneCfgEntry—Information about the optics FRUs

    • jnxOpticsTraceToneCfgContainerIndex—The associated jnxContentsContainerIndex, for example, shelf.

    • jnxOpticsTraceToneCfgL1Index—The level one index associated with this subject, for example slot.

    • jnxOpticsTraceToneCfgL2Index—The level two index associated with this subject, for example port.

    • jnxOpticsTraceToneCfgL3Index—The level three index associated with this subject, for example channel.

    • jnxOpticsTraceToneCfgTxEnable—Enable/disable the transmit Trace tone feature.

    • jnxOpticsTraceToneCfgRxEnable—Enable/disable the receive Trace tone feature.

    • jnxOpticsTraceToneCfgDestId—The destination Id of the link ID/ the chassis and the blade. The transmit messages will also have the src id, which is this chassis id and this port info.

    • jnxOpticsTraceToneCfgTxMsg—The transmit data in the tracetone message.

    • jnxOpticsTraceToneCfgRxMsg—The received data in the trace tone message.

  • jnxOpticsPMCurrentTable—A table of current performance monitoring entries.

    • jnxOpticsPMCurrentEntry—A conceptual row that contains information about the Performance Monitoring Current Table.

    • jnxPMCurChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port.

    • jnxPMCurDiffGroupDelay—Differential group delay.

    • jnxPMCurPolarizationState—Polarization state.

    • jnxPMCurPolarDepLoss—The polarization dependent loss (PDL) is the difference (in dB) between the maximum and minimum values of the channel insertion loss (or gain) of the black-link from point SS to RS due to a variation of the state of polarization (SOP) over all SOPs.

    • jnxPMCurQ—'Q' factor estimated at Rx Transceiver port.

    • jnxPMCurSNR—SNR–signal-to-noise ratio.

    • jnxPMCurTxOutputPower—TxOutputPower–transmit output power.

    • jnxPMCurRxInputPower—RxInputPower–receive output power

    • jnxPMCurMinChromaticDispersion—Minimum Residual Chromatic Dispersion measured at Rx Transceiver port.

    • jnxPMCurMaxChromaticDispersion—Maximum Residual Chromatic Dispersion measured at Rx Transceiver port.

    • jnxPMCurAvgChromaticDispersion—Average Residual Chromatic Dispersion measured at Rx Transceiver port.

    • jnxPMCurMinDiffGroupDelay—Minimum Differential group delay

    • jnxPMCurMaxDiffGroupDelay—Maximum Differential group delay

    • jnxPMCurAvgDiffGroupDelay—Average Differential group delay

    • jnxPMCurMinPolarState—Minimum Polarization state

    • jnxPMCurMaxPolarState—Maximum Polarization state

    • jnxPMCurAvgPolarState—Average Polarization state

    • jnxPMCurMinPolarDepLoss—Minimum polarization dependent loss (PDL)

    • jnxPMCurMaxPolarDepLoss—Maximum polarization dependent loss (PDL)

    • jnxPMCurAvgPolarDepLoss—Average polarization dependent loss (PDL)

    • jnxPMCurMinQ—Minimum 'Q' factor estimated at Rx Transceiver port.

    • jnxPMCurMaxQ—Max 'Q' factor estimated at Rx Transceiver port.

    • jnxPMCurAvgQ—Average 'Q' factor estimated at Rx Transceiver port.

    • jnxPMCurMinSNR—Minimum SNR–signal-to-noise ratio

    • jnxPMCurMaxSNR—Maximum SNR–signal-to-noise ratio

    • jnxPMCurAvgSNR—Average SNR–signal-to-noise ratio

    • jnxPMCurMinTxOutputPower— Minimum TxOutputPower–transmit output power

    • jnxPMCurAvgTxOutputPower—Average TxOutputPower–transmit output power

    • jnxPMCurMinRxInputPower—Minimum RxInputPower–receive output power

    • jnxPMCurMaxRxInputPower—Maximum RxInputPower–receive output power

    • jnxPMCurAvgRxInputPower—Average RxInputPower–receive output power

    • jnxPMCurSuspectedFlag—If true, the data in this entry may be unreliable.

    • jnxPMCurSuspectReason —If SuspectedFlag is true, the reason for the performance monitoring data being suspect.

  • jnxOpticsPMIntervalTable—A table of current performance monitoring entries.

    • jnxOpticsPMIntervalEntry—A conceptual row that contains information about the Performance Monitoring Interval Table.

    • jnxOpticsPMIntervalNumber—This is the 15 minute interval number.

    • jnxPMIntMinChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–minimum in the 15 minute interval.

    • jnxPMIntMaxChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–maximum in the 15 minute interval.

    • jnxPMIntAvgChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–average in the 15 minute interval.

    • jnxPMIntMinDiffGroupDelay—Differential group delay measured at Rx Transceiver port–minimum in the 15 minute interval.

    • jnxPMIntMaxDiffGroupDelay—Differential group delay measured at Rx Transceiver port–maximum in the 15 minute interval

    • jnxPMIntAvgDiffGroupDelay—Differential group delay measured at Rx Transceiver port–average in the 15 minute interval

    • jnxPMIntMinPolarState—Polarization state–minimum in the 15 minute interval

    • jnxPMIntMaxPolarState—Polarization state–max in the 15 minute interval

    • jnxPMIntAvgPolarState—Polarization state–average in the 15 minute interval

    • jnxPMIntMinPolarDependentLoss—Polarization Dependent Loss–minimum in the 15 minute interval

    • jnxPMIntMaxPolarDependentLoss—Polarization Dependent Loss–maximum in the 15 minute interval

    • jnxPMIntMinQ—Q–minimum in the 15 minute interval

    • jnxPMIntMaxQ—Q–maximum in the 15 minute interval

    • jnxPMIntAvgQ—Q–Average in the 15 minute interval

    • jnxPMIntMinSNR—SNR–minimum in the 15 minute interval

    • jnxPMIntMaxSNR—SNR–maximum in the 15 minute interval

    • jnxPMIntAvgSNR—SNR–average in the 15 minute interval

    • jnxPMIntMinTxOutputPower—TxOutputPower–minimum in the 15 minute interval

    • jnxPMIntMaxTxOutputPower—TxOutputPower–maximum in the 15 minute interval

    • jnxPMIntAvgTxOutputPower—TxOutputPower–average in the 15 minute interval

    • jnxPMIntMinRxInputPower—RxInputPower–minimum in the 15 minute interval

    • jnxPMIntMaxRxInputPower—RxInputPower–maximum in the 15 minute interval

    • jnxPMIntAvgRxInputPower—RxInputPower–average in the 15 minute interval

    • jnxPMIntTimeStamp—Time stamp performance monitoring interval

    • jnxPMIntSuspectedFlag—If true, the data in this entry may be unreliable.

    • jnxPMIntSuspectReason—If SuspectedFlag is true, the reason for the performance monitoring data being suspect.

  • jnxOpticsPMDayTable—A table of current performance monitoring Day entries.

    • jnxOpticsPMDayEntry—A conceptual row that contains information about the performance monitoring Day Table

    • jnxOpticsPMDayIndex—This is 0 - cur day/ 1- prev day

    • jnxPMDayMinChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–minimum in the day

    • jnxPMDayMaxChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–maximum in the day

    • jnxPMDayAvgChromaticDispersion—Residual Chromatic Dispersion measured at Rx Transceiver port–average in the day

    • jnxPMDayMinDiffGroupDelay—Differential Group Delay measured at Rx Transceiver port–minimum in the day

    • jnxPMDayMaxDiffGroupDelay—Differential Group Delay measured at Rx Transceiver port–maximum in the day

    • jnxPMDayAvgDiffGroupDelay—Differential Group Delay measured at Rx Transceiver port–average in the day

    • jnxPMDayMinPolarState—Polarization state–minimum in the day

    • jnxPMDayMaxPolarState—Polarization state–maximum in the day

    • jnxPMDayAvgPolarState—Polarization state–average in the day

    • jnxPMDayMinPolarDependentLoss—Polarization Dependent Loss–minimum in the day

    • jnxPMDayMaxPolarDependentLoss—Polarization Dependent Loss–maximum in the day

    • jnxPMDayAvgPolarDependentLoss—Polarization Dependent Loss–average in the day interval

    • jxPMDayMinQ—Q–minimum in the day

    • jnxPMDayMaxQ—Q–maximum in the day

    • jnxPMDayAvgQ—Q–Average in the day

    • jnxPMDayMinSNR—SNR–min in the day

    • jnxPMDayMaxSNR—SNR–max in the day

    • jnxPMDayAvgSNR—SNR–avg in the day

    • jnxPMDayMinTxOutputPower—TxOutputPower–minimum in the day

    • jnxPMDayMaxTxOutputPower—TxOutputPower–maximum in the day.

    • jnxPMDayAvgTxOutputPower—TxOutputPower–average in the day.

    • jnxPMDayMinRxInputPower—RxInputPower–minimum in the day.

    • jnxPMDayMaxRxInputPower—RxInputPower–maximum in the day.

    • jnxPMDayAvgRxInputPower—RxInputPower–average in the day.

    • jnxPMDayTimeStamp—Time for the Day.

    • jnxPMDaySuspectedFlag—If true, the data in this entry may be unreliable.

    • jnxPMDaySuspectReason—If SuspectedFlag is true, the reason for the performance monitoring data being suspect.

Alarms for OTN Interfaces

The following alarms are applicable for management of OTN interface for Juniper products.

  • jnxIfAdminStates–Administraion state of the interface.

    • jnxAdminStatInService(1)—In service.

    • jnxAdminStateInServiceMA(2)—In service maintenance, the link is in service, but the alarms are suppressed.

    • jnxAdminStateOutofService(3)—Out of service due to a fault.

    • jnxAdminStateOutofServiceMA(4)—Out of service maintenance as configured by the user, may or may not have alarms.

  • jnxIfOperStates—Operation states of the interface.

    • jnxOperStateInit(1)—Starting state of the interface.

    • jnxOperStateNormal(2)—The interface is working normally.

    • jnxOperStateFault(3)—There is some traffic affecting fault on the interface, for example, LOS.

    • jnxOperStateDegraded(4)—There is some function affecting the performance on the interface resulting in degradation, for example BER.

  • jnxIfOtnRate—Rates for an interface.

  • jnxIfOtnFecType—FEC modes of an interface.

  • jnxIfOtnLayer—Layer which describes the table.

  • jnxIfOtnType—Near end of far end

  • jnxIfOtnDirection—Direction for the entities in the table.

  • jnxIfOtnSeverity—Severity of the notification.

  • jnxIfOtnServiceStateAction—Notification action on the service state.

  • jnxIfOtnOtukNotificationId–Identifies specific OTN alarms that may exist on an interface.

    • jnxIfOtnOtnLosAlarm(1)

    • jnxIfOtnOtnLofAlarm(2)

    • jnxIfOtnOtnLomAlarm(3)

    • jnxIfOtnOtnOtuSsfAlarm(4)

    • jnxIfOtnOtnOtuBdiAlarm(5)

    • jnxIfOtnOtnOtuTtimAlarm(6)

    • jnxIfOtnOtnOtuIaeAlarm(7)

    • jnxIfOtnOtuBiaeAlarm(8)

    • jnxIfOtnOtuDegAlarm(9)

    • jnxIfOtnOtuFecExcessiveErrsAlarm(11)

    • jnxIfOtn15MinThreshBBETCA(12)

    • jnxIfOtn15MinThreshESTCA(13)

    • jnxIfOtn15MinThreshSESTCA(14)

    • jnxIfOtn15MinThreshUASTCA(15)

    • jnxIfOtn15MinThreshFcsTCA(16)

    • jnxIfOtn15MinThUnCorrectedWordsTCA(17)

    • jnxIfOtn15MinThreshPreFECBERTCA(18)

  • JnxIfOtnOdukTcmNotificationId—Alarms from the ODUk and TCM layers.

    • jnxIfOtnOdukTcmOciAlarm(1)

    • jnxIfOtnOdukTcmLckAlarm(2)

    • jnxIfOtnOdukTcmBdiAlarm(3)

    • jnxIfOtnOdukTcmTimAlarm(4)

    • jnxIfOtnOdukTcmDegAlarm(5)

    • jnxIfOtnOdukTcmIaeAlarm(6)

    • jnxIfOtnOdukTcmLTCAlarm(7)

    • jnxIfOtnOdukTcmCSfAlarm(8)

    • jnxIfOtnOdukTcmSSfAlarm(9)

    • jnxIfOtnOdukTcmTSfAlarm(10)

    • jnxIfOtnOdukTcm15MinThreshBBETCA(11)

    • jnxIfOtnOdukTcm15MinThreshESTCA(12)

    • jnxIfOtnOdukTcm15MinThreshSESTCA(13)

    • jnxIfOtnOdukTcm15MinThreshUASTCA(14)

    • jnxIfOtnOdukTcm15MinThreshFcsTCA(15)

    • jnxIfOtnOdukTcmAisAlarm(16)

  • jnxIfOtnOChCfgTable—This table provides information on the Otn OCh configuration.

    • jnxIfOtnOChCfgEntry

    • jnxIfOtnOChCfgContainerIndex

    • jnxIfOtnOChCfgL1Index

    • jnxIfOtnOChCfgL3Index

  • jnxIfOtnLocalLoopback—Local loopback at the line after the optics.

  • jnxIfOtnLineLoopback—Line loopback at the line.

  • jnxIfOtnPayloadLoopback—Payload loopback after the optics.

  • jnxIfOtnAdminState

  • jnxIfOtnOperState—Operation state of the interface.

  • jnxIfOtnIndex-IfIndex of the interface.

  • jnxIfOtnOChStatus

  • jnxIfOtnOChPortMode— Port mode of the interface.

  • jnxIfOtnOTUkCfgTable—This table provides information on the Otn OTUk configuration.

    • jnxIfOtnOTUkCfgEntry—A conceptual row that contains the Otn OTUk configuration table.

    • jnxIfOtnOTUkCfgContainerIndex—The associated jnxContentsContainerIndex, for example, shelf.

    • jnxIfOtnOTUkCfgL1Index—The level one index associated with the subject, for example, slot.

    • jnxIfOtnOTUkCfgL2Index—The level two index associated with the subject, for example, port.

    • jnxIfOtnOTUkCfgL3Index— The level three index associated with the subject, for example channel.

    • jnxIfOtnOTUkCfgRate— The rate for the interface, depending on the interface/fru type.

    • jnxIfOtnOTUkCfgFecMode—The FEC type in the OTU frame, the selection depends on the interface/fru type.

    • jnxIfOtnOTUkEnableAutoFrrByteInsert—Enable or disable the automatic insertion of the frr SF/SD byte in the overhead bytes(RES).

    • jnxIfOtnOTUkEnableBERFrrSupport—Enable of disable the FRR support for BER.

    • nxIfOtnOTUkPreFecBERThresholdMantissa—Sets the BER threshold(mantissa), which when crossed triggers signal degrade.

    • jnxIfOtnOTUkPreFecBERThresholdExponent —Sets the BER threshold(exponent), which when crossed triggers signal degrade.

    • jnxIfOtnOTUkPreFecBERThresholdTime—The collection time to calculate the BER.

    • jnxIfOtnOTUkTIMActEnabled—Indicates whether or not the Trace Identifier Mismatch (TIM) consequent action function is enabled.

    • jnxIfOtnOTUkTxTTI— The Trace TTI SAPI 0..15, DAPI 16..31 32..63 user defined.

    • jnxIfOtnOTUkRxTTI— The Receive Trace TTI SAPI 0..15, DAPI 16..31 32..63 user defined.

    • jnxIfOtnOTUkExpectedRxSapi — Expected receive SAPI.

    • jnxIfOtnOTUkExpectedRxDapi-Expected receive DAPI.

    • jnxIfOtnOTUkStatus—The status of the interface.

    • jnxIfOtnOTUkPreFecBERThresholdClearMantissa—Sets the BER threshold(mantissa) for clear signal degrade condition, which signal degrade condition will be cleared when Pre-FEC error count is below the clear threshold error count.

    • jnxIfOtnOTUkPreFecBERThresholdClearExponent—Sets the BER threshold(exponent) for clear signal degrade condition, which signal degrade condition will be cleared when Pre-FEC error count is below the clear threshold error count.

    • jnxIfOtnODUkCfgTable-This table provides information on the Otn ODUk configuration.

      • jnxIfOtnODUkCfgEntry—A conceptual row that contains information about the Otn ODUk configuration.

      • jnxIfOtnODUkCfgContainerIndex—The associated jnxContentsContainerIndex, for example, shelf.

      • jnxIfOtnODUkCfgL1Index—The level one index associated with this subject, for example slot.

      • jnxIfOtnODUkCfgL2Index—The level two index associated with the subject, for example, port.

      • jnxIfOtnODUkCfgL3Index—The level three index associated with the subject, for example channel.

      • jnxIfOtnODUkAPSPCC0—Read/Write APS PCC byte 0 for this ODUk only.

      • jnxIfOtnODUkAPSPCC1—Read/Write APS PCC byte 1 for this ODUk only.

      • jnxIfOtnODUkAPSPCC2—Read/Write APS PCC byte 2 for this ODUk only.

      • jnxIfOtnODUkAPSPCC3—Read/Write APS PCC byte 3 for this ODUk only.

      • jnxIfOtnODUkPayloadType—Read/Write Payload Type for ODUk only.

      • jnxIfOtnODUkTIMActEnabled—Indicates whether or not the Trace Identifier Mismatch (TIM) consequent action function is enabled. The default value of this object is false(2).

      • jnxIfOtnODUkTxTTI—The Trace TTI SAPI 0..15, DAPI 16..31 32..63 user defined for this layer.

      • jnxIfOtnODUkRxTTI—The Receive Trace TTI SAPI 0..15, DAPI 16..31 32..63 user defined.

      • jnxIfOtnODUkExpectedRxSapi—Expected receive SAPI for this layer.

      • jnxIfOtnODUkExpectedRxDapi–-Expected receive DAPI for this layer.

      • jnxIfOtnODUkStatus—The status of the interface. Only some of these alarms are valid for the TCM layer.

      • jnxIfOtnODUkRxPayloadType—Receive payload type for ODUk only.

    • jnxIfOtnTcmCfgTable—This table provides information on the Otn TCM configuration.

      • jnxIfOtnTcmCfgEntry—A conceptual row that contains information about the Otn Tcm configuration.

      • jnxIfOtnTcmCfgContainerIndex—The associated jnxContentsContainerIndex, for example shelf.

      • jnxIfOtnTcmCfgL1Index—The level one index associated with this subject, for example, slot.

      • jnxIfOtnTcmCfgL2Index—The level one index associated with this subject, for example, port.

      • jnxIfOtnTcmCfgL3Index—The level one index associated with this subject, for example, channel.

      • jnxIfOtnTcmCfgLevel—The TCM level for the table.

      • jnxIfOtnTCMEnable—Enable this TCM layer (only for TCM layers)

      • jnxIfOtnTcmTxTTI—The Trace TTI SAPI 0..15, DAPI 16..31 32 ..63 user defined for this layer.

      • jnxIfOtnTcmRxTTI—The Receive Trace TTI SAPI 0..15, DAPI 16..31 32 ..63 user defined for this layer.

      • jnxIfOtnTcmExpectedRxSapi—Expected receive SAPI for this layer.

      • jnxIfOtnTcmExpectedRxDapi—Expected receive DAPI for this layer.

      • jnxIfOtnTcmStatus—Status of this layer.

  • jnxIfOtnODUkTcmTestTable—This table provides information on the Otn ODUk test function.

    • jnxIfOtnODUkTcmTestEntry—A conceptual row that contains information about the Otn ODUk test function.

    • jnxIfOtnODUkTcmTestLayer—The OTU/ODU/TCM layer for the alarm.

    • jnxIfOtnODUkTcmTestTCMLevel—For ODUk will be this will be 0 If layer is TCM then this will give the TCM level 1..6.

    • jnxIfOtnODUkTcmInsertAis—Insert ODU Ais into OTN stream.

    • jnxIfOtnODUkTcmInsertLck—Insert ODU Lck into OTN stream.

    • jnxIfOtnODUkTcmInsertOci—Insert ODU Oci into OTN stream.

  • jnxIfOtnODUkPayloadPRBS—Insert Payload PRBS, For ODUk layer and TCM level is 0.

  • jnxIfOtnODUkPayloadPRBSResult—Result of the Payload PRBS.

  • jnxIfOtnODUkTcmDMTable—Table for OTN ODUk/TCM Delay Measurement configuration table.

  • jnxIfOtnODUkTcmDMEntry—A conceptual row that contains information about the Delay Measurement (DM) test table.

    • jnxIfOtnODUkTcmDMLayer—The layer OTU/ODU/TCM layer for the alarm

    • jnxIfOtnODUkTcmDMLevel—For ODUk, this value is 0, if layer is TCM then this gives the TCMlevel 1..6.

  • jnxIfOtnDMConnectionMonitoringEndpoint—Originate Connection Monitoring Endpoint for the Delay Measurement.

  • jnxIfOtnDMBypass—Act as tandem, passing DM value through node.

  • jnxIfOtnDMPersistFrames—Number of consecutive frames required to declare DM Complete.

  • jnxIfOtnDMEnable—Start/Stop the DM measurement.

Configuring Global Alarm Notifications

You can configure global e-mail notifications to be sent when any alarm with notifications enabled is generated. To configure global e-mail notifications, enter the e-mail addresses to receive global alarm notifications in the Alarm Notifications Destinations field in the Global Settings section. Separate addresses with a comma (,). For information about enabling notification for an alarm, see Configuring Individual Alarm Notifications.

Retaining Alarm History

Use the No. of days to keep Alarm field in the Global Settings section to specify the number of days to keep alarm history. The default retention time is 120 days; but you can specify a period of 7 through 1000 days. Specifying a longer retention time consumes more database resources. To change the alarm retention duration, type a new value and click OK and Yes to confirm the change.

Specifying Event History

Use the Events/Alarm field in the Global Settings section to specify the number of event entries that are kept in the alarm history. The default setting for events is 20. To change the setting, type a new value and click OK and Yes to confirm the change.

Enabling Alarms

Ensure all devices are configured to send traps to Connectivity Services Director. This task is performed for the devices in Deploy mode through Set SNMP Trap Configuration.

Use the Individual Alarms and Threshold Settings section to disable and re-enable individual alarms or all alarms. Alarms appear on both tabs in the section: Alarm Settings and Threshold Settings. Fault alarms are preconfigured and initially enabled. To enable or disable alarms:

  1. (Optional) Sort the alarms. By default, the list of alarms is sorted alphabetically within each category. You can also sort by description or alarm severity within a category by clicking a column heading.
  2. Review the alarms and either select the check box in the heading to select all of the alarms or select the check box for the individual alarms you want to enable.
  3. Click OK and Yes to confirm the alarm change.

Changing the Severity of Individual Alarms

You can change the severity of the alarms to match your corporate procedures and guidelines. For example, at your company a DoS attack might be considered a critical alarm, while Connectivity Services Director has a default severity for DoS attacks as a major alarm. Alarms appear on both tabs in the Individual Alarms and Threshold Settings section: Alarm Settings and Threshold Settings.

To change the severity of an alarm:

  1. Select the current severity in the Severity column. A list of the severity levels appear.
  2. Select the new severity level for the alarm.
  3. Click OK and Yes to confirm the change to the severity setting.

    To configure alarm notifications, see Configuring Individual Alarm Notifications.

Configuring Individual Alarm Notifications

You can configure e-mail notifications to be sent when an individual alarm is generated. When you enable notification for an alarm, the notifications are sent to the e-mail addresses configured for the alarm and the addresses configured for global alarm notifications. Alarms appear on both tabs in the Individual Alarms and Threshold Settings section: Alarm Settings and Threshold Settings.

To configure e-mail notification for an alarm name:

  1. Select the check box in the alarm’s Notification column.

    If you later want to disable notification for the alarm, clear the check box.

  2. Click Edit Notification in the Notification column. The Alarm Notification Details window opens.
  3. Enter one or more e-mail addresses in the Notification Email Addresses field. Separate addresses with a comma (,).

    You can later edit the addresses to send notifications to different addresses.

  4. (Optional) Enter a comment in the Comments field. This comment is included in the e-mail notification message.
  5. Click Save.