COSINE-ORION-MIB: View SNMP OID List / Download MIB

The MIB module to describe generic objects for IPNOS system.

A orionBladeRemoved trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the one of the existing Blade was removed from it's slot.

A csOrionBladeInserted trap signifies that SNMPv2 entity, acting in an agent role, has detected that the one of the Blade was inserted in the empty slot.

A csOrionBladeStateChange signifies that the SNMPv2 entity acting in an agent role, has detected that a Blade has changed states. A description of the Blade as well as the entered state is identified in this trap.

A csOrionFanStatusChange trap signifies that the SNMPv2 entity, acting in an agent role, has detected a change in the status of a fan.

A csOrionConfigChange trap signifies that the SNMPv2 entity, acting in an agent role, has detected that Configuration was changed. The Trap PDU for this csOrionConfigChange, also carries each of the modified object's OID followed by the changed value. In effect, there are one or more VarBinds follows the csOrionNumConfigChanges object of the Trap PDU. Since these OIDs are the member of one of the table defined in this MIB, type information of the value shall be got from the OID. If the csOrionConfigChangeType is delete, the VarBind that follows the csOrionNumConfigChanges contains the Index(es) of the entry which was deleted. If the csOrionConfigChangeType is addModify, then the VarBind contains all the changed OID-Value pairs followed by the index(es).

This trap indicates that the temperature status of the Orion system has changed states. If the value of csOrionSystemTempStatus is tempRisingAboveUpperCriticalThreshold(1), the given sensor has detected a transition from the normal temperature range to the hot range. If the value of csOrionSystemTempStatus is tempFallingBelow- UpperCriticalThreshold (2), the given sensor has detected a transition from the 'hot' range back down to the normal range.

This trap indicates one of the power supplies has changed state. The following events are reported: supplyModuleInserted (1) supplyModuleRemoved (2) inputVoltageRisingAbovePastLowerCriticalThreshold (3) inputVoltageFallingBelowLowerCriticalThreshold (4) outputVoltageRisingAboveLowerCriticalThreshold (5) outputVoltageFallingBelowLowerCriticalThreshold (6) outputCurrentRisingAboveUpperCriticalThreshold (7) outputCurrentFallingBelowUpperCriticalThreshold (8) auxVoltageRisingAboveLowerCriticalThreshold (9) auxVoltageFallingBelowLowerCriticalThreshold (10) temperatureRisingAboveUpperCriticalThreshold (11) temperatureFallingBelowUpperCriticalThreshold (12) currentShareRisingAboveLowerCriticalThreshold (13) currentShareFallingBelowLowerCriticalThreshold (14)

This trap indicates that a Logical Link on the Orion is about to enter the down state.

This trap indicates that a Logical Link on the Orion is about to enter the up state.

A csOrionVIfDown trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the csOrionVIfOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of csOrionVIfOperStatus.

A csOrionVIfUp trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.

An csOspfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup).

A csOspfIfStateChange trap signifies that there has been a change in the state of an OSPF vir- tual interface. This trap should be generated when the inter- face state regresses (e.g., goes from Point- to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point).

A csOspfNbrStateChange trap signifies that there has been a change in the state of a non- virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When an neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be gen- erated by the designated router. A designated router transitioning to Down will be noted by csOspfIfStateChange.

An csOspfIfStateChange trap signifies that there has been a change in the state of an OSPF vir- tual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).

An csOspfIfConfigError trap signifies that a packet has been received on a non-virtual in- terface from a router whose configuration parameters conflict with this router's confi- guration parameters. Note that the event op- tionMismatch should cause a trap only if it prevents an adjacency from forming.

An csOspfConfigError trap signifies that a pack- et has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an ad- jacency from forming.

An csOspfIfAuthFailure trap signifies that a packet has been received on a non-virtual in- terface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.

An csOspfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or au- thentication type conflicts with this router's authentication key or authentication type.

An csOspfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.

An csOspfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.

An csOspfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a non- virtual interface. All packets that may be re- transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.

An csOspfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmit- ted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.

An csOspfOriginateLsa trap signifies that a new LSA has been originated by this router. This trap should not be invoked for simple refreshes of LSAs (which happesn every 30 minutes), but instead will only be invoked when an LSA is (re)originated due to a topology change. Addi- tionally, this trap does not include LSAs that are being flushed because they have reached MaxAge.

An csOspfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.

An csOspfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data- base has exceeded csOspfExtLsdbLimit.

An csOspfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link- state database has exceeded ninety percent of csOspfExtLsdbLimit.

A csOrionCustomerVrUp trap signifies that a Virtual Router which services a customer network has has come up.

A csOrionCustomerVrDown trap signifies that a Virtual Router which services a customer network has gone down.

A csOrionServiceProviderVrUp trap signifies that a Virtual Router which is designated as a service provider VR has has come up.

A csOrionServiceProviderVrDown trap signifies that a Virtual Router which is designated as a service provider VR has gone down.

A csOrionControlVrUp trap signifies that a Virtual Router which is designated as a control VR has come up. If a csOrionBladeRemoved Trap precedes this trap and if that blade is the master control blade then this trap might be from the control VR of the new master blade.

A csOrionControlVrDown trap signifies that a Virtual Router which is designated as a control VR has gone down.

A csOrionServiceProviderVIfUp trap signifies that a Virtual Interface on a Service Provider VR has come up.

A csOrionServiceProviderVIfDown trap signifies that a Virtual Interface on a Service Provider VR has gone down.

A csOrionLossOfSignal trap signifies that a physical port on a blade experiencing loss of signal(LOS) on the line. Applicable to both DS3 and E3.

A csOrionLossOfFrame trap signifies that a physical port on a blade experiencing loss of Frame(LOF) on the line. Applicable to both DS3 and OC3.

A csOrionAlarmIndication trap signifies that a physical port on a blade generates an alarm (AIS) that indicates a failure in upstream far end.

A csOrionLossOfClock trap signifies that a physical port on a blade experiencing loss of Clock(LOC) on the line. Applicable to both DS3 and OC3.

A csOrionBladeRestore trap signifies that a blade had been restored successfully or not. The VarBind that follow contains the list of VPN/VRs affected.

A csOrionDs3PortIdle trap signifies that a physical port on a blade received an IDLE signal from the far end indicating it is unequipped to handle any data transfer.

A csOrionAlarmClear trap signifies that a physical port on a blade, which had sent an alarm earlier, indicates that the previous alarm is cleared. Applicable to DS3.

A csOrionOc3Alarm trap signifies that an OC3 physical port on a blade, which had sent an alarm.

A csOrionOc3AlarmClear trap signifies that an OC3 physical port on a blade, which had sent an alarm earlier, indicates that the prvious alarm is cleared.

A csOrionPacketRingStatusChange trap signifies that the packet ring status of the chassis has changed. If both endpoints change from zero to r[1,26], that means the status has changed to protection ring. If both endpoints change from r[1,26] to zero, that means the status has changed to no protection ring. If one/both endpoints change from r[1,26] to different r[1,26], that means the topology has changed but not ring status.

This trap indicates that the inlet air temperature has changed states. If the value of csOrionSystemTempStatus is tempRisingAboveUpperCriticalThreshold(1), the given sensor has detected a transition from the normal temperature range to the hot range. If the value of csOrionSystemTempStatus is tempFallingBelowUpperCriticalThreshold (2), the given sensor has detected a transition from the 'hot' range back down to the normal range.

This trap indicates that a given I2C device is present. This trap will occur on 9500 and 3500 chassis only.

This trap indicates a power supply monitor event. The following events are reported: redundancyRegained (1) redundancyLost (2) auxVoltageRisingAboveLowerCriticalThreshold (3) auxVoltageFallingBelowLowerCriticalThreshold (4)

A csOrionFarEndReceiveFailure trap signifies that the physical port on the remote end is receiving an alarm. Applicable to DS3.

This trap reports on the status of the copy operation of a system file from master to standby control blade. Generated only if there is control blade redundancy (cbr).

This trap reports that max-prefix limit has been reached for the given neighbor

This trap reports that max-prefix limit has been reached for the given neighbor

A system Ip address.

A system network mask.

A system default gateway address.

The fw version used by Orion

The version for a Orion as a system.

This object identifies the current temperature status within the Orion system. If this object has the value normal(1), the temperature is within the normal range. If the status is hot(2), the temperature is above the normal range and measures should be taken to bring the temperature down. Enumeration: 'hot': 2, 'normal': 1.

The software reset. It is an action object such that when set to 'reset' will reset all the blades. Setting it to 'none' has no effect, and when it is retrieved the value will always be 'none' . Enumeration: 'reset': 2, 'none': 1.

To set the system date & time with the standard format specified by RFC 2579. Below is the date-time specification. (Display Format: YYYY-MM-DD,HH:MM:SS.ss,+/-:HH:MM) field contents range ----- -------- ----- 1 year* 1999..2098 2 month 1..12 3 day 1..31 4 hour 0..23 5 minutes 0..59 6 seconds 0..60 (use 60 for leap-second) 7 deci-seconds 0..9 8 direction from UTC '+' / '-' 9 hours from UTC* 0..13 10 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 2000 at 1:30:15 PM EDT would be displayed as: 2000-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present.

The system version number applies to the IPSX system as a whole. This number has the format: a.b.c.d where 'a.b' is major release number, 'c' is the patch nubmer, and 'd' is the internal release number.

The software shutdown. It is an action object such that when set to 'shutdown' will stop the file-system of all the blades. that when set to 'shutdown' will stop the file-system of all the blades. Setting it to 'none' has no effect, and when it is retrieved the value will always be 'none' . Enumeration: 'none': 1, 'shutdown': 2.

When set to 'failover', the master control blade switches over to stand-by control blade. Setting it to 'none' has no effect, and when it is retrieved the value will always be 'none' . Enumeration: 'none': 1, 'failover': 2.

