CISCO-WAN-AXIPOP-MIB

type

type

type

type

type

OBJECT-TYPE

The ASM Alarm table. The table size is given by the value of ASMNumOfValidEntries.

OBJECT-TYPE

An entry in the Basis ASM Alarm Table.

OBJECT-TYPE

This object is the identifier of a ASM alarm entry. The Alarm is further identified by the objects ASMAlarmType & ASMAlarmUnitNum.

OBJECT-TYPE

The value for this object indicates the type of Alarm represented in the entry of ASMAlarmTable indexed by ASMAlarmNum.

OBJECT-TYPE

This object identifies one unit among a number of identical units represented in ASMAlarmTable having the same ASMAlarmType.

OBJECT-TYPE

This object specifies the threshold beyond which the alarmable unit is said to be in an abnormal state.

OBJECT-TYPE

This variable specifies the severity of the alarm to be declared when the ASMAlarmThreshold specified is exceeded for the entry of ASMAlarmTable indexed by ASMAlarmNum.

OBJECT-TYPE

This object indicates if the alarm unit is measurable by the AXIS shelf.

OBJECT-TYPE

This object gives the mesaured value of the entity addressed by asmAlarmNum if it is measurable.

OBJECT-TYPE

This object indicates the status of the ASM alarm represented in this entry. It is a bitmap where a set bit indicates an abnormal condition. A reset bit signifies normal operation.

OBJECT-TYPE

This object when set to ASMAlarmClear causes the entry in the ASMAlarmTable represented by ASMAlarmNum to be cleared.

OBJECT-TYPE

The number of valid ASMAlarmTable entries (regardless of how many are actually configured) in the table.

OBJECT-TYPE

This object indicates whether any Shelf Alarm has been declared in the BASIS system.

OBJECT-IDENTITY

OBJECT-TYPE

A table implemented by the UNI Management Entity on the user-side of an ATM UNI port, containing the network-prefix(es) for ATM-layer addresses in effect on the user-side of the UNI.

OBJECT-TYPE

An entry in the table, containing information about the ATM Prefix status.

OBJECT-TYPE

The unique value which identifies the ILMI port.

OBJECT-TYPE

The network prefix for ATM addresses which is in effect on the user-side of the ATM UNI port.

OBJECT-TYPE

An indication of the validity of the network prefix for ATM addresses, on the user-side of the UNI port.

OBJECT-TYPE

An indication of the current registration state for the prefix: registering, de-registering, success, fail.

OBJECT-IDENTITY

OBJECT-TYPE

A table implemented by the network-side of an ATM UNI port, containing the ATM-layer addresses in effect on the user-side of the UNI.

OBJECT-TYPE

Information about a single ATM-layer address in effect on the user-side of a UNI port.

OBJECT-TYPE

A unique value which identifies this port. The value of 0 has the special meaning of identifying the local UNI.

OBJECT-TYPE

The ATM address which is in effect on the user-side of the ATM UNI port.

OBJECT-TYPE

An indication of the validity of the ATM address at the user-side of the UNI port.

OBJECT-IDENTITY

OBJECT-TYPE

The common port table is for the common ports.

OBJECT-TYPE

An entry for every common port group.

OBJECT-TYPE

This is the index to the port number.

OBJECT-TYPE

This is the type of the port. 1 - Frame Relay Port. 2 - ATM Port. 3 - IMA Port.

OBJECT-TYPE

This variable enables or disables the port 1 - disable 2 - enable

OBJECT-TYPE

This is the speed of the port in cells per second.

OBJECT-TYPE

This variable states the alarm status of the port 1 - port in alarm 2 - port out of alarm

OBJECT-TYPE

This variable indicates the signalling protocol type of the port. This field is TBD. It is unused in IMATM/AUSM.

OBJECT-TYPE

This variable indicates the signalling state of the port.

OBJECT-TYPE

This variable indicates the list of physical lines in the port delimited by dots.

OBJECT-TYPE

The variable indicates the list of channels that are used in the ds1 frame.

OBJECT-IDENTITY

OBJECT-TYPE

The common port table is for the common ports.

OBJECT-TYPE

An entry for every common port group.

OBJECT-TYPE

This is the index to the channel number.

OBJECT-TYPE

This specifies the connection type 1 ==> Virtual Path Connection 2 ==> Virtual Channel Connection

OBJECT-TYPE

