Carrier Access AB II manual ColdStart Trap and warmStart Trap

Page 32

coldStart Trap and warmStart Trap

These traps are combined in the Access Bank II:

A coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the agent’s configu- ration or the protocol entity implementation may be altered. This is typically a power reset.

A warmStart(1) trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. This is typically a software reset.

linkDown Trap

A linkDown(2) trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent’s configuration. The Trap-PDU of type linkDown contains as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface.

linkUp Trap

A linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communication links rep- resented in the agent’s configuration has come up. The Trap-PDU of type linkUp contains as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface.

authenticationFailure Trap

An authenticationFailure(4) trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation-specific mechanism.

enterpriseSpecific Trap

A enterpriseSpecific(6) trap signifies that the sending protocol entity recognizes that some enterprise-specific event has occurred. The specific-trap field identifies the particular trap, which occurred (to be implemented in the future).

Warning: To use the Trap Facilities, you must configure at least one of the three available NMS addresses to receive the trap messages.

2-6

Page 31 Page 33
Image 32
Page 31 Page 33
Contents Access Bank Page Page Page Access Bank Access Bank Access Bank II SnmpAccess Bank II Sdsl Access Bank II Snmp SdslPage Contents Data Port Setup Getting Started System RequirementsSoftware Installation Installing Remote MonitorSoftware Overview Creating a Shortcut on the DesktopRemote Monitor Connecting the PC Directly to the Access Bank 560DQDJHPHQW&DEOHConnecting a Modem to the Access Bank II for Remote Access WR%0Starting Up Remote Monitor Pull-Down Menus Setting Up Remote Monitor Selecting the Current ProductSetting Up Remote Management Connecting to the Access Bank Click on Connect Now, orSetting Up Remote Monitor Help General Rules and Tips for Using the Remote Monitor Reading and Sending ScreensPage Changing to a New Product Saving ConfigurationsScreen Flagging Loading Configurations MiscellaneousFlagging Changed Screens System SetupSystem Setup Screens Names Screen Problem Reporting Screen System Clock Screen Snmp ScreenConfiguring Network Parameters ColdStart Trap and warmStart Trap Configuring System Group Information Page T1 Setup T1 Setup2 T1 Hardware Setup System Clock SourceT1 Definitions Line Build Out LBO Data Port Setup V.35 Data Port SetupSetting the CTS Control Option Setting the Synchronous Data Rate or Asynchronous Subrate RS-232 Data Port SetupRS-232 Data Port Setup Synchronous Data Rate Option Asynchronous Subrate Options Page Connections Static ConnectionsConnecting Individual Channels Configuring Contiguous Channels Channel TypeChannel/Signal Type Screen Performance Event Log ScreenMessage Event Log Screen 3 T1 History Retrieving Events from the Event LogClearing the Event Log Loss of Received T1 Signal Also called Loss of Carrier DefinitionsSeverely Errored Seconds 5 T1 History Last 24 HoursLoopback Configuration MaintenanceTesting TSI Bert Internal Bert Configuration Loopback Configuration SettingsAnalog Ports Update Interval Update IntervalsFXS Lcfo LCF LEDs System LEDs DIP Switches Definition of V.35 Status LED last LEDDIP Switches
Top Page Image Contents