NOTE: This object has been replaced by csOrionSystemLoginServer. When this object is set to radius, radius server will be used to authenticate a user logging into a CLI session. When this object is set to localDatabase, the password file resided locally will be used to authenticate the CLI user. Enumeration: 'radius': 1, 'localDatabase': 2.

A list of Sources from which this Orion will boot.

An entry containing Boot information applicable to this Orion System. Note, currently there is only one entry in this table. More entries may be added in future releases.

A unique value, greater than zero, for each boot record.

The absolute path and file name for the boot image. If this string is prefaced with 'FLSH', tftp will be used to boot over the network. This applies to all 6 images.

The 2nd absolute path and file name for the boot image. This will be used only if the previous boot images fail.

The 3rd absolute path and file name for the boot image. This will be used only if the previous boot images fail.

The 4th absolute path and file name for the boot image. This will be used only if the previous boot images fail.

The 5th absolute path and file name for the boot image. This will be used only if the previous boot images fail.

The 6th absolute path and file name for the boot image. This will be used only if the previous boot images fail.

When booting over the network, the port used to load the image

A boot server Ip Address. Note, this only applies if this entry specifies booting over the network.

When booting over the network using a boot protocol that does not supply a source IP address, This object specifies the local IP address to use when booting via the network.

When booting over the network using a boot protocol that does not supply a source IP address, This object specifies the local IP address mask to use when booting via the network.

When booting over the network, this object is used to identify the gateway to use in communicating with the boot server.

The absolute path and file name for the configuration file. Note, the configuration file must be on the local flash.

This object specifies whether the IPSX system will save the boot image in local flash. Note this applies only if the csOrionSystemBootProtocol is tftp(2). Enumeration: 'disabled': 2, 'enabled': 1.

User Name to use if the download is via FTP

Password to use if the download is via FTP

All the blades in the system make a internal network. This attribute defines the network part (255.255.0.0) of this subnet. Default is 172.168.0.0

Maximum number of downloads that can occur concurrently. if configured to 0, then there is no limit to number of simultaneous download sessions. This is useful if the TFTP/FTP server cannot handle a large number of TFTP/FTP sessions

A login information for Orion, using console or telnet.

An entry contains information for one CLI login user.

The login user name.

User information

A sequence of alphabetical and numerical characters, MUST not be less than 8 characters.

A row status type for the table entry.

A operational status for this table entry.

A role for a login user.

An entry contains information for one role type. A role is a group of feature access permissions. Each login user is associated with a single role.

The name of a role.

Information about the role.

Access rights of a role are a list of feature-wise permissions. The permissions of a feature are represented by a 4-byte tuple {rights (1-byte),featureid(3-bytes)}. The features in this list are in the ascending order of their feature-id. rights: Access rights are classified into the following categories (given below along with the mapping to unix-style read,write and execute permissions): 0 : none (rwx-style = ---) 1 : all (rwx-style = rwx) 2 : view (rwx-style = r--) 3 : config (rwx-style = rw-) 4 : monitor (rwx-style = r-x) Feature-id's: A feature is a set of commands which are grouped into a read, write or execute command-type. all (1), access (2), clear (3), device (4), dialup (5), diff_serve (6), event_log (7), field (8), firewall (9), froip (10), nat (11), routing (12), service_selection (13), show (14), tunnel (15), vpnvr (16)

A row status type for the table entry.

A domain for a login user.

An entry contains information for one domain. A domain is a group of object instances which defines the scope a role for for a user. Each login user is associated with a single domain.

The name of an access domain.

Information about the access domain.

A list of VPN/VRs a user can access. A VPN/VR is represented as /. The VPN/VRs in the list are separated either by a space(s). The following are valid wildcards for a VR: /* : All VRs with the given VPN. */* : All VRs. If it used then it should be the only entry in the list.

List of interfaces which an user can access. The interfaces in the list are separated either by space(s). Each interface is represented as follows: [/[:channel-range>[:]]] where each range above has the follog syntax: = { * | | - } If the optional elements (,,etc) are not specified they default to '*', which denotes all values. is always less than . If '*' or range is specified for an element then all following elements MUST be wildcard enrtries The chassis as an interface can also be included in the list and is represented by the key-word 'chassis' Valid interface examples: * - same as */*/*/* 5-6/* chassis 5/3-5/* 5/3/2-4 Invalid interface Eg: 5/*/3

A row status type for the table entry.

Access permissions for a login user. A permission id represented as a :. A user can have multiple permissions.

An entry contains information for one login user permission.

A row status type for the table entry.

When this object is set to remote, a remote authentication server (csOrionSystemLoginServerListName) will be used to authenticate a user logging into a CLI session. When this object is set to localDatabase, the password file residing locally will be used to authenticate the CLI user. Enumeration: 'remote': 1, 'localDatabase': 2.

The name of the server list to use for remote authentication, if no list is specified then the server specified in the default server list is used. Cli authentication uses the server list and default servers configured on the system virtual router.

This object controls access to this device via Dial In modem. Enumeration: 'enable': 1, 'disable': 2.

This object sets the target baud rate of the modem connection.

This object specifies the type of flow control used by the modem. Enumeration: 'hardware': 1, 'software': 2.

This object sets the length of time, in seconds, the modem will wait for a connection.

This object is used when the save configuration is launched on an Orion box by setting the csOrionConfigSave object. The device handle the default value for this object. When this object is not set, the device look for the csOrionSystemBootConfig of the csOrionSystemBootTable. If that is not NULL, that name is used as the file name. Otherwise the default filename of config.dat is used.

This object triggers the configuration saving on the divice. The result of this action is stored in csOrionConfigSaveStatus. Enumeration: 'none': 2, 'save': 1.

This object triggers the configuration saving on the divice. The result of this action is stored in csOrionConfigSaveStatus. Enumeration: 'none': 1, 'saveSuccess': 3, 'saveInProgress': 2, 'saveFailed': 4.

This object controls whether output from loading configuration file should be printed out to the console. Loading configuration will be quicker if this object is disabled. Enumeration: 'enable': 1, 'disable': 2.

File System Request Table.

An entry of File System Request Table.

This object identifies a specific File System request entry. NMSs are expected to come up with a unique ID each request. This ID will also be used to index the File System result entry.

This object specifies the filesystem operation stated in the enumeration above. We will add entries as we support additional filesystem commands. Objects that hold the parameters must also be set for commands that requires some arguments. Enumeration: 'rename': 5, 'load': 6, 'none': 1, 'copy': 4, 'dir': 2, 'delete': 3.

This object is used to hold the source file for the file system operation. Must be set for 'delete', 'copy' and 'rename' requests. For 'load' request, the file to be loaded should be set using this object. If not set, the default file defined in csOrionSystemBootConfig will be loaded.

This object is used to hold the source file for the file system operation. Must be set for copy and rename requests.

This object is used to store the status of the File System request. operation. For 'dir' operation, csOrionFileSysResultTable should only be evaluated after this object yields opSuccess(3). Enumeration: 'opInProgress': 2, 'none': 1, 'opFailed': 4, 'opSuccess': 3.

The RowStatus object for this table. This is used to add/delete rows from this table.

File System Result Table. The object csOrionFileSysReqStatus should be evaluated before acquiring the results from this table.

An entry of File System Result Table. Each file returned from 'dir' request corresponds to an entry in csOrionFileSysResultEntry. Additional 'getnext' is expected to obtain the succeeding files. We will add objects in this table as we expose more file attributes.

This object identifies a specific File System result entry. This index corresponds to the ID provided by NMSs on File System request.

This object is used to hold the filename from the 'dir' request.

This object is used to hold the filesize from the 'dir' request.

Midplane laser ID for this chassis.

Chassis type. Enumeration: 'ipsx9000': 2, 'ipsx9500': 3, 'ipsx3500': 1, 'unknown': 4.

Status of the packet ring. noProtection means protection ring is inactive. onProtection means protection ring is active. Enumeration: 'noProtection': 1, 'onProtection': 2.

Slot number of the primary to protection endpoint. If csOrionChassisPacketRingStatus is noProtection, this object will have a value of 0.

Slot number of the protection to primary endpoint. If csOrionChassisPacketRingStatus is noProtection, this object will have a value of 0.

CRC count on the primary packet ring.

CRC count on the protection packet ring.

The Orion Ethernet Table.

An entry in the Ethernet Table.

This object identifies the slot in which the blade that supports this port is installed.

This object identifies a specific module on the blade installed in csEthSlotIndex.

This object identifies a specific port on the module installed in csEthModuleIndex.

This object identifies the encapsulation method used on this Ethernet port. Enumeration: 'snap': 3, 'eth': 1, 'ieee': 2.

This object is used to enable or disable the autonegotiation feature of this Ethernet port. This feature is used to automatically negotiate the Speed and Duplex mode for 10/100 Mbps Ethernet ports. Enumeration: 'disabled': 2, 'enabled': 1.

This object is used to specify the Duplex mode of this Ethernet port. This is used only if csEthAutoneg is disabled. Note: The default value is removed because it is not fixed in the system after reboot when autonegotiation enabled. It is hardware configuration dependent. Enumeration: 'full': 2, 'half': 1.

This object is used to specify the speed of this Ethernet port. This is used only if csEthAutoneg is disabled. Note: The default value is removed because it is not fixed in the system after reboot when autonegotiation enabled. It is hardware configuration dependent. Enumeration: 'mbps1000': 3, 'mbps100': 2, 'mbps10': 1.

This object is used to specify the interval, in seconds, between Link Test packet transmissions. If this object is set to 0, no Link Test packets are sent.

This object is used to enable/disable thie Ethernet port. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this Ethernet port.

This object is used to enable or disable PPPoE service on Ethernet Ports. Enumeration: 'enable': 1, 'disable': 2.

The Orion Ethernet Sub-Interface Table.