This variable indicates the state of the VC (channel)(

OBJECT-TYPE

This is the alarm state of the port.

OBJECT-TYPE

This variable indicates the port number associated with the channel

OBJECT-TYPE

This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 3 ==> Associated Bit Rate

OBJECT-TYPE

This variable indicates the transmit state of the VC (channel) on the CellBus side (Ingress)

OBJECT-TYPE

This variable indicates the status of port receive (Ingress)

OBJECT-TYPE

indicates the status of port transmit(Egress)

OBJECT-TYPE

Indicates the receiving state of the VC (channel) on the Cellbus side (Egress)

OBJECT-TYPE

Connection paramter 1

OBJECT-TYPE

Connection paramter 2

OBJECT-IDENTITY

OBJECT-TYPE

This object specified the type of partition on LCN: 1. noPartition -- means that all controllers compete for the totoal (G)LCNs limited by the card 2. controllerBased -- means that the total number of (G)LCNs available to each controller is fixed but no reservation on each port. The number for each controller is specified in the smCardResPartGrpTable. 3. portControllerBased -- means that a certain number of (G)LCNs available on each port for each controller is reserved, it is specified in the port resouce partition table. NOTE: This object has to be configured before adding any connections and once a connection is added, this object cannot be changed until all of the connections are deleted.

OBJECT-TYPE

This table contains the configuration of all the resource partition(s) that are on the card level, such as (G)LCN (if the object cardLcnPartitionType is configured as controller-based, if not, there is no need to configure this table since it'll be useless).

OBJECT-TYPE

This is an entry for a controller

OBJECT-TYPE

This object is the index to the table

OBJECT-TYPE

This object is records the status of this entry

OBJECT-TYPE

This object is configured to reserve the number of (G)LCNs for one controller on a SM card, it can be used on any port but the total number of connections added on all of the ports for that particular controller cannot exceed this number.

OBJECT-IDENTITY

OBJECT-TYPE

Primary Mux Clock source for AUM card.

OBJECT-TYPE

Secondary clock source for AUM card.

OBJECT-TYPE

clock source currently selected for AUM card.

OBJECT-TYPE

clock source switched.

OBJECT-TYPE

Status of External T1/E1 Clock on AUM card.

OBJECT-TYPE

Impedance on external clock input for AUM card.

OBJECT-TYPE

This object describes the type of connector available for connecting the external clock source to the AUM-LM. The T3 and E3 cards are separate hence this field is not configurable for any BNM card type except bnm-155

OBJECT-IDENTITY

OBJECT-TYPE

This table contains address translation parameters for AXIS connections.

OBJECT-TYPE

This entry exists when the connection specified by connShelfNum, connSlotNum and connChanNum exists.

OBJECT-TYPE

Index to shelf list on BASIS.

OBJECT-TYPE

Index to slot list on BASIS.

OBJECT-TYPE

Index to channel list on BASIS.

OBJECT-TYPE

Virtual channel connection or Virtual Path Connection

OBJECT-TYPE

Virtual channel connection or Virtual Path Connection

OBJECT-TYPE

This table contains address translation parameters for AXIS connections.

OBJECT-TYPE

This entry controls bulk deletion of connections on a given AXIS slot.

OBJECT-TYPE

Index to shelf list on AXIS.

OBJECT-TYPE

Index to slot list on BASIS.

OBJECT-TYPE

Number of rows in aumAddressTranslationTable.

OBJECT-IDENTITY

OBJECT-TYPE

The counter table is for the ATM interface, initially there is only one interface, but by making it a table multiple ATM interfaces can be accommodated later.

OBJECT-TYPE

An entry for DS3 ATM counters

OBJECT-TYPE

This specifies the BNM port being referenced.

OBJECT-TYPE

The count of Received cells at the BNM port.

OBJECT-TYPE

The count of cells transmitted by the BNM port.

OBJECT-TYPE

This object when set to bnmPortCounterClear causes all counters in the row referenced by bnmPortCounterIndex to be cleared.

OBJECT-TYPE

The number of cells received from the BNM port (trunk) per second .

OBJECT-TYPE

The received percentage utilization of the BNM port (trunk)

OBJECT-TYPE

The number of cells transmitted to the BNM port (trunk) per second.

OBJECT-TYPE

The transmitted percentage utilization of the BNM port (trunk)

OBJECT-TYPE

This object specifies the number of rows in bnmPortCounterTable.

OBJECT-TYPE

This objects is a count of cells transmitted by the BNM Cell Bus Master to the cell bus.

OBJECT-TYPE

This object is a count of cells transmitted by the BNM Cell Bus Master to the cell bus for which no acknowledgement was received i.e the slave card was missing or inactive.

OBJECT-TYPE

This object is a count of receiver grants given by the BNM Cell Bus Master

OBJECT-TYPE

This object is a count of cells transmitted by the Egress Engine to the port i while a T3 Alarm condition was in effect.

OBJECT-TYPE

This object is a count of cells with disabled channel headers, received by the Egress Engine on the BNM and dropped.

OBJECT-TYPE

This object gives the header of the first invalid cell that was dropped by the Egress Engine on the BNM since this object was last read and/or cleared.

OBJECT-TYPE

This object is a count of cells from disabled channels received by the Ingress Engine on the BNM. This is not available in Release 1.

OBJECT-TYPE

This object gives the header of the first invalid cell that was dropped by the Ingress Engine on the BNM since this object was last read and/or cleared. This is not available in Release 1.

OBJECT-TYPE

This object clears the BNM counters

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for DS3 line interface

OBJECT-TYPE

An entry for logical line

OBJECT-TYPE

Refers to the logical line index

OBJECT-TYPE

VPI used for ATM LMI signalling

OBJECT-TYPE

VCI used for ATM LMI signalling

OBJECT-TYPE

This will enable ATM LMI signalling, or ATM LMI with the Node Status Extensions

OBJECT-TYPE

This will enable ATM LMI polling

OBJECT-TYPE

Status Enq Polling Interval in seconds Default is 10 seconds

OBJECT-TYPE

Status Enq timeout interval in seconds Default is 10 seconds

OBJECT-TYPE

Update Status timeout interval in seconds Default is 10 seconds

OBJECT-TYPE

Status Enq maximum retry count Default is 3

OBJECT-TYPE

Update Status maximum retry count Default is 3

OBJECT-TYPE

Operational status

OBJECT-IDENTITY

OBJECT-TYPE

The counter table is for DS3 line interface

OBJECT-TYPE

An entry for logical line

OBJECT-TYPE

Refers to the logical line index

OBJECT-TYPE

The number of Status PDUs transmitted

OBJECT-TYPE

The number of Status Enquiry PDUs transmitted

OBJECT-TYPE

The number of Status Ack PDUs transmitted

OBJECT-TYPE

The number of Update Status PDUs transmitted

OBJECT-TYPE

The number of Status PDUs received

OBJECT-TYPE

The number of Status Enquiry PDUs received

OBJECT-TYPE

The number of Status Ack PDUs received

OBJECT-TYPE

The number of Update Status PDUs received

OBJECT-TYPE

The number of Invalid PDUs received. These are PDUs with invalid SSCOP or Q.2931 header, or invalid Protocol Discriminator

OBJECT-TYPE

The number of PDUs received with invalid length. ATM LMI PDU Length field plus Q.2931 Header length does not equal actual message length

OBJECT-TYPE

The number of PDUs with unknown Message Type received

OBJECT-TYPE

The number of PDUs received with invalid Information Elements. This includes IEs with invalid length and missing mandatory IEs

OBJECT-TYPE

The number of invalid transactions. The transaction number of a transmitted Update Status PDU does not match the transaction number of the corresponding received Status Ack PDU, or, the transaction number of a transmitted Status Enq PDU does not match the transaction number of the corresponding received Status PDU.

OBJECT-TYPE

The number of timeout failures

OBJECT-TYPE

The number of Node Status PDUs transmitted

OBJECT-TYPE

The number of Node Status Ack PDUs transmitted

OBJECT-TYPE

The number of Node Status PDUs received

OBJECT-TYPE

The number of Node Status Ack PDUs received

OBJECT-IDENTITY

OBJECT-TYPE

The ATM LMI Channel State table

OBJECT-TYPE

An entry for a Channel

OBJECT-TYPE

Refers to the line number

OBJECT-TYPE

Refers to the Virtual Path Indicator

OBJECT-TYPE

Refers to the Virtual Channel Indicator

OBJECT-TYPE

This is the transmit A bit state 0 - A bit clear = not active 1 - A bit set = active

OBJECT-TYPE

This is the receive A bit state 0 - A bit clear = not active 1 - A bit set = active

OBJECT-IDENTITY

OBJECT-TYPE

BRAM parameter indicating whether redundancy is allowed in this shelf.

OBJECT-IDENTITY

OBJECT-TYPE

BRAM parameter indicating whether this card will support DS0 channels.

OBJECT-TYPE

BRAM parameter indicating whether this card will support foresight.

OBJECT-TYPE

BRAM parameter indicating whether this card will support svc.

OBJECT-TYPE

BRAM parameter indicating whether this card will support FUNI.

OBJECT-TYPE

BRAM parameter indicating whether this card will support Inverse Multiplexing for ATM (IMA) feature

OBJECT-TYPE

BRAM parameter indicating whether this card will support multiple IMA trunks feature. A value of 1 indicates that the feature is not allowed and a value of 2 indicates that the features is allowed

OBJECT-TYPE

If this is set to egrQosFeatureEnabled then the various class of service viz. Hi Priority, VBR rt, etc. as defined by the channel MIB object chanServType are supported. If this is set to egrQosFeatureDisabled then, the priority based queuing as defined by the channel MIB object egressQSelect is supported.

OBJECT-IDENTITY

OBJECT-TYPE

Rate Up value for this card.

OBJECT-TYPE

Rate Down value for this card.

OBJECT-TYPE

Rate Fast Down value for this card.

OBJECT-TYPE

Round Trip delay measurement time in secs for this card.

OBJECT-TYPE

QIR timeout in secs for this card.

OBJECT-IDENTITY

OBJECT-TYPE

Primary reference for the clock source. Each of these codes are to be interpreted as follows: liu-rclk0: Recovered clock from physical line 0 liu-rclk1: Recovered clock from physical line 1 liu-rclk2: Recovered clock from physical line 2 liu-rclk3: Recovered clock from physical line 3 liu-rclk4: Recovered clock from physical line 4 liu-rclk5: Recovered clock from physical line 5 liu-rclk6: Recovered clock from physical line 6 liu-rclk7: Recovered clock from physical line 7 dsx3: Recovered clock from the T3/E3 line bp8clk: Back-plane 8 KHz clock

OBJECT-TYPE

Secondary reference for the clock source. Each of these codes are to be interpreted as follows: liu-rclk0: Recovered clock from physical line 0 liu-rclk1: Recovered clock from physical line 1 liu-rclk2: Recovered clock from physical line 2 liu-rclk3: Recovered clock from physical line 3 liu-rclk4: Recovered clock from physical line 4 liu-rclk5: Recovered clock from physical line 5 liu-rclk6: Recovered clock from physical line 6 liu-rclk7: Recovered clock from physical line 7 dsx3: Recovered clock from the T3/E3 line bp8clk: Back-plane 8 KHz clock none : No secondary clock is configured

OBJECT-TYPE

This object holds the current source for the clock

OBJECT-IDENTITY

OBJECT-TYPE

The dsx3 port counters table is for the DS3 port in IMATM. At present there is only one entry (corresponding to the single DS3 port available). This structure has been made a table for flexibility (although there is only one entry in the table at present)

OBJECT-TYPE

An entry for each T3 port (total of only one entry at present)

OBJECT-TYPE

Index to the dsx3 port number

OBJECT-TYPE

Number of cells received on the DS3 port

OBJECT-TYPE

Number of cells transmitted on the DS3 port

OBJECT-TYPE

Number of invalid cells received on the DS3 port

OBJECT-TYPE

This variable is used to clear all the counters maintained by the card for this DS3 port

OBJECT-TYPE

This variable denotes the last mismatch VPI/VCI value that was received over the DS3 interface.

OBJECT-TYPE

This variable is used to count the number of cells from the DS3 interface that were discarded due to match with IMA Control header

OBJECT-IDENTITY

OBJECT-TYPE

The SRM 3T3 configuration table, it is the distribution of a T3 line.

OBJECT-TYPE

an entry in the T3 configuration table

OBJECT-TYPE

Select T3 line number. There is no default value for this object.

OBJECT-TYPE

The start T1 number to be affected. There is no default value for this object.

OBJECT-TYPE

a command is used to add, delete, or modify one or more DS1 mapping. Default value is delete.

OBJECT-TYPE

specify the target slot number to be linked. There is no default value for this object. For MGX8850: SRM01 services slots 1 - 6 and 9 - 14, SRM02 services slots 17 - 22 and 25 - 30 For MGX8220: SYNTAX INTEGER (5 ..14)

OBJECT-TYPE

0 means not assigned. There is no default value for this object.

OBJECT-IDENTITY

OBJECT-TYPE

This variable indicates the whether the card is over subscribed or not

OBJECT-TYPE

Percentage Utilization of the Card in the Ingress direction.

OBJECT-IDENTITY

OBJECT-TYPE

This indicates the format of the cells going out on the BNM trunk For T3 and E3 cards its currently fixed at STI mode. BNM-155 sonet cards can take on UNI or NNI options

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The imatmVpTrkMapGrpTable entry contains the information for mapping VPI ranges to different trunks in IMATM.

OBJECT-TYPE

An entry for each VPI range

OBJECT-TYPE

An index to the VpTrkTbl

OBJECT-TYPE

This variable refers to the trunk number on the IMATM card. The trunk number is the same as logical port number.

OBJECT-TYPE

This variable refers to the minimum VPI value to be configured in the range of VPIs that are to be mapped to an IMATM trunk.

OBJECT-TYPE

This variable refers to the maximum VPI value to be configured in the range of VPIs that are to be mapped to an IMATM trunk. It should be necessarily greater than or equal to the value of imatmTrkMinVp.

OBJECT-TYPE

This variable refers to the operation type for the VPI range in question. 'disable' deletes an existing row from the table 'enable' adds a new row to the table 'modify' modifies the attributes of an existing row to the table

OBJECT-TYPE

This variable indicates the next range number to be used as the index for the VpTrkTbl.

OBJECT-IDENTITY

OBJECT-TYPE

This table is for each trunk in IMATM and is used if the user wishes to remove all VPI ranges for an IMATM trunk.

OBJECT-TYPE

An entry for each IMATM trunk

OBJECT-TYPE

This variable is used to identify the IMATM trunk number on which the 'Clear Map Table' operation needs to be done.

OBJECT-TYPE

This variable implements the 'Clear Map Table' for a specified IMATM trunk.

OBJECT-IDENTITY

OBJECT-TYPE

The dsx3 Card spec Config group table will contain all the configuration variable for DSX3. Right now there is only one configurable parameter in this group. Moreover this structure has been made a table for flexibility (although there is only one entry in the table at present).

OBJECT-TYPE

Each entry gives the config parameters for the given port.

OBJECT-TYPE

Index to the dsx3 port number

OBJECT-TYPE

This variable refers to dsx3 HEC correction enabled/disabled default is disable.

OBJECT-IDENTITY

OBJECT-TYPE

This respesents bit map of the VSI Controllers supported. Currently, we have BIT 0 - PAR BIT 1 - PNNI BIT 2 - TAG (e.g. A value of 1 in BIT 0 indicates the presence of PAR ) Remaining bits are set to 0.

OBJECT-TYPE

This respesents bit map of the APS card attributes supported. Currently, we have BIT 0, 1 - unused BIT 2 - APS standard protocol configured (1 = TRUE ; 0 = FALSE) BIT 3, 4 ,5 - unused BIT 6 - Card HW supports APS 1+1 on two cards (1 = TRUE ; 0 = FALSE) BIT 7 - Card FW supports APS (1 = TRUE ; 0 = FALSE) Remaining bits are set to 0.

OBJECT-TYPE

This MIB variable allows one to add a new connection on the feeder trunk even if it is over-subscribed.

OBJECT-IDENTITY

OBJECT-TYPE

Primary Mux Clock source for PXM card. For pxmInbandClock1 and pxmInbandClock2, the pxmPrimaryInbandClockSourceLineNumber described the Line number that the clock is derived from. For pxmServiceModuleClock1 and pxmServiceModuleClock2, the pxmPrimarySMClockSourceSlotNumber described the SM slot number For pxmExternalClock and pxmExternalClock2, pxmPrimaryExternalClockSourcePortNumber describes the Port number from where the clock is derived. Also the pxmExtClockPresent and pxmExtClkConnectorType are used with the pxmExternalClock. And pxmExtClock2Present and pxmExtClk2ConnectorType are used with pxmExternalClock2.

OBJECT-TYPE

If pxmPrimaryMuxClockSource is pxmInbandClock1 (1) or pxmServiceModuleClock2 (5), then this entry indicates Inband Line number.

OBJECT-TYPE

If pxmPrimaryMuxClockSource is pxmServiceModuleClock1(2) or pxmServiceModuleClock2 (6), then this entry indicates SM slot number.

OBJECT-TYPE

Secondary clock source for PXM card. For pxmInbandClock1 and pxmInbandClock2, the pxmSecondaryInbandClockSourceLineNumber described the Line number that the clock is derived from. For pxmServiceModuleClock1 and pxmServiceModuleClock2, the pxmSecondarySMClockSourceSlotNumber described the SM slot number pxmSecondaryExternalClockSourcePortNumber describes the Port number from where the clock is derived. Also the pxmExtClockPresent and pxmExtClkConnectorType are used with the pxmExternalClock. And pxmExtClockPresent2 and pxmExtClkConnectorType2 are used with pxmExternalClock2.

OBJECT-TYPE

If pxmSecondaryMuxClockSource is pxmInbandClock1 (1) or pxmServiceModuleClock2 (5), then this entry indicates Inband Line number .

OBJECT-TYPE

If pxmSecondaryMuxClockSource is pxmServiceModuleClock1(2) or pxmServiceModuleClock2 (6), then this entry indicates SM slot number .

OBJECT-TYPE

Clock source currently selected for PXM card. If the pxmCurrentClock is primary then the pxmPrimaryMuxClockSource described further the source of the clock. If the pxmCurrentClock is secondary then the pxmSecondaryMuxClockSource described further the source of the clock.

OBJECT-TYPE

Clock source Previously selected for PXM card.

OBJECT-TYPE

Status of External T1/E1 Clock on PXM card.

OBJECT-TYPE

Impedance on external clock input for PXM card.

OBJECT-TYPE

This object describes the type of connector available for connecting the external clock source to the PXM-LM.

OBJECT-TYPE

This object describes the lowest stratum level provided by the interface the external clock source to the PXM-LM.

OBJECT-TYPE

This object gives more information about clock status (if known).

OBJECT-TYPE

Status of External T1/E1 Clock on port 2 of UI-S3 back card of PXM card.

OBJECT-TYPE

Impedance on external clock input on port 2 of UI-S3 back card of PXM card.

OBJECT-TYPE

This object describes the type of connector available for connecting the external clock source to the port 2 of UI-S3 back card of PXM-LM.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The IP address of VISM card. Each VISM card has its own IP address. IP address for each VISM card is required to communicate with the Call agent. The IP address should be configured before adding endpoints. This object is applicable if the mode is voIP or switching. From vism 2.0.3 release onwards this object can be configured in any application but will be applicable only in switching applications.

OBJECT-TYPE

SUB-NETMASK of the VISM IP interface. This object is applicable if the mode is voIP or switching. From vism 2.0.3 release onwards this object can be configured in any application but will be applicable only in switching applications.

OBJECT-TYPE

This object is used to provision the bitmask used for the TOS (Type Of Service) octet for cells carrying the control (xGCP ) traffic. Default value 96 = 0x60 => Precedence = 3 and TOS nibble = 0 The bitmask can be only a byte value.

OBJECT-TYPE

The bearer IP address of VISM card. This is an optional second IP address of the VISM card. If this bearer IP address is defined, the vismIpAddress automatically becomes the control IP address. From vism 2.0.3 release onwards this object can be configured in any application but will be applicable only in switching applications.

OBJECT-TYPE

Bearer SUB-NETMASK of the VISM IP interface. This optional bearer subnet mask must be provided when vismBearerIpAddress is provided. From vism 2.0.3 release onwards this object can be configured in any application but will be applicable only in switching applications.

OBJECT-IDENTITY

OBJECT-TYPE

This object is used to provision the bitmask used for the TOS (Type Of Service) octet for cells carrying VoIP bearer (RTP ) traffic. Default value 160 = 0xA0 => Precedence = 5 and TOS nibble = 0 The bitmask can be only a byte value.

OBJECT-TYPE

This attribute defines the RTCP report interval ( defined in RFC 1889). This indicates the interval at which the RTCP reports should be sent to the participating members. The value is expressed in units of milliseconds. The RTCP reports are not sent at a fixed rate at this interval. Rather, this value is used as a base value to arrive at a random number between 0.5 and 1.5 times this value. This interval timer also serves the purpose of RTP packets receive timer. At every 'vismRtcpRecvMultiplier' times this interval, where 'vismRtcpRecvMultiplier'is specified in the MIB object below, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval timer is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only. From vism 2.0.3 release onwards this object can be configured in any mode/adaptations, but will be applicable only in voip adaptation.

OBJECT-TYPE

This object defines whether the RTP packets receive timer on the VISM needs to be enabled or not. For some VoIP applications (as in South Carolina release), if a connection is in send-recv mode or recv-only mode, after the bearer cur-through is done, the RTP stream should be monitored for RTP packets. If there are no packets received within a time interval specified by 5 seconds, then a Gateway initiated DLCX (Delete connection) should be sent on that connection. If this object is set to enable, the RTP stream is monitored. Otherwise, it is not monitored. This value is applicable for VoIP adaptation only. From vism 2.0.3 release onwards this object can be configured in any mode/adaptations, but will be applicable only in voip adaptation.

OBJECT-TYPE

This object is used to provision the packetization period to be applied. This object is applicable for VoIP adaptation only. For VoAAL2 adaptations, the packetization period is derived from the profile table entry. For VoAAL1 adaptation, it is fixed at 5.875 ms.

OBJECT-TYPE

This attribute defines whether the DTMF (Dual Tone, Multi-Frequency) digits need to be transported to the other endpoint via NSE packets. The value in this object will be utilised when the Call Agent does not specify this.

OBJECT-TYPE

This attribute defines whether the CAS (ABCD bits) bits need to be transported to the other endpoint via NSE packets. The value in this object will be utilized when the Call Agent does not specify this.

OBJECT-TYPE

This attribute defines whether triple redundancy is enabled or not. With triple redundancy, NSEs are sent three times at 20 ms intervals. For reliable channels, triple redundancy can be disabled in order to save the bandwidth and the processing overheads. The value in this object will be utilized when the Call Agent does not specify this.

OBJECT-TYPE

This attribute defines the hangover time for VAD in milliseconds. Once the voice inactivity is detected, the gateway will wait for this duration before activating silence suppression. The value in this object will be utilized when the Call Agent does not specify this.

OBJECT-TYPE

This attribute defines whether the VISM has the capability to negotiate the list of events either NSE (Named Signal Event) or NTE (Named Telephony Events), using rtpmap and fmtpmap in the SDP. If the value is TRUE, then VISM will include / accept rtpmap and fmtpmap in the SDP. Any events NSE / NTE not listed will be interpreted as not supported. If the value is FALSE, then VISM will neither include nor accept rtpmap for X-NSE & X-NTE, and fmtpmap. For the backward compatibility sake VISM will transmit DTMF digits using NSEs if the value is FALSE

OBJECT-TYPE

This attribute sets the payload type of a RTP packet carrying SID which is sent to the other end when silence is detected. The default value is in accordance to the earlier revisions of draft-ietf-avt-provile-new-10.txt

OBJECT-TYPE

This attribute defines the inter cell gap for dual PVC OAM cells. The value represents the time in milliseconds.

OBJECT-TYPE

This attribute defines the threshold for failure of a PVC. If the number of consecutive OAM cells sent for which no ack was received equals this number then the connection is considered failed.

OBJECT-TYPE

This attribute defines the threshold for recovery of a PVC. If the number of consecutive OAM cells sent for which ack was received equals this number then the connection is considered recovered from failure.

OBJECT-TYPE

The 'vismRtcpRepInterval' MIB object specified above defines an approximate RTCP report interval (defined in RFC 1889) which indicates the interval in milliseconds at which the RTCP reports should be sent to the participating members. This MIB object, 'vismRtcpRecvMultiplier', defines how many times the RTCP reports may fail before exception condition activity may be done. At this number of times specified in this MIB object times the RTCP Report Interval, a check is made on a VoIP connection (which is in SENDRECV or RECVONLY xGCP modes) to see if any RTP packets have been received. If not, gateway-initiated DLCX should be sent to the Call Agent. Currently, this interval multiplier is a card-specific value, which means the value is configurable on a per card basis and not on a per call basis. This value is applicable for VoIP adaptation only.

OBJECT-TYPE

This object should be used for VoIP Trunking applications and only if the signalling type is configured to be CCS. By default the PRI D-channel information will be sent on the control channel. If the control network is totally seperated from the bearer network then the user needs to set this object to 'bearer' to send his Lapd trunk messages to the remote VISM.

OBJECT-TYPE

This attribute defines whether or not the VISM should advertise the event codecs, NSE (Named Signal Events), NTE (Named Telephony Events), or Cisco-rtp, in addition to the list of events specified by the call agent. If the value is none, then VISM will not include any more event codecs than what has been specified by the call agent. If the value is proprietary, then VISM can advertise proprietary event codecs in addition to the event codecs specified by the call agent. If the value is all, then VISM can advertise both proprietary as well as standard event codecs in addition to the event codecs specified by the call agent.

OBJECT-IDENTITY

OBJECT-TYPE

Echo Canceller pattern for Idle code. Mu-Law : 1 - 7f, 2 - ff, 3 - 7f or ff, 4 - f7 A-Law : 1 - None, 2 - 54, 3 - 55, 4 - Programable Idle code. DEFVAL : pattern3 (7f or ff) for Mu-law and pattern2 (54) for A-Law.

OBJECT-TYPE

Echo Canceller Idle Direction. This determines in which direction the Idle code must be present.

OBJECT-TYPE

Compressed output packet size - This value is used in the DSP interface API commands to configure the DSPs for the maximum packet size. The valid values are 80 and 160 only. NOTE: This object is not used currently. In future it is applicable only if the mode is VoAAL1. From vism 2.0.3 release onwards this object can be configured in any mode/adaptations, but will be applicable only in aal1 adaptation.

OBJECT-TYPE

This object is used to provision the return echo lost, i.e the db loss of the echo that the DSPs are supposed to cancel.

OBJECT-TYPE

This object is used to provision the jitter buffer mode to be apply to a call connection. The possible values are: fixed - means use a constant jitter buffer size, which is defined by the vismJitterInitialDelay mib variable. adaptive - means let the DSP pick the optimal value for the call connection.

OBJECT-TYPE

Defines the jitter buffer size. If the vismJitterDelayMode is set to be fixed, the jitter buffer is fixed at this value for the call. If vismJitterDelayMode is adaptive, this is the initial jitter buffer size, and the DSP will adapt to an optimal size. The range 10,20,30,40,50,60,70,80,90,100 is applicable to 1.5 release only. The range 1,5,10,15,20,25,30,35 .... is applicable from vism2.0 release onwards. The valid range for template 1 : 1,10,20,30,40,50,60,70,80,90,100 The valid range for template 2 : 1,5,10,15,20,25,30,35,40,45,50, 55,60,65,70,75,80,85,90,95,100. When the template of the card changes, either from template 1 to 2 or vice versa the value of this object will be implicitly set to default value.

OBJECT-TYPE

If set to on, the DSP will adjust the gain of the of the call connection to an optimal value.

OBJECT-TYPE

This attribute indicates the health of the DSPs. It is a percentage of the total number of DSPs that are currently functional. Currently No action is planned upon the failure of a DSP chip in a card, other than resetting the card.

OBJECT-TYPE

This object specifies the codec to be used when fax upspeed happens. The default value for this object is G.711u when the line type is T1 and G.711a when the line type is E1 This object is applicable only in the case of VOIP applications, for AAL2 the upspeedCodec is obtained from profile table and this object will have no affect.

OBJECT-TYPE

This object specifies the payload type to be used when fax upspeed happens. IANA values (0..95) are static payload and (96..127) are dynamic payload type. This object is applicable only in the case of VOIP applications, for AAL2 the upspeedCodec is obtained from profile table and this object will have no affect.

OBJECT-IDENTITY

OBJECT-TYPE

A unique value for each VISM daughter card, entered in nvram by manf. The serial No. is on the non-volatile RAM on the VISM daughter card.

OBJECT-TYPE

Describes the VISM daughter card.

OBJECT-TYPE

Hardware revision number for the daughter card.

OBJECT-TYPE

Voice encoding type, Mu-law or A-law. mu-law is returned for T1 lines and a-law is returned for E1 lines.

OBJECT-TYPE

This attribute defines the connection model that the VISM card is configured to operate with. This object can be modified by CLI only. The CLI 'cnfvismmode' can be used to set this object. VISM card will be reset after modifying this parameter for the VISM card to come up in the new mode. Each mode enables a set of features on the VISM card. The feature set for each of the above modes is : voipSwitching - VoIP mode. In this mode VISM interacts with the Call Agent using XGCP protocol, bearer path is VoIP (AAL5). This mode is also used for VoIP applications that dosen't use call agent. (VoIP Trunking) aal2Trunking - AAL2 Trunking mode. In this mode VISM does not interact with the Call Agent. Bearer Path is AAL2. aal1Svc - AAL1 SVC mode. In this mode VISM interacts with Call Agent using XGCP protocol over AAL5 control PVCs. In this mode, bearer path is VoAAL1 and the bearer connections are SVCs. i.e VISM dynamically sets-up and tears down bearer connections. This value is applicable in VISM2.0 and onwards. switchedVoipCASBh, switchedVoipPRIBh, switchedAal2CASBh, switchedAal2Svc and superMode are ignored. switchedAal2Pvc - Switched and trunked AAL2 PVC with CAS xGCP backhaul, CCS and CAS forwarding. switchedAal2Svc - Switched AAL2 SVC with PRI backhaul. voipAndAal1Svc - VoIP and ATM Groomer. unknowMode - Unknown mode, when user change vismFeatureBitMap to a combination of Features that are not in the above modes. This object has to be synchronized with vismFeatureBitMap. When vismFeatureBitMag is changed this object will be implictly set to the mode that has the right combination of features. From Indiana release and onwards, when user change mode VISM card is not reset and the configuration is not cleared.

OBJECT-TYPE

This attribute indicates the mode in which VISM was operating before the vismMode value was changed. i.e It gives the value of vismMode before it got changed to the current value. When the card comes up in the default mode, the value of vismPrevMode will be the same as vismMode. From Indiana release and onwards, when user change mode VISM card is not reset and the configuration is not cleared. Therefore we don't need this object anymore.

OBJECT-TYPE

This attribute describes whether CAC (Connection Admission Control) functionality needs to be applied on the VISM card, on a per PVC basis. For some applications, the CAC functionality may not be required and in that case, it has to be disabled on a card basis.

OBJECT-TYPE

This attribute describes the no. of DS0s available for new connections on VISM. This is modified by the VISM firmware after each connection is setup. In indiana release the number of connections has been increased to 248, as the number of endpoints supported has been increased.

OBJECT-TYPE

This attribute describes the Codec template currently configured on the VISM card. The value refers to an index to the vismCodecTemplate table. This template is applicable for all connections on the card. When a switch is made to a new template, the number of channels (endpoints) in use will be checked to ensure the switch will not occur if there are more endpoints active at the present time than what the new template (vismCodecTemplateMaxChanCount) allows. Also whenever an attempt is made to add a new endpoint for any template, this template maximum number will limit the number of endpoints that may be added for this template.

OBJECT-TYPE

This object holds the domain name of the tftp server from where the cas module will download the cas files. This domain name can be resolved internally or externally. Before configuring this object the domain name should be added in the mgDomainNameTable and at least one Ip address (internal or external) should be associated with this domain name in mgcResolutionTable. By default, the object is set to TFTPDOMAIN. Before the last entry corresponding to the tftp domain is deleted from the mgDomainNameTable or the last Ip address associated with this object is deleted from mgcResolutionTable, it should be set to 'TFTPDOMAIN'. If the user configures 'localhost' to be the tftp server domain then the cas files will be downloaded from PXM. If the user configures the domain name to be TFTPDOMIAN or localhost then that entry need not be present in mgDomainNameTable or mgcResolutionTable.

OBJECT-TYPE

This object specifies the network type to use in order to transport bearer traffic. The user can configure this to IP or ATM based on where the VISM will be located. If the call agent specifies the network type in the MGCP local connection options (CRCX request), then the configuration of this object will have no effect, else the value of this object will be used when sending CRCX response. This object is applicable only from vism 2.0.3 release onwards.

OBJECT-TYPE

This object specifies the vc type to use in order to transport bearer traffic. If the call agent specifies the VC type in the MGCP local connection options (CRCX request), then the configuration of this object will have no effect, else the value of this object will be used when sending CRCX response. This object is applicable only from vism 2.0.3 release onwards.

OBJECT-TYPE

This object specifies the connection type used to transport bearer traffic. If the BearerNetworkType is chosen to be IP then the value of this object has to be/will be set to not-applicable. If the call agent specifies the connection type in the MGCP local connection options (CRCX request), then the configuration of this object will have no effect, else the value of this object will be used when sending CRCX response. This object is applicable only from vism2.0.3 release onwards.

OBJECT-TYPE

This object specifies the co4 (bearer continuity) timer in millisecs. The timer will be started in the terminating/orginating gateway for a duration as specified in this MIB object when a co3 message is sent from the terminating/orginating gateway to the originating/terminating gateway. If the terminating/originating gateway does not receive co4 as an acknowledgement from the originating/termintaing gateway and the timer expires, gateway initiated DLCX is sent to the call agent from the terminating/originating gateway. This object is applicable when the call agent feature is available.

OBJECT-TYPE

This object helps in forming an ordered intersection of lists and one of the lists must be used in determining the resulting order of codecs. Lco - local connection options Rcd - remote connection description Lcl - local codec list If the value of this object is 1 then effectively we are giving first priority to the local connection options sent by the Call Agent, followed by remote connection description sent by the remote gateway (CA) and the last priority will be to local codec list stored in vism. If the value of this object is 2 then effectively we are giving first priority to local connection options sent by the call agent, followed by local codec list stored in vism and the last priority will be to remote connection description sent by the remote gateway (or remote CA). If the value of this object is 3 then effectively we are giving first priority to remote connection description sent by the remote gateway /call agent, followed by local connection options sent by the call agent and the last priority will be to the local codec list stored on the local gateway(vism). If the value of this object is 4 then effectively we are giving first priority to remote connection description sent by the remote gateway/CA followed by local codec list stored on the local gateway and the last priority will be to the local connection options sent by the CA. If the value of this object is 5 then effectively we are giving first priority to local codec list stored on the local gateway (vism) followed by local connection options sent by the call agent and the last priority will be to remote connection description sent by the remote gateway (or remote CA). If the value of this object is 6 then effectively we are giving first priority to local codec list stored on the vism followed by remote connection description sent by the remote gateway (or remote CA) and the last priority will be to local connection options sent by the call agent.

OBJECT-TYPE

This object helps in forming an ordered intersection of lists and one of the lists must be used in determining the resulting order of profiles. Lco - local connection options Rcd - remote connection description Lcl - local codec list If the value of this object is 1 then effectively we are giving first priority to the local connection options sent by the Call Agent, followed by remote connection description sent by the remote gateway (CA) and the last priority will be to local codec list stored in vism. If the value of this object is 2 then effectively we are giving first priority to local connection options sent by the call agent, followed by local codec list stored in vism and the last priority will be to remote connection description sent by the remote gateway (or remote CA). If the value of this object is 3 then effectively we are giving first priority to remote connection description sent by the remote gateway /call agent, followed by local connection options sent by the call agent and the last priority will be to the local codec list stored on the local gateway(vism). If the value of this object is 4 then effectively we are giving first priority to remote connection description sent by the remote gateway/CA followed by local codec list stored on the local gateway and the last priority will be to the local connection options sent by the CA. If the value of this object is 5 then effectively we are giving first priority to local codec list stored on the local gateway (vism) followed by local connection options sent by the call agent and the last priority will be to remote connection description sent by the remote gateway (or remote CA). If the value of this object is 6 then effectively we are giving first priority to local codec list stored on the vism followed by remote connection description sent by the remote gateway (or remote CA) and the last priority will be to local connection options sent by the call agent.

OBJECT-TYPE

This object defines the policy that needs to be applied when a carrier loss is detected. This states whether to switch to the pre-upspeed codec or to remain with the upspeed codec. This object is applicable in case of SVCs. This object will be applicable in case of PVC if the per PVC object - vismChanCarrierLossPolicy (defined in vismChanCacTable) is set to 'unspecified'. Configuring this object will not have any affect when card level cac is disabled (vismCacEnable).

OBJECT-TYPE

This attribute defines the policy that needs to be applied once the CAC function rejects the upspeeding of a connection, due to a fax/modem switch-over request. The applicable options are: 1 - To delete the connection that got rejected by CAC for upspeed 2 - To maintain the connection with the prior compression scheme. This object is applicable in case of SVCs . This object will be applicable in case of PVCs if the per PVC object - vismChanCacRejectionPolicy (defined in vismChanCacTable) is set to 'unspecified'. Configuring this object will not have any affect when card level cac is disabled (vismCacEnable).

OBJECT-TYPE

This object refers to the domain name of the external DNS server which will be used to resolve other domain name. Currently this domain name can only be resolved internally. Therefore, before configuring this object not only the domain name has to be added in the mgDomainNameTable with resolution type 'internalOnly' but also at least one IP address has been added with this domain name in mgcResolutionTable. Before deleting external DNS server from mgDomainNameTable or deleting the last IP address associated with the external DNS server this object should be set to 'NULL'. After we change the value of this object to NULL, all the externally resolved IP address in mgcResolutionTable will be purged. By default this object will be set to 'NULL'.

OBJECT-TYPE

This object denotes the bit map for VISM features. It indicates the current features that are enabled. It should be consistant with vismMode. When user change vismMode, this object is implicitly set to the feature combination that inidicate to that mode. The change of vismFeatureBitMap will not cause VISM to reset and the configuration will not be cleared. For each bit, value 1 means the feature is enabled, 0 means disabled. Bit 0 - AAL1 adaptation Bit 1 - AAL2 adaptation Bit 2 - AAL5 adaptation (Bearer network type is IP). Bit 3 - Switching (with Call Agent) Bit 4 - Trunking (without Call Agent) Bit 5 - Bearer VC type is PVC. Bit 6 - Bearer VC type is SVC. Bit 7 - CAS signaling Bit 8 - PRI backhaul Bit 9 - CCS signaling Bit 10 - Domain Name For example, 0x5AC corresponds to vismMode 1 (VoipSwitching). Currently this object is not settable, it can only be set thru some debug commands.

OBJECT-TYPE

The value in this object refers to the customer accepted drop rate for voice connections when the bandwidth usage exceeds allowed value. The actual range of this object is 0.0001% - 1.00 % The unit is in percentage, since the default is 0.01 %, and since we cannot express such fractions in MIB , it is being multiplied by 10000 . However, when the underlying CAC module is notified of the change in this object, then the value has to be divided by a factor of 10000. Multiplication factor 10000 is picked as someone might be interested in a tolerance as low as 0.0001%. This object will be applicable in case of aal2 SVCs where the user does not add a PVC and also this object will be applicable if the per PVC level object (vismChanVADTolerance) is configured to have a value of zero. Configuring this object will not have any affect when card level cac is disabled (vismCacEnable).

OBJECT-TYPE

This object refers to the talk-spurts duty cycle. The unit is in percentage. When the value of this object is to be passed to underlying CAC module in VISM this value has to be divided by 100. This causes the actual range of this object to be 0.01 to 0.99 and not 0.01 to 1.00 as specified in the range of values above. Since a value of 100 will cause a floating point exception, this value is disallowed. The default value is 0.61 and since we cannot have fractions in a MIB variable the value is being multiplied by 100 and is expressed as 61. This object will be applicable in case of aal2 SVCs where the user does not add a PVC and also this object will be applicable if the per PVC level object (vismChanVADDutyCycle) is configured to have a value of zero. Configuring this object will not have any affect when card level cac is disabled (vismCacEnable).

OBJECT-TYPE

This attribute defines the aggregate traffic clipping policy which is applicable to all bearer traffic generated at VISM card. The applicable options are: 1 - aggregate traffic clipping is disabled, VISM card traffic management does not perform aggregate traffic clipping. 2 - aggregate traffic clipping is enabled, VISM card traffic management performs aggregate traffic clipping. This is applicable to only AAL2 SVC voice bearer traffic. When aggregate traffic clipping is enabled, VISM card can discard cells which are exceeding VISM card aggregate SVC bandwidth which is specified as vismAggregateSvcBandwidth value.

OBJECT-TYPE

The aggregate svc bandwidth is used for AAL2 SVC aggregate SVC Connection Admision Control and also used for aggregate traffic clipping at VISM card when vismAggregateTrafficClipping is enabled. This is expressed in cells per second. This need to be configured for AAL2 SVC aggregate bandwidth call admision control to admit AAL2 SVC connections at VISM card.

OBJECT-TYPE

This attribute defines whether the bearer continuity test for a connection will be performed at the time of call setup or not. When the vismBearerContinuityTest is enabled, the terminating media Gateway initiates a NSE/type 3 packet towards the originating gateway and starts a timer defined by vismBearerContinuityTimer. The originating gateway, on receipt of co3, responds by sending a co4 to the terminating end. If the terminating gateway doesn't receive co4 NSE/type 3 packet with in the time defined by co4 timer, it initiates a GW-initiated DLCX to the call agent which in turn deletes the connection. The value in this object will be utilised when the Call Agent does not specify this.

OBJECT-TYPE

This attribute describes whether CALEA (Communication Assistance for Law Enforcement Agency)) functionality needs to be enabled on the VISM card. This attribute enables/disables this feature at a card level. This command is only applicable for CALEA enable image.

OBJECT-IDENTITY

OBJECT-TYPE

Configuration change Type BitMap used in vismTableChanged trap and vismScalarChanged trap. When used in vismTableChanged trap, the bits indicate the following: bit 0 set = mgcTable changed bit 1 set = mgEndpointTable changed bit 2 set = mgcResolutionTable changed bit 3 set = srcpPeerTable changed bit 4 set = vismDsx1Table changed bit 5 set = vismXgcpPeerTable changed bit 6 set = xgcpPackageTable changed bit 7 set = vismChanCacTable changed bit 8 set = vismCasVariantTable changed bit 9 set = vismCasXgcpVariantTable changed bit 10 set = vismAal2CidCnfTable changed bit 11 set = dsx0VismCnfTable changed bit 12 set = vismHdlcChanCnfTable changed bit 13 set = lineAssignmentTable changed bit 14 set = vismCodecCnfTable changed bit 15 set = vismLapdTable changed bit 16 set = vismRudpSessionCnfTable changed bit 17 set = aal2ProfilesGrpTable changed bit 18 set = mgDomainNameTable changed bit 19 set = vismPortCnfGrpTable changed bit 20 set = mgcRedundancyGrpTable changed bit 21 set = mgcRedundancyGrpParamTable changed bit 22 set = srcpPeerGrpParamTable changed bit 23 set = vismRtpConnGrpTable changed bit 24 set = vismCodecGenParmTable changed bit 25 set = t38FaxRelayGrpTable changed bit 26 set = mgcRedundancyProtocolTable changed bit 27 set = vismSessionSetTable changed bit 28 set = vismSessionGrpTable changed When used in vismScalarChanged trap, the bits indicate the following: bit 0 set = mediaGateway group changed bit 1 set = mediaGatewayEndpoint group changed bit 2 set = mediaGatewayControllerResolution group changed bit 3 set = srcpAdminObjects group changed bit 4 set = vismConfig group changed bit 5 set = vismXgcpCoreObjects group changed bit 6 set = xgcpCoreObjects group changed bit 7 set = xgcpExtensionObjects group changed bit 8 set = xgcpPackageObjects group changed bit 9 set = vismSvcAtmQosGrp Objects group changed bit 10 set = vismSvcTrfScalingGrp Objects group changed bit 11 set = vismSvcAal2CidGrp Objects group changed bit 12 set = srcpAdminRetryObjects Objects group changed bit 13 set = vismConfig IpGrp group objects changed bit 14 set = vismConfig VoipGrp group objects changed bit 15 set = vismConfig DspGrp group objects changed bit 16 set = vismConfig SystemGrp group objects changed bit 17 set = vismConfig Aal2Grp group objects changed bit 18 set = vismConfig InteropGrp group objects changed bit 19 set = announceControlGrp Objects group changed bit 20 set = vismXgcpEnhancementsObjects group changed default value is 0, no change This MIB makes sense only in traps. A GET on this may not return a Useful result.

OBJECT-TYPE

This object is used only for the purpose of sending it in the trap varbind. This object is used for two purposes: 1. When the integer index of a SMIv2 table has to be sent, this object will be used instead of the actual index object. The instance value of the object will be the instance value of the actual index. 2. In the config change trap trapVismTableChange, to send the index value of the table entry which got changed. This object will contain the value of the first integer index. The NMS applications should not depend on the implementation of this object. The SNMP Requests(GET,GET-NEXT) may not be valid for this object.

OBJECT-TYPE

This object is used only for the purpose of sending it in the trap varbind. This object is used for two purposes: 1. This object will be used when the SMIv2 table has two index objects and the 2nd object is an integer. This object will be used instead of the actual second index object. The instance value of the object will be the instance value of the actual second index. 2. In the config change trap trapVismTableChange, to send the index value of the table entry which got changed. This object will contain the value of the second integer index. The NMS applications should not depend on the implementation of this object. The SNMP Requests(GET,GET-NEXT) may not be valid for this object.

OBJECT-TYPE

This object is used only for the purpose of sending it in the trap varbind. This object is used for two purposes: 1. When the OctetString index of a SMIv2 table has to be sent, this object will be used instead of the actual index object. The instance value of the object will be the instance value of the actual index. 2. In the config change trap trapVismTableChange, to send the index value of the table entry which got changed. This object will contain the value of the first OctetString index. The NMS applications should not depend on the implementation of this object. The SNMP Requests(GET,GET-NEXT) may not be valid for this object.

OBJECT-IDENTITY

OBJECT-TYPE

This object is a card level parameter for AAL2 adaptation and it identifies the mutiplexing function of the AAL2 Common Part Sublayer. When it is disabled then each CPS-Packet would fill only one or two cells with padding. (Partial fill cells) Note that the length field for each CPS-Packet can be up to 64bytes. When this option is enabled then mutiple streams of CPS-Packets are mutiplexed to a single ATM connection without partial fill unless there is time-out. Refer to ITU-T I.363.2 for more information. When the muxing type changes if cids are present, then we need to check for CAC voilation for all cids, if the CAC fails then the change request will be rejected else the muxing status will be changed and the vismAal2MuxingTrap will be sent and the card will be reset . All the existing connecitons will come up in new muxing type. when the muxing type changes while there are no cids then the card will NOT be reset, but the vismAal2MuxingTrap will be sent.

OBJECT-TYPE

This attribute defines whether the DTMF (Dual Tone Multi Frequency) digits need to be transported to the other end-point or not. The value in this object will be utilised when the Call Agent does not specify this in CRCX.

OBJECT-TYPE

This attribute defines whether the CAS (ABCD bits) bits need to be transported to the other endpoint. In the case of switching application, the CAS bits are backhauled to the Call Agent through xGCP-CAS protocol. The value in this object will be utilised when the Call Agent does not specify this in CRCX.

OBJECT-TYPE

This attribute defines whether the triple redundancy is supported for type 3 packets in AAL2 SVC/PVC . When Triple redundancy is enabled , the type 3 packets (CAS bits, dialled digits and user state control packets) are transmitted in triplicates with an interval defined as per the standards I.366.2. For channels which are quite reliable, triple redundancy can be disabled in order to save the bandwidth and the processing overheads. The value in this object will be utilised when the Call Agent does not specify this in CRCX.

OBJECT-TYPE

This attribute defines the hangover time for VAD in milliseconds. Once the voice inactivity is detected, the gateway will wait for this duration before activating silence suppression on an AAL2 SVC/PVC. The value in this object will be utilised when the Call Agent does not specify this in CRCX.

OBJECT-TYPE

This attribute defines the time (millisecs) to wait for filling up the cell when the next packet is not ready. After waiting for the time configured in this object, the cell will be sent out. This timer has no effect when vismAal2SubcellMuxing is disabled. This object is applicable only for aal2 adaptations.

OBJECT-IDENTITY

OBJECT-TYPE

This object is used to enable/disable building of s=,t=,o= lines in SDP message. If this object is set to 'enable' then it indicates that the o=, s=, t= lines be built before sending SDP (Session Description Protocol), if it set to 'disable' then it indicates that the o=,s=,t= parameters need not be built for SDP. where o field indicates the owner/creator and session identifier s field indicates the session name t field indicates the duration while a session is valid.

OBJECT-TYPE

This object is used to enable / disable dynamic payload type configuration on the VISM Card.

OBJECT-IDENTITY

OBJECT-TYPE

Object indicating whether RAS- OAM loopback test is enabled or disabled for this card.

OBJECT-TYPE

Object indicating the frequency in minutes in which RAS task sends one OAM loopback cell per idle connection.

OBJECT-IDENTITY

OBJECT-TYPE

Each trap will send status for 256 channels bitmapping the status. This object identities the chunk of 256 channels. The channel numbers for which the trap indicates the status is found as chanPacketNumber * 256 + bitoffset + 16. This object cannot be set or read.

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 16 to chanPacketNumber * 256 + 47 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 48 to chanPacketNumber * 256 + 79 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 80 to chanPacketNumber * 256 + 111 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 112 to chanPacketNumber * 256 + 143 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 144 to chanPacketNumber * 256 + 175 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 176 to chanPacketNumber * 256 + 207 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 208 to chanPacketNumber * 256 + 239 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-TYPE

Bit map indicating Ras_oam_lpbk test state of 32 channels from chanPacketNumber * 256 + 240 to chanPacketNumber * 256 + 271 MSB represent lower channel and LSB represent higher channel 0 in bit position indicate lpbk test ok 1 in bit position indicate lpbk test failed This object cannot be set or read

OBJECT-IDENTITY

OBJECT-TYPE

A SwitchCC command either to invoke switchcc or take noAction on the Core Card Set

OBJECT-IDENTITY

OBJECT-TYPE

This object allows the user to enable/disable the IMA group auto-restart feature on IMA capable cards. The effect of this object is card-wide. A value of 1 disables the feature. A value of 2 enables the feature.

OBJECT-IDENTITY

OBJECT-TYPE

The SRME configuration table for bulk distribution of SRME lines.

OBJECT-TYPE

an entry in the SRME Distribution configuration table

OBJECT-TYPE

Select SRME line number. For OC3/STM1: SYNTAX INTEGER 1 There is no default value for this object.

OBJECT-TYPE

The start T1 or E1 number (virtual tributary) to be affected. For OC3 with T1 tributaries: SYNTAX INTEGER (1 .. 84) For STM1 with E1 tributaries: SYNTAX INTEGER (1 .. 63) There is no default value for this object.

OBJECT-TYPE

Command used to add, delete, or modify one or more T1 or E1 mappings. Only the srmeVtFramingType object can be modified once the distribution link is added. To modify all other objects, user should first delete the link and add it again. Default value is modify.

OBJECT-TYPE

specify the target slot number to be linked. There is no default value for this object. For MGX8x50: SRM01 services slots 1 - 6 and 9 - 14, SRM02 services slots 17 - 22 and 25 - 30 For MGX8x30: service slots 3-6 and 10-13

OBJECT-TYPE

Specify the target slot's line to be linked. 0 means not assigned. There is no default value for this object.

OBJECT-TYPE

Specifies the Framing Type of the target slot line. This is applicable only if the target module is a T1 Service Module and byte sync mapping is used on SRME. Not applicable to E1 Service Modules. sf: Superframe or D4 esf: Extended Superframe. Default is esf if SRME lines are configured for byte-synchronous mapping. Else, the default is notApplicable.

OBJECT-IDENTITY

OBJECT-TYPE

This table represents Physical serial interfaces on the module

OBJECT-TYPE

An entry for the serial interface

OBJECT-TYPE

serial interface number port 1. is always defined as debug port port 2. on BSC can perform SLIP.

OBJECT-TYPE

On the BSC board IP stack is mounted on the manager port, on the debug port dumb terminal can be connected function of the ports cannot be changed, except for enabling and disabling

OBJECT-TYPE

ports can be enabled or diabled

OBJECT-TYPE

baud rate of the ports, each port can be config different

OBJECT-TYPE

Number of rows in serialPortTable. This number is equal to the number of serial ports on the module.

OBJECT-IDENTITY

OBJECT-TYPE

ethernet address stored in the BSC BRAM, entered by manfacturing.

OBJECT-IDENTITY

OBJECT-TYPE

The X21 Configuration table. The table size is given by the value of x21LineNumofValidEntries

OBJECT-TYPE

An entry in the X21 Configuration table.

OBJECT-TYPE

This object is the identifier of a X.21 interface. No defaults. FRSM-HS2/HS2B-HSSI supports a range from 1 to 2 FRSM-HS2B-12IN1 supports a range from 1 to 8

OBJECT-TYPE

This variable disables, enables or modifies a line 1 - disable 2 - enable 3 - modify Default is enable.

OBJECT-TYPE

This variable indicates the type X21 line type. The line-type affects the clock -- the DCE device always provides the clock and DTE accepts it. dteST is only applicable to V.35 interfaces Default is DTE.

OBJECT-TYPE

This variable configures the X.21/HSSI/V.35 line-rate. Note that enumerations 51 through 108 are supported only by FRSM-HS2/HS2B card. default is r48Kbps on FRSM-HS2B-12IN1 default is r52Mbps on FRSM-HS2/HS2B-HSSI

OBJECT-TYPE

This variable represents the loopback state x21NoLoop Not in the loopback state. Normal traffic can be sent x21DiagnosticMetallicLoop Loopbacks the line on the back-card towards the Network. x21DiagnosticFrontcardLoop Loopbacks the line on the frontcard toward the Network. x21RemoteLoop The remote NTU is in the loop back mode. In this state, the FRSM-HS1 is sending the loopback code to remote NTU. Default is x21NoLoop. Note: Before going into one of the loopbacks the state should be x21NoLoop.

OBJECT-TYPE

This variable indicates what type of code is being sent across the X.21/HSSI interface by the device. The values mean: x21NoCode: No loopback. x21SendLoopACode: Start sending Loop A code. Valid only if the backcard is HSSI and the line-type is DTE. This command loops the line module of the remote device. x21SendLoopBCode: Start sending Loop B code. Valid only if the backcard is HSSI and the line-type is DTE. This command loops the digital section of the remote device. x21SendLocalLoopCode: Start sending CCITT X.21 Loopback Type 3 code. This is valid only if the backcard is X.21 type. x21SendRemoteLoopCode: Start sending CCITT X.21 Loopback Type 2 code. This is valid only if the backcard is X.21 type. x21SendUnLoopCode: Sending a loopback termination request. Valid for both HSSI and X.21 lines. To execute any of the loop-codes the x21LineLoopbackCommand should be set to x21RemoteLoop. Once the x21SendUnLoopCode succeeds the x21LineLoopbackCommand would transition back to x21NoLoop state. Default is x21NoCode.

OBJECT-TYPE

Enable detection of line Loopback Codes. In the current release, the loopback detection is implemented only in HSSI DCE mode. Default is codeDetectDisabled.

OBJECT-TYPE

back card type This object is not used by FRSM-HS2/HS2B

OBJECT-TYPE

This object configures two options: a) To invert the clock sent by HS1/HS2B with the TX data or not. b) If DCE,to expect the receive clock looped back from DTE or not. If DTE,to loop back the receive clock from DCE or not. nonInvertedAndNotLooped(1)- a)=dont invert, b)=dont expect rcv clock/ dont loop rcv clock invertedAndNotLooped(2) - a)=invert, b)=dont expect rcv clock/ dont loop rcv clock nonInvertedAndLooped(3) - a)=dont invert, b)=expect rcv clock/ loop rcv clock invertedAndLooped(4) - a)=invert, b)=expect rcv clock/ loop rcv clock Enums 1 and 2 are applicable for X.21/HSSI/V.35 interfaces. Enums 3 and 4 are applicable only for V.35. Default for X.21/HSSI is nonInvertedAndNotLooped(1) Default for V.35 is nonInvertedAndLooped(3) This object is not used by FRSM-HS2/FRSM-HS2B-HSSI This object is used by FRSM-HS2B-12IN1 and default values are nonInvertedAndNotLooped(1) for X.21, nonInvertedAndLooped(3) for V.35

