NMS-553-MIB: View SNMP OID List / Download MIB

Identifies the version of the MIB. The format of the version is x.yzT, where 'x' identifies the major revision number, 'y' identifies the minor revision number, 'z' identifies the typographical revision, and T identifies the test revision. Upon formal release, no designation for the test revision will be present. Acceptable values for the individual revision components are as follows: x: 1 - 9, y: 0 - 9, z: 0 - 9, T: A - Z

An entry in the GDC NMS 553 Version Table.

Identifies Version parameters associated with the managed object.

The version number of the firmware, to allow products to know which revision is installed. The released version number is sequenced from --, A-, ... AA, ... ZZ. Test versions are numerical from 01 to 99.

The GDC NMS 553 DS0 allocation table

The GDC NMS 553 Configuration table entry.

The index value which uniquely identifies the DSU to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and sub-identifier. The sub-identifier for this SC instance is the DSU.

Identifies the DSU DS0 allocation scheme.The value consecutive(2) indicates that bundles of DS0s are allocated to channels consecutively from the starting DS0. The value of alternate(3) indicates that bundles of DS0s are allocated to channels alternatly, or every other DS0 from the starting DS0. The unused DS0s are forced to marks. Note that DS0 bundles cannot be split across frames (wrap around from the highest numbered DS0 of one frame to DS0 1 of the next frame. For example, on a T1 frame using consecutive DS0 allocation, a channel configuration of starting DS0 = 20 and number of DS0s = 5 is an illegal channel configuration because the DS0 bundle wraps from DS0 #24 of 1 frame to DS0 #1 of the next. Enumeration: 'consecutive': 1, 'alternate': 2.

The GDC DS0 Allocation Configuration table. Information in the entries of this table define the configuration of DS0 allocation for channels. There are entries in this table for each channel of the associated DSU.

The GDC DS0 Allocation Configuration table entry.

The index value which uniquely identifies the channel to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and sub-identifier. The sub-indentifier for this SCinstance is the channel.

Indicates the DS0 base rate: either 56K or 64K bits per second. This is used in conjunction with the number of DS0s to determine the bandwidth of the channel. Note that base rate of 64K defines the DS0 as clear channel in which all 8 bits of the DS0 are used. A base rate of 56K defines the DS0 as non-clear in which bits 1-7 are used for channel data and the 8th bit is either unused and forced to marks or used to pass signaling information. Enumeration: 'nx64k': 2, 'nx56k': 1.

Indicates the starting DS0 number for the bundle of DS0s used for the channel. DS0 bundles are allocated starting at the DS0 defined by this integer. When this integer is set to 0, the channel is disabled and no DS0s are allocated to the channel. Note that DS0 bundles cannot be split across frames (wrap around from the highest numbered DS0 of one frame to DS0 1 of the next frame. For example, on a T1 frame using consecutive DS0 allocation, a channel configuration of starting DS0 = 20 and number of DS0s = 5 is an illegal channel configuration because the DS0 bundle wraps from DS0 #24 of 1 frame to DS0 #1 of the next.

Indicates the number of DS0s for the bundle allocated to the channel. The number of DS0s, in conjunction with the DS0 base rate, also determines the bandwidth of the channel. Note that DS0 bundles cannot be split across frames (wrap around from the highest numbered DS0 of one frame to DS0 1 of the next frame. For example, on a T1 frame using consecutive DS0 allocation, a channel configuration of starting DS0 = 20 and number of DS0s = 5 is an illegal channel configuration because the DS0 bundle wraps from DS0 #24 of 1 frame to DS0 #1 of the next.

The mode of propagation of inband Diagnostics Communication Channel to the dedicated remote NMS553 unit. None specifies no inband DCC. Embedded is an allowed value when the mib object nms553DS0BaseRate is set to Nx56K, and specifies that DCC is propagated in the 8th bit of the assigned DS0's. dccDs0 specifies that a DS0 is used for propagation of DCC, this value would be selected if the nms553DS0BaseRate is Nx64k (clear channel) since all data bits are used for user data, a minimum of two DS0's must be assigned to this device in this mode, the last ds0 should be set as the nms553DccDs0 when using this mode. Enumeration: 'none': 1, 'dccDs0': 3, 'embedded': 2.

The GDC 553 Channel Configuration table.

The nms553 Channel Configuration table entry.

The index value which uniquely identifies the channel to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and sub-identifier. The sub-indentifier for this SCinstance is the channel.

Indicates whether or not to use split timing. The value disabled(1) indicates that channel's transmit timing is provided by the DSU. The value enabled(2) indicates that the channel's transmit timing is provided by the customer business equipment (ext Tx Clk). Split timing refers to the activation of elastic storage to allow the channel interface to receive data using the customer business equipment's timing source (ext Tx Clk) and transmit that same data to the network using the networks timing source. Enumeration: 'disabled': 1, 'enabled': 2.

The channel interface type. The value none(1) indicates that there is no channel interface for the index. The value v35(2) indicates the channel interface is standard V.35 and the value eia530(3) indicates the channel interface is standard EIA 530. Enumeration: 'none': 1, 'eia530': 3, 'v35': 2.

Clock invert option Enumeration: 'txClockInvertRxClockNorm': 3, 'txClockNormRxClockInvert': 2, 'txClockNormRxClockNorm': 1, 'txClockInvertRxClockInvert': 4.

Data invert option Enumeration: 'txDataInvertRxDataInvert': 4, 'txDataNormRxDataInvert': 2, 'txDataInvertRxDataNorm': 3, 'txDataNormRxDataNorm': 1.

Controls the operation of Data Carrier Detect (DCD) signal. The value followsSignal(1) indicates that the channel's DCD follows the inband control mode idle (CMI). The value forcedOn(2) indicates that DCD is forced on. Enumeration: 'forcedOn': 2, 'followsSignal': 1.

Controls the operation of the Data Set Ready (DSR) signal. The value followsSignal(1) indicates that the channel's DSR follows the inband control mode idle (CMI). The value forcedOn(2) indicates that DSR is forced on. Enumeration: 'forcedOn': 2, 'followsSignal': 1.

Flow Control Option. This object is valid only when the control mode idle object nms553ChannelControlModeIdle is set to enabled(2). Enumeration: 'txRtsRxDcd': 1, 'txDtrRxDcd': 3, 'txRtsRxDsr': 2, 'txDtrRxDsr': 4.

Controls the function of the channel's Request To Send (RTS) and Clear To Send signals used for flow control. The value of ctsDelay10ms(1) indicates that CTS is to respond to RTS after a 10ms delay. The value of ctsOn(2) indicates that CTS is forced on at all times. The value of ctsDelayStandard(3) indicates that CTS is to respond to RTS after the standard delay of 40 bits times. For 56Kbps applications using CMI flow control, this object must be set for ctsDelayStandard(3). Enumeration: 'ctsDelay10ms': 1, 'ctsOn': 2, 'ctsDelayStandard': 3.

Controls the channel's EIA test leads. The EIA test leads allow customer business equipment to initiate diagnostic tests through the assertion of the EIA test leads RDL, LL, and ST. When this object is enabled(1), then the assertion of these leads is recognized and acted upon by the DSU. When this object is disabled(2), then the assertion of these leads is ignored by the DSU. Enumeration: 'disabled': 1, 'enabled': 2.

In-band loopcode enable/disable. The value disabled(1) indicates the channel does not enter an RDL loop when an inband RDL code is detected. The value enable(2) indicates the channel does enter an RDL loop when an inband RDL code is detected. Enumeration: 'disable': 1, 'enabled': 2.

In-band RDL code to send and/or receive by the channel. The value pn127(1) indicates that the in-band code sent/received is in accordance with CCITT V.54 PN-127 scrambled codes. Enumeration: 'pn127': 1.

The time limit in seconds before terminating a channel's RDL. The value inhibit(1) indicates that the loopdown time is disabled and the loopback will only terminate by the in-band loopdown code. The value enable10Min(2) indicates the time before terminating the RDL in the event the loopdown code is never received. Enumeration: 'inhibit': 1, 'enable10Min': 2.

Control Mode Idle (CMI) enable/disable. When the channel application is Nx56k and RTS/CTS delay is standard, then this object defines the the use of CMI to provide flow control. The value disabled(1) indicates the channel using CMI to pass control flow information. The value enabled(2) indicates the channel is using the DDS secondary channel CMI format to pass flow control information. Enumeration: 'disabled': 1, 'enabled': 2.

The GDC 553 Network Configuration table.

The nms553 Network Configuration table entry.

The index value which uniquely identifies the interface to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and sub-identifier.

The values, in sequence, describe: 'auto' indicates the unit will determine framing. 'manEsf' indicates manual selection of extended superframe format. 'manD4'indicates manual selection of D4 framing format. 'unframed' indicates manual selection of unframed format. Enumeration: 'manEsf': 2, 'auto': 1, 'unframed': 4, 'manD4': 3.

The values, in sequence, describe: 'manEsf' indicates the current setting of Line type. 'manD4'indicates the current setting of Line type. 'unframed' indicates the current setting of Line type. Enumeration: 'manEsf': 1, 'manD4': 2, 'unframed': 3.

The operating mode of the interface. Setting the value of this object to ds1(1) configures the interface as standard DS1. Setting the value of this object to dsx1(2) configures the interface to operate as a standard cross-connect DSX-1. This object interoperates with the nms553NetworkPreequalization object. When this object is set to ds1(1), then the value of nms553NetworkPreequalization does not apply. This object interoperates with the nms553NetworkAdminLineBuildout object. When this object is set to dsx1(2), then the value of nms553NetworkLineBuildout does not apply. Enumeration: 'dsx1': 2, 'ds1': 1.

Is the preequalization of the transmitter of the interface. This object interoperates with the object nms553NetworkInterfaceType. When the value of nms553NetworkInterfaceType is ds1(2) then this value is not applicable. Enumeration: 'none': 1, 'preeq260': 3, 'preeq390': 4, 'preeq130': 2, 'preeq655': 6, 'preeq530': 5.

This variable is used to set the Transmit Ntwk Build-Out value on the network side and is only valid if the nms553NetworkInterfaceType is set for ds1(1). The values, in sequence, describe: auto(1) indicates auto detection of receive level to determine the appropriate Ntwk build out without controller intervention man00dB(2) indicates manual selection of 0.0 dB transmit Ntwk build out man75dB(3) indicates manual selection of -7.5 dB transmit Ntwk build out man150dB(4) indicates manual selection of -15.0 dB transmit Ntwk build out Enumeration: 'man150dB': 4, 'auto': 1, 'man00dB': 2, 'man75dB': 3.

This variable is used to report the current Ntwk build-out setting if the nms553NetworkInterfaceType is set for ds1(1). tx00dB(1) indicates the unit is set for 0.0 dB of attenuation when the nms553NetworkAdminLineBuildout is set for auto (1) or man00dB (2) tx75dB(2) indicates the unit is set for -7.5 dB of attenuation when the nms553NetworkAdminLineBuildout is set for auto (1) or man75dB (3) tx150dB(3) indicates the unit is set for -15.0 dB of attenuation when the nms553NetworkAdminLineBuildout is set for auto (1) or man150dB (4) Enumeration: 'tx75dB': 2, 'tx00dB': 1, 'tx150dB': 3.

The ones density restriction for the interface. The values of this object define the ones density restriction that is enforced on the interface. The value inhibit(1) indicates that no ones density restriction is enforced. The value max15zeros(2) indicates that a maximum of 15 zeros are transmitted to the network before a one is inserted. The value max39zeros(3) indicates that a maximum of 39 zeros are transmitted to the network before a one is inserted. The value restrict8nX1(4) indicates a minimum of N ones per 8(N+1) bits, where N is in the range 1 to 24. The value min1in8(5) indicates a minimum of 1 one per 8 bits. With this value, pulse density violations are enforced but not recorded. Enumeration: 'min1in8': 5, 'max39zeros': 3, 'inhibit': 1, 'max15zeros': 2, 'restrict8XNplus1': 4.

Enumeration: 'composite': 8, 'extChannelClkA': 5, 'extChannelClkB': 6, 'extChannelClkC': 7, 'receive': 1, 'cascade': 2, 'station': 4, 'internal': 3.

Enumeration: 'receive': 1, 'internal': 2.

Controls whether or not the DCC uses the FDL as its transport. The FDL is only available when the DS1 line type is ESF, a full DS1 interface is being used, and transportation of the FDL completely through the network is supported. The value enabled(1) enables the transportation of the DCC using the FDL. The value disabled(2) disables the use of the FDL to transport the DCC, which implies that the DCC is transported by some other means. This object interoperates with the nms553NetworkLineType object. The value of this object can be set to enabled(1) only when the value of the nms553NetworkLineType is one of the ESF values. Enumeration: 'disabled': 2, 'enabled': 1.

The time in seconds when receiving a continuous AIS signal before a remotely initiated loopback is terminated. When this object has the value 4, then there is no time limit and the loop must be terminated by remotely issued in-band loopdown codes. When the object has a value between 5 and 60, then this is time in seconds of continuous AIS signal before the loopback is terminated.

This variable is used to set the In-Band DS1 Loopback Code Detection. Framed(1) framing is done upon recognition of he inband loopback code. Unframed(2) no framing is done upon recognition of the inband loopback code. Enumeration: 'unframed': 2, 'framed': 1.

This variable is used to set the In-Band DS1 Loopback Code Detection. none(1) refers to when the in-band loopback codes are ignored. payload(2) designates a payload loopback is done upon recognition of the inband loopback code. lineloop(3) designates a line loopback is done upon recognition of the inband loopback code. Enumeration: 'lineloop': 3, 'none': 1, 'payload': 2.

This variable describes the variety of Zero Code Suppression used on the link, which in turn affects a number of its characteristics. nms553B8ZS refers to the use of a specified pat- tern of normal bits and bipolar violations which are used to replace a sequence of eight zero bits. nms553AMI refers to a mode wherein no zero code suppression is present and the line encoding does not solve the problem directly. In this application, the higher layer must provide data which meets or exceeds the pulse density re- quirements, such as inverting HDLC data. Enumeration: 'nms553B8ZS': 1, 'nms553AMI': 2.

This bitmap describes the use of the facili- ties data link, and is the sum of the capabili- ties: nms553Fdl-none(1) indicates that the device does not use the FDL. nms553Ansi-T1-403(2) refers to the FDL exchange recommended by ANSI. nms553Att-54016(3) refers to ESF FDL exchanges. Enumeration: 'nms553Fdl-none': 1, 'nms553Att-54016': 3, 'nms553Ansi-T1-403': 2.

This variable is used to set the update status flag for saving network and channel configuration settings. Management can only set to network(1), channel(2), or both(3) A norm(4) will always be read. Both Network configuration and Channel configuration are saved at the same time on both(3). Configuration settings are not saved to network element by default. This permits the configuration of several objects before saving. After all objects are set-up, a (1),(2) or (3) must be sent. This will enable and save the new configuration(s). Enumeration: 'both': 3, 'norm': 4, 'network': 1, 'channel': 2.

The nms553 DTE Signal Status table. Information in the entries of this table define the status of DSU channel interface leads. There are entries in this table for each channel of the associated DSU.

The nms553 DTE Signal Status table entry.

The index value: slot, line, drop, and interface

Returns a bitwise snapshot of the DTE signals. Octet 1 bit 7 - not used bit 6 - CTS (1:ON; 0:OFF) bit 5 - RTS (1:ON; 0:OFF) bit 4 - DTR (1:ON; 0:OFF) bit 3 - DSR (1:ON; 0:OFF) bit 2 - future use bit 1 - DCD (1:ON; 0:OFF) bit 0 - future use Octet 2 bit 7 - not used bit 6 - RXC (1:Transitions) bit 5 - DCD (1:Transitions) bit 4 - RTS (1:Transitions) bit 3 - CTS (1:Transitions) bit 2 - RXD (1:Transitions) bit 1 - TXC (1:Transitions) bit 0 - TXD (1:Transitions)

The NMS 553 Diagnostics table.

The SNMP553S Diagnostics table entry.

The index value which uniquely identifies the interface to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and sub-identifier, which in this case is a network interface.

Selects the duration to run a diagnostic test. The value(1) noLimit signifies that the test should run indefinitely until explicitly terminated. Enumeration: 'testTime15Mins': 12, 'testTime10Mins': 11, 'testTime3Mins': 4, 'testTime7Mins': 8, 'testTime4Mins': 5, 'testTime25Mins': 14, 'testTime5Mins': 6, 'testTime20Mins': 13, 'testTime9Mins': 10, 'noLimit': 16, 'testTime2Mins': 3, 'testTime30Secs': 1, 'testTime30Mins': 15, 'testTime1Min': 2, 'testTime6Mins': 7, 'testTime8Mins': 9.

The 16 bit user programmable test pattern. This object works with the nms553DiagSendCode object in that when nms553DiagSendCode is set to sendProgPattern(4), the the value of this object is used as the 16 bit user programmable test pattern. This object is used for all tests defined in both the GDC dsx1 mib.

A set of 1-8 will start the selected test with the indicated pattern. A 9 cannot be set by management. A read will always return a 9. Enumeration: 'dsu2047Pattern': 6, 'unit2047Pattern': 2, 'unit511Pattern': 1, 'noselftestrunning': 9, 'unitProgPattern': 4, 'dsuProgPattern': 8, 'dsu511Pattern': 5, 'dsuQRSPattern': 7, 'unitQRSPattern': 3.

A set will start the selected test. Enumeration: 'digitalLoopback': 2, 'remoteDigitalLoopback': 3, 'nolooptestrunning': 4, 'localLoopback': 1.

The results of the last diagnostic test. This can be the current test running or the last completed test. The units of the value of this object depend on the type of diagnostic test run. For all cases except a network delay measurement, the units of the value of this object is the number of bit errors that occurred. Bit errors can be read at any time during the duration of the test. The valid range for bit errors is 0 to 4,095. 65,535 will be returned if for any reason the test was terminated early. 32,770 will be returned if the number of bit errors exceeds 4,095. For a network delay measurement, the units of the value of this test are milliseconds. If the test is terminated early then 65,535 will be returned and if the delay is greater than 4,095 then 32,770 will be returned.

This object will halt the execution of any and all diagnostic test that may be running with the exception of the Network Delay Test. Enumeration: 'resetTest': 2, 'normal': 1.

This object will return the test current test in progress, if any. Enumeration: 'unitSelfTest': 2, 'noTestinProgress': 1, 'digitalLoopback': 5, 'dsuSelfTest': 3, 'localLoopback': 4.

The table describes the maintenance functions for the nms553.

An entry in the GDC maintenance Table

The index value: slot, line, drop, and interface

Returns a bitwise snapshot of the front panel LED state and front panel switches. Octet 1 bit 7 - not used bit 6 - ON (0:LED inactive 1:LED active) bit 5 - DSX1 bit 4 - NMSRSP bit 3 - NMSDAT bit 2 - ER bit 1 - DSX OOF bit 0 - DSX LOS Octet 2 bit 7 - not used bit 6 - NET OOF bit 5 - NET LOS bit 4 - NET BPV bit 3 - NET AIS bit 2 - TM/ALM bit 1 - LBK bit 0 - future use Octet 3 bit 7 - not used bit 6 - CHA SD bit 5 - CHA RD bit 4 - CHB SD bit 3 - CHB RD bit 2 - CHC SD bit 1 - CHC RD bit 0 - future use

Supports the action of soft resetting the unit. When this object is set to reset(1), then the unit performs a soft reset. The value norm will be returned when the reset is complete. The value of norm can not be set by management. Enumeration: 'reset': 1, 'norm': 2.

This is used to allow the NonVolatile Configuration to be set to a factory default state. When this value is set to factoryDefault, the unit will reset to the default configuration. The value of normal will be returned when the initialization is complete. The value normal can not be set by management. Enumeration: 'normal': 2, 'factoryDefault': 1.

This variable is used to indicate whether the front panel switches are operational or not. Enumeration: 'inhibit': 1, 'enable': 2.

Indicates the product type of the unit. Enumeration: 'nms553d3ifp': 3, 'nms553cifp': 5, 'nms553d1ifp': 2, 'nms553d1': 1, 'nms553c': 4.

Supports the action of soft resetting the nms553ValidIntervals object. When this object is set to reset(2), then the unit will reset the nms553ValidIntervals object to zero. The value of norm(1) can not be set by management. Enumeration: 'reset': 2, 'norm': 1.

The number of previous intervals for which valid data was collected. The value will be 96 unless the interface was brought on-line within the last 24 hours, in which case the value will be the number of complete 15 minute intervals the since interface has been online.

Identifies whether or not the cascade interface cards are installed. Enumeration: 'notPresent': 1, 'present': 2.

This variable reports the absolute value of the network relative receive level of -40dB to +3dB when the nms553networkInterfaceType is set for ds1(1). Values 1 thru 40 are to be interpreted as negative values, example a value 10 equals -10dB. Values 41,42,43 are to be interpreted as +1,+2 and +3dB respectively.

The nms553AlarmConfigTable contains entries that configure alarm reporting. The structure of the table is such that alarm configuration is supported on a unit and interface basis, and then on an alarm type basis within the interface. For simplicity sake alarms, be they unit or interface related, are represented in one table.

An entry in the GDC Alarm Configuration table.

The index value which uniquely identifies the interface to which this entry is applicable.

The unique alarm identifier assigned to this alarm type. The format of this identifier is an OBJECT IDENTIFIER that has the following format: {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) xxx(x) alarm(z) yyy(y) where xxx(x) is the administratively assigned family object identifier (z) is the object identifier for alarms in the family defined MIB and yyy(y) is the administratively assigned alarm type identifier for this alarm.

This variable sets/reads the BPV alarm window. This window is used with the alarm threshold to determine how long the alarm should be active before reporting. Enumeration: 'disabled': 1, 'last1hr': 4, 'infinite': 5, 'last1sec': 2, 'last1min': 3.

This function sets/reads the BPV alarm threshold criteria. This threshold is used along with the the alarm window to determine the number of instances in a given time frame for an alarm to occur before the alarm is considered active. Enumeration: 'thresGT10': 1, 'thresGT100': 2, 'thresGT1000': 3, 'thresGT10000': 4.

The nms553AlarmHistoryTable contains entries that report the history of all supported alarms. The history consists of the the number of times the alarm has occurred since last history reset, the time of the first alarm occurence (hours,minutes, seconds,day,month,year), and the time of the last alarm occurrence (hours,minutes,seconds,day,month,year). The structure of the table is such that alarm status is supported on a unit or interface basis, and then on an alarm type basis within the interface. For simplicity sake and to support the reporting of status of all alarms, a unit is treated as an interface 1 in this table.

An entry in the GDC NMS553 Alarm History table.

The index value which uniquely identifies the interface to which this entry is applicable.

The unique alarm identifier assigned to this alarm type. The format of this identifier is an OBJECT IDENTIFIER that has the following format: {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) xxx(x) alarm(z) yyy(y) where xxx(x) is the administratively assigned family object identifier (z) is the object identifier for alarms in the family defined MIB and yyy(y) is the administratively assigned alarm type identifier for this alarm.

The number of occurrences of this alarm. This objects value is incremented once for each time that the alarm occurs. This count is incremented regardless of whether or not the alarm is masked or is not reporteded because of the threshold configuration.

The hour (0-23) the alarm first occurred.

The minute (0-59) the alarm first occurred.

The second (0-59) the alarm first occurred.

The month (1-12) the alarm first occurred.

The day (1-31) the alarm first occurred.

The year (0-99) the alarm first occurred.

The hour (0-23) the alarm last occurred.

The minute (0-59) the alarm last occurred.

The second (0-59) the alarm last occurred.

The month (1-12) the alarm last occurred.

The day (1-31) the alarm last occurred.

The year (0-99) the alarm last occurred.

The nms553AlarmMaintenanceTable contains entries that configure the real time clock and that clear the alarm history table.

An entry in the GDC nms553 Alarm Maintenance Table.

The index value which uniquely identifies the interface to which this entry is applicable.

Supports the action of clearing the alarm history table. When this object is set to clear(1), then the unit clears the alarm history table. The value of norm(2) will be returned when the clear is complete. The value of norm(2) can not be set by management. Enumeration: 'clear': 1, 'norm': 2.

The hour of day (0-23) to be set or read.

The minute of the hour (0-59) to be set or read.

The second of the minute (0-59) to be set or read.

The month of the year (1-12) to be set or read.

The day of the month (1-31) to be set or read.

The year (0-99) to be set or read.

Returns the time (hours,minutes,seconds,month,day,year) of the last alarm clear command sent to the unit. Octet 1 - Hour of last alarm clear (0-23) Octet 2 - Minute of last alarm clear (0-59) Octet 3 - Second of last alarm clear (0-59) Octet 4 - Month of last alarm clear (1-12) Octet 5 - Day of last alarm clear (1-31) Octet 6 - Year of last alarm clear (0-99).

The nms553 Current table. This table supplements the entries in the DS1 AT&T performance table of the DS1 MIB defined in RFC1406.

An entry in the nms553 Current table.

The index value which uniquely identifies the interface to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and interface, which in this case is a network interface.

The number of Errored Seconds, encountered by a DS1 interface in the current 15 minute inter- val.

The number of Severely Errored Seconds encoun- tered by a DS1 interface in the current 15 minute interval.

The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the current 15 minute interval.

The number of Unavailable Seconds encountered by a DS1 interface in the current 15 minute in- terval.

The number of Loss of Frame Counts (LOFCs) encountered by a DS1 interface in the current 15 minute interval.

The number of Controlled Slip Seconds encoun- tered by a DS1 interface in the current 15 minute interval.

The nms553 Interval table. This table supplements the entries in the DS1 AT&T performance table of the DS1 MIB defined in RFC1406.

An entry in the DS1 Interval table.

The index value which uniquely identifies the interface to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and interface, which in this case is a network interface.

A number between 1 and 96, where 1 is the most recently completed minute interval and 96 is the least recently completed 15 minutes interval (assuming that all 96 intervals are valid).

The number of Errored Seconds encountered by a DS1 interface in one of the previous 96, indi- vidual 15 minute, intervals.

The number of Severely Errored Seconds encoun- tered by a DS1 interface in one of the previous 96, individual 15 minute, intervals.

The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in one of the previous 96, individual 15 minute, intervals.

The number of Unavailable Seconds encountered by a DS1 interface in one of the previous 96, individual 15 minute, intervals.

The number of Loss of Frame Counts (LOFCs) encountered by a DS1 interface in the current 15 minute interval.

The number of Controlled Slip Seconds encoun- tered by a DS1 interface in one of the previous 96, individual 15 minute, intervals.

The DS1 Total table. 24 hour interval. This table supplements the entries in the DS1 AT&T performance table of the DS1 MIB defined in RFC1406.

An entry in the DS1 Total table.

The index value which uniquely identifies the interface to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, drop, and interface, which in this case is a network interface.

The number of Errored Seconds encountered by a DS1 interface in the previous 24 hour interval

The number of Severely Errored Seconds encoun- tered by a DS1 interface in the previous 24 hour interval.

The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24 hour interval.

The number of Unavailable Seconds encountered by a DS1 interface in the previous 24 hour in- terval.

The number of Loss of Frame Counts (LOFCs) encountered by a DS1interface in the current 15 minute interval.

The number of Controlled Slip Seconds encoun- tered by a DS1 interface in the previous 24 hour interval.