The Parameters for a VLAN Interface.

Channel ID of this VLAN connection. Currently, it will always be 0.

The Sub Interface Id of the Logical Interface.

The unipue number between 0 and 4095 that identifies a particular VLAN. The range of VLAN IDs supported per port is from 2 to 4094. The null VLAN Id (0) indicates that the tag header contains only user priority information. The VLAN Id 1, 4095 is reserved for implementation use.

The user priority for this VLAN

The name for this VLAN

This object is used to enable/disable this VLAN. Enumeration: 'enable': 1, 'disable': 2.

The operational status for this VLAN.

This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.

This object is used to enable or disable PPPoE service on VLAN. Enumeration: 'enable': 1, 'disable': 2.

The Orion Ethernet Table.

An entry in the Ethernet Statistic Table.

The counter associated with the number of packets deferred upon the first transmit attempt due to a busy line .

The counter associated with the number of Regular collisions during transmission.

The counter associated with the number of packets transmitted without any errors following a single collisions.

The counter associated with the number of packets transmitted without any errors following multiple collisions.

The counter associated with the number of packets that have experienced 16 consecutive collisions or more.

The counter associated with the number of transmission abortions due to a collision occurring after the transmission of packets that are 64 bytes in length.

The counter associated with the number of transmitted packets 64 bytes in length, including bad packets.

The counter associated with the number of packets 64 to 127 bytes in length, including bad packets.

The counter associated with the number of packets 128 to 255 bytes in length, including bad packets.

The counter associated with the number of packets 256 to 511 bytes in length, including bad packets.

The counter associated with the number of transmitted packets 512 to 1023 bytes in length, including bad packets.

The counter associated with the number of transmitted packets 1024 to 1518 bytes in length, including bad packets.

The counter associated with the number of transmitted packets with length larger than 1518 bytes, including bad packets.

The counter associated with the number of correct transmitted flow-control packets.

The counter associated with the number of packets transmitted with an error due to transmit FIFO underflow or txerr signal assertion.

The counter associated with the number of bytes transmitted in packets with errors.

The counter associated with the number of frames received without SFD detection but with carrier assertion .

The counter associated with the number of received packets not fully accepted due to receive FIFO overflow .

The counter associated with the number of received packets without error, less than 64 bytes length .

The counter associated with the number of packets received with an integral number of bytes and a CRC error with lengths between 64 bytes and maximum packet size .

The counter associated with the number of packets received with an nonintegral number of bytes and a CRC error with lengths between 64 bytes and maximum packet size.

The counter associated with the number ofpackets larger than maximum packet size received without any error .

The counter associated with the number of packets larger than maximum packet size received with a CRC error

The counter associated with the number of received packets 64 bytes in length, including bad packets.

The counter associated with the number of received packets 65 to 127 bytes in length, including bad packets.

The counter associated with the number of packets 128 to 255 bytes in length, including bad packetsO.

The counter associated with the number of packets 256 to 511 bytes in length, including bad packets

The counter associated with the number of packets 512 to 1023 bytes in length, including bad packets.

The counter associated with the number of packets 1024 to 1518 bytes in length, including bad packets.

The counter associated with the number of packets with length larger than 1518 bytes and the maximum packet size, including bad packets.

The counter associated with the number of correct received flow-control packets.

The counter associated with the number of false carrier events detected

The counter associated with the number of bytes received in packets with errors.

The counter associated with the number of received packets during which PHY symbol errors were detected.

The counter associated with the number of transmitted packets 1024 bytes or more in length, including bad packets. It's only for Giga bit Ethernet card.

The counter associated with the number of packets 1024 bytes or more in length, including bad packets. It's only for Giga bit Ethernet card.

The DS3 configuration table.

An entry in the DS3 Configuration table.

This object identifies the blade to which this Ds3 Port is attached. Together with csDs3ConfigModuleIndex, csDs3ConfigPortIndex, it uniquely identifies a physical port.

This object identifies the type of of the Ds3 Module on the blade identified by csChDs3SlotIndex.

This object identifies the location of the Ds3 Port on the module identified by csChDs3ModuleIndex. Together with csDs3ConfigSlotIndex, csDs3ConfigModuleIndex, it uniquely identifies a physical port.

The length of the DS3 cable. NOTE: This is applicable only for DS3.

The framing format used on this Ds3 Interface. The default value is cbit if the interface is DS3. If the interface is E3, e3Framed will be used, and cannot be configured to any other types. Enumeration: 'cbit': 1, 'auto': 3, 'e3Framed': 4, 'm23': 2.

This object controls the transmission of the MDL Path message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object controls the transmission of the MDL Idle Signal message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object controls the transmission of the MDL Test Signal message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object specifies the Equipment Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Location Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Frame Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Unit Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Facility Identification Code sent in the MDL Path message. NOTE: This is applicable only for DS3.

This object specifies the Port number string sent in the MDL Idle Signal message. NOTE: This is applicable only for DS3.

This object specifies the Generator number string sent in the MDL Test Signal message. NOTE: This is applicable only for DS3.

This object identifies which of the 28 T1's within this DS3 are to be broken out into the Test T1 port. If none of the T1's are to be broken out, this object should be set to 0. NOTE: This is applicable only for DS3.

This object is used to enable/disable this Ds3 port. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this Ds3 port.

This object specifies the source of the Transmit Clock used on this (unchannelized) DS3. If this object is set to internal(1), a local clock source is used. If this object is set to line(2), the recovered received clock is used as the transmit clock. NOTE: This is applicable only for DS3. Enumeration: 'line': 2, 'internal': 1.

This object indicates whether the interface is DS3 or E3. Enumeration: 'ds3': 1, 'e3': 2.

This variable indicates what type of code is being sent across the DS3 interface by the device. Setting this variable causes the interface to begin sending the code requested. The values mean: sendNoCode sending looped or normal data sendLineCode sending a request for a line loopback sendPayloadCode sending a request for a payload loopback (i.e., all DS1/E1s in a DS3/E3 frame) sendResetCode sending a loopback deactivation request NOTE: This is applicable only for DS3. Enumeration: 'ds3SendLineCode': 2, 'ds3SendPayloadCode': 3, 'ds3SendResetCode': 4, 'ds3SendNoCode': 1.

This object represents the desired loopback configuration of the DS3 interface. The values mean: noLoop Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. It is the default value. payloadLoop The received signal at this interface is looped through the device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function. lineLoop The received signal at this interface does not go through the device (minimum penetration) but is looped back out. otherLoop Loopbacks that are not defined here. Currently not used in the IPSX system. inwardLoop The sent signal at this interface is looped back through the device. dualLoop Both lineLoop and inwardLoop will be active simultaneously. Enumeration: 'lineLoop': 3, 'noLoop': 1, 'payloadLoop': 2, 'otherLoop': 4, 'inwardLoop': 5, 'dualLoop': 6.

This variable represents the current state of the loopback on the DS3 interface. It contains information about loopbacks established by a manager and remotely from the far end. The csDs3ConfigLoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously. The various bit positions are: 1 ds3NoLoopback 2 ds3NearEndPayloadLoopback 4 ds3NearEndLineLoopback 8 ds3NearEndOtherLoopback 16 ds3NearEndInwardLoopback 32 ds3FarEndPayloadLoopback 64 ds3FarEndLineLoopback

This variable indicates the Line Status of the interface. It contains loopback state information and failure state information. The csDs3ConfigLineStatus is a bit map represented as a sum, therefore, it can represent multiple failures and a loopback (see csDs3ConfigLoopbackStatus object for the type of loopback) simultaneously. The ds3NoAlarm must be set if and only if no other flag is set. If the ds3LoopbackState bit is set, the loopback in effect can be determined from the csDs3ConfigLoopbackStatus object. The various bit positions are: 0 ds3NoAlarm No alarm present 1 ds3RcvRAIFailure Receiving Yellow/Remote Alarm Indication 2 ds3XmitRAIAlarm Transmitting Yellow/Remote Alarm Indication 3 ds3RcvAIS Receiving AIS failure state 4 ds3XmitAIS Transmitting AIS 5 ds3LOF Receiving LOF failure state 6 ds3LOS Receiving LOS failure state 7 ds3LoopbackState Looping the received signal 8 ds3RcvTestCode Receiving a Test Pattern 9 ds3OtherFailure any line status not defined here 10 ds3UnavailSigState Near End in Unavailable Signal State 11 ds3NetEquipOOS Carrier Equipment Out of Service

The number of seconds that have elapsed since the beginning of the near end current error-measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.

The number of previous near end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute near end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.

The number of intervals in the range from 0 to csDs3ConfigValidInterval for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).

This variable describes the variety of Zero Code Suppression used on this interface, which in turn affects a number of its characteristics. ds3B3ZS and e3HDB3 refer to the use of specified patterns of normal bits and bipolar violations which are used to replace sequences of zero bits of a specified length. NOTE: This is applicable only for E3 for now. Enumeration: 'ds3Other': 1, 'e3NRZ': 4, 'e3HDB3': 3, 'ds3B3ZS': 2.

Bit 12 of the E3 G.751 frame. NOTE: This is applicable only for E3.

The DS3 DS1 configuration table. This is used to configure each of the DS1 connections within a complete DS3.

An entry in the DS3 DS1 Configuration table.

This identifies a single DS1 within a complete DS3.

This object specifies the framing used on the DS1 assigned to this channel. Enumeration: 'e1UnFramed': 6, 'e1CrcMultiframe': 3, 'esf': 1, 'e1CrcMultiframeFebe': 4, 'sf': 2, 'e1FrameAlignSignal': 5.

This object specifies whether Yellow Alarm detection is active on the DS1 assigned to this channel. Enumeration: 'enable': 1, 'disable': 2.

This object specifies whether Yellow Alarm generation is active on the DS1 assigned to this channel. NOTE: This is applicable only for T1. Enumeration: 'enable': 1, 'disable': 2.