OBJECT-TYPE

This object indicates serial interface type. Default is hssi. This object is not is configurable in FRSM-HS2 and FRSM-HS2B-HSSI. It will be set hssi by default for these cards This object is configurable in FRSM-H2B-12IN1. Default is v35

OBJECT-TYPE

This object indicates user configurable percentage of clock frequency, which is used by DTE clock monitoring to declare clock rate out of bound alarm. This object is valid only for X.21/v.35/HSSI DTE interfaces. This object is supported by FRSM-HS2 and FRSM-HS2/B

OBJECT-TYPE

line rate for X.21/HSSI/V.35 interfaces in bps. This object is supported only by FRSM-HS2/B card, only multiples of 1000 are accepted. Default is 48Kbps for X.21/V.35 interfaces and 51840Kbps for HSSI interface

OBJECT-TYPE

This object indicates line rate variation of HSSI/X.21/V.35 DCE interfaces in ppm (parts per million). i.e. clock generated from DCE hardware interface = (serialLineRate +/- (serialLineRateVariation * 10^6)/ serialLineRate) This object is supported only by FRSM-HS2/B card

OBJECT-TYPE

The number of X.21/HSSI configuration entries (regardless of their current configuration) in the x21ConfigTable table.

OBJECT-IDENTITY

OBJECT-TYPE