This object specifies the variety of Zero Code Suppression used on the on the DS1 assigned to this channel. NOTE: This is applicable only for T1. Enumeration: 'ami': 1, 'b8zs': 2.

This object specifies whether the 'invert data' feature is enabled on the DS1 assigned to this channel. This feature must be enabled if the Line Code parameter (csDs3Ds1LineCode) is set to ami. NOTE: This is applicable only for T1. Enumeration: 'on': 1, 'off': 2.

This object specifies the source of the Transmit Clock used on the DS1 assigned to this channel. If this object is set to internal(1), a local clock source is used. If this object is set to line(2), the recovered received clock is used as the transmit clock. NOTE: This is applicable only for T1. Enumeration: 'line': 2, 'internal': 1.

This is used to enable/disable 1 second transmission of performance reports via ANSI 403 FDL. If this is disabled, the AT&T 54016 version of FDL is used. Note, FDL is available only for ESF framing. And so it is only applicable for T1. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this DS1.

This variable indicates what type of code is being sent across the DS1 interface by the device. Setting this variable causes the interface to send the code requested. NOTE: This is applicable only for T1.. The values mean: ds1SendNoCode sending looped or normal data ds1SendLineCode sending a request for a line loopback ds1SendPayloadCode sending a request for a payload loopback ds1SendResetCode sending a loopback termination request Enumeration: 'ds1SendLineCode': 2, 'ds1SendResetCode': 4, 'ds1SendNoCode': 1, 'ds1SendPayloadCode': 3.

This object represents the desired loopback configuration of the DS1 interface. This variable will be interpreted only when csDs3Ds1LoopbackDestination is set to a valid value. NOTE: This is applicable only for T1. noLoop Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. payloadLoop The received signal at this interface is looped through the device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function. lineLoop The received signal at this interface does not go through the device (minimum penetration) but is looped back out. otherLoop Loopbacks that are not defined here. Currently not used in the IPSX system inwardLoop The transmitted signal at this interface is looped back and received by the same interface. What is transmitted onto the line is product dependent. Cannot be applied to far end. dualLoop Both dsx1LineLoop and dsx1InwardLoop will be active simultaneously. Cannot be applied to far end. Enumeration: 'lineLoop': 3, 'noLoop': 1, 'payloadLoop': 2, 'otherLoop': 4, 'inwardLoop': 5, 'dualLoop': 6.

This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks established by a manager and remotely from the far end. NOTE: This is applicable only for T1. The csDs3Ds1LoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously. The various bit positions are: 1 ds1NoLoopback 2 ds1NearEndPayloadLoopback 4 ds1NearEndLineLoopback 8 ds1NearEndOtherLoopback 16 ds1NearEndInwardLoopback 32 ds1FarEndPayloadLoopback 64 ds1FarEndLineLoopback

This variable represents DS1/E1 transmit line configuration. This is normally used for dignostic or service purpose, it is not supposed for user to configure. The various bit positions are: BIT(0) not used BIT(1) ds1NoAlarm BIT(2) ds1RcvFarEndLOF BIT(3) ds1XmtFarEndLOF BIT(4) ds1RcvAIS BIT(5) ds1XmtAIS BIT(6) ds1LossOfFrame BIT(7) ds1LossOfSignal BIT(8) ds1LoopbackState BIT(9) ds1T16AIS BIT(10) ds1RcvFarEndLOMF BIT(11) ds1XmtFarEndLOMF BIT(12) ds1RcvTestCode BIT(13) ds1OtherFailure BIT(14) ds1UnavailSigState BIT(15) ds1NetEquipOOS BIT(16) ds1RcvPayloadAIS BIT(17) ds1Ds2PerfThreshold BIT(18) ds1XmtTrnkCond

This variable represents DS1/E1 transmit and receive line status. The various bit positions are: BIT(0) not used BIT(1) ds1NoAlarm BIT(2) ds1RcvFarEndLOF BIT(3) ds1XmtFarEndLOF BIT(4) ds1RcvAIS BIT(5) ds1XmtAIS BIT(6) ds1LossOfFrame BIT(7) ds1LossOfSignal BIT(8) ds1LoopbackState BIT(9) ds1T16AIS BIT(10) ds1RcvFarEndLOMF BIT(11) ds1XmtFarEndLOMF BIT(12) ds1RcvTestCode BIT(13) ds1OtherFailure BIT(14) ds1UnavailSigState BIT(15) ds1NetEquipOOS BIT(16) ds1RcvPayloadAIS BIT(17) ds1Ds2PerfThreshold BIT(18) ds1XmtTrnkCond

This variable is used to configure the 2-bits international bits for the E1 interface. NOTE: This is applicable only for E1.

This 4-bit object is added for the E1 sub-multiframe aligned national bit codeword configuration. NOTE: This is applicable only for E1.

The Channelized DS3 Channel configuration table.

An entry in the DS3 Fractional table.

This object identifies the blade to which this Ds3 Port is attached. Together with csChDs3ModuleIndex, csChDs3PortIndex, it uniquely identifies a physical port.

This object identifies the module of the Ds3 Blade

This object identifies the location of the Ds3 Port on the blade identified by csChDs3SlotIndex. Together with csChDs3SlotIndex, it uniquely identifies a physical port.

The channel number for this entry.

This object identifies the DS1 number that is assigned to this channel. This number for E1 is 1 to 16. NOTE: This object can only be set during row creation. Once the row is created, this object cannot be modified.

This object specifies the individual DS0 time slots within the DS1(T1 or E1, identified by csChDs3T1Number) that are assigned to this channel. The format can be a range of slots (1-8), a list of slots (1, 3, 7), or a mix of both. NOTE: This object can only be set during row creation. Once the row is created, this object cannot be modified.

This object specifies the speed (and, hence the signaling mode) of the DS1 assigned to this channel. Enumeration: 'kbps64': 1, 'kbps56': 2.

This object specifies the encapsulation used on this DS3 channel. If the encapsulation type is frameRelay(2), use the csFrameRelayTable to configure the Frame Relay specific parameters. Enumeration: 'ciscoHdlc': 3, 'none': 0, 'ppp': 1, 'frameRelay': 2.

A row status type for this Channel.

A operational status for this Channel.

The DS3/E3 current table contains various statistics being collected for the current 15 minute interval.

An entry in the DS3/E3 Current table.

The counter associated with the number of P-bit Errored Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of P-bit Severely Errored Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of Severely Errored Framing Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of Unavailable Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of Line Coding Violations. NOTE: This is applicable for both E3 and DS3.

The counter associated with the number of P-bit Coding Violations. NOTE: This is applicable only for DS3.

The number of Line Errored Seconds. NOTE: This is applicable for both E3 and DS3.

The number of C-bit Coding Violations. NOTE: This is applicable only for DS3.

The number of C-bit Errored Seconds. NOTE: This is applicable only for DS3.

The number of C-bit Severely Errored Seconds. NOTE: This is applicable only for DS3.

The number of Line Severely Errored Seconds. NOTE: This is applicable for both E3 and DS3.

The DS3/E3 Interval Table contains various statistics collected by each DS3/E3 Interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents one such interval (identified by csDs3StatIntervalNumber) and for one specific DS3 port (identifed by csDs3ConfigPortIndex).

An entry in the DS3/E3 Interval table.

A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.

The counter associated with the number of P-bit Errored Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of P-bit Severely Errored Seconds. NOTE: This is applicable only for DS3.

The counter associated with the number of Severely Errored Framing Seconds. NOTE: This is applicable for both DS3 and E3.

The counter associated with the number of Unavailable Seconds. This object may decrease if the occurance of unavailable seconds occurs across an inteval boundary. NOTE: This is applicable only for DS3.

The counter associated with the number of Line Coding Violations. NOTE: This is applicable for both E3 and DS3.

The counter associated with the number of P-bit Coding Violations. NOTE: This is applicable only for DS3.

The number of Line Errored Seconds (BPVs or illegal zero sequences). NOTE: This is applicable for both E3 and DS3.

The number of C-bit Coding Violations. NOTE: This is applicable only for DS3.

The number of C-bit Errored Seconds. NOTE: This is applicable only for DS3.

The number of C-bit Severely Errored Seconds. NOTE: This is applicable only for DS3.

The number of Line Severely Errored Seconds. NOTE: This is applicable for both E3 and DS3.

This variable indicates if the data for this interval is valid.

The DS3/E3 Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding the current interval.

An entry in the DS3/E3 Total table.

The counter associated with the number of P-bit Errored Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The counter associated with the number of P-bit Severely Errored Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The counter associated with the number of Severely Errored Framing Seconds, encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The counter associated with the number of Unavailable Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The counter associated with the number of Line Coding Violations encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable for both E3 and DS3.

The counter associated with the number of P-bit Coding Violations, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The number of Line Errored Seconds (BPVs or illegal zero sequences) encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable for both E3 and DS3.

The number of C-bit Coding Violations encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The number of C-bit Errored Seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The number of C-bit Severely Errored Seconds encountered by a DS3 interface in the previous 24-hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable only for DS3.

The number of Line Severely Errored Seconds encountered by a DS3 interface in the previous 24-hour interval. Invalid 15 minute intervals count as 0. NOTE: This is applicable for both E3 and DS3.

The DS1 current table contains various statistics being collected for the current 15 minute interval.

An entry in the DS1 Current table.

The number of Errored Seconds.

The number of Severely Errored Seconds.

The number of Severely Errored Framing Seconds.

The number of Unavailable Seconds.

The number of Controlled Slip Seconds.

The number of Path Coding Violations.

The number of Line Errored Seconds.

The number of Bursty Errored Seconds.

The number of Degraded Minutes.

The number of Line Code Violations (LCVs).

The DS1 Interval Table contains various statistics collected by each DS1 Interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents one such interval (identified by csDs3Ds1IntervalNumber) for one specific instance (identified by csDs3Ds1Id).

An entry in the DS1 Interval table.

A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.

The number of Errored Seconds.

The number of Severely Errored Seconds.

The number of Severely Errored Framing Seconds.

The number of Unavailable Seconds. This object may decrease if the occurance of unavailable seconds occurs across an inteval boundary.

The number of Controlled Slip Seconds.

The number of Path Coding Violations.

The number of Line Errored Seconds.

The number of Bursty Errored Seconds.

The number of Degraded Minutes.

The number of Line Code Violations.

This variable indicates if the data for this interval is valid.

The DS1 Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding the current interval.

An entry in the DS1 Total table.

The sum of Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Severely Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Severely Errored Framing Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Unavailable Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Controlled Slip Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Path Coding Violations encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Line Errored Seconds encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Degraded Minutes (DMs) encountered by a DS1 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.

The number of Line Code Violations (LCVs) encountered by a DS1 interface in the current 15 minute interval. Invalid 15 minute intervals count as 0.

The Unchannelized DS3 configuration table.

An entry in the Unchannelized DS3 Configuration table.

This object identifies the blade to which this Unchannelized Ds3 Port is attached. Together with csUnchanDs3ConfigPortIndex, it uniquely identifies a physical port.

This object identifies the module on the Unchannelized Ds3 Blade.

This object identifies the location of the Unchannelized Ds3 Port on the blade identified by csUnchanDs3SlotIndex. Together with csUnchanDs3ConfigSlotIndex, it uniquely identifies a physical port.

The length of the DS3 cable.

The framing format used on this Ds3 Interface. The default value is cbit if the interface is DS3. If the interface is E3, e3Framed will be used, and cannot be configured to any other types. Enumeration: 'cbit': 1, 'auto': 3, 'e3Framed': 4, 'm23': 2.

This object controls the transmission of the MDL Path message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object controls the transmission of the MDL Idle Signal message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object controls the transmission of the MDL Test Signal message. NOTE: This is applicable only for DS3. Enumeration: 'enable': 1, 'disable': 2.

This object specifies the Equipment Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Location Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Frame Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Unit Identification Code. NOTE: This is applicable only for DS3.

This object specifies the Facility Identification Code sent in the MDL Path message. NOTE: This is applicable only for DS3.

This object specifies the Port number string sent in the MDL Idle Signal message. NOTE: This is applicable only for DS3.

This object specifies the Generator number string sent in the MDL Test Signal message. NOTE: This is applicable only for DS3.

This object is used to enable/disable this Ds3/E3 port. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this Ds3/E3 port.

This object specifies the source of the Transmit Clock used on this (unchannelized) DS3. If this object is set to internal(1), a local clock source is used. If this object is set to line(2), the recovered received clock is used as the transmit clock. NOTE: This is applicable only for DS3. Enumeration: 'line': 2, 'internal': 1.

This object specifies the encapsulation used on this DS3/E3 port. If the encapsulation type is frameRelay(2), use the csFrameRelayTable to configure the Frame Relay specific parameters. Enumeration: 'ciscoHdlc': 3, 'none': 0, 'ppp': 1, 'frameRelay': 2.

This variable indicates what type of code is being sent across the DS3 interface by the device. Setting this variable causes the interface to begin sending the code requested. NOTE: This is applicable only for DS3. The values mean: sendNoCode sending looped or normal data sendLineCode sending a request for a line loopback sendResetCode sending a loopback deactivation request Enumeration: 'ds3SendLineCode': 2, 'ds3SendResetCode': 3, 'ds3SendNoCode': 1.

This object represents the desired loopback configuration of the DS3 interface. The values mean: noLoop Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. lineLoop The received signal at this interface does not go through the device (minimum penetration) but is looped back out. otherLoop Loopbacks that are not defined here. Currently not used in the IPSX system. inwardLoop The sent signal at this interface is looped back through the device. dualLoop Both lineLoop and inwardLoop will be active simultaneously. Enumeration: 'lineLoop': 2, 'noLoop': 1, 'inwardLoop': 4, 'dualLoop': 5, 'otherLoop': 3.

This variable represents the current state of the loopback on the DS3 interface. It contains information about loopbacks established by a manager and remotely from the far end. The csUnchanDs3ConfigLoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously. The various bit positions are: 1 ds3NoLoopback 2 ds3NearEndPayloadLoopback 4 ds3NearEndLineLoopback 8 ds3NearEndOtherLoopback 16 ds3NearEndInwardLoopback 32 ds3FarEndPayloadLoopback 64 ds3FarEndLineLoopback

This variable indicates the Line Status of the interface. It contains loopback state information and failure state information. The csUnchanDs3ConfigLineStatus is a bit map represented as a sum, therefore, it can represent multiple failures and a loopback (see csUnchanDs3ConfigLoopbackStatus object for the type of loopback) simultaneously. The ds3NoAlarm must be set if and only if no other flag is set. If the ds3LoopbackState bit is set, the loopback in effect can be determined from the csUnchanDs3ConfigLoopbackStatus object. The various bit positions are: 0 ds3NoAlarm No alarm present 1 ds3RcvRAIFailure Receiving Yellow/Remote Alarm Indication 2 ds3XmitRAIAlarm Transmitting Yellow/Remote Alarm Indication 3 ds3RcvAIS Receiving AIS failure state 4 ds3XmitAIS Transmitting AIS 5 ds3LOF Receiving LOF failure state 6 ds3LOS Receiving LOS failure state 7 ds3LoopbackState Looping the received signal 8 ds3RcvTestCode Receiving a Test Pattern 9 ds3OtherFailure any line status not defined here 10 ds3UnavailSigState Near End in Unavailable Signal State 11 ds3NetEquipOOS Carrier Equipment Out of Service

The number of seconds that have elapsed since the beginning of the near end current error-measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.

The number of previous near end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute near end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.

The number of intervals in the range from 0 to csDs3ConfigValidInterval for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).

This object indicates whether the interface is DS3 or E3. Enumeration: 'ds3': 1, 'e3': 2.

The OC3 configuration table.

An entry in the DS3 Configuration table.

This object identifies the blade to which this OC3 Port is attached. Together with csOc3ModuleIndex, csOc3PortIndex, it uniquely identifies a physical port.

This object identifies the module on the OC3 blade

This object identifies the location of the OC3 Port on the blade identified by csOc3SlotIndex, csOc3ModuleIndex. Together with csOc3SlotIndex, it uniquely identifies a physical port.

This object identifies the source of the clock signal for this OC3 port. Enumeration: 'line': 2, 'internal': 1.

This object identifies the type of CRC used on this OC3 port. This is only used by Packet Over Sonet. Enumeration: 'crc32': 2, 'crc16': 1.

This object identifies the section trace byte (j0) used on this OC3 port. If this object is set to hex01(1), the value sent within the j0 (section trace byte) element of the frame header is 0x01. This value should be set for interoperability with some SDH devices in Japan. If this object is set to hexCC(2), the value of the j0 element is 0xcc. This is the default value and should be used in the majority of cases. Enumeration: 'hex01': 1, 'hexCC': 2.

This object identifies the payload pointer byte (s1s0) used on this OC3 port. If this object is set to oc3c(1), the value sent within the s1s0 (payload pointer byte) element of the frame header is 0. If this object is set to au4(2), the value of the s1s0 element is 2. Enumeration: 'oc3c': 1, 'au4': 2.

This object identifies the path signal identifier used on this OC3 port. If this object is set to pppOrHdlc(1), the value sent within the c2 (path signal identifier) element of the frame header is 0xCF. If this object is set to atm(2), the value of the c2 element is 0x13. Enumeration: 'atm': 2, 'pos': 1.

This object is the path trace sent in the J1 byte of path overhead. It is padded by the OC3 driver with and to make up the 64-byte length.

The expected path trace of the far end interface.

This object controls the scrambling feature on this OC3 port. If this object is enabled, the SPE payload will be scrambled. If this object is diabled, the SPE payload will not be scrambled. SPE payload refers to that of either ATM or POS depending on the value of csOc3PathC2. Enumeration: 'enable': 1, 'disable': 2.

Enumeration: 'enable': 1, 'disable': 2.

Enumeration: 'enable': 1, 'disable': 2.

Enumeration: 'enable': 1, 'disable': 2.

Force protection switch. When set to 'forceToSwitch' it switches the active port between the two internal ports indicated by csOc3ApsActivePort object. NOTE: This is an action object. Read operation returns 'none'. Enumeration: 'none': 1, 'forceToSwitch': 2.

This object indicates which of the internal port is currently active. The non-active one is used for protection. Enumeration: 'portOne': 1, 'portTwo': 2.

Enumeration: 'enable': 1, 'disable': 2.

The current loopback state of the SONET/SDH interface. The values mean: noLoop Not in the loopback state. A device that is not capable of performing a loopback on this interface shall always return this value. facilityLoop The received signal at this interface is looped back out through the corresponding transmitter in the return direction. terminalLoop The signal that is about to be transmitted is connected to the associated incoming receiver. Enumeration: 'noLoop': 1, 'facilityLoop': 2, 'terminalLoop': 3.

This object is used to enable/disable this Ds3 port. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this Ds3 port.

The number of seconds that have elapsed since the beginning of the current measurement period.

This object indicates the number of previous 15-minute intervals for which data was collected.

This object indicates the number of previous 15-minute intervals for which data was not able to be collected.

This object specifies the encapsulation used on this port. If the encapsulation type is frameRelay(2), use the csFrameRelayTable to configure the Frame Relay specific parameters. Enumeration: 'ciscoHdlc': 3, 'none': 0, 'ppp': 1, 'frameRelay': 2.

This object is used to select the type of empty cell to be transmitted. It is deprecated due to not being supported in POS. Enumeration: 'idle': 2, 'unassigned': 1.

This object specifies the maximum packet size required for this port. This object applies to POS only.