The FRSM-HS1/HS2 interface alarm configuration table.

OBJECT-TYPE

An entry in the X.21/HSSI Alarm Configuration table

OBJECT-TYPE

X.21/HSSI line number. No defaults. FRSM-HS2/HS2B-HSSI supports a range from 1 to 2 FRSM-HS2B-12IN1 supports a range from 1 to 8

OBJECT-TYPE

This variable is used to setup the severity of LOS or clock mismatch alarm. Whenever the above condition arises, the FRSM-HS1/HS2/HS2B will send the alarm with appropriate status.

OBJECT-IDENTITY

OBJECT-TYPE

The X.21/HSSI interface alarm configuration table. The size of table is given by the value of x21LineNum

OBJECT-TYPE

An entry in the X21 Alarm table

OBJECT-TYPE

This object is the identifier (line number) of a X.21/HSSI interface. FRSM-HS2/HS2B-HSSI supports a range from 1 to 2 FRSM-HS2B-12IN1 supports a range from 1 to 8

OBJECT-TYPE

This variable is a bitmap of the X21 Line ALarms on the FRSM-HS1. A value of zero indicates no alarms. Itemized below are the individual bits: BitPosition Alarm ----------- ----- 0 C/I signal is OFF (also used to indicate LOS) 1 Clock rate mismatch (used in DTE mode) 2 Internal Loopback (diagnostic loopback) 3 HSSI Local LoopA (line is in loopback) 4 HSSI Local LoopB (line is in loopback) 5 Remote Loopback (line is transmitting loopcodes) 6 For V35 DTE mode, DCD and CTS both are inactive 7 For V35 DCE mode, RTS is inactive 8 No cable attached to V35 backcard 9 Wrong cable attached to V35 backcard If all the bit-states are 0s: - line is not in alarm, or - line not in loopback, or - line is transmitting any loopback codes.

OBJECT-TYPE

Indicates the status of X.21/HSSI lines: 0x01 -- c-lead high 0x02 -- i-lead high 0x04 -- LC-lead high (valid only for HSSI DCE mode).

OBJECT-TYPE

This variable is used to clear all the alarms for the line. 1 = No action 2 = Clear alarm

OBJECT-TYPE

The entries in this table are created and deleted implicitly at the time of adding and deleting the line. For every DS0 on a line, one row will be created.

OBJECT-TYPE

This ds0 table contains both cas related and non cas related parameters. The non cas related parameters are applicable accross all line signaling types, while the following cas related parameters are applicable only if the signaling type of the line to which this ds0 belongs is cas. ds0IdleCode ds0SeizedCode ds0ReceivedCode ds0CasVariantName ds0CasCadenceOnTime ds0CasCadenceOffTime ds0InsertLocalCas ds0LocalCasPattern ds0CasParameterSource ds0CasOnHookMinMakeTime ds0CasOffHookMinMakeTime ds0CasWinkMinMakeTime ds0CasWinkMaxMakeTime ds0CasWinkBreakTime ds0CasGlareTime ds0CasGaurdTime ds0CasDelayImmedStart ds0CasMinDelayDialTime ds0CasMinStartDialTime ds0CasFlashMinMakeTime ds0CasFlashMaxMakeTime ds0CasDirectionality ds0CasGlarePolicy ds0CasIncomingMgcpPackage ds0CasOutgoingMgcpPackage When the line signaling type changes from cas to non-cas and vice versa, then the user will be forced to delete endpoint/ccs channels associated with any ds0 on that line When an endpoint is deleted the ds0CasVariantName associated with that endpoint will also be implicitly deleted. Other than that none of the above cas related parameters are modified across line signaling type changes.

OBJECT-TYPE

This attribute defines the index for this table. This is derived from the following formula: index = 31 * (Ds1# - 1) + ds0# where : Ds1# - The T1/E1 line number in the range 1 - 8. ds0# - The ds0 channel number ranging from 1 to 24 for T1 and 1 to 31 for E1.

OBJECT-TYPE

This object indicates if Robbed Bit Signalling is turned on or off for a given ds0. This only applies to DS0s on a DS1 link. For E1 links the value is always off (false). For T1 links, the default value is true if the line is configured for CAS signaling, the default value is false if the line is configured for CCS signaling or no signaling.

OBJECT-TYPE

This object contains the code transmitted in the ABCD bits when the ds0 is not connected and ds0TransmitCodesEnable is enabled. The object is a bitmap and the various bit positions are: Bit 0 (value 1) D bit Bit 1 (value 2) C bit Bit 2 (value 4) B bit Bit 3 (value 8) A bit This object is useful for ds0 conditioning to be done if an alarm condition is detected from the network side. DS0 conditioning is implemented in the trunking application only. This object is not applicable in the CAS backhaul application. From vism 2.0.3 release onwards this object can be configured in any mode, but will be applicable only in trunking application and will be ignored in other applications.

OBJECT-TYPE

This object contains the code transmitted in the ABCD bits when the ds0 is connected and ds0TransmitCodesEnable is enabled. The object is a bitmap and the various bit positions are: Bit 0 (value 1) D bit Bit 1 (value 2) C bit Bit 2 (value 4) B bit Bit 3 (value 8) A bit This object is useful for ds0 conditioning to be done if an alarm condition is detected from the network side. DS0 conditioning is implemented in the trunking application only. This object is not applicable in the CAS backhaul application. From vism 2.0.3 release onwards this object can be configured in any mode, but will be applicable only in trunking application and will be ignored in other applications.

OBJECT-TYPE

This object contains the code being received in the ABCD bits. The object is a bitmap and the various bit positions are: Bit 0 (value 1) D bit Bit 1 (value 2) C bit Bit 2 (value 4) B bit Bit 3 (value 8) A bit

OBJECT-TYPE

This object determines if the idle and seized codes are transmitted. If the value of this object is true then the codes are transmitted. This object is not applicable in the CAS backhaul application.

OBJECT-TYPE

This object indicates endpoint number as specified by mgEndpointNumber of endpoint table. If it is not associated with any endpoint, then it is set to -1. It should be noted that the endpoint is associated with bearer DS0s only. For signaling channel or DS0 as in the case of CCS channel, there is no endpoint number associated with it and the value is set to -1.

OBJECT-TYPE

This object indicates the interface type associated with the ds0. ds0 ifType is considered as bearer if it the DS0 is used for carrying voice traffic. ds0 ifType is considered as ccs-signaling, if the DS0 is configured as the D-channel

OBJECT-TYPE

This object indicates the index to the CAS variant table. This parameter can be configured after configuring this ds0 as an endpoint. This object cannot be modified while connections exist on this endpoint. The CAS variant table is used for configuring the system parameters associated with various types of CAS signaling methods supported on VISM.

OBJECT-TYPE

This attribute describes the duration during which the digit tone is generated. This object is applicable only for CAS backhaul applications. For trunking application it is not applicable. The value is expresssed in units of milliseconds. From vism2.0.3 release onwards this object can configured in any application, but will be applicable only in non-trunking applications and will be ignored in other applications.

OBJECT-TYPE

This attribute corresponds to the silence between the digit tones. This object is applicable only for CAS backhaul applications. For trunking application it is not applicable. The value is expresssed in units of milliseconds. From vism2.0.3 release onwards this object can configured in any application, but will be applicable only in non-trunking applications and will be ignored in other applications.

OBJECT-TYPE

This object tells the framer whether to force the cas bits to a value defined by ds0LocalCasPattern or not. If this is enabled the framer will force the cas (ABCD) bits to a value defined in ds0LocalCasPattern by ignorning the cas bits sent by DSP. Else the framer will transmit the cas bits sent by DSP. Setting of this object is not allowed when the signaling type of this line is cas. Also setting of this object is not allowed when the ds0LoopbackCommand is set to RemoteLoop, because in this situation we are suppose to loopback whatever comes from the TDM side and not force the cas bits to something else. This object can be set only if the line type is T1.

OBJECT-TYPE

This object contains the pattern that the cas (ABCD) bits will have when ds0InsertLocalCas is enabled.

OBJECT-TYPE

This object represents the loopback type at the ds0 level.The ds0 configuration overrides the line level configuration. NoLoop There is no loopback on this ds0. LocalLoop The data received from the ATM side is loopedback to the ATM side. RemoteLoop The data from the TDM side is looped back to the TDM side. Setting of this object to RemoteLoop will not be allowed when insert local cas for this ds0 (ds0InsertLocalCas object) is enabled as we are suppose to force the cas bits to the pattern configured in ds0LocalCasPattern, and not do loopback on the TDM side.

OBJECT-TYPE

This object indicates VISM whether to read the cas related timer parameters from the casAppl file downloaded for that endpoint or to read from this mib. This gives the flexibility of configuring different cas related timer values for different endpoints associated with the same cas variant. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint.

OBJECT-TYPE

This indicates the the minimum time in msecs for which the on hook pattern should be present in order for it to be recognised else the signal will be considered to be a spurious signal and will be ignored. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint. This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000

OBJECT-TYPE

This indicates the minimum time in msecs for which the off hook pattern should be present in order for it to be recognised else the signal will be considered to be a spurious signal and will be ignored. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000

OBJECT-TYPE

The wink consists of off-hook A-B bit pattern, followed by on-hook A-B bit pattern in timed sequence. This object indicates the minimum duration for which the off-hook part of wink signal should persist. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000 and the range is in msecs.

OBJECT-TYPE

The wink consists of off-hook A-B bit pattern, followed by on-hook A-B bit pattern in timed sequence. This object indicates the maximum duration for which the off-hook part of the wink signal should persist, if it exceeds this time limit the signal will be considered to be spurious and will be ignored. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..3000 and the units is in msecs. This object should be greater than or equal to ds0CasWinkMinMakeTime

OBJECT-TYPE

The wink consists of off-hook A-B bit pattern, followed by on-hook A-B bit pattern in timed sequence. This object indicates the minimum duration for which the on-hook part of wink signal should persist. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000 and the units. is in msecs.

OBJECT-TYPE

When the terminating gateway receives off Hook event from the Call Agent it starts the timer specified in this object to see if the terminating side is also trying to originate a call. If this is true, we have a 'glare' condition. The way glare is resolved is thru this user programmable timer, we will not honor any off hook events from the originating PBX during this time. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non CAS. For a CAS line this object can only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..10000 and the units is in msecs.

OBJECT-TYPE

The gaurd time is the duration between the end of one call and the start of next call. This object specifies what should be such a duration. All state changes from the PBX are ignored for this duration. After receiving DLCX, this timer will be started for a period as configured in this object, and will not honor any off-hook events before the expiration of this timer. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000 and the units is in msecs.

OBJECT-TYPE

This timer indicates the time that VISM should wait before outpulsing digits to the PBX after sending an off hook event. This applies only to immediate start protocol. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non cas. For a cas line this object CAN only be configured only after associating this ds0 with an endpoint. This object will be applicable if ds0CasParameterSource has a value of mibValue (2). The allowed range for this object is 10..1000 and the units is in msecs.

OBJECT-TYPE

This attribute indicates the type of signaling on the line to which this ds0 belongs. CAS - Channel Associated Signaling CCS - Common Channel Signaling none - no signaling used. This object will be implicitly set to line signaling type every time it changes.

OBJECT-TYPE

This is an object for an E & M signaling protocol like wink-start for this ds0. The difference is that the address-control signal is different from wink. The originating VISM, on receiving a seize (AB=11) from the PBX, responds by sending the delay-dial (AB=11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends a start-dial (AB=00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB=11 (as an ack that the trunk is operational). Subsequently, when it receives the start signal (AB=00) from the connected PBX, it should outpulse the digits. The rest of the operation is similiar to wink-start. The allowed range for this object is 100..1000 with units in milliseconds. In delay-dial operation, the outgoing interface (this interface), after sending a seize signal (AB = 11), waits for the delay-dial signal (AB = 11). The delay-dial signal, apart from acknowledging the seize signal, tells this interface that the connected equipment is not ready for the digits yet. This object specifies the time in milliseconds, after which incoming AB=11 will be interpreted by this interface as the delay-dial signal. References: Generic Requirements, GR-506-CORE, Issue 1, June 1996, Revision 1, November 1996, LSSGR: Signaling for Analog Interfaces Section 11.2.3 is about 'Delay-Dial Operation' (in general) In particular, section 11.2.3.1 ([R11-21] is about these timing requirements.

OBJECT-TYPE

This is an object for an E & M signaling protocol like wink-start for this ds0. The difference is that the address-control signal is different from wink. The originating VISM, on receiving a seize (AB=11) from the PBX, responds by sending the delay-dial (AB=11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends a start-dial (AB=00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB=11 (as an ack that the trunk is operational). Subsequently, when it receives the start signal (AB=00) from the connected PBX, it should outpulse the digits. The rest of the operation is similiar to wink-start. The allowed range for this object is 70..1000 with units in milliseconds. In delay-dial operation, the outgoing interface (this interface), after receiving a delay-dial signal (AB=11) from the connected equipment, waits for the start-dial signal (AB = 00) before sending the digits to the connected equipment. The start-dial signal tells this interface that the connected equipment is ready for the digits. This object specifies the time in milliseconds, after which incoming AB=00 will be interpreted by this interface as the start dial signal. References: Generic Requirements, GR-506-CORE, Issue 1, June 1996, Revision 1, November 1996, LSSGR: Signaling for Analog Interfaces Section 11.2.3 is about 'Delay-Dial Operation' (in general) In particular, section 11.2.3.1 ([R11-22] and [R11-23]) is about these timing requirements.

OBJECT-TYPE

Flash is a CAS signal generated by users to request special services. The interpretation of the flash depends on the protocol in use. The signal itself is an on-hook followed by an off-hook. This object specifies the minimum duration for the signal to be recognized as a flash by VISM. This duration, expressed in milliseconds, is defined as the elapsed time between the off-to-on-hook transition followed by the on-to-off-hook transition. If the on-hook duration is shorter than the value of this object, the signal will be ignored. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non-CAS. For a CAS line, this object can only be configured after associating this ds0 with an endpoint. If no endpoint was added for this Ds0, any configuration attempt will be rejected. This object will be applicable if ds0CasParameterSource has a value of mibvalue (2). The allowed range for this object is 50..1550 (msec).

OBJECT-TYPE

Flash is a CAS signal generated by users to request special services. The interpretation of the flash depends on the protocol in use. The signal itself is an on-hook followed by an off-hook. This object specifies the maximum duration for the signal to be recognized as a flash by VISM. This duration, expressed in milliseconds, is defined as the elapsed time between the off-to-on-hook transition followed by the on-to-off-hook transition. If the on-hook duration is longer than the value of this object, the signal will be ignored. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non-CAS. For a CAS line, this object can only be configured after associating this ds0 with an endpoint. This means that if no endpoint was added for this Ds0, any configuration set attempt will be rejected, but any get will be allowed. This object will be applicable if ds0CasParameterSource has a value of 'mibvalue'(2). The allowed range for this object is 50..1550 (msec.) with the additional requirement that the value of this object should be greater than or equal to ds0CasFlashMinMakeTime.

OBJECT-TYPE

This object specifies the direction in which CAS calls will be accepted on this endpoint. If this object is set to incoming, then calls from the connected PBX will be accepted by VISM on this endpoint. If set to outgoing, VISM will send calls towards the connected PBX and not accept calls from the PBX. For VISM to both send and receive calls on this endpoint, this object should be set to bidirectional. The main difference between bidirectional and one-way trunks is the occurrence of glare. On bidirectional trunks, since both VISM and the connected PBX can seize the endpoint at approximately the same time, glare (dual seizure) is likely to occur. The protocol assigned to a bidirectional endpoint should be capable of detecting and resolving glare. Wink-start and delay-dial are examples of protocols capable of glare handling and immediate-start, ground-start and loop-start, of those that cannot. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non-CAS. For a CAS line, this object can only be configured after associating this ds0 with an endpoint. This means that if no endpoint was added for this Ds0, any configuration set attempt will be rejected, but any get will be allowed.

OBJECT-TYPE

This object specifies how a bidirectional endpoint should resolve glare. This object will be used only if dsx0VismDirectionality of the endpoint is bidirectional. When glare is detected, if this object is set to controlling, VISM will wait for the connected PBX to assert on-hook. When the connected PBX goes on-hook, VISM proceeds to dial the numbers out waits for answer. If this object is set to releasing, VISM indicates the glare situation to the Call Agent (as specified by the control protocol), prepares to collect digits from the PBX and asserts on hook. The incoming call should go through. If the CAS protocol assigned to the endpoint cannot detect glare or if it cannot resolve glare according to the policy provisioned via this object, this object will not be used. This object cannot be configured if the signaling type for the line to which this ds0 belongs is non-CAS. For a CAS line, this object can only be configured after associating this ds0 with an endpoint. This means that if no endpoint was added for this Ds0, any configuration set attempt will be rejected, but any get will be allowed.

OBJECT-TYPE

This object, in conjunction with the card level persistentXgcpEventsTable, controls how persistent CAS events (like seize, disconnect, etc) related to an incoming call observed on this DS0 are notified to the Media Gateway Controller (MGC). At the card level, the persistentXgcpEventsTable allows MGCP package-event combinations to be configured as persistent. For example, when L/hd is added to the persistentXgcpEventsTable, the hook-down event in line package will be notified to the MGC every time it is observed without the MGC requesting for that event. Since the same CAS event can map to different MGCP events under different packages (eg. the CAS event 'seize' can be 'sup' in 'MS' package and 'hd' in 'BL' package) and different lines could be running different packages at a given time, there needs to be a per-DS0 object indicating what package should be used while notifying CAS events observed on that DS0. This object, ds0CasIncomingMgcpPackage specifies the package that will be used while notifying CAS events observed on an incoming call on this DS0. This object can be set to a package name from xgcpCapabilityPackageTable whose xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one of the basic packages in that table (G, T, L, H, R, D or M) to which the observed event belongs can be used. This object is used only if the protocol is MGCP. If the notification is in response to an RQNT, VISM uses the package (and event name) that the MGC used to request the event regardless what this object is set to. In the absence of an RQNT, the observed CAS event is encoded according to the package that this object specifies. A 'seize' observed on the CAS signaling channel on this DS0, for example is encoded as 'ms/sup' if this object is set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is set to 'basic'. If this package/event is present in persistentXgcpEventsTable, a notification is generated, otherwise this event is discarded. An attempt to set this object to a package name whose xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail. This object is used only if the ds0CasDirectionality is set to bidirectional or incoming.

OBJECT-TYPE

This object, in conjunction with the card level persistentXgcpEventsTable, controls how persistent CAS events (like answer, disconnect, etc) related to an outgoing call observed on this DS0 are notified to the Media Gateway Controller (MGC). At the card level, the persistentXgcpEventsTable allows MGCP package-event combinations to be configured as persistent. For example, when L/hd is added to the persistentXgcpEventsTable, the hook-down event in line package will be notified to the MGC every time it is observed without the MGC requesting for that event. Since the same CAS event can map to different MGCP events under different packages (eg. the CAS event 'answer' can be 'ans' in 'MS' package and 'hd' in 'BL' package) and different lines could be running different packages at a given time, there needs to be a per-DS0 object indicating what package should be used while notifying CAS events observed on that DS0. This object, ds0CasOutgoingMgcpPackage specifies the package that will be used while notifying CAS events observed on an outgoing call on this DS0. This object can be set to a package name from xgcpCapabilityPackageTable whose xgcpCapabilityPackageEnable is true or the string 'basic' indicating that one of the basic packages in that table (G, T, L, H, R, D or M) to which the observed event belongs can be used. This object is used only if the protocol is MGCP. If the notification is in response to an RQNT, VISM uses the package (and event name) that the MGC used to request the event regardless what this object is set to. In the absence of an RQNT, the observed CAS event is encoded according to the package that this object specifies. An answer observed on the CAS signaling channel on this DS0, for example is encoded as 'ms/ans' if this object is set to 'ms', 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is set to 'basic'. If this package/event is present in persistentXgcpEventsTable, a notification is generated, otherwise this event is discarded. An attempt to set this object to a package name whose xgcpCapabilityPackageEnable is false in xgcpCapabilityPackageTable will fail. This object is used only if the ds0CasDirectionality is set to bidirectional or outgoing.

OBJECT-TYPE

This object indicates the amount of gain inserted at the receiver side of a ds0 channel, in dB (decibel) units. The default value of this object is 0 dB. The input gain settings only define a gain/loss relative to the 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan. This object can be set when there are active call going on, and in this case the new gain will take effective immediately. It can also be set at both unbound endpoints and bound but non-active endpoints.

OBJECT-TYPE

This object contains the amount of attenuation inserted at the transmit side of a ds0 channel, in dB (decibel) units. The output attenuation settings only define a loss relative to 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan. This object can be set when there are active call going on, and in this case the new gain will take effective immediately. It can also be set at both unbound endpoints and bound but non-active endpoints.

OBJECT-TYPE

The indicates Music On Hold Threshold in dBm. Based on this value, VISM DSP will interprete the incoming signal from TDM side as either silence or voice, and consequently turn on or off VAD. This object can be set when there is active call going on at the ds0 channel, and at both unbound endpoints and bound non-active endpoints.

OBJECT-TYPE

This object specifies whether the Silence Indication Detection (SID) packet should be generated when silence suppression is in active mode. The SID packet indicates the noise level during silence, which is used as a reference to generate comfort noise on the other side of the gateway. This object is used for VoIP only.

OBJECT-TYPE

This table is created implicitly at the time of creating and deleting the endpoints. This table provides the mapping information from a line and channel to obtain an index for that channel.

OBJECT-TYPE

Please see the above description.

OBJECT-TYPE

This object describes the physical line number on VISM card.

OBJECT-TYPE

This object describes the ds0 number or channel number within a T1 or E1 line. The valid channel numbers are 1 to 24 for T1 line and 1 - 31 for E1 line.

OBJECT-TYPE

This object describes the ifIndex derived based on the line number and the channel number within the line according to the formula: IfIndex = 31 * (Ds1# - 1) + ds0# where : Ds1# - The T1/E1 line number in the range 1 - 8. ds0# - The ds0 channel number ranging from 1 to 24 for T1 and 1 to 31 for E1.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface. In FRSM-VHS, there are upto 256 entries for FRSM-2CT3 card and 2 entries for FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI cards and 8 entries for FRSM-HS2B-12IN1 card. For other cards, there are upto 192 entries (for 8 DS1s) and upto 248 entries (for 8 E1s). For FRSM12 cards: There are upto 12 entries. When a new row is added to this table, the corresponding row is created in ifTable.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is logical port number. If we have T1 card then the maximum port number is 192 and if we have E1 card the maximum port number can be 248. For FRSM-2CT3 card, the maximum port number is 256 and for unchannelized FRSM-VHS cards (FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI), the maximum port number is 2 For FRSM-HS2B-12IN1 card, the maximum port number is 8 For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

This represents the line number For FRSM12 card: The ifIndex of the physical line on which this port is provisioned.

OBJECT-TYPE

This variable enables or modifies the port 1- add 2 - del 3 - mod For FRSM12 card: For Snmp GET operations, only mod is returned.

OBJECT-TYPE

This respesents bit map of DS0s for a line which are used to form this logical port. Bit 0 represents DS0-1. This entry is not used for unchannelized FRSM-VHS/FRSM12 cards. For these cases, this field carries a value of 'ffffff'h always.

OBJECT-TYPE

This represents port speed of 64 or 56 1 - speed56k 2 - speed64k 3 - unUsed. This field is not used for unchannelised FRSM-VHS (FRSM-2T3/ FRSM-2E3/FRSM-HS2/FRSM-T3B/FRSM-E3B/FRSM-HS2B) cards; in such cards, the portDs0Speed field carries a value of 'unUsed' always. For FRSM12 card: This is set to 3 - unUsed.

OBJECT-TYPE

Number of flags transmitted between FR frames For FRSM12 card: Only the values 1 to 8 are supported. The mapping is as follows: MIB object value No. of HDLC flags inserted 1 1 2 2 3 4 4 8 5 16 6 32 7 64 8 128

OBJECT-TYPE

Number of times queue 1 is serviced for every time queue 2 is serviced. The value 0 is supported only by FRSM-VHS. FRSM-VHS supports two different egress queue servicing algorithms depending on the Egress Qos Feature. if EgrQosFeature is ENABLED, Weighted Fair queueing algorithm will be used to select one queue out of 4 data queues and this object will be set to a default value of 0 in this case and this value cannot be modified by user. In case of EgrQosFeature being DISABLED, this object will be set to a default value of 1 and can be configured to user desired value. This value will be used to decide number of times High priority queue has to be serviced for every time low priority queue is serviced. For FRSM12 card: There is only one scheme of egress scheduling of COS queues within ports, which uses only two COS queues for user data. The scheduling scheme uses a pre-defined ratio to schedule these COS queues on a given port. This object will be used to decide number of times High priority queue has to be serviced for every time low priority queue is serviced.

OBJECT-TYPE

Configured speed of port in kbps

OBJECT-TYPE

used to up and down the port For FRSM12 card: This variable will be equivalent to ifAdminStatus of of ifTable. The write-only is not used.

OBJECT-TYPE

This represents port type For FRSM12 card: frFUNI not Applicable. For frame-relay the ifType is frameRelayService(44) and for frame-forward it is frForward(158).

OBJECT-TYPE

This represents SVC status For FRSM12 card: Not Supported

OBJECT-TYPE

This represents port svc in use For FRSM12 card: Not Supported

OBJECT-TYPE

This represents port type For FRSM12 card: Not Supported

OBJECT-TYPE

This represents low end of reserved LCN for svc For FRSM12 card: Not Supported

OBJECT-TYPE

This represents high end of reserved LCN for svc For FRSM12 card: Not Supported

OBJECT-TYPE

This represents low end of reserved DLCI for svc For FRSM12 card: Not Supported

OBJECT-TYPE

This represents high end of reserved DLCI for svc For FRSM12 card: Not Supported

OBJECT-TYPE

Setting this object to 1 indicates that all the SVC connections on the given port has to be deleted For FRSM12 card: Not Supported

OBJECT-TYPE

This represents Ingress Bandwidth reserve for SVC For FRSM12 card: Not Supported

OBJECT-TYPE

This represents Egress Bandwidth reserve for SVC For FRSM12 card: Not Supported

OBJECT-TYPE

This variable enables BERT For FRSM12 card: Not Supported

OBJECT-TYPE

This variable enables/disables enhanced SIW feature. Enabling this permits support for SIW translation of Appletalk. This feature is currently supported only in the FRSM-VHS card. For FRSM12 card: Not Supported This object is not required in FRSM12 since Appletalk is supported by default in FRF.8.1 and FRSM12 supports FRF.8.1

OBJECT-TYPE

This represents the M32 logical port Egress Queue threshold in bytes. Frames will not be queued until the number of bytes in the queue is less than the threshold. The default value is 6000. Using a very low value could under utilize the logical port. This is supported in FRSM 8t1e1 and FRSM 4t1e1 Service Modules only. For FRSM12 card: Not Supported

OBJECT-TYPE

This object is added for FRSM12. The value of this object identifies the Q.922 Address field length and DLCI length for this UNI/NNI logical port. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12. The value of this object identifies the CRC Length in the HDLC Packet. Applicable for FrameForwarding ports only. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

The ID of the SCT file that holds module specific configuration parameters for this FR virtual interface. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12. When this object is enabled the port will be allowed to be over subscribed. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 1

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 2

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 3

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 4

OBJECT-TYPE

This variable contains the next UNUSED logical port number. This number can be used in channel config table, the portNextAvailable gets updated if the number gets used to create a logical port. A '0' indicates that no more ports are available. For FRSM12 Card: Not Supported

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 5

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 6

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 7

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1 This is for line 8

OBJECT-TYPE

Contains a sequence of entries for each DS1 line. each entry gives the number of DS0 slots being used added for FRSM_VHS

OBJECT-TYPE

One entry per DS1

OBJECT-TYPE

This is the Index to the table containing the portsUsedLine for the 56 DS1s

OBJECT-TYPE

Each bits set represents a DS0 that is used by all the logical ports defined so far for that DS1, the most significant byte is invalid for DS1

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface there are upto 248 entries (8 E1s) and 192 entries (8 T1s). In FRSM-VHS, there are a total of 256 entries. In FRSM12, there are 12 entries.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

This will set the signalling protocol 1 - other 2 - noSignalling 3 - strataLMI 4 - annexAUNI 5 - annexDUNI 6 - annexANNI 7 - annexDNNI Only noSignalling is applicable to frame forwarding ports For FRSM12: strataLMI is not supported for portHeaderLen of fourOctets.

OBJECT-TYPE

disable - disable Asynchronous Status Updates & Unsolicited Full Status enable - enable Asynchronous Status Updates fsenable - enable Unsolicited Full Status updfsenable - enable Asynchronous Status Updates & Unsolicited Full Status The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

Interval in seconds for NNI to do status polling The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

Interval in seconds for UNI to expect status polling The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

Number of UNI/NNI Polling cycles The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

UNI/NNI Error Threshold The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

UNI/NNI Events, always greater than n392 The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

This object defines if enhanced LMI is enabled on a logical port. The signalling parameters are not applicable for the frame forwarding port.

OBJECT-TYPE

This object is added for FRSM12. This variable enables/disables FRF 1.2 feature. This object is not applicable to MGX Release 1.x

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

This will enable CLLM 1 - disabled 2 - enabled CLLM is not applicable for frame forwarding ports

OBJECT-TYPE

Interval in milliseconds for CLLM to send CLLM updates CLLM parameters are not applicable for frame forwarding ports

OBJECT-TYPE

Timeout value for receiving CLLM updates CLLM parameters are not applicable for frame forwarding ports

OBJECT-TYPE

The config table is for X.21/HSSI logical port interface

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is logical port number. The HSSI backcard can support upto 3 ports, whereas the X.21 can support 4 logical ports. No defaults.

OBJECT-TYPE

This represents the line number. On FRSM-HS1 the HSSI can support 3 lines and X.21 4 lines. No defaults.

OBJECT-TYPE

This variable adds, deletes, or modifies the port 1- add 2 - delete 3 - modify Default is add.

OBJECT-TYPE

Number of flags transmitted between two consecutive HDLC frames. Default is 1 flag.

OBJECT-TYPE

Number of times queue 1 is serviced for every time queue 2 is serviced. Default is 1.

OBJECT-TYPE

Port speed in kbps. At present it is same as line speed. No defaults.

OBJECT-TYPE

Up/down used to up and down the port. Default is the up state.

OBJECT-TYPE

This represents port type. The processing of the frames depends on the type of the port.

OBJECT-TYPE

This represents SVC status

OBJECT-TYPE

This represents port svc in use

OBJECT-TYPE

This represents port type

OBJECT-TYPE

This represents low end of reserved LCN for svc

OBJECT-TYPE

This represents high end of reserved LCN for svc

OBJECT-TYPE

This represents low end of reserved DLCI for svc

OBJECT-TYPE

This represents high end of reserved DLCI for svc

OBJECT-TYPE

Setting this object to 1 indicates that all the SVC connections on the given port has to be deleted

OBJECT-TYPE

This represents Ingress Bandwidth reserve for SVC

OBJECT-TYPE

This represents Egress Bandwidth reserve for SVC

OBJECT-TYPE

The config table is for logical port interface. In FRSM-VHS, there are 256 entries for FRSM-2CT3 card and 2 entries for FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI cards and 8 entries for FRSM-HS2B-12IN1. The table is currently supported only in FRSM-VHS when the object egrQosFeature in the cardSpecific group is set to egrQosFeatureEnabled.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is the logical port number.

OBJECT-TYPE

This identifies the Q depending on the Service Type 1 High Priority Queue 2 rt VBR Queue 3 nrt VBR and ABR Queue 4 UBR Queue queue5(5) to queue8(8) are reserved for future use There are 8 queues but only four are being used as of now.

OBJECT-TYPE

Indicates the peak Egress queue depth for the logical port. The total queue depth of all connections mapped to this queue should not exceed this value.

OBJECT-TYPE

ECN threshold for the logical port. If the total queue depth of all connections mapped to this port queue exceeds this threshold, then the appropriate ECN bit (FECN in the downstream direction and BECN in the upstream direction) get set.

OBJECT-TYPE

DE threshold for the logical port. If the total queue depth of all connections mapped to this port queue exceeds this threshold, and the DE bit is set in the incoming frame, then the frame gets dropped.

OBJECT-TYPE

Denotes the bandwidth increment for this port queue. The bandwidth increment is the percentage of the port bandwidth used by all connections mapped to a particular queue scaled by the value 16384.

OBJECT-TYPE

Counter maintained for the no of bytes discarded due to port queue depth exceeded.

OBJECT-TYPE

Counter maintained for the no of bytes discarded due to DE threshold exceeded.

OBJECT-TYPE

This table contains the configuration of port resource partition

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is the logical port number, the index to this table. If we have T1 card then the maximum port number is 192 and if we have E1 card the maximum port number can be 248 For FRSM VHS 2CT3 the maximum port number is 256. For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

This is index for controller using the port In MGX release 1.0, the value par should be used In MGX release 2.0, the value pnni should be used

OBJECT-TYPE

This will add, delete or modify the partition. In MGX Release1.0: To add an entry, this object should be set to add, value for other objects should not be specified. FRSM will choose default values for all other objects. In MGX Release2.0: To add an entry, this object should be set to add, value for frResPartCtrlrID may be specified. FRSM will choose default values for all other objects. Currently the value mod is not supported. To delete an entry, this object has to be set to del. The resource partition can be deleted only after deleting all the connections (LCNs).

OBJECT-TYPE

This represents number of LCNs available for this controller and this port FRSM VHS 2CT3 can support LCNs upto 4000. FRSM12 can support LCNs upto 16000.

OBJECT-TYPE

This represents low end of reserved DLCI

OBJECT-TYPE

This represents high end of reserved DLCI

OBJECT-TYPE

The percentage of total ingress bandwidth reserved

OBJECT-TYPE

The percentage of total egress bandwidth reserved

OBJECT-TYPE

This is the controller identifier for the resource patition. The default value is set for PNNI controller.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface there are upto 248 entries (for 8 E1s) or 192 (for 8 T1s). In FRSM-VHS, there is support for upto 256 entries.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

The number of frames Received on the ingress

OBJECT-TYPE

The number of bytes Received on the ingress

OBJECT-TYPE

The number of frames with DE bit set Received on the ingress

OBJECT-TYPE

The number of frames with FECN bit set Received on the ingress

OBJECT-TYPE

The number of frames with BECN bit set Received on the ingress

OBJECT-TYPE

The number of frames discarded on the ingress due to CRC error

OBJECT-TYPE

The number of frames discarded on the ingress due to Alignment error

OBJECT-TYPE

The number of frames discarded on the ingress due to illegal length

OBJECT-TYPE

The number of frames discarded on the ingress due to illegal header

OBJECT-TYPE

The number of received frames aborted

OBJECT-TYPE

The number of frames received with an unknown DLCI

OBJECT-TYPE

The last unknown DLCI received

OBJECT-TYPE

The number of frames received that were tagged with FECN bit

OBJECT-TYPE

The number of frames received that were tagged with BECN bit

OBJECT-TYPE

The number of frames received that were tagged with DE bit

OBJECT-TYPE

The number of frames discarded on the ingress due to exceeded DE Threshold

OBJECT-TYPE

Received Average Information Rate in KBPS

OBJECT-TYPE

The number of times the receiver is turned off

OBJECT-TYPE

The number of frames transmitted

OBJECT-TYPE

The number of bytes transmitted

OBJECT-TYPE

The number of frames transmittedc with FECN bit already set

OBJECT-TYPE

The number of frames transmitted with BECN bit already set

OBJECT-TYPE

The number of frames discarded on the egress due to exceeded queue depth For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of bytes discarded on the egress due to exceeded queue depth For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames transmitted during LMI logical port alarm

OBJECT-TYPE

The number of bytes transmitted during LMI logical port alarm

OBJECT-TYPE

The number of transmit frames aborted For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded due to underrun

OBJECT-TYPE

Transmit Average Information Rate in KBPS

OBJECT-TYPE

The number of times the transmitter is turned off For FRSM12 Card: Not Supported

OBJECT-TYPE

Port clear button. Resets all counters.

OBJECT-TYPE

The number of frames received when no channel is setup

OBJECT-TYPE

The number of frames discarded in Ingress direction due to FIFO overrun in HDLC Controller. This object is not applicable to MGX Release 1.x

OBJECT-IDENTITY

OBJECT-TYPE

The LMI counter table is for logical port interface there are upto 248 entries (for 8 E1s) and upto 192 entries (for 8 T1s). In FRSM-VHS, there are upto 256 entries.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

The number of Status Inquiry messages received

OBJECT-TYPE

The number of Invalid Request messages received

OBJECT-TYPE

The number of times UNI messages with sequence number mismatches were received

OBJECT-TYPE

The number of times Status response messages transmitted

OBJECT-TYPE

The number of times Asynch Status messages transmitted

OBJECT-TYPE

The number of times UNI Status requests were not received

OBJECT-TYPE

The number of Status Inquiry messages transmitted

OBJECT-TYPE

The number of times Status response messages received

OBJECT-TYPE

The number of times Asynch Status messages received

OBJECT-TYPE

The number of times NNI messages with sequence number mismatches were received

OBJECT-TYPE

The number of times NNI Status requests were not received

OBJECT-IDENTITY

OBJECT-TYPE

The CLLM counter table is for logical port interface

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

The number of CLLM frames received

OBJECT-TYPE

The number of CLLM bytes received

OBJECT-TYPE

The number of CLLM frames transmitted

OBJECT-TYPE

The number of CLLM bytes transmitted

OBJECT-TYPE

The number of times an expected CLLM message was not received

OBJECT-IDENTITY

OBJECT-TYPE

Table of transmit/receive states of ports.

OBJECT-TYPE

An entry for logical port.

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

This variable indicates the state of the logical port

OBJECT-TYPE

Bit 0 = 0 -> LMI O.K. or not enabled Bit 0 = 1 -> LMI failed Bit 1 = 0 -> CLLM O.K. or not enabled Bit 1 = 1 -> CLLM failed

OBJECT-TYPE

This variable indicates the whether the port is over subscribed or not

OBJECT-TYPE

Percentage Utilization of the Port in the Ingress direction.

OBJECT-TYPE

Percentage Utilization of the Port in the Egress direction.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical channel interface (upto 4000 entries). The actual number of entries supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports 256 entries FRSM-8T1/E1 supports 1000 entries FRSM-T3/E3/HS2/HS2B-HSSI/T3B/E3B supports 2000 entries FRSM-2CT3/HS2B-12IN1 supports 4000 entries FRSM12 supports 16000 entries

OBJECT-TYPE

An entry for logical channel

OBJECT-TYPE

Refers to the virtual connection index Note that the actual range of the index supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries) FRSM-8T1/E1 supports a range from 16..1015 (1000 entries) FRSM-T3/E3/HS2/HS2B-HSSI/T3B/E3B supports a range from 16..2015 (2000 entries) FRSM-2CT3/HS2B-12IN1 supports a range from 16..4015 (4000 entries) For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = channel Number. Lower two bytes range from 16..16015 (16000 entries)

OBJECT-TYPE

This will add, delete or modify the channel 1 ==> ADD 2 ==> DELETE 3 ==> MODIFY Setting this object to outOfService takes the channel out of service or brings the channel 'down'. The channel can be brought 'up' again by setting the object to mod

OBJECT-TYPE

Refers to the logical ports that are possible on this card, the user must set this variable For FRSM12 Card: This object contains the port's ifIndex value.

OBJECT-TYPE

This variable is the DLCI number of the channel. The user has to set this variable. All the connections on the same port should have a unique DLCI number. Note that if we are adding a channel to a port that has LMI signalling enabled, then we can not use DLCI number 0(ANNEX A & D) and 1023(STRATA LMI). For FRSM12 Card: For FR header length of 2-bytes, DLCI range is (0 .. 1023) and 0, 1007, 1023 DLCIs cannot be used. For FR header length of 4-bytes, DLCI range is (0 .. 8388607) and 0, 8257535 DLCIs cannot be used.

OBJECT-TYPE

Selects one out of two possible port queues. The default port queue number is 1 which is the high pririty queue. 1 = High priority queue 2 = Low priority queue 3 = Indicates that this entry is not used (eg: in FRSM-VHS, chanServType indicates the channel service type and would determine the queue to which the channel gets mapped) For FRSM12 Card: This object is used to select between the two ATM-COS queues in the egress direction.

OBJECT-TYPE

This variable sets the max depth for queue, before it starts dropping the cells. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (4510..'ffff'h). ingressQDepth should be greater than ingressQECNThresh and ingressQDEThresh For FRSM12 Card: Not Supported

OBJECT-TYPE

This variable sets the max depth for queue, before it starts flow control. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (0..'ffff'h). For FRSM12 Card: Not Supported

OBJECT-TYPE

This variable sets the max depth for queue, before they become discard eligible. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (0..'ffff'h). For FRSM12 Card: Not Supported

OBJECT-TYPE

This variable sets the max depth for queue, before it starts dropping the cells. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (0..'ffff'h). egressQDepth should be greater than egressQDEThresh and egressQECNThresh For FRSM12 Card: Not Supported

OBJECT-TYPE

This variable sets the max depth for queue, before they become discard eligible. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (0..'ffff'h). For FRSM12 Card: Not Supported

OBJECT-TYPE

This variable sets the max depth for queue, before it starts flow control. It is defined in terms of number of bytes. In all cards except the FRSM-VHS card, the range is limited to (0..'ffff'h). For FRSM12 Card: Not Supported

OBJECT-TYPE

The default value is 2. This variable enables DE tagging in the ingress direction only. enable = 1 disable = 2 For FRSM12 Card: When this object is disabled, the ingress policer will never set the DE bit to 1 in the Frame Relay frames even if the incoming frame exceeds the Bc bucket.

OBJECT-TYPE

The default value is 2400 cir defines committed information rate cir is in bits per second Maximum value for cir for an E1 card is 2048000 and for a T1 card is 1536000. cir has to be less than or equal to the port speed. Maximum value for cir for an E3 card is 34368000, for a T3 card is 44736000m, and for HSSI it is 52000000. Note that for FRSM-2CT3 card, the peak value of permissible CIR is 1536000. Maximum value for FRSM-HS2B-12IN1 is 10240000 Any value from 1 to 2399 will be rounded off to 2400. For FRSM12 Card: The range is 0-44736000 bps for T3, and The range is 0-34368000 bps for E3. cir can be 0 only for chanServType of uBR.

OBJECT-TYPE

The default value is 5100 bc defines burst committed. bc is in bytes. bc can not be 0 when cir is not 0. bc has to be 0 if cir is 0. The peak value for bc in FRSM-VHS cards is (2^21 -1), i.e. 2097151 and for all other cards, it is 65535. For FRSM-VHS cards, the relation between CIR and Bc should be such that Tc is always less than 512 seconds. For FRSM12 Card: The range is 0-2097151

OBJECT-TYPE

The default value is 5100 be defines the burst excess. be can not be 0 when cir is 0. be is in bytes. The peak value for be in FRSM-VHS cards is (2^21 -1), i.e. 2097151 and for all other cards, it is 65535. For FRSM-VHS cards, setting the value of 2091751 will cause the policing to be disabled. For FRSM12 Card: The range is 0-2097151

OBJECT-TYPE

The default value is 100 ibs should be less or equal to bc when cir is greater than 0. ibs has to be 0 when cir is 0. The peak value for ibs in FRSM-VHS cards is (2^21 -1), i.e. 2097151 and for all other cards, it is 65535. For FRSM12 Card: Not Supported

OBJECT-TYPE

The default value is 2 This variable sets foreSight option Note that when you enable foresight option then you can modify qir, mir and pir, otherwise you CAN NOT change these values if you are disabling foresight or if foresight option is already disabled. The RATE CONTROL FEATURE has to be ON in order to enable foresight and also modify its parameter. enable = 1 disable = 2 For FRSM12 Card: Not Supported

OBJECT-TYPE

The dafault is 160 qir is defined in fastpackets/sec and it defines quiescent information rate for Foresight. 1 cell/sec is equal to 16 fastpackets/sec. Following information about cps is for reference only: The peak value for qir in FRSM-VHS cards is 285714 cps and for all other cards, it is 10000 cps. For FRSM-VHS cards, cell will be the ATM cell (48 byte payload). For FRSM12 Card: Not Supported

OBJECT-TYPE

The dafault is 160 mir is defined in fastpackets/sec and it defines minimum information rate for Foresight. 1 cell/sec is equal to 16 fastpackets/sec. Following information about cps is for reference only: The peak value for qir in FRSM-VHS cards is 285714 cps and for all other cards, it is 10000 cps. For FRSM-VHS cards, cell will be the ATM cell (48 byte payload). For FRSM12 Card: Not Supported

OBJECT-TYPE

The dafault is 160 pir is defined in fastpackets/sec and it defines peak information rate for Foresight. 1 cell/sec is equal to 16 fastpackets/sec. Following information about cps is for reference only: The peak value for qir in FRSM-VHS cards is 285714 cps and for all other cards, it is 10000 cps. For FRSM-VHS cards, cell will be the ATM cell (48 byte payload). For FRSM12 Card: Not Supported

OBJECT-TYPE

The default is disable. This variable enables or disables the remote loopback for each channel. When you enable this option on a connection (channel) then all the cells that are coming from the network side would be looped back toward the network and all the frames coming from the user side would be dropped. This channel remote loopback has nothing to do with the chanTestType option, each one does a different function. For example, the channel remote loopback is used for looping the data toward the network and if this connection is terminated on an IPX then they can put a test equipment and measure some of the characteristics of the network. 1 = enable 2 = disable For FRSM12 Card: Not Supported

OBJECT-TYPE

The default is notest. The chanTestType starts testing the continuity or delay of a connection. It sends specific cell patterns toward the network and the terminating end of this connection has to be an AXIS or ASI of a BPX in order for this test to be working. The receiving node would loop back when it receives these cells. The test should be done in about couple of seconds. The testcon tests the continuity of the connection and testdelay uses the same test except that it measures for delay through the network. To test the delay follow this procedure: a- set chanTestType to testdelay b- read chanTestState till it is Pass or Fail c- Read chanRTDResult for the delay if it is Pass *Note that the chanTestType would go back to notest when the test is completed To test the continuity follow this procedure: a- set chanTestType to testcon b- read chanTestState till it is Pass or Fail *Note that the chanTestType would go back to notest when the test is completed You CAN NOT select 2 tests back to back, you have selcelt one and wait the result and then start the other one. SYNTAX When you select testdelay This is the type of the test 1 = Test Continuity 2 = Test Delay 3 = No Test

OBJECT-TYPE

This shows the state of the test When you add a connection then the chanTestState becomes notinprogress and when you select any test, it would go to inprogress state and after it completes the test, it will go to failed or passed state. 1 = Passed 2 = Failed 3 = In Progress 4 = Not In Progress

OBJECT-TYPE

This is round trip delay in milliseconds. When you select testdelay option for the chanTestType, the result of the test that is measured in milliseconds can be read in chanRTDResult.

OBJECT-TYPE

sets channel type Type 1 is frame-relay network interworking (NIW-unicast) type 2 is service interworking with out any SDU translation type 3 is service interworking with SDU translation type 4 is frame-relay UNI, currently mode-1a which is ALL5 type 5 is frame forwarding types 1,2,3 and 5 are supported as explained above type 4 (frame-relay UNI) is NOT supported type 6 is also supported. It means frame-relay Network Interworking with DLCI in FRSSCS-PDU always set to 1022 For FRSM12 Card: frFUNI is not supported.

OBJECT-TYPE

sets FECN config mapEFCI valid only for SIW The FECN bits in frame-relay are mapped to EFCI bit in the ATM cells.

OBJECT-TYPE

sets mapping of CLP bit The DE bit is mapped to CLP bit in ATM cell in Case 2 and 3, the DE bit is ignored and CLP bit is set to a constant value For FRSM12 Card: Should not be mapCLP for chanType of frForward.

OBJECT-TYPE

sets mapping of DE bit 1,2,3 valid for SIW 1,4 valid for NIW The CLP bit is mapped to DE bit in frame-relay in the Case of 2 and 3, the CLP bit is ignored and DE bit is set to a constant value ignoreCLP ignores CLP bit and DE bit remains as received. For FRSM12 Card: Should be ignoreCLP for chanType of frForward. Should not be setDEzero/setDEone for chanType of frNIW and frNIWReplace. Should not be ignoreCLP for chanType of frSIW-transparent and frSIW-translate.

OBJECT-TYPE

the channel ingress utilized percentage

OBJECT-TYPE

the channel egress utilized percentage

OBJECT-TYPE

The channel egress cir. Maximum value for chanEgrSrvRate for an E1 card is 2048000 and for a T1 card is 1536000. chanEgrSrvRate has to be less than or equal to the port speed. Maximum value for chanEgrSrvRate for an E3 card is 34368000, for a T3 card is 44736000m, and for HSSI it is 52000000. Note that for FRSM-2CT3 card, the peak value of permissible chanEgrSrvRate is 1536000. For FRSM12 Card: This object is used only for CAC and the range will be same as the range for cir object. The Maximum value is 44736000m.

OBJECT-TYPE

This MIB variable allows one to add a new connection on a port even if it is over subscribed. For FRSM12 Card: Not Supported

OBJECT-TYPE

channel connection type 1 for pvc 2 for svc 3 for spvc 4 par (only for trunk connection) 5 pnni (only for trunk connection) 6 tag (only for trunk connection) For FRSM12 Card: Not Supported

OBJECT-TYPE

This is the key to correlate cell/frame counts, start/end record. For FRSM12 Card: Not Supported

OBJECT-TYPE

This VPI together with the local VCI and NSAP represents the local end point in this connection, this object is read only, therefore it'll be assigned by SM to 0.

OBJECT-TYPE

This VCI together with the local VPI and NSAP represents the local end point in this connection, this object is read only, therefore it'll be assigned by SM to be equal to DLCI.

OBJECT-TYPE

This NSAP is 20 bytes binary, among these 20 bytes: 13 bytes as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for logical interface: slot (1 byte) and port number (2 bytes), the last byte is for SEL For FRSM12 Card: This object will have the NSAP format as required by the PNNI controller

OBJECT-TYPE

This VPI together with the remote VCI and NSAP represents the remote end point in this connection

OBJECT-TYPE

This VCI together with the remote VPI and NSAP represents the remote end point in this connection

OBJECT-TYPE

This NSAP is 20 bytes binary, among these 20 bytes: 13 bytes as prefix, 2 bytes for Cisco ID, 1 byte rsvd, 3 bytes for logical interface: slot (1 byte) and port number (2 bytes), the last byte is for SEL

OBJECT-TYPE

This is used by PXM to determine if this end point is master or slave, a new type unknown is added to identify the SM in AXIS shelf and the SM in MGX shelf. In AXIS shelf, user can still use addchan to add a channel without specifying X/Y/P parameters. But in MGX shelf, if the user uses addchan without X/Y/P set (based on this object being set to type 3 unknown), SPM on PXM will reject the request. It must be supplied in connection setup request. In the feeder mode, this is always set to master.

OBJECT-TYPE

This represents the connection type, used for PXM to identify VPC/VCC but FRSM card doesn't use it always set to vcc for FRSM card For FRSM12 Card: This object is used by the PNNI controller and is always set to VCC

OBJECT-TYPE

This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 3 ==> Not used 4 ==> Unspecified Bit Rate 5 ==> ATM frame relay 6 ==> standard ABR 7 ==> foresight ABR Note that this is used by PXM card, SV+ doesn't need to set it, if not set in the connection setup request, it'll be defaulted to ATFR type for FRSM. Also to make it compatible with existing AUSM MIB definition, value 3 is not used. The following types are being added for PNNI support. and are based on UNI 4.0 cbr1 (21) - CBR.1 vbr1rt (22) - Real time VBR.1 vbr2rt (23) - Real time VBR.2 vbr3rt (24) - Real time VBR.3 vbr1nrt(25) - Non Real time VBR.1 vbr2nrt(26) - Non Real time VBR.2 vbr3nrt(27) - Non Real time VBR.3 ubr1 (28) - UBR.1 ubr2 (29) - UBR.2 stdabr (30) - TM 4.0 compliant standard ABR cbr2 (31) - CBR.2 cbr3 (32) - CBR.3 For FRSM12 Card: Not Supported. Derived from chanServType.

OBJECT-TYPE

This is used by PXM to determine how important this connection is when selecting connections to route

OBJECT-TYPE

Maximum allowed cost. It is related to Cost Based Routing. This is used by PXM so that it won't choose a path with a cost greater than this configured level. This is not necessary to be provided in the connection setup request, if not provided, the default value 255 will be used. When used with PAR controller the valid range is 1..65535 and the default value is 255. When used with PNNI controller the valid range is 1..2147483647 and the default value is 2147483647.

OBJECT-TYPE

Restricted trunk type for routing, used by PXM. It specifies that the connection either cannot be routed over satelite trunks, or terrestrial trunks, or it can be on any type of trunk. It is not necessary to be provide in the connection setup request, the default value is norestriction(1). For FRSM12 Card: Not Supported

OBJECT-TYPE

Peak cell rate, if not provided in the connection setup request, it'll be derived from pir. For FRSM12 Card: Default value is (1.44 * CIR)

OBJECT-TYPE

Peak cell rate of the other end, if not set, will be set to the same as local end PCR (frConnPCR). However, note that if the CIRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end PCR. For FRSM12 Card: Default value is frConnPCR

OBJECT-TYPE

Minimum cell rate, if not provided in the connection setup request, it'll be derived from mir. For FRSM12 Card: Default value is frConnPCR

OBJECT-TYPE

Minimum cell rate of the other end, if not set, will be set to the same as local end MCR (frConnMCR). However, note that if the CIRs for both local and remote end are set to the different value (i.e., asymmetric conn), then this should be set differently from local end MCR. For FRSM12 Card: Default value is frConnMCR

OBJECT-TYPE

This is the expected long-term utilization of the channel by this end-point. If this is not specified in the connection setup request, it'll be defaulted to 100 percent For FRSM12 Card: Not Supported

OBJECT-TYPE

This is the expected long-term utilization of the channel by the other end-point. If this is not specified in the connection setup request, it'll be set to be the same as the local end frConnPercentUtil value assuming that the connection is symmetric. In a asymmetric connection, this object is supposed to be set. For FRSM12 Card: Not Supported

OBJECT-TYPE

This object is used by the controller(PAR/PNNI/TAG) to set up the Qbin for the connection, if this is not set, it'll be defaulted by SM to the same as foreSightEnable in the end point parameters. For FRSM12 Card: Not Supported

OBJECT-TYPE

enables/disables Frame based GCRA (early packet discard). For FRSM12 Card: Not Supported

OBJECT-TYPE

This indicates the class of the connection 1-High priority (typically CBR connections) 2- real-time VBR 3- non-real time VBR 4- Available Bit Rate 5- Unspecified Bit Rate 9- Standard ABR There are 8 queues actually but only 4 are currently being used (the 4 queues are for CBR, VBR-rt, <VBR-nrt and ABR>, UBR traffic). This object is currently suuported only in FRSM-VHS and FRSM-8T1E1. For FRSM-8T1E1, a 0 indicates that the connections are of old model type where chanServType object is unused. Note that chanServType is not modifiable after a channel has been enabled For FRSM12 Card: The types aBR, queue6, queue7, queue8 are not supported

OBJECT-TYPE

This variable sets the SAR IR programming option. Foresight and chanServiceRateOverride are mutually exclusive. For FRSM12 Card: Not Supported

OBJECT-TYPE

This is the rate to which IR can be set to when chanServiceRateOverride is set to enabled. If chanServiceRateOverride is disabled then this object does not have any significance. For FRSM-8P, this is defined in fastpackets/sec. For FRSM-VHS, this is defined in atm cells per second. For VHS the range in cells per second will be 10 to 400000 cps. For FRSM12 Card: Not Supported

OBJECT-TYPE

zeroCirConEir defines EIR value for '0' CIR connection. If zeroCirConEir is '0', EIR is set to port speed. If zeroCirConEir is non-zero value, EIR is set to value of this object, and this value is used for policing in ingress direction. This object is valid only for a zero cir connection. zeroCirConEir has to be less than or equal to the port speed.

OBJECT-TYPE

This is used by the administrator to trigger the re-routing of the connection. The rerouting takes effect, when this object is set to true(1). When set to false (2), no action is taken. A get on this object always returns false (2). This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

Sustained cell rate, Used for VBR connections setup with PNNI controller. For FRSM12 Card: Default value is frConnPCR This object is not applicable to MGX Release 1.x

OBJECT-TYPE

Sustained cell rate of the other end, Used for VBR connections setup with PNNI controller. For FRSM12 Card: Default value is frConnSCR This object is not applicable to MGX Release 1.x

OBJECT-TYPE

This object specifies the template identifier for the connection template associated with this connection. The valid range for templates is 1..16. A value of 17 indicates no template is associated with this connection For FRSM12 Card: Not Supported This object is not applicable to MGX Release 1.x

OBJECT-TYPE

This object specifies channel admin status. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added only for FRSM12 card. This counter tracks the number of configuration changes that happen on a channel. The counter is associated only with the end point and NOT with the connection itself. This counter is used by the NMS to determine if a connection configuration had been modified and requires an upload. This functionality is conventionally achieved by time stamping using a time-of-day clock. However, in switches where time-of-day clock is not available, the following scheme is used: The upload counter is incremented, when: * assignment of connection to an end point channel. This happens when a connection is added and assigned this channel number. * de-assignment of connection from a channel number. This happens when a connection is deleted and the end point resource is released. * When there is a configuration change done to the connection that is associated with this end point channel number. In a new system, an unutilised resouce (channel number) has a counter value of zero. When a connection is added to this channel end point, the counter is incremented. And is incremented for any of the above operations. When a connection is deleted the value of this counter is incremented and preserved till a new connection gets associated with this channel end point. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. When this object is enabled, the incoming frames with DE(Discard Eligible) bit set to 1 are counted in the Bc bucket instead of Be bucket This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. This object serves to enable or disable continuity check(CC) on a connection endpoint. When continuity check is enabled on an endpoint, the endpoint anticipates OAM CC cells from its peer endpoint. OAM CC cells are sent when the peer endpoint does not have traffic cells to send. If the connection is idle and this endpoint has not received OAM CC cells for a period of 3.5 +/- 0.5 seconds, it declares continuity failure. This object serves to administratively control the CC feature. Typical implementations (of this feature) may choose to ignore this control or impose other conditions to actually enable CC cell flow. However, if this object is set to false(2), then this feature should be disabled This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. Limits imposed by software or hardware implementations could restrict the amount of statistical data that can be maintained in a physical entity (like a service module card). Hence there could be a need to restrict statistics collection to a smaller subset. This object serves the purpose of enabling/disabling statistics collection on a per connection basis. In implementations which do not have such limitations, this object can be set to enable(1) for all connections This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. This object when enabled adds a channel-level loopback towards the port side. If the connection is in loopback, Connection MIB (FrChanCnfGrpEntry) variables cannot be modified. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. This object when disabled, disables Frame Relay policing. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This object is added for FRSM12 card. This object indicates whether a master endpoint has a persistent slave or not. A connection with a master and a non-persistent slave is considered a single-ended SPVC. This object is only meaningful when 'frMastership' contains the value of 'master(1)'. And this variable must be used with 'frMastership' to decide if a connection is single-ended or not. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

Remote Maximum Burst Size in terms of number of cells. This object should be set by the user in cases when the remote end of the connection is an ATM end-point where the Local MBS can be explicitly specified. In such cases, this element should be set to be equal to the remote end-point's local MBS. This object is not applicable to MGX Release 1.x.

OBJECT-TYPE

This variable contains the next UNUSED channel number of the possible 4000 (ranging from 16 to 4015). This number can be used in channel config table, the ChanNumNextAvailable gets updated if the number gets used to create a logical channel. A '0' indicates that no more channels are available. For FRSM12 Card: Not Supported

OBJECT-TYPE

The ABR config table is for logical channel interface (upto 4000 entries). The actual number of entries supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports 256 entries FRSM-8T1/E1 supports 1000 entries FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI supports 2000 entries FRSM-2CT3/HS2B-12IN1 supports 4000 entries FRSM12 supports 16000 entries

OBJECT-TYPE

An entry for logical channel

OBJECT-TYPE

Refers to the virtual connection index Note that the actual range of the index supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries) FRSM-8T1/E1 supports a range from 16..1015 (1000 entries) FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI supports a range from 16..2015 (2000 entries) FRSM-2CT3/HS2B-12IN1 supports a range from 16..4015 (4000 entries) For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = channel Number. Lower two bytes range from 16..16015 (16000 entries)

OBJECT-TYPE

Transient Buffer Exposure. The unit is number of cells.

OBJECT-TYPE

Fixed Round-Trip Time. The unit is milliseconds. Value 0 signifies that FRTT is not available.

OBJECT-TYPE

Rate Decrease Factor. This unitless value has to be inverted to arrive at the actual value. The valid values possible are only powers of 2; i.e. 1, 2, 4, 8 ..... 32768. The SNMP agent has to verify this compliance.

OBJECT-TYPE

Rate Increase Factor. This unitless value has to be inverted to arrive at the actual value. The valid values possible are only powers of 2; i.e. 1, 2, 4, 8 ..... 32768. The SNMP agent has to verify this compliance.

OBJECT-TYPE

Maximum number of cells a source may send for each forward RM cell. The valid values possible are only powers of 2 starting from 2; i.e. 2, 4, 8 ..... 256. The SNMP agent has to verify this compliance.

OBJECT-TYPE

Upper bound on the time between forward RM cells for an active source. The unit is in milliseconds.

OBJECT-TYPE

Cutoff Decrease Factor. This unitless value has to be inverted to arrive at the actual value. The valid values possible are 0 and only powers of 2; i.e., 1, 2, 4, 8, 16, 32, 64. The SNMP agent has to verify this compliance.

OBJECT-TYPE

ACR DecreaseTime Factor. Unit of this value is milliseconds. Granularity allowed is 10 milli seconds. The SNMP agent has to verify this compliance.

OBJECT-TYPE

Initial Cell Rate is the rate at which the source should send initially and after an idle period. This includes the bandwidth allocated for both data cells as well as all in-rate RM cells. Unit is cells/sec. The Range will be 10 to 400000. .

OBJECT-TYPE

Minimum Cell Rate is the rate at which the source is allowed to send. This includes the bandwidth allocated for both data cells as well as all in-rate RM cells. Unit is cells/sec. The Range will be 10 to 400000. .

OBJECT-TYPE

Peak Cell Rate is the rate at which the source is allowed to send. This includes the bandwidth allocated for both data cells as well as all in-rate RM cells. Unit is cells/sec. The Range will be 10 to 400000.

OBJECT-IDENTITY

OBJECT-TYPE

Table of transmit/receive states of channels.

OBJECT-TYPE

An entry for FrChannelStateGrpEntry.

OBJECT-TYPE

Refers to the virtual connection index Note that the actual range of the index supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries) FRSM-8T1/E1 supports a range from 16..1015 (1000 entries) FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries) FRSM-2CT3 supports a range from 16..4015 (4000 entries) For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = channel Number. Lower two bytes range from 16..16015 (16000 entries)

OBJECT-TYPE

This variable indicates the LMI state of the VC (channel) failed(4) is added to distinguish between alarm (when the connection in the PNNI n/w is not actually broken) and failed (when the connection in the PNNI n/w is actually broken). This is applicable only to the PNNI environment.

OBJECT-TYPE

The A bit transmit state 1 - LMI off 2 - LMI on and connection is O.K. 3 - LMI on and connection has failed

OBJECT-TYPE

The A bit receive state 1 - LMI off 2 - LMI on and connection is O.K. 3 - LMI on and connection has failed

OBJECT-TYPE

This variable indicates the transmit state of the VC (channel) on the ATM side 1 - Not sending any state 2 - Sending AIS OAM state 3 - Sending FERF OAM state

OBJECT-TYPE

This variable indicates the receiving state of the VC (channel) on the ATM side 1 - Not receiving any state 2 - Receiving AIS OAM 3 - Receiving FERF OAM

OBJECT-TYPE

This variable indicates the consolidated bit map of the channel alarm state. Individual bit positions are as defined below. Bit position Fail/Alarm Reason ------------ ---------- ------ 0 Alarm Reserved 1 Alarm n/w side AIS/RDI Rx 2 Fail Conditioned(A bit from n/w) 3 Alarm Reserved 4 Fail CC failed/RAS failed 5 Fail Mismatch 6 Alarm ingress A bit (LMI) 7 Alarm Reserved Fail bitmap mask : 0x34 Alarm bitmap mask: 0xCB This object is not applicable to MGX Release 1.x.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical channel interface there are upto 4000 entries.

OBJECT-TYPE

An entry for logical channel

OBJECT-TYPE

Refers to the virtual connection index Note that the actual range of the index supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries) FRSM-8T1/E1 supports a range from 16..1015 (1000 entries) FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries) FRSM-2CT3 supports a range from 16..4015 (4000 entries) FRSM12 supports a range from 16..16015 (16000 entries) For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = channel Number

OBJECT-TYPE

The number of frames Received on the ingress

OBJECT-TYPE

The number of bytes Received on the ingress

OBJECT-TYPE

The number of DE frames Received on the ingress

OBJECT-TYPE

The number of DE bytes Received on the ingress

OBJECT-TYPE

The number of frames discarded on the ingress

OBJECT-TYPE

The number of bytes discarded on the ingress

OBJECT-TYPE

The number of frames discarded on the ingress due to shelf alarm For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded on the ingress due to exceeded queue depth

OBJECT-TYPE

The number of bytes discarded on the ingress due to exceeded queue depth

OBJECT-TYPE

The number of frames discarded on the ingress due to exceeded DE Threshold

OBJECT-TYPE

The number of frames received with FECN bit already set

OBJECT-TYPE

The number of frames received with BECN bit already set

OBJECT-TYPE

The number of frames received that were tagged with FECN bit

OBJECT-TYPE

The number of frames received that were tagged with BECN bit

OBJECT-TYPE

The number of frames received that were tagged with DE bit

OBJECT-TYPE

The number of bytes received that were tagged with DE bit

OBJECT-TYPE

Received Average Information Rate in KBPS

OBJECT-TYPE

The number of frames transmitted

OBJECT-TYPE

The number of bytes transmitted

OBJECT-TYPE

The number of frames transmitted with FECN bit already set

OBJECT-TYPE

The number of frames transmitted with BECN bit already set

OBJECT-TYPE

The number of DE frames transmitted

OBJECT-TYPE

The number of DE bytes transmitted

OBJECT-TYPE

The number of frames discarded on the eggress

OBJECT-TYPE

The number of bytes discarded on the egress For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded on the egress due to exceeded queue depth For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of bytes discarded on the egress due to exceeded queue depth For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded on the egress due to exceeded DE Threshold For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded on the egress due to physical layer failure

OBJECT-TYPE

The number of frames discarded on the egress due to CRC Error

OBJECT-TYPE

The number of frames discarded on the egress due to reassembly failure For FRSM12 Card: Not Supported

OBJECT-TYPE

The number of frames discarded on the egress due to source abort

OBJECT-TYPE

The number of frames transmitted during LMI logical port alarm

OBJECT-TYPE

The number of bytes transmitted during LMI logical port alarm

OBJECT-TYPE

The number of frames transmitted that were tagged with FECN bit

OBJECT-TYPE

The number of frames transmitted that were tagged with BECN bit

OBJECT-TYPE

Transmitted Average Information Rate in KBPS

OBJECT-TYPE

Channel clear button. Clears Channel Counters.

OBJECT-TYPE

The number of frames transmitted which have been DE tagged at the far end ingress in excess of CIR

OBJECT-TYPE

The number of bytes transmitted which have been DE tagged at the far end ingress in excess of CIR

OBJECT-TYPE

The number of frames discarded at ingress due to the UPC measurement in excess of CIR+EIR

OBJECT-TYPE

The time in seconds the PVC stay in service

OBJECT-TYPE

Number of frames transmitted with invalid CPI header. currently valid is 0

OBJECT-TYPE

The number of frames discarded due to violation of length in the egress direction.

OBJECT-TYPE

The number of frames discarded because the size is beyond the max in the egress direction

OBJECT-TYPE

The number of frames discarded for Unknown protocol in the egress direction. Used only in SIW for PDUs that are dropped.

OBJECT-TYPE

Number of frames discarded for Unknown protocol in the ingress direction. Used only in SIW for PDUs that are dropped

OBJECT-IDENTITY

OBJECT-TYPE

Table of transmit/receive states of channels.

OBJECT-TYPE

An entry for FrEndPtMapGrpEntry.

OBJECT-TYPE

Refers to the logical port index For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port.

OBJECT-TYPE

Refers to the DLCI index

OBJECT-TYPE

Logical connection number 0 if port.dlci is a multicast group Note that the actual range of endChanNum supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 16..271 (256 entries) FRSM-8T1/E1 supports a range from 16..1015 (1000 entries) FRSM-T3/E3/HS2 supports a range from 16..2015 (2000 entries) FRSM-2CT3 supports a range from 16..4015 (4000 entries) For FRSM12 Card: Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = channel Number. Lower two bytes range from 16..16015 (16000 entries)

OBJECT-TYPE

Refers to the physical line index. Note that the actual range of endLineNum supported by a card depends on the type of card. eg: FRSM-4T1/E1 supports a range from 1..4 (4 entries) FRSM-8T1/E1 supports a range from 1..8 (8 entries) FRSM-T3/E3/HS2 supports a range from 1..2 (2 entries) FRSM-2CT3 supports a range from 1..56 (56 entries) For FRSM12 Card: The ifIndex of the physical line on which this channel is provisioned.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface there are 8 entries for either T1 or E1

OBJECT-TYPE

An entry for logical port. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This is logical port number. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This variable enables or disables the port 1 - disable 2 - enable

OBJECT-TYPE

This variable indicates whether UNI/NNI/STI interface STI mode is supported only in IMATM. vpTrkUni should be used only in IMATM when virtual trunks are passing through IMATM (i.e. the cell format is UNI but ForeSight information is carried in the lower 16 bits)

OBJECT-TYPE

This variable indicates the type of interface

OBJECT-TYPE

The speed of the port in cells per second

OBJECT-TYPE

The line number associated with the logical port. For AUSM (4 port), the line number is same as the logical port. In AUSM-8p, these two can be different

OBJECT-IDENTITY

OBJECT-TYPE

In AUSM (4port): the Service queue table has 64 entries, 16 each for every port, in addition there are 4 queues for OAM/ILMI traffic In AUSM (8-port), the Service queue table has 128 entries, 16 each for every port, in addition there are 8 queues for OAM/ILMI traffic

OBJECT-TYPE

An entry for a single queue

OBJECT-TYPE

Egress queue number. In AUSM (4 port), only range from 1..12 is permissible

OBJECT-TYPE

Logical port number to which egress queue is associated. In AUSM (4-port card), a logical port is same as a physical port. This is read only and queue mapping is as follows 1-16 port no 1 17-32 port no 2 33-48 port no 3 49-64 port no 4 For AUSM 8-port card, the following queue mapping is used in addition to the above: 65-80 port no 5 81-96 port no 6 97-112 port no 7 113-128 port no 8

OBJECT-TYPE

Egress queue state

OBJECT-TYPE

Egress queue number sequence in the priority list. In AUSM (4 port), range from only 1..12 is permissible

OBJECT-TYPE

The maximum depth of the egress queue. In AUSM (4 port), range from only 1..8000 is permissible

OBJECT-TYPE

High CLP threshold of the egress queue. In AUSM (4 port), range from only 1..8000 is permissible.This value should be less than or equal to egrQDepthMax.

OBJECT-TYPE

Low CLP threshold of the egress queue. In AUSM (4 port), range from only 1..8000 is permissible. This value should be less than or equal to egrQCLPThreshHigh.

OBJECT-TYPE

Threshold of the egress queue for EFCI. In AUSM (4 port), range from only 1..8000 is permissible.This value should be less than or equal to egrQDepthMax.

OBJECT-TYPE

The algorithm number for the Egress queue 1-5 are valid values 'ff'h is disable

OBJECT-TYPE

The increment for the Maximum carry for the queue. In AUSM (8 port), range from only 1..511 is permissible

OBJECT-TYPE

The increment for the minimum carry for the queue. In AUSM (8 port), range from only 1..511 is permissible

OBJECT-TYPE

this variable indicates the CLP state for the queue

OBJECT-TYPE

The number of cells discarded due to Egress Q full

OBJECT-TYPE

The number of CLP set cells discarded in Egress direction

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for upto 8 logical port interfaces

OBJECT-TYPE

An entry for a logical port. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

Refers to the logical port index. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This will set the signalling protocol 1 - other 2 - noSignalling 3 - ILMI

OBJECT-TYPE

indicates the VPI on which signalling cells arrive

OBJECT-TYPE

indicates the VCI on which signalling cells arrive

OBJECT-TYPE

Network Prefix for the ATM address

OBJECT-TYPE

for the INS as a read/write variable

OBJECT-TYPE

for the INS as a read/write variable

OBJECT-TYPE

Enable/disable ILMI Trap sending

OBJECT-TYPE

number of seconds between traps

OBJECT-TYPE

Enable/disable Keep Alive Polling

OBJECT-TYPE

Error Threshold (N491) value

OBJECT-TYPE

Event Threshold (N492) value

OBJECT-TYPE

Polling Interval (T491) value

OBJECT-TYPE

Minimum Enquiry Interval (T493)

OBJECT-TYPE

Enable/disable ILMI Address Registration

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for the IMA port (IMA group). There are 8 entries in all.

OBJECT-TYPE

An entry for every IMA port (total of 8 entries)

OBJECT-TYPE

This is the logical port number.

OBJECT-TYPE

This variable enables, disables or modifies the configuration of the port 1 - delport (Disables the entire IMA group) 2 - addport (Enables the IMA group) 3 - addlinks (Adds links to an existing IMA group) 4 - dellinks (Deletes links from an existing IMA group) 5 - modify (Modifies parameters in an existing IMA group) An IMA group is synonymous with an IMA port. To configure an IMA port, the different lines in the IMA port should be enabled and then the IMA port should be added using the enumeration 'addport'. To delete an IMA port, the enumeration 'delport' should be used. To increase the bandwidth of an IMA group, the enumeration 'addlinks' should be used. To decrease the bandwidth of an IMA group, the enumeration 'dellinks' should be used. 'modify' is used to change parameters other than links in the IMA group

OBJECT-TYPE

The speed of the port in cells per second. This depends on the nuber of links in the IMA group and the configuration of the physical interface on each link (eg: T1, Normal E1, Clear E1 etc).

OBJECT-TYPE

The number of links configured in the IMA group This is same as axisImaGroupNumTxCfgLnks in Forum Compliant Ima

OBJECT-TYPE

The list of links in the IMA group delimited by dots

OBJECT-TYPE

Period at wich LCP cells of the IMA protocol can be transmitted. A value of 32 indicates that after 32 cells, one LCP cell is transmitted on that link of the IMA group. Currently, the only value supported is 128 This has same meaning as axisImaGroupTxFrameLength in Forum Compliant Ima.

OBJECT-TYPE

The number of IMA frames for which an LCP cell on any link can be missed before the IMA state machine should remove the link from the IMA group. At present, this is hard-coded to 1 and is not programmable. Not supported in Forum Compliant Ima

OBJECT-TYPE

The difference between the read and write pointer of a link in the common cell buffer. A lower value reduces the latency in the common cell buffer but also increases the probability of an IMA group being stalled for a cell-time due to a slower link in the IMA group Not supported in Forum Compliant Ima.

OBJECT-TYPE

The degree of resiliency in the IMA group. This indicates the number of links the system can lose from this IMA group without bringing it down. By default, the system can tolerate {configured #links - 1} to go down. Not supported in Forum Compliant Ima.

OBJECT-TYPE

This indicates the maximum tolerable differential delay in milliseconds between the various links in the IMA group. The default value is variable and depends on the type of card with IMA feature: For AUSM-8p: 200 milliseconds for an IMA group consisting of E1 lines 275 milliseconds for an IMA group consisting of T1 lines. For IMATM: 50 milliseconds for an IMA group consisting of either T1/E1 lines. This is same as axisImaGroupDiffDelayMax of Forum Compliant Ima.

OBJECT-TYPE

This indicates whether the port is to be configured for UNI/NNI/STI mode. STI mode is supported only in the case of IMATM. vpTrkUni should be used only in IMATM when virtual trunks are passing through IMATM (i.e. the cell format is UNI but ForeSight information is carried in the lower 16 bits)

OBJECT-TYPE

The current cell rate(truncated value in cells per second) provided by the IMA group in the transmit direction, considering all the transmit links in the Active state. The generic formula for the link rate with N links active is : N * link Rate * (M-1)/M * (2048/2049), where M is the Ima Frame length. Suppose M = 128, then following are the link rates : In case of T1,for 8 lines the value is 28728 cells/sec. In case of Normal E1(for 8 Lines), the value is 35920 cells/sec. In case of Clear E1(for 8 Lines),the value is 38312 cells/sec.

OBJECT-TYPE

Symmetry of the IMA group. AsymmetricOperation,AsymmetricConfiguration are not supported.

OBJECT-TYPE

Minimum number of receive links required to be active for the IMA group to be in the Up state.At present since only symmetric configuration is supported,this should be equal to axisImaGroupMinNumTxLinks.

OBJECT-TYPE

Transmit clocking mode used by the near-end IMA group. ITC is not available in ausm8(B). Only default value (ctc) is supported.

OBJECT-TYPE

This indicates the 'alpha' value used to specify the number of consecutive invalid ICP cells to be detected before moving to the IMA HUNT state. Only default values are supported.

OBJECT-TYPE

This indicates the 'beta'value used to specify the number of consecutive errored ICP cells to be detected before moving to the IMA HUNT state. Only default values are supported.

OBJECT-TYPE

This indicates the 'gamma' value used to specify the number of consecutive valid ICP cells to be detected before moving to the IMA SYNC state from the PRESYNC state. Only default values are supported.

OBJECT-TYPE

The Number of links that are configured to receive in this IMA Group.

OBJECT-TYPE

This object is used to designate an interface as the test link. A value of -1 specifies that the implementation may choose the test link. In this case ,the implementation may also choose the value of axisImaGroupTestPattern.

OBJECT-TYPE

The value of this object is used to specify the test pattern in an IMA group loopback operation. A value in the range 0 to 255 designates a specific pattern. A value of -1 specifies that the implementation may choose the value. In this case,the implementation may also choose the value of 'axisImaGroupTestLinkIfIndex.

OBJECT-TYPE

This object is used to enable or disable the Test Pattern Proceudre,and to note whether at least one link failed the test. The test is started by setting operating(2) status.If any link should fail the test ,the IMA will set the status to linkfail(3).The linkfail(3) state will persist until either the disabled(1) state is set or until no instance of imaLinkTestProcStatus has the value linkfail(3). Only the values disabled(1) and operating(2) may be written. Writing the opersting(2) value will not cause clearing of the linkfail(3) state.

OBJECT-TYPE

Integration UP time for alarm integration.Persisting checking time to enter a failure alarm condition,in case of LIF,LODS,RFI-IMA fault failure alarms. Time in Milli Seconds.

OBJECT-TYPE

Integration DOWN time for alarm integration.Persisting clearing time to exit the LIF,LODS,RFI-IMA failure alarm conditions. Time in Milli seconds.

OBJECT-TYPE

Minimum number of transmit links required to be active for the IMA group to be in the Up state.Eventhough the range is 1..8,this value should be <= maximum number of configured links in IMA group.

OBJECT-TYPE

The Ima id used by the far end.

OBJECT-TYPE

Indicates the next logical port number (i.e. either ATM T1/E1 UNI or IMA port) that is available

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface there are 4/8 entries for either T1 or E1 or AIMUX ports For PXM (MGX), there are 32 entries.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is logical port number In PXM, a port refers to the Logical Broadband Interface. Refer bbIfCnfPortGrp.my for more information.

OBJECT-TYPE

Setting this object to 1 indicates that the resources (LCN/Local VPID/VCI/VPI) have been partitioned and INS and SV+ are currently using this information. The resource partition information can be changed after setting this variable to 2. The default value is 2 (NotInUse).

OBJECT-TYPE

Indicates whether or not the LCN and VPid address spaces are shared across all the ports. Default value is 2 (cardBased).

OBJECT-TYPE

The beginning of the LCN range reserved for SVCs. Both the LCN low and high values apply to all ports when the 'atmPortSvcShareLcnVpid' object is set to 2 (CardBased). When they are changed for one port the change is applicable/propagated to all ports.

OBJECT-TYPE

The end of the LCN range reserved for SVCs.

OBJECT-TYPE

The beginning of the VPID range reserved for SVCs. Both the VPID low and high values apply to all ports when the 'atmPortSvcShareLcnVpid' object is set to 2 (CardBased). When they are changed for one port the change is applicable/propagated to all ports.

OBJECT-TYPE

The end of the VPID range reserved for SVCs.

OBJECT-TYPE

The beginning of the VCI range reserved for SVCs. For VPI connections the valid VCI values are 0 - 4095

OBJECT-TYPE

The end of the VCI range reserved for SVCs. For VPI connections the valid VCI values are 0 -4095

OBJECT-TYPE

The beginning of the VCI range reserved for SVCs.

OBJECT-TYPE

The end of the VPI range reserved for SVCs.

OBJECT-TYPE

This represents Ingress Bandwidth reserved for SVC

OBJECT-TYPE

This represents Egress Bandwidth reserved for SVC

OBJECT-IDENTITY

OBJECT-TYPE

The table is for logical port interface there are 4/8 entries for either T1 or E1 or AIMUX ports For PXM (MGX), there are 32 entries.

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is logical port number In PXM, a port refers to the Logical Broadband Interface. Refer bbIfCnfPortGrp.my for more information.

OBJECT-TYPE

Setting this object to 1 indicates that all the SVC connections on the given port has to be deleted

OBJECT-IDENTITY

OBJECT-TYPE

The restart table is for the IMA port (IMA group). There are 8 entries in all.

OBJECT-TYPE

An entry for every IMA port (total of 8 entries)

OBJECT-TYPE

This is the logical port number.

OBJECT-TYPE

This variable restarts the Ima grp. We have the option of relearning the Ima id or retaining the stored ID.

OBJECT-IDENTITY

OBJECT-TYPE

The state table for the port interface there are 8 entries for either T1 or E1 or IMA.

OBJECT-TYPE

An entry for logical port. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This is logical port number. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This variable indicates the status of the port

OBJECT-TYPE

This variable indicates the whether the port is over subscribed or not

OBJECT-TYPE

Percentage Utilization of the Port in the Ingress direction.

OBJECT-TYPE

Percentage Utilization of the Port in the Egress direction.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical port interface there are 8 entries for either T1 or E1

OBJECT-TYPE

An entry for logical port

OBJECT-TYPE

This is the logical port number. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

The number of cells received in Ingress direction

OBJECT-TYPE

The number of cells received in Ingress direction with non zero-GFC

OBJECT-TYPE

The number of cells received in Ingress direction with unknown VpiVci

OBJECT-TYPE

The last unknown Vpi Vci value

OBJECT-TYPE

The number of cells transmitted in the egress direction

OBJECT-TYPE

The number of cells discarded due to port alarm

OBJECT-TYPE

The number of cells transmitted in Egress direction with CLP bit set

OBJECT-TYPE

The number of cells transmitted in Egress direction with EFCI bit set

OBJECT-TYPE

The number of AIS cells transmitted towards port

OBJECT-TYPE

The number of Segment Loopback cells transmitted towards port

OBJECT-TYPE

The number of AIS cells received in Ingress direction

OBJECT-TYPE

The number of FERF cells received in Ingress direction

OBJECT-TYPE

The number of Segment Loopback cells received in Ingress direction

OBJECT-TYPE

The number of OAM cells received in Ingress direction with CRC error

OBJECT-TYPE

writing a value of 2 resets all the counters

OBJECT-TYPE

The number of cells received from the port which had the CLP bit in the ATM cell header equal to 1.

OBJECT-TYPE

The number of cells out of the received cells from the port that were sent to the network. This count is taken after policing and ingress queueing.

OBJECT-TYPE

The number of cells received from the network in the egress direction

OBJECT-TYPE

The number of cells received per second from the port in the ingress direction. Maximum value is 5000 because because clear E1 rate is 4830.

OBJECT-TYPE

The percentage utilization of the port speed in the ingress direction.

OBJECT-TYPE

The number of cells received transmitted to the port in the egress direction.

OBJECT-TYPE

The percentage utilization of the port speed in the egress direction.

OBJECT-TYPE

The number of cells received per second from the network in the egress receive direction.

OBJECT-TYPE

The percentage utilization of the port speed in the egress receive direction.

OBJECT-TYPE

The total number of cells dropped on all the channels on this port because the the ingress Q was full. Adds up all the IngressQfull discard per channel statistics for all the channels in the port.

OBJECT-TYPE

This statistics provides a count of the number of times the AUSM card tried to send a cell, but was unable to send because the Transmit FIFO was full. Note that this is NOT a count of the number of cells dropped. This statistics is per card statistics. This counter is duplicated in channel count group to help monitoring.

OBJECT-TYPE

The total number of cells with CLP=1 dropped on all the channels on this port because of either PCR Exceeded, SCR exceeded (with CLP tagging disabled) or CLP Hysteris. Adds up all the IngressClpSet discard per channel statistics for all the channels in the port.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for physical port interface there are 8 entries for either T1 or E1 or IMA

OBJECT-TYPE

An entry for logical port. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

This is the logical port number.

OBJECT-TYPE

The number of snmp packets received

OBJECT-TYPE

The number of get request messages received

OBJECT-TYPE

The number of get-next messages received

OBJECT-TYPE

The number of set messages received

OBJECT-TYPE

The number of traps received

OBJECT-TYPE

The number of Keep Alive response messages received

OBJECT-TYPE

The number of response messages transmitted

OBJECT-TYPE

The number of Keep Alive get request messages transmitted

OBJECT-TYPE

The number of trap messages transmitted

OBJECT-TYPE

The number of invalid PDUs received

OBJECT-TYPE

The number of parse errors on ASN.1

OBJECT-TYPE

The number of errors for name not present

OBJECT-TYPE

The number of messages received with len > 484

OBJECT-TYPE

writing a value of 2 resets all the counters

OBJECT-IDENTITY

OBJECT-TYPE

The counter table is for the IMA groups (8 possible entries)

OBJECT-TYPE

An entry for the IMA group

OBJECT-TYPE

This is the logical port number. This object does not have any default value.

OBJECT-TYPE

This is the number of ICP cells received. This object does not have any default value.

OBJECT-TYPE

This is the number of errored ICP cells on this IMA group. This object does not have any default value.

OBJECT-TYPE

This is the number of ACP cells transmitted on this IMA group. This object does not have any default value. Not supported in Forum Compliant Ima.

OBJECT-TYPE

This is the number of ACP cells that could not be transmitted on this IMA group due to lack of resources (buffers). This object does not have any default value. Not supported in Forum Compliant Ima.

OBJECT-TYPE

This is the number of HEC errored cells received on all the links currently in the IMA group This object does not have any default value.

OBJECT-TYPE

This is the number of HEC errored seconds for the IMA group-- that is the number of seconds in which at least one link in the IMA group experienced a HEC error This object does not have any default value.

OBJECT-TYPE

This is the number of severely errored seconds received on all the links currently in the IMA group. A severely errored second for an IMA group is defined if the following condn is true: if (sigma (number of HEC errors of all links in IMA group) > (HEC_SE_COUNT * nlinks)) where HEC_SE_COUNT is defined as 10 This object does not have any default value.

OBJECT-TYPE

writing a value of 2 resets all the counters This object does not have any default value.

OBJECT-TYPE

The amount of time(in seconds) since this IMA group has been in opeartion(UP or DOWN.)

OBJECT-TYPE

Count of one second intervals where IMA group traffic state machine is down.

OBJECT-TYPE

The number of times a near-end group failure(Config-abort, Insufficient-Links) has been reported since power-up or reboot.

OBJECT-TYPE

The number of times a far-end group failure(config-abort-FE, Insufficient-links-FE,Blocked-FE) has been reported since power-up or reboot.

OBJECT-IDENTITY

OBJECT-TYPE

The state table for the IMA port interface: there are 8 entries for the 8 (maximum possible) IMA groups

OBJECT-TYPE

An entry for every IMA group

OBJECT-TYPE

This is the logical port number This object does not have any default value

OBJECT-TYPE

Indicates the state of the IMA port. The following error conditions are currently reported: 1 - Unconfigured state 2 - Active state 3 - Bandwidth changed due to addition/deletion of links. The addition/deletion can be triggered by either end 4 - FailedDueToACPTimeout (indicates that a timeout occurred due to non-arrival of an ACP cell) 5 - FailedDueToMajorAlarmOnIMAGroup (issued when the bandwidth of an IMA group falls below a certain threshold due to loss of links from an IMA group) 6 - FailedDueToImaSigFailure (this indicates configuration mismatch or non-arrival of LCP cells during set up of an IMA group) 7 - FailedDueToBadDiffDelay (indicates that the differential delay exceeded the maximum threshold) 8 - FailedDueToArbConflict (indicates that the IMA-ID could not be resolved between the 2 ends of the IMA pipe) 9 - Receiving Local OAM AIS from peer IMA node (valid only for network modules) 10- Receiving LOAM RDI from peer IMA node (valud only for network modules) 20- Failed due to ILMI signalling failure This object does not have any default value

OBJECT-TYPE

Indicates the number of links that are currently present in the IMA group. This object does not have any default value Same as axisImaGroupNumTxActLnks in Forum Compliant Ima.

OBJECT-TYPE

Indicates the list of links currently present in the IMA group. Different links in the IMA group are delimited by dots. The position of each link in the displayed string indicates the relative order of the links in the round-robin (multiplexing order) This object does not have any default value

OBJECT-TYPE

Indicates the IMA-ID in use at the remote end when sending LCP/ACP cells. Same as axisImaGroupRxImaId in Forum Compliant Ima . This object does not have any default value

OBJECT-TYPE

Indicates the IMA-ID in use at the local end when sending LCP/ACP cells. This is same as axisImaGroupTxImaId in Forum Compliant Ima This object does not have any default value

OBJECT-TYPE

Result of arbitration between the two ends of the IMA pipe. This object does not have any default value Retaining for the backward compatibility. Not supported in Forum Compliant Ima.

OBJECT-TYPE

The observed differential delay in milliseconds between the different physical links in the IMA group This object does not have any default value Same as axisImaGroupDiffDelayMaxObs in Forum Compliant Ima.

OBJECT-TYPE

This variable indicates whether the port is over-subscribed or not This object does not have any default value

OBJECT-TYPE

Percent Utilization of the IMA Port in the Ingress direction This object does not have any default value

OBJECT-TYPE

Percent Utilization of the IMA Port in the Egress direction This object does not have any default value

OBJECT-TYPE

The current cell-rate (truncated value in cells per second) provided by this IMA group in the receive direction,considering all the receive links in the active state.

OBJECT-TYPE

The current operational state of the far-end IMA group state machine 1) notConfigured : The Group doesn't exist.This is the GSM initial state. 2) startUp : On UM configuring the IMA group,GSM comes to this state. 3) startUpAck : On getting the Start-up-ack from FE(this info from received ICP cell. i.e. FE accepting the proposed group parameters by this END.), GSM goes to this state. 4) configAbortUnsupportedM : This state is entered when FE is not accepting the parameter M. 5) configAbortIncompatibleSymmetry : When Group symmetry is not supported by the FE,this group is entered. 6) configAbortOther : If any of the other group parameters are not supported by the FE,then this state is entered. 7) insufficientLinks : On getting one of the following events from FE, when GSM is in startUpAck state,GSM moves to insufficientLinks state. evens : 1) Start-up-ack 2) insufficient links 3) Blocked or operational 8) blocked : For to maintenance purpose,if group is blcoked (inhibited by UM),GSM goes to this state. 9) operational : When the group has sufficient links in both Tx and Rx directions GSM goes to this state.

OBJECT-TYPE

The current failure status of the IMA group(the reason why the GTSM is in the DOWN state. 1) noFailure : The group is UP. 2) startUpNe : When the NE GSM is in startUp state. 3) startUpFe : When the FE GSM is in startUp state. 4) invalidMValueNe : If FE doesn't support M value this end 5) invalidMValueFe : When the FE M value is not supported by NE. 6) failedAssymetricNe : If FE doesn't support Assymetric operation of the NE. 7) failedAssymetricFe : When the FE assymetry is not supported by the NE. 8) insufficientLinksNe: When the NE is in insufficient links state 9) insufficientLinksFe: If the FE is in insufficient links state and if that message is conveyed to this end by ICP cell. 10) blockedNe : If the GSM is in blocked state. 11) blockedFe : If the FE is in blocked state. 12) otherFailure: Start-up-ack and others.