This object indicates the current operational status of this channel. It is deprecated in favor of using csOc3AdminStatus instead.

This object describes the line type for this interface. The line types are Short and Long Range Single Mode fiber or Multi-Mode fiber interfaces, and coax and UTP for electrical interfaces. The value sonetOther should be used when the Line Type is not one of the listed values. Enumeration: 'ocNCoax': 5, 'ocNUTP': 6, 'ocNLongSingleMode': 3, 'ocNOther': 1, 'ocNShortSingleMode': 2, 'ocNMultiMode': 4.

The actual received path trace of the far end interface.

The speed of OCn interface. Enumeration: 'mbps155': 1, 'mbps622': 2.

The SONET/SDH Section Current table.

An entry in the SONET/SDH Section Current table.

This variable indicates the status of the interface. The sonetSectionCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The csOc3SectionNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 csOc3SectionNoDefect 2 csOc3SectionLOS 4 csOc3SectionLOF

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in the current 15-minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section in the current 15-minute interval.

The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Section in the current 15 minute interval.

The SONET/SDH Section Interval table.

An entry in the SONET/SDH Section Interval table.

A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.

This variable indicates if the data for this interval is valid.

The SONET/SDH Section Day table.

An entry in the SONET/SDH Section Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section for the day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section for the day.

The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section for the day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Section for the day.

The SONET/SDH Section Previous Day table.

An entry in the SONET/SDH Section Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section for the previous day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section for the previous day.

The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section for the previous day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Section for the previous day.

The SONET/SDH Line Current table.

An entry in the SONET/SDH Line Current table.

This variable indicates the status of the interface. The sonetLineCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetLineNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 csOc3LineNoDefect 2 csOc3LineAIS 4 csOc3LineRDI

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line in the current 15 minute interval.

The counter associated with the number of failure counts encountered by a SONET/SDH Line in the current 15 minute interval.

The SONET/SDH Line Interval table.

An entry in the SONET/SDH Line Interval table.

A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.

This variable indicates if the data for this interval is valid.

The counter associated with the number of failure counts encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.

The SONET/SDH Line Day table.

An entry in the SONET/SDH Line Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line for the day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line for the day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Line for the day.

The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line for the day.

The counter associated with the number of failure counts encountered by a SONET/SDH Line for the day.

The SONET/SDH Line Day table.

An entry in the SONET/SDH Line Previous Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line for the previous day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line for the previous day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Line for the previous day.

The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line for the previous day.

The counter associated with the number of failure counts encountered by a SONET/SDH Line for the previous day.

The SONET/SDH Path Current table.

An entry in the SONET/SDH Path Current table.

A value that indicates the type of the SONET/SDH Path. For SONET, the assigned types are the STS-Nc SPEs, where N = 1, 3, 12, 24, and 48. STS-1 is equal to 51.84 Mbps. For SDH, the assigned types are the STM-Nc VCs, where N = 1, 4, and 16. Enumeration: 'sts3cSTM1': 2, 'sts1': 1, 'sts12cSTM4': 3, 'sts48cSTM16': 5, 'sts24c': 4.

This variable indicates the status of the interface. The sonetPathCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetPathNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetPathNoDefect 2 sonetPathSTSLOP 4 sonetPathSTSAIS 8 sonetPathSTSRDI 16 sonetPathUnequipped 32 sonetPathSignalLabelMismatch

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in the current 15 minute interval.

The counter associated with the number of Unavailable Seconds encountered by a Path in the current 15 minute interval.

The counter associated with the number of failure counts encountered by a Path in the current 15 minute interval.

The SONET/SDH Path Interval table.

An entry in the SONET/SDH Path Interval table.

A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.

The counter associated with the number of Unavailable Seconds encountered by a Path in a particular 15-minute interval in the past 24 hours.

This variable indicates if the data for this interval is valid.

The counter associated with the number of failure counts encountered by a Path in a particular 15-minute interval in the past 24 hours.

The SONET/SDH Path Day table.

An entry in the SONET/SDH Path Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path for the day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path for the day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Path for the day.

The counter associated with the number of Unavailable Seconds encountered by a Path for the day.

The counter associated with the number of failure counts encountered by a Path for the day.

The SONET/SDH Path Previous Day table.

An entry in the SONET/SDH Path Day table.

The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path for the previous day.

The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path for the previous day.

The counter associated with the number of Coding Violations encountered by a SONET/SDH Path for the previous day.

The counter associated with the number of Unavailable Seconds encountered by a Path for the previous day.

The counter associated with the number of failure counts encountered by a Path for the previous day.

The OC3/POS statistics counter table.

An entry in the OC3/POS statistics counter table.

The counter associated with the number of bytes written to receive FIFO.

The counter indicates the number of frames successfully received in a 15 minute interval.

The counter indicates the number of aborted frames received.

The counter indicates the number of received frames with FCS error.

The counter indicates the number of received frames violating the minimal packet length.

The counter indicates the number of received frames violating the maximum packet length.

The counter indicates the number of bytes trasmitted.

The counter indicates the number of frames trasmitted.

The counter indicates the number of transmit frames aborted by the user.

The counter indicates the number of transmit frames aborted due to FIFO underrun.

End of this group. value undefined

The OC3 ATM statistics counter table.

An entry in the OC3 statistics counter table.

The counter indicates the number of transmitted cells at OC3-ATM interface

The counter indicates the number of received cells at OC3-ATM interface

The counter indicates the number of idle cells at OC3-ATM interface

The counter indicates the number of corrected HEC cells at OC3-ATM interface

The counter indicates the number of uncorrected HEC cells at OC3-ATM interface

End of this group. value undefined

The OC3 ATM Interval statistics counter table.

An entry in the OC3 ATM Interval statistics counter table.

A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.

The counter indicates the number of transmitted cells at OC3-ATM interface in a given interval number

The counter indicates the number of received cells at OC3-ATM interface in a given interval number

The counter indicates the number of idle cells at OC3-ATM interface in a given interval number

The counter indicates the number of corrected HEC cells at OC3-ATM interface in a given interval number

The counter indicates the number of uncorrected HEC cells at OC3-ATM interface in a given interval number

This variable indicates if the data for this interval is valid.

End of this group. value undefined

The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.

The Parameters for a particular Data Link Connection Management Interface.

This table entry configures Frame Relay Dlcmi-specific parameters for a single interface. The interface is identified by the slot its blade resides in, the physical port on that blade that contains the interface, and (if applicable) the specific DS3 channel on that port. This object is used to identify the Slot.

This table entry configures Frame Relay Dlcmi-specific parameters for a single interface. The interface is identified by the slot its blade resides in, the moduel, the port on that blade that contains the interface, and (if applicable) the specific DS3 channel on that port. This object is used to identify the Port.

This table entry configures Frame Relay Dlcmi-specific parameters for a single interface. The interface is identified by the slot its blade resides in, the physical port on that blade that contains the interface, and (if applicable) the specific DS3 channel on that port. This object is used to identify the Port.

This table entry configures Frame Relay Dlcmi-specific parameters for a single interface. The interface is identified by the slot its blade resides in, the physical port on that blade that contains the interface, and (if applicable) the specific DS3 channel on that port. This object is used to identify the Channel. If there is no DS3 channel (or unchannelized), this object should have the value 0.

This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface. Enumeration: 'itut933A': 5, 'ansiT1617D1994': 6, 'lmiRev1': 2, 'ansiT1617B': 4, 'ansiT1617D': 3, 'cisco': 7, 'noLmiConfigured': 1.

This variable states which address format is in use on the Frame Relay interface. Enumeration: 'q921': 1, 'q922': 4, 'q922March90': 2, 'q922November90': 3.

This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion. Enumeration: 'threeOctets': 3, 'twoOctets': 2, 'fourOctets': 4.

This is the number of seconds between successive status enquiry messages.

Number of status enquiry intervals that pass before issuance of a full status enquiry message.

This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.

This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down.

The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond badValue

This indicates whether the Frame Relay interface is using a multicast service. Enumeration: 'broadcast': 2, 'nonBroadcast': 1.

This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely. Enumeration: 'down': 5, 'fault': 2, 'running': 1, 'up': 4, 'initializing': 3.

This indicates the type of interface. Enumeration: 'dce': 1, 'dte': 2.

This object enables or disables the BECN flow control. Enumeration: 'enable': 1, 'disable': 2.

. Enumeration: 'forced': 1, 'standard': 3, 'buffered': 2.

.

The DLCI of the LMI for this interface.

LMI error threshold. For DCE IF Type. This is the maximum number of unanswered unreceived Status Enquiries the equipment shall accept before declaring the interface down.

LMI monitored event count. For DCE IF Type. This is the number of status polling intervals over which the error threshold is counted.

LMI monitored event count. For DCE IF Type. This indicates the expected number of seconds between heartbeat polls.

. Enumeration: 'enable': 1, 'disable': 2.

A table containing information about specific Data Link Connections (DLC) or virtual circuits.

The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in csFrCircuitCreationTime.

The identifier for this Frame Relay Circuit. This corresponds to the 'subinterface' entered via the CLI.

The Data Link Connection Identifier for this virtual circuit. Note, this impelemtation supports only values between 16 and 1023 (inclusive).

Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of csFrCircuitRowStatus. Enumeration: 'active': 2, 'inactive': 3, 'invalid': 1.

Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.

Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.

The number of frames sent from this virtual circuit since it was created.

The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.

Number of frames received over this virtual circuit since it was created.

Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.

The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.

The value of sysUpTime when last there was a change in the virtual circuit state

This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.

This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval.

Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst size and throughput are both non-zero, the measurement interval, T, is T=csFrCircuitCommittedBurst/csFrCircuitThroughput. If the configured committed burst size and throughput are both zero, the measurement interval, T, is T=csFrCircuitExcessBurst/ifSpeed.

This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to Enumeration: 'unicast': 1, 'nWay': 4, 'twoWay': 3, 'oneWay': 2.

Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface. Enumeration: 'dynamic': 2, 'static': 1.

The number of inbound frames dropped because of format errors, or because the VC is inactive.

Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.

Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.

The remote IP address mapped to this VC.

This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.

The operational status of this circuit.

Indication of whether the DLCI corresponding to the forward link of this DLCI, is a Frame Relay DLCI or Frame over IP DLCI. Depending on this the csFrCircuitFwdLink object is interpreted differently. When setting a csFrCircuitFwdLink object, this object also must be set. Enumeration: 'froipDlci': 2, 'frDlci': 1.

The forwarding link of this DLCI. This is a switching parameters for intra blade and inter-blade switching. It takes the following format: If csFrCircitFwdDlciType is frDlci byte #0 to #3 : Slot number (csFrDlcmiSlot) byte #4 to #7 : Port number (csFrDlcmiPort) byte #8 to #11 : Channel number (csFrDlcmiChannel, zero for unchannelized blade) byte #12 to #15: DLCI number (csFrCircuitDlci) If csFrCircitFwdDlciType is froipDlci byte #0 to #3 : VPN Id (csOrionGlobalVPNIndex) byte #4 to #7 : VR Id (csOrionVPNVRouterIndex) byte #8 to #11 : Transport Id (csOrionFRoIPTransportPeer) byte #12 to #15: DLCI number (csFroIPCircuitDlci) NOTE: all zero indicates that this DLCI is not connected to any link.

This object enables or disables ingress traffic rate-policing. Ingress rate-policing is controlled by the values configured for csFrCircuitThroughput, csFrCircuitCommitedBurst and CsFrCircuitExcessBurst. If the number of bits received in the measurement interval is less than or equal to the committed burst size, the frame is forwared for further processing. If the number of bits received in the measurement interval is greater than the commited burst size but less than the sum of commited burst size and excess burst size, the DE bit is set in the frame and then forwared for further processing. If the number of bits received in the measurement interval is greater than the sum of commited burst size and excess burst size, the frame is dropped. Enumeration: 'enable': 1, 'disable': 2.

This object is used to set the upper protocol. For PPP over FR this is set to 'ppp'. NOTE: This object cannot be set to 'ip'. Only when a VI is connected to this interface that it becomes 'ip'. Enumeration: 'ip': 2, 'none': 1, 'ppp': 3.

A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.

The error information for a single frame relay interface.

The type of error that was last seen on this interface: receiveShort: frame was not long enough to allow demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete. receiveLong: frame exceeded maximum length configured for this interface. illegalAddress: address field did not match configured format. unknownAddress: frame received on a virtual circuit which was not active or administratively disabled. dlcmiProtoErr: unspecified error occurred when attempting to interpret link maintenance frame. dlcmiUnknownIE: link maintenance frame contained an Information Element type which is not valid for the configured link maintenance protocol. dlcmiSequenceErr: link maintenance frame contained a sequence number other than the expected value. dlcmiUnknownRpt: link maintenance frame contained a Report Type Information Element whose value was not valid for the configured link maintenance protocol. noErrorSinceReset: no errors have been detected since the last cold start or warm start. Enumeration: 'dlcmiUnknownRpt': 9, 'dlcmiUnknownIE': 7, 'illegalAddress': 4, 'noErrorSinceReset': 10, 'dlcmiSequenceErr': 8, 'unknownAddress': 5, 'receiveLong': 3, 'receiveShort': 2, 'dlcmiProtoErr': 6, 'unknownError': 1.

An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information.

The value of sysUpTime at which the error was detected.

The number of times the interface has gone down since it was initialized.

The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.

A table containing information about the statistics on every DLCMI.

The statistics information for a single frame relay interface.

Number of times the Status Equiry is sent.

Number of times the Full Status Equiry is sent.

Number of times the Status Response is received.

Number of times the Full Status Response is received.

Number of times the Asyn Update is made.

Number of times the Unknown Messages is encountered.

Number of times the Lost Sequence is encountered.

Number of times the Missing Response is encountered.

The local sequence number.

The network sequence number.

This table contains ATM local interface configuration parameters, one entry per ATM interface port.

This list contains ATM interface configuration parameters and state variables.

This object identifies the blade to which this ATM Port is attached. Together with csAtmInterfaceConfModuleIndex, csAtmInterfaceConfPortIndex, it uniquely identifies a physical port.

This object identifies the module to which this ATM Port is attached.

This object identifies the blade to which this ATM Port is attached. Together with csAtmInterfaceConfSlotIndex, it uniquely identifies a physical port.

The maximum number of VPCs (PVPCs and SVPCs) supported at this ATM interface. At the ATM UNI, the maximum number of VPCs (PVPCs and SVPCs) ranges from 0 to 256 only.

The maximum number of VCCs (PVCCs and SVCCs) supported at this ATM interface.

The number of VPCs (PVPC, Soft PVPC and SVPC) currently in use at this ATM interface. It includes the number of PVPCs and Soft PVPCs that are configured at the interface, plus the number of SVPCs that are currently established at the interface. At the ATM UNI, the configured number of VPCs (PVPCs and SVPCs) can range from 0 to 256 only.

The number of VCCs (PVCC, Soft PVCC and SVCC) currently in use at this ATM interface. It includes the number of PVCCs and Soft PVCCs that are configured at the interface, plus the number of SVCCs that are currently established at the interface.

The maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum number of active VPI bits configured for use ranges from 0 to 8 only.

The maximum number of VPI Bits that may currently be used at this ATM interface. The value is the minimum of AtmInterfaceMaxActiveVpiBits, and the AtmInterfaceMaxActiveVpiBits of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the number of VPI Bits that can be used on the interface, then the value of this object must equal AtmInterfaceMaxActiveVpiBits.

The maximum number of active VCI bits configured for use at this ATM interface.

The maximum number of VCI Bits that may currently be used at this ATM interface. The value is the minimum of AtmInterfaceMaxActiveVciBits, and the AtmInterfaceMaxActiveVciBits of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the number of VCI Bits that can be used on the interface, then the value of this object must equal AtmInterfaceMaxActiveVciBits.

The VPI value of the VCC supporting the ILMI at this ATM interface. If the values of AtmInterfaceIlmiVpi and AtmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.

The VCI value of the VCC supporting the ILMI at this ATM interface. If the values of AtmInterfaceIlmiVpi and AtmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.

A textual name of this interface. if this system is manageable through SNMP, and supports the object ifName, the value of this object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. This interface must be uniquely named on this system to distinguish parallel links with a neighboring system. if this interface does not have a textual name, the value of this object is a zero length strin.

The IP address of the neighbor system connected to the far end of this interface, to which a Network Management Station can send SNMP messages, as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system.

The textual name of the interface on the neighbor system on the far end of this interface, and to which this interface connects. If the neighbor system is manageable through SNMP and supports the object ifName, the value of this object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. If this interface does not have a textual name, the value of this object is a zero length string. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system.

An indication of the latest version of the ATM Forum ILMI specification that is supported on this ATM interface. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. If this object is not present, a version of the ILMI earlier than 4.0 is supported. Enumeration: 'version4point0': 2, 'unsupported': 1.

The type of the ATM device, either public or private. Enumeration: 'public': 1, 'private': 2.

An indication of the latest version of the ATM Forum UNI Signalling Specification that is supported on this ATM Interface. if this value is not present, a version of the UNI earlier than 3.1 is supported. If the peer IME's value of this object is the same as, or earlier than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise compatibility of the two IMEs cannot be assumed. Enumeration: 'version4point0': 4, 'version2point0': 1, 'unsupported': 5, 'version3point1': 3, 'version3point0': 2.

The object used to enable/disable this ATM interface. Enumeration: 'enable': 1, 'disable': 2.

The operational status of this ATM interface.

The object is used to enable/disable the ILMI on this ATM interface. Enumeration: 'enable': 1, 'disable': 2.

The object is used to monitor the status of the ILMI on this ATM interface. Enumeration: 'down': 2, 'up': 1.

This object is used to set the level for details for event logs for ATM port. This value will not be applied to VCCs. Events with level higher than this object will not be logged.

This object is used to set the area of event logs for ATM Port. This value will not be applied to VCCs. Events which area is not specified in this object will not be logged.

This table can be used to creata virtual connections in this ATM interface.

This list contains ATM virtual connections.

Channel ID of this ATM connection. Currently, it will always be 0.

The identifier for this ATM connection. This corresponds to the 'subinterface' entered via the CLI.

Virtual Path ID of this connection. This is mandatory in creating a connection.

Virtual Channel ID of this connection. This is mandatory in creating a connection.

The ATM service category. NOTE : The type other(1) is not implemented for write operation. Setting to this type will default to ubr(6).

Enumeration: 'pvpc': 1, 'pvcc': 2.

Peak Cell rate for the connection.

Sustain Cell rate for the connection. NOTE: This value is applicable for VBR service categories.

Maximum Burst Size for the connection. NOTE: This value is applicable for VBR service categories.

Inital Cell rate for the connection. NOTE: This value is applicable for ABR service category.

Minimum Cell rate for the connection. NOTE: This value is applicable for ABR service category.

This object is used to enable/disable the loopback. Enumeration: 'enable': 1, 'disable': 2.

This object is used to enable/disable the continuity. Enumeration: 'enable': 1, 'disable': 2.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the transmit direction of this VCC. NOTE : For now, a maximum of 1744 is supported.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the receive direction of this VCC.

The use of call control. Enumeration: 'unknown': 1, 'llcBridgedEncapsulation': 4, 'vcMultiplexRoutedProtocol': 3, 'llcRoutedEncapsulation': 2, 'vcMultiplexedBridged802dot3': 5.

The use of call control. Enumeration: 'spvc': 3, 'pvc': 1, 'svc': 2.