OBJECT-TYPE

Transmit clocking mode used by the far-end IMA group.

OBJECT-TYPE

The IfIndex of the transmit timing reference link to be used by the near-end for IMA data cell clock recovery from the ATM layer.

OBJECT-TYPE

The IfIndex of the receive timing reference link to be used by the near-end for IMA data cell clock recovery toward the ATM layer.

OBJECT-TYPE

The time-of-day the IMA group last changed operational state( i.e. value of axisImaGroupNeState changed.) SPLAY-HINT 2d-1d-1d,1d:1d:1d.1d,1a1d:1d field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-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. This variable is not supported anymore in forum Ima.

OBJECT-TYPE

Value of IMA frame length as received from remote IMA function.

OBJECT-TYPE

The IfIndex of the link configured in the IMA group which has the smallest link propagation delay. This value has meaning only if at least 1 link has been configured in IMA group.

OBJECT-TYPE

The number of links which are configured to receive and are currently Active in this IMA group.

OBJECT-TYPE

The current operational state of the near-end IMA group state machine. 1) notConfigured : The Group doesn't exist.This is the GSM initial state. 2) startUp : On UM configuring the IMA group,GSM comes to this state. 3) startUpAck : On getting the Start-up-ack from FE(this info from received ICP cell. i.e. FE accepting the proposed group parameters by this END.), GSM goes to this state. 4) configAbortUnsupportedM : This state is entered when FE is not accepting the parameter M. 5) configAbortIncompatibleSymmetry : When Group symmetry is not supported by the FE,this group is entered. 6) configAbortOther : If any of the other group parameters are not supported by the FE,then this state is entered. 7) insufficientLinks : On getting one of the following events from FE, when GSM is in startUpAck state,GSM moves to insufficientLinks state. evens : 1) Start-up-ack 2) insufficient links 3) Blocked or operational 8) blocked : For to maintenance purpose,if group is blcoked (inhibited by UM),GSM goes to this state. 9) operational : When the group has sufficient links in both Tx and Rx directions GSM goes to this state.

OBJECT-TYPE

The number of IMA groups configured with the lines.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

This list contains ATM interface configuration parameters and state variables and is indexed by ausmInterfacePortNum values of ATM interfaces.

OBJECT-TYPE

This is logical port number. In AUSM, a logical port is same as a physical port.

OBJECT-TYPE

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.

OBJECT-IDENTITY

OBJECT-TYPE

The config table is for logical channel interface there are 1000 entries for the 8 logical ports in AUSM (8-port) and 256 entries for the 4 logical ports in AUSM (4-port card). In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

An entry for logical channel

OBJECT-TYPE

Refers to the virtual connection index. In AUSM (4-port card), valid range is from 16..271.

OBJECT-TYPE

This will add, delete or modify the channel 1 ==> ADD 2 ==> DELETE 3 ==> MODIFY Setting this object to outOfService takes the channel out of service or brings the channel 'down'. The channel can be brought 'up' again by setting the object to mod

OBJECT-TYPE

This specifies the connection type 1 ==> Virtual Path Connection 2 ==> Virtual Channel Connection

OBJECT-TYPE

This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 3 ==> Available Bit Rate 4 ==> Unspecified Bit Rate 5 ==> Real-Time Variable Bit Rate

OBJECT-TYPE

A string that has been defined to give a descriptive name to the connection