This object is instanciated only for a connection which terminates a VCC (i.e., one which is NOT cross-connected to other connections). Its value specifies the desired administrative state of the connection. Enumeration: 'enable': 1, 'disable': 2.

The current operational status of the connection.

This object is used to create, delete or modify a row in this table.

This object is used to set the upper protocol. For PPP over ATM this is set to 'ppp'. For PPP over Ethernet this is set to 'pppoe'. NOTE: This object cannot be set to 'ip'. Only when a VI is connected to this interface that it becomes 'ip'. Enumeration: 'ip': 2, 'none': 1, 'ppp': 3, 'pppoe': 4.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports Bridging format. This objects specifies aging time (in minutes) for ARP Cache entries and it takes effect when ATM ARP module restarts.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports Bridging format. This objects specifies the size of ARP Cache and it takes effect when ATM ARP module restarts.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports Bridging format. This objects specifies the active MAC Address on the VCC end-point.

This object is used to set the level for details for event logs forATM VCC. Events with level higher than this object will not be logged.

This object is used to set the area of event logs for ATM VCC. Events which area is not specified in this object will not be logged.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports LLC-SNAP format. This objects specifies aging time (in minutes) for InARP entries and it takes effect immediately. Also this object is active when IP protocol is enabled on VC

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports LLC-SNAP format. This objects specifies whether PVC services to layer 3 is managed by InArp status in addition to PVC opertional status and it takes immediate effect . Also this object is active when IP protocol is enabled on VC Enumeration: 'enable': 1, 'disable': 2.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports LLC-SNAP format. This objects specifies the PVC InARP status and thus will be used to control services to l3, when AtmConnInArpManageVc is enabled. Also this object is meaning full when IP protocol is enabled on VC Enumeration: 'down': 2, 'none': 3, 'up': 1.

An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 Encapsulation type supports LLC-SNAP format. This objects specifies whether InARP services can be enabled or disbaled. Operation on this object takes immediate effect. Also this object is active when IP protocol is enabled on VC Enumeration: 'enable': 1, 'disable': 2.

OAM retry count before declaring the PVC up.

OAM retry Frequency in seconds.

OAM Time to wait before transmitting OAM requests for UP status(in minutes)

OAM retry count before declaring the PVC down.

OAM retry Frequency in seconds (for down status).

OAM Time to wait before transmitting OAM requests (in minutes)

This object is used to enable/disable the oam loopback manage vc. Enumeration: 'enable': 1, 'disable': 2.

The current loopback status of the connection. Enumeration: 'down': 2, 'none': 3, 'up': 1.

This list contains Dynamic ARP Entries for ATM virtual connections.

This object holds IP address associated with MAC Address.

This object holds MAC address associated with IP Address.

This object is used to delete a row in this table.

This list contains Static (configured) ARP Entries for ATM virtual connections.

This object holds IP address associated with MAC Address.

This object holds MAC address associated with IP Address.

This object is used to create, delete or modify a row in this table.

This list contains ARP Entries for ATM virtual connections.

This object holds IP address for which ATM ARP module responds positively.

This object is used to create, delete or modify a row in this table.

This object specifies the type of IP address, i.e.,NON-PROXY-IP, or PROXY IP. Enumeration: 'none': 3, 'proxyIp': 2, 'nonProxyIp': 1.

End of this group. value undefined

This list contains statistics entries for ATM interfaces.

The counter indicates the number of packets transmitted on ATM interface

The counter indicates the number of bytes transmitted on ATM interface

The counter indicates the number of packets dropped due to transmit path errors on ATM interface caused by buffer operation failures, and invalid protocol types

The counter indicates the number of packets dropped in transmit path on ATM interface, because of inactive PVCs

The counter indicates the number of packets dropped due to transmit queue is full on driver interface

The counter indicates the number of packets dropped in transmit path due to bad length on driver interface

The counter indicates the number of packets transmitted incompletely on driver interface

The counter indicates the number of packets dropped in transmit path due to non-existing VCCs on driver interface

The counter indicates the number of packets Received on ATM interface

The counter indicates the number of bytes Received on ATM interface

The counter indicates the number of packets dropped due to LLC/SNAP errors in Receive path on ATM interface

The counter indicates the number of packets dropped due to unknown protocols errors in Receive path on ATM interface

The counter indicates the number of packets dropped due to Receive path errors on ATM interface

The counter indicates the number of packets dropped in Receive path on ATM interface, because of inactive PVCs

The counter indicates the number of received packets dropped due to buffer allocation on Driver interface

The counter indicates the number of received packets dropped due to buffer allocation on Driver interface

The counter indicates the number of received packets dropped due to non-existing VCs on Driver interface

The counter indicates the number of received packets dropped due to unsupported AAL type on Driver interface

The counter indicates the number of received packets dropped due to bad PDU length on Driver interface

The counter indicates the number of received packets dropped due to CRC errors on Driver interface

The counter indicates the number of cells dropped on Driver interface

The counter indicates the number of received cells dropped due to invalid VPI/VCI values on Driver interface

The counter indicates the number of OAM loop-back requests transmitted on ATM interface

The counter indicates the number of OAM loop-back responses received on ATM interface

The counter indicates the number of responded OAM loop-back requests on driver interface

The counter indicates the number of OAM loop-back requests/responses failed to transmit on ATM/driver interface

The counter indicates the number of packets (data and OAM) aborted due collisions at driver interface

The counter indicates the number of total number of cells transmitted on driver interface

The counter indicates the number of packets (OAM & data) failed in reassemble path in ATM/driver interface due bad AAL5 trailer length

The counter indicates the total number of received on open channels at ATM/driver interface

End of this group. value undefined

This list contains statistics entries for ATM interfaces.

The counter indicates the number of packets transmitted on ATM VC

The counter indicates the number of bytes transmitted on ATM VC

The counter indicates the number of packets dropped due to transmit path errors on ATM VC

The counter indicates the number of packets dropped in transmit path on ATM VC, because of inactivity

The counter indicates the number of packets dropped due to transmit queue is full on driver interface

The counter indicates the number of packets dropped in transmit path due to bad length on driver interface

The counter indicates the number of packets Received on ATM VC

The counter indicates the number of bytes Received on ATM VC

The counter indicates the number of packets dropped due to encapsulation errors in Receive path errors on ATM VC

The counter indicates the number of packets dropped due to unknown protocol in r eceive path errors on ATM VC

The counter indicates the number of packets dropped due to Receive path generic errors on ATM VC. These errors includes, when protocol is none, or any other operations failed while accessing LLC/SNAP header

The counter indicates the number of packets dropped in Receive path on ATM VC, because of inactivity

The counter indicates the number of received packets dropped due to buffer allocation on Driver interface

The counter indicates the number of received packets dropped due to buffer allocation on Driver interface

The counter indicates the number of received packets dropped due to unsupported AAL type on Driver interface

The counter indicates the number of received packets dropped due to bad PDU length on Driver interface

The counter indicates the number of received packets dropped due to CRC errors on Driver interface

The counter indicates the number of OAM loop-back requests transmitted on ATM VC

The counter indicates the number of OAM loop-back responses received on ATM VC

The counter indicates the number of responded OAM loop-back requests on driver interface

The counter indicates the number of OAM loop-back requests failed to transmit on ATM VC

The counter indicates the number of transmitted ARP requests on ATM VC

The counter indicates the number of transmitted ARP responses on ATM VC

The counter indicates the number of received ARP requests on ATM VC

The counter indicates the number of received ARP responses on ATM VC

The counter indicates the number of received ARP requests for which, no ARP responses send due to non-existing IP address on ATM VC

The counter indicates the number of ARP requests/responses failed due other reasons, on ATM VC

The counter indicates the total number of data cells transmitted on ATM VC

The counter indicates the total number of packets (OAM/RAW/data) packets dropped or aborted on ATM VC

The counter indicates the total number of cells received on ATM VC

End of this group. value undefined

This list contains ARP Entries for ATM virtual connections.

The number of InATMARP requests received on the PVC.

The number of InATMARP requests sent on the PVC.

The number of InATMARP replies received on the PVC.

The number of InATMARP replies sent on the PVC.

The number of Invalid InATMARP requests received on the PVC.

The number of InATMARP requests for which replies did not received on the PVC.

The number of generic errors encountered while processing InATMARP requests and replies on the PVC.

End of this group. value undefined

This object identifies the blade to which this POS Port is attached. Together with csPosInterfaceConfPortIndex, it uniquely identifies a physical port.

This object identifies the specific module of this POS blade.

This object identifies the blade to which this POS Port is attached. Together with csPosInterfaceConfPortIndex, it uniquely identifies a physical port.

This object identifies the encapsulation format used on this Packet Over Sonet port. Enumeration: 'none': 1, 'ppp': 3, 'frameRelay': 4, 'hdlc': 2.

This object is used to enable/disable this POS interface. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the current operational status of this POS interface.

A list of VPNs which belong to Orion box.

An entry containing management information applicable to a particular interface or management Blade.

A globally unique value, greater than zero, for each VPN, configured across all existing Orion boxes.

A textual string containing information about the VPN. By default this is set to 'VPN x', where x is the VPN ID.

This object identifies a prioritized list of RADIUS servers (from the csRadiusSvrTable) that will be used when a packet needing RADIUS services is processed. NOTE: This object has been obsoleted. Each VR has its own Radius server list. see csOrionRadiusInfo

This object identifies a prioritized list of DNS servers (from the csDnsSvrTable) that will be used when a packet needing DNS services is processed. NOTE: This object has been obsoleted.

A row status type for the VPN.

A operational status for the VPN.

A list of Virtual Routers, configured for the VPN.

An entry containing management information applicable to a particular virtual router, configured for the VPN.

A unique value, greater than zero, for each VPN Virtual Router.

A textual string containing information about the Virtual Router, configured to the particular VPN.