OBJECT-TYPE

This specifies the connection type 1 ==> SVC connection 2 ==> PVC connection 3 ==> SPVC connection 4 ==> connection added by PAR 5 ==> connection added by PNNI 6 ==> connection added by TAG

OBJECT-TYPE

This connection ID is for future use Currently not supported

OBJECT-TYPE

Refers to the logical port on the board to which logical channel is associated. In AUSM (4-port card), a logical port is same as a physical port.

OBJECT-TYPE

The VPI value for this channel

OBJECT-TYPE

The VCI value for this channel

OBJECT-TYPE

Selects one out of the 16 possible queues Each queue may have a different service algorithm

OBJECT-TYPE

This variable sets the max depth for queue, before it starts dropping the cells. In AUSM (4-port card), the valid range is from 1..8000.

OBJECT-TYPE

This variable sets the higher threshold for dropping CLP set cells in the ingress direction. In AUSM (4-port card), the valid range is from 1..8000.This value should be less than or equal to ingrQDepth. Default value depends on the ingrQDepth.

OBJECT-TYPE

This variable sets the lower threshold for dropping CLP set cells in the ingress direction. In AUSM (4-port card), the valid range is from 1..8000.This value should be less than or equal to ingrQCLPThreshHigh. Default value depends on the ingrQDepth.

OBJECT-TYPE

This variable indicates the CLP state for the channel

OBJECT-TYPE

This variable sets the efci threshold value for setting efci bit in the ingress direction. In AUSM (4-port card), the valid range is from 1..8000.This value should be less than or equal to ingrQDepth.

OBJECT-TYPE

enables/disables UPC for Ingress cells

OBJECT-TYPE

Peak Cell Rate for CLP [0+1] cells. The actual value depends on the speed of the logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's speed is variable and depends on the number of links in the port. In AUSM (4-port), maximum value is 4830.

OBJECT-TYPE

Complaint Information Rate. The actual value depends on the speed of the logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's speed is variable and depends on the number of links in the port. In AUSM (4-port), maximum value is 4830.

OBJECT-TYPE

Complaint Cell Delay Variation for all cells

OBJECT-TYPE

Complaint Burst Size The unit of this parameter is in terms of number of cells. CBS is applicable only for VBR and ABR connections. In MGX switches, release 3.0.0.0 and above, the default value is 1024

OBJECT-TYPE

Initial Burst Size. The Burst size allowed for a connection that has been idle for some time. The unit of this parameter is in terms of number of cells. IBS is applicable only for VBR and ABR connections. IBS value should be less than CBS for VBR and ABR connections. IBS value will be ignored for other service types.

OBJECT-TYPE

Maximum Frame Size

OBJECT-TYPE

selects SCR policing for CLP = 0 or all cells

OBJECT-TYPE

Peak Cell Rate for CLP=0 cells. The actual value depends on the speed of the logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's speed is variable and depends on the number of links in the port. In AUSM (4-port), maximum value is 4830.

OBJECT-TYPE

Complaint Cell Delay Variation for CLP=0 cells

OBJECT-TYPE

enables/disables CLP tagging for Ingress cells

OBJECT-TYPE

enables/disables Frame based GCRA

OBJECT-TYPE

enables/disables Foresight

OBJECT-TYPE

Minimum Information Rate. The actual value depends on the speed of the logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's speed is variable and depends on the number of links in the port. In AUSM (4-port), maximum value is 4830.

OBJECT-TYPE

Peak Information Rate. The actual value depends on the speed of the logical port (which can be a T1, E1 (normal), E1 (clear), IMA T1, IMA E1 (normal) or IMA E1 (clear) port. Note that the IMA port's speed is variable and depends on the number of links in the port. In AUSM (4-port), maximum value is 4830.