OPTIMUX-MIB: View SNMP OID List / Download MIB

The events for the WAN V5.1.

This trap is sent when the Active Variant of a Link is changed (that includes the case when a user performs Save to the Variant that is Active).

NPL Mode.

National Protocol Country.

Maximum time of a voice path, in msec.

NPL Pulse table. This table is written directly to the agent.

An entry in table nplPulseTable.

Pulse Type

Validity of the Pulse Type.

Pulse Duration Type. - If meteringPulse1 and meteringPulse2 are both valid, the value of this object must be different for them. - If initRinging1 and initRinging2 are both valid, the value of this object must be different for them.

How much time the pulse is ON, in msec. 0 is a valid value only when nplPulseValid=notValid.

How much time the pulse is OFF, in msec.

The write operation into the Table Objects is valid only to the TmpCnfg entry.

An entry in table v51VarTable.

This attribute indicates the Idx of the Cnfg being accessed. 255 = TmpCnfg. 1 = Current Cnfg. Write is allowed only to TmpCnfg.

Slot Index. For V5.2, this index will be the Slot of the V5.2 Master ML.

This attribute indicates a unique port number of the ML having V5 interface. Valid values: exPrt1 (1)..exPrt4 (4), inPrt1(101)..inPrt4(104), notApplicable(255) - for V5.2 only.

Variant Id. Valid values: - for Current Cnfg: 0..127 - for Tmp Cnfg: until MP R9 : 255 only. from MP R10: 0..127.

This object indicates which TS will be used for PSTN C channel. For V5.2 - notApplicable.

This object indicates which TS will be used for S-Type C channel. For V5.2 - notApplicable.

This object describes the Variant.

This object reports the status of an existing Variant of a link. notActive - the variant exists on this link but is not active active - the variant exists on this link AND is active activeReq - the variant exists on this link and it was requested to be active, but the request is still in negotiation (it can be either accepted as active, or not). This object is not applicable for v51VarCnfgIdx=255=TmpCnfg.

This object enables to create new entries and delete existing entries from the table. It is applicable only from MP R10.

The write operation into the Table Objects is valid only to the TmpCnfg entry.

An entry in table v51VarCfgTable.

This attribute indicates the Idx of the Cnfg being accessed. 255 = TmpCnfg. 1 = Current Cnfg.

Slot Index. For V5.2, this index will be the Slot of the V5.2 Master ML.

This attribute indicates a unique port number of the ML having V5 interface. Valid values: exPrt1 (1)..exPrt4 (4), inPrt1(101)..inPrt4(104) notApplicable(255) - for V5.2 only.

Variant Id. Valid values: - for Current Cnfg: 0..127 - for Tmp Cnfg: until MP R9 : 255 only. from MP R10: 0..127.

For V5.1: Time Slot index (1..31). For V5.2: Running Index (1..1320) for Address Table.

Time Slot Type.

This object indicates the IO Port Id this TS is connected to. For V5.2, the Port Id is a concatenation of SS:PP:TS of the port connected to V5.2 Master. SS=IO Slot (1..12) PP=Port (01..04) TS = TS (00 for ports that dont have TSs ..31). Example: 50327 means IO-5, port-3, TS27.

This object indicates the Address of the IO port this TS is connected to. The IO port is identified according to its Address: - for ISDN ports: EF Address. Valid values: 0..8175 - for PSTN ports: L3 Address. Valid values: 0..32767 65535=notApplicable (FFFF).

For V5.1 - this object indicates which TS will be used for F-Type C channel. notApplicable (1), ts15 (2), ts16 (3), ts31 (4) For V5.2 - this object indicates the Logical C Channel F Type (0..65535). 65536=not applicable in this case.

For V5.1 - This object indicates which TS will be used for P-Type C channel. notApplicable (1), ts15 (2), ts16 (3), ts31 (4) For V5.2 - this object indicates the Logical C Channel P Type (0..65535). 65536=not applicable in this case.

The Slot containing the IO port this TS is connected to. For V5.2 this object is notApplicable.

The IO Port this TS is connected to. Valid values: exPrt1 (1)..exPrt12 (12), inPrt1(101)..inPrt4(104). 100=noConnect For V5.2 this object is notApplicable=255.

The State of the IO port this TS is connected to. This object is not applicable for v51VarCfgIndex=255=TmpCnfg. normal(2) - will be used for operating normally (operate) localBlocked(5) - will be used for general Block state

This object indicates if this TS will be Blocked or not and how: block - done locally blockRequest - according to external request of the telephone exchange.

For V5.1: This object indicates if this TS is an ISDN D channel that comes via Bypass from a non-V5.1 ML. For V5.2: this object will be notApplicable (not supported).

This object is applicable only if v51VarCfgExtDch=yes(3). It indicates the Slot of the non-V5.1 ML on which the External D channel TS is defined (and is transferred via Bypass between the V5.1 ML and the non-V5.1 ML.) Not Applicable for V5.2 (it is part of Port Id).

This object is applicable only if v51VarCfgExtDch=yes(3). It indicates the Port on the Slot of v51VarCfgExtDchSlot of the non-V5.1 ML on which the External D channel TS is defined (and is transferred via Bypass between the V5.1 ML and the non-V5.1 ML.) Valid values: exPrt1 (1)..exPrt4 (4), inPrt1(101)..inPrt4(104). 100=noConnect. Not Applicable for V5.2 (255; it is part of Port Id).

This object is applicable only if v51VarCfgExtDch=yes(3). It indicates the TS on the non-V5 ML on which the External D channel TS is defined (and is transferred via Bypass between the V5 ML and the non-V5 ML.) For V5.1: 0=notApplicable For V5.2: 0=None, 32=notApplicable.

For V5.1 - this object is applicable only if v51VarCfgExtDch=yes(3). It indicates if this ISDN D channel TS is Compressed or not.

For V5.1 - this object is applicable only if v51VarCfgExtDch=yes(3). It indicates the Rate of the ISDN D channel.

For V5.1 - this object is applicable only if v51VarCfgExtDch=yes(3). It indicates the Start Bit of the ISDN D channel on the TS of the non-V5.1 ML on which it is defined. Valid values: - for v51VarCfgExtDchRate=twoBits(2): 1, 3, 5, 7 - for v51VarCfgExtDchRate=fourBits(3): 1, 5 - for v51VarCfgExtDchRate=eightBits(4): 1 - 0=notApplicable

This object is supported only by V5.2. It indicates the Logical C Channel S Type (0..65535). 65536=not applicable.

This object is supported only by V5.2. It enables to create new entries and delete existing entries from the table.

This object is supported only by V5.2. This will be the V5.2 Master, Switch Allocated Location. It is a concatenation of SS:PP:TS of the V5.2 Master. It indicates which is the exact port and TS allocated by the Local Exchange on the V5.2 Link. SS=IO Slot (1..12) PP=Port (01..04) TS = TS (1..31). Example: 50323 means IO-5, port-3, TS23.

The write operation into the Table Objects is valid only to the TmpCnfg entry.

An entry in table v5VarCchTable.

This attribute indicates the Idx of the Cnfg being accessed. 255 = TmpCnfg. 1 = Current Cnfg.

Variant Id. Valid values: 0..127.

C-CH Id. There are only 8 possible C-CHs per Variant.

C-CH Type.

The Physical Link Number of the card (1..4). This object is applicable only if v51VarCchType is not none. notApplicable=255.

The Logical C-CH Id. (0..65535) When v51VarCchType is none, this object is irrelevant.

The C-CH TS. Valid values: 16, 15, 31. If v51VarCchType=primary or secondary, the value must be 16 (RO). This object is applicable only if v51VarCchType is not none. notApplicable=0.

PSTN C-CH. Only one entry can have the value yes. notApplicable - when v51VarCchType is none, secondary or standby.

ISDN Types of C-CH. This object is a sum of 2**n, where n=Bit No. and Bit is 1: Bit No. ISDN Type 0 P 1 F 2 S Bit value 1= Yes Bit value 0= No Example: P=No, F=Yes, S=Yes (110H) will have the value 6. Each Type is NA (notApplicable) when v51VarCchType is none, secondary or standby. There is no special value for it, since each type can have only 2 values (1 or 0). When this object is NA, Agent will not refer its value (dont care).

This is a RO table. It includes only the Active Addresses of the Active Variant, their minimal Config data and Status.

An entry in table v5VarStatTable.

Running Index (1..120). Up to 120 calls can be active at the same time on the Active Variant.

This object indicates the IO Port Id, the Address is connected to. The Port Id is a concatenation of SS:PP:TS of the port connected to an Address of the Active Variant running on the V5.2 Master card. SS=IO Slot (1..12) PP=Port (01..04) TS = TS (00 for ports that dont have TSs ..31). Example: 50327 means IO-5, port-3, TS27.

Address Port Type.

This object indicates the EF/L3 Address of the IO port this entry is connected to. The IO port is identified according to its EF/L3 Address: - for ISDN ports: EF Address. Valid values: 0..8175 - for PSTN ports: L3 Address. Valid values: 0..32767 65535=notApplicable (FFFF).

The State of the IO port this Address entry is connected to. The values were designed to match the relevant values of v51VarCfgIoState.

This will be the V5.2 Master Switch Allocated TSA Location. It is a concatenation of SS:PP:TS of the V5.2 Master card. It indicates which is the exact port and TS allocated by the Local Exchange on the V5.2 Link. SS=IO Slot (1..12) PP=Port (01..04) TS = TS (1..31). Example: 50323 means IO-5, port-3, TS23.

Call State of the Address.

Variant Command and Status table.

An entry in table v51MlTable.

Slot Index. For V5.2 this index is notApplicable.

This attribute indicates a unique port number of the ML having V5 interface. Valid values: exPrt1 (1)..exPrt4 (4), inPrt1(101)..inPrt4(104), notApplicable(255) - for V5.2 only.

For V5.1: the currently Active Variant Id. on this ML. For V5.2: the currently Active Variant Id. 128=none.

For V5.1: the Variant Id. that the Local Exchange (LE) requested to be Active on this ML. For V5.2: the Variant Id. that the Local Exchange (LE) requested to be Active. 128=none.

Protocol State of the ML Active Variant. - sysStartUp - an Establish request arrived to the V5.1 interface. - waitForVarId - the variant and the Interface Id were requested during the system start-up procedure. - activatePstn - activation of the PSTN Data Link was requested during the system start-up procedure. - restart1 - the PSTN restart procedure is in process. - inService - the V5.1 interface is IN SERVICE. - restart2 - the V5.1 is in AN5 state (sends restart complete to all PSTN protocols and changes status to In-Service). - restart3 - the V5.1 is in AN6 state (sends restart complete to all PSTN protocols and changes status to In-Service). - waitV5Init - this state is entered when the systems management is in In-Service state, Switch to a new Variant is received and V5.1 interface will not be restarted. - switchOver - this state is entered when the systems management is in In-Service state, Switch to a new Variant is received and V5.1 interface will be restarted. - ctrlDataLinkRel1 - this state is entered when the systems management is in In-Service state and Release Indication is received. Timer TC1 is running in this state. - ctrlDataLinkRel2 - this state is entered on reception of Release-Indication in restart3 state. - outOfService - the V5.1 interface is Out-of-Service. - notDefined - V5.1 is not defined for this interface.

User Request to turn a certain Variant of the ML, to Active. This object specifies the Variant Id. requested by user to be Active. Users request is not always accepted.

For V5.1: User Request to Delete a certain Variant of the ML. For V5.2: User Request to Delete a certain Variant This object specifies the Variant Id. requested by user to be Delete. Users request will not be accepted if the required Variant Id is Active or during Reprovision process. This object is supported only up to MP R9.

User Command to Save the TmpCnfg Variant data to a certain Variant Id of the selected ML, in Current Cnfg. The value of this object specifies the target Variant Id. The data transferred should be: - for V5.1: v51VarTable and v51VarCnfgTable parameters. - for V5.2: v51VarTable, v51VarCnfgTable and v51VarCchTable parameters. Upon Set command, the MUX will initiate a Sanity-Check process first: - If successful, the actual transfer will be performed. - If warnings are detected, the user will have to perform the command again to confirm the operation. - If errors are detected, transfer will NOT be performed. This object is supported only up to MP R9.

User Command to Read data from a certain Variant Id of the selected ML, (in Current Cnfg) to the TmpCnfg. The value of this object specifies the source Variant Id. The data transferred should be: - for V5.1: v51VarTable and v51VarCnfgTable parameters. - for V5.2: v51VarTable, v51VarCnfgTable and v51VarCchTable parameters. The operation is valid only on existing Variants of the ML. This object is supported only up to MP R9.

User Request to Deactivate a certain Variant of the ML. This object specifies the Variant Id. requested by user to be Deactivated. User can deactivate a variant having Active Request status or Active status. Deactivating the variant having Active Status wil stop the V5.1 operations on this link (for V5.2 it will stop completely the V5 activity).

The write operation into the Table Objects is valid only to the TmpCnfg entry.

An entry in table v51MlCnfgTable.

This attribute indicates the Idx of the Cnfg being accessed. 1..10 = Current Cnfg (data will be the same for all Current Configurations) 255 = TmpCnfg.

Slot Index. For V5.2 this index will be notApplicable(255).

This attribute indicates a unique port number of the ML having V5 interface. Valid values: exPrt1 (1)..exPrt4 (4), inPrt1(101)..inPrt4(104) NA=255 (for V5.2 only).

V5.1 Interface Id.

Startup Mode.

Reprovision Support. - no : no reprovision support (=default) - yes: reprovision is supported.

Unblock IO Ports on Startup. - disabled - disable sending Unblock request on restart - enabled - request unblock of all IO ports ON RESTART (=default).

Send Restart Complete. - uponLeRestart - after receiving restart from the other side. - uponPstnProtocolAck - after receiving restart ack from PSTN protocol (=default).

The V5.2 Application of the Mux. notApplicable - for Agents that dont support this object. none - V5.2 is not used in the Mux. endPoint - this V5.2 Application transfers voice of Analog Voice and ISDN cards of the Mux, to/from V5.2 Local Exchange. exchangePoint - this V5.2 Application exchanges voice of ML cards (coming from other devices) to/from V5.2 Local Exchange.

The write operation into the Table Objects is valid only to the TmpCnfg entry.

An entry in table v51IoCnfgTable.

This attribute indicates the Idx of the Cnfg being accessed. 1..10 = Current Cnfg (data will be the same for all Current Configurations) 255 = TmpCnfg.

Slot Index

This attribute indicates a unique port number of the Io having V5 interface. Valid values: exPrt1 (1)..exPrt16 (16)

This object indicates if S Type Signaling will be used by this ISDN port (yes/no). notApplicable - for PSTN ports.

This object indicates if F Type Signaling will be used by this ISDN port (yes/no). notApplicable - for PSTN ports.

This object indicates if P Type Signaling will be used by this ISDN port (yes/no). notApplicable - for PSTN ports.

Channels Configuration Table.

Application layer configuration per link

The channel index, which is actualy the bundle ID.

This parameter allows NMS to create/delete entries of this table.

The actual link status. remoteFail - No Rx. localFail - No Tx. unavailable - No echo replay or replay with invalid code or when connection is in Test state. valiodationFail - Connection is in not valid state. standby - offline (can be in pre-sync mode). tdmFail - oper status is down cause of failure in the tdm. hwMismatch - the bundle exists on a card that is not installed or has a different type than the programmed card.

The desired state of the link.

The destination IP address.

The next hop to which the frame should be sent. Default value - 0.0.0.0. Upon setting the default value the frame is sent to the default Gateway.

The destination Bundle at the far-end device.

The Destination MAC address of the next hop or destination station.

The maximum cell arrival jitter in 10 usec that the reassembly process will tolerate in the cell stream, without producing errors on the CBR service interface. Default value - 100. For KM2100: KML.11 - The range that will be used is 3...300 msec in steps of 1 msec. For Vmux: The range that will be used is 20...300 msec in steps of 10 msec.

The TOS (Type of Service) value: 0..255.

The number of TDM bytes to be placed in a single IP frame payload.

VLAN support (Tagging). no - No support to VLAN. yes - 4 VLAN bytes will be added to the frame.

VLAN ID.

VLAN Frame priority.

This object determines to which external port the traffic will be sent. auto - the device will decide automatically the exit port. If there is an option for Tx via more than one ETH card then use ext1 (1) and ext2(2) for ETH card #1 (ex. LAN1 or Ggabit-ETH1) and use card2Ext1(5) and card2Ext2(6) for card #2 (ex. LAN1 or Ggabit-ETH1). In Vmux-110 ext5 is used for ETH-NET, ext7 is used for Serial Link.

Voice Out-Of-Service code. Valid range: (0 - FF HEX). For agents that do not support this feature, the value will always be 0.

Data Out-Of-Service code. Valid range: (0 - FF HEX). For agents that do not support this feature, the value will always be 0.

The Bundle Resource usage in Kbps.

This parameter determine the OAM configuration. The LSB (Bit 0 the most right one) is used for OAM connectivity. Values: 0 = disable, 1= enable.

The TDMoIP Mode configuration. Static- means TS can Tx any time. dynamicLES - means TS can Tx only when line is enabled according to LES protocol. dynamicCAS - means TS can Tx only when line is enabled according to CAS protocol. cesOverIp - use for information that this bundle is used for CES Over IP. voiceOverMpls - Voice over Multi Protocol Label Switching.

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

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

This object defines the type of the Far-End device. This data is important for signaling.

This object defines the role this bundle plays in the redundancy scheme: none(2) - means this bundle is not part of redundancy pair. primary/ secondary - means this bundle is not part of redundancy pair, and that is the primary bundle or the secondary bunle.

Source IP Address of the bundle.

Number of Time Slots in The Bundle. For T1 the value will be: 1..24 For E1 the value will be: 1..31 For T3 the value will be: 1..84 For E3 the value will be: 1..63 This parameter is required for devices like Emux where the bandwidth of the bundles is unknown. The bundles that are received should be transmitted without any change in the bandwidth. It is the users responsibility to enter the correct bandwidth.

This object shows the percentage of Silence that was measured by the device for the current bundle. Relevant values: 0..100, 255. Default value is 50. 0 means that there is no silence on the line. 100 means that there is only silence. In this case, there might be no traffic. 255 - value for not applicable or unknown.

This object defines the TDMoIP payload type.

This object defines the TDMoIP protocol Version.

Defines the TDM bundle default router in case there was a switch from the Primary Link (for example an ETH port) to a TDM backup Link like E1, T1 or Serial Link. This parameter is relevant only when a Backup Link is configured. When a Backup Link is not configured the value will be: 0.0.0.0

This object defines whether OOS will be Transmitted. Note that for IPmux1000 the Lbit is always sent, but the OOS will be sent according to user selection in this parameter.

Time in sec. between 2 Bundle Connectivity Check packets. Valid values: 0..60. 0 = Not Applicable.

No. of cycles the agent will send Bundle Connectivity packets without receiving a response from the remote device before declaring that the bundle connection to the remote side is down - Time Out. Valid values: 0..5. 0 = Not Applicable.

Multi Frequency Signaling Detection.

Transmit gain in dBm.

The Super Tandem feature provides end to end compression over multiple hops, solving the double compression problem detected in Voice compressing systems. The Super Tandem allows transmission of compressed voice between a few Vmux 2100 hubs, and eliminates the need to decompress an recompress it over each voice card and PBX, thus improving voice quality and reducing delay.

The source Bundle at the local device, this parameter used for cases where there is no match between ip2IfChannelIndex and the Source Bundle ID.

This MIB object shows whether Modem Calls are enabled via the bundle. relay option (3) means that the bundle will send to the network only modulated data.

Indicates the minimum width in milliseconds of the MF (Multi Frequency) tone transmitted by the switch. Valid values: 45-300 msec. notApplicable=0.

Indicates the minimum power level in dBm of the MF (Multi Frequency) tone transmitted by the switch. Valid values: -1...-35 dBm.

Echo canceler activation.

This attribute indicates the Method/Law for decoding/encoding the voice information. aLaw(1) is the standard Law for E1 links. uLaw(2) is the standard Law for T1 links.

Custom Tone Detection (COT) is a Control operation of a 2Khz tone detector. This tone is sent between PBX devices in order to check that the line status is OK. When the COT is enabled the device will not compress/decompress the tone. In this case, if the tone is initiated by the local PBX, the Device runs a 2Khz detector tone and once detected by the Remote Device, if the COT is enabled in the Remote Device, the Remote Device will generate a 2khz tone to the remote PBX.

Time in msec between CLID (Caller ID) signal detection on the line and CLID signal transmission. The CLID must be sent between ringing signals and the value of the delay is used for synchronizing the CLID transmission with the ringing signals transmission. Valid values: 0 - 3000 msec.

This MIB object shows whether to send Pings or OAM frames over the bundle.

This MIB object defines whether the MFC (Multi Frequency Compelled) protocol spoofing will exist in the bundle. When the MFC Spoofing is used, the Local and Remote PBXs will send MFC Signaling to each other. The Vmuxes between the PBXs will send proprietary signaling to each other. They will however create and send MFC tones to their local PBX. The PBXs will not know that the actual signaling was not sent from a PBX but from a Vmux.

Time Interval in milli seconds from the time a Vmux sends tone/s to a local PBX until it receives an acknowledgement from this PBX. Valid values: 60...400 in steps of 20. Default: 80.

This object defines the Level of Noise on the line, the Voice Activation Detector (VAD) will have to handle.

The number of TDM bytes to be placed in a single IP frame payload.

The TOS value to write in the IP frame.

VLAN support. no - No support to VLAN. yes - 4 VLAN bytes will be added to the frame.

VLAN ID.

Frame priority.

Channels (Bundles) Statistics Table.

IP Statistics per bundle

The channel index, which is actualy the bundle ID.

Number of times that the sequence number of an incoming Frame causes a transition from the sync state to the out of sequence state.

Number of buffer underflows. This records the count of the number of times the Receive (Eth to TDM) buffer underflows. In the case of a continuous underflow caused by a loss of Frame flow, a single buffer underflow should be counted.

Number of buffer overflows. This records the count of the number of times the Receive (Eth to TDM) buffer overflows.

Number of frames that were transmitted due to time interval elapse. The user can choose to Tx the Frame when it reaches the Max size or when the packetizing time interval elapses. The packetizing time interval is the interval in msec that it takes to build a Max. size frame.

Number of frames that were transmitted due to reaching max. frame size. The user can choose to Tx the Frame when it reaches the Max size or when the packetizing time interval elapses.

Number of signaling frames that were received.

Number of voice frames that were received.

Number of HDLC frames that were received.

Number of signaling frames that were transmitted.

Number of voice frames that were transmitted.

Number of HDLC frames that were transmitted.

Number of redundancy flips occured. This parameter counts only flips from this bundle to the other bundle in the redundancy couple.

The maximum rate permitted to transfer via the network portin Mbps.

Port Table.

Application layer configuration per Port

The Port index, which is actualy the ifIndex.

This parameter indicates the usage of the port (percents).

This parameter defines whether Agent will mask ports alarms and statistics or not.

This parameter indicates the total Throughput of the port in bps.

Channels (Bundles) Current Statistics Table.

IP Current Statistics per bundle

Number of times that the sequence number of an incoming Frame causes a transition from the sync state to the out of sequence state in the current interval.

Number of buffer underflows in the current interval. This records the count of the number of times the Receive (Eth to TDM) buffer underflows in the current interval. In the case of a continuous underflow caused by a loss of Frame flow, a single buffer underflow should be counted.

Number of buffer overflows in the current interval. This records the count of the number of times the Receive (Eth to TDM) buffer overflows in the current interval.

The maximum size of the buffer (in 10s of usec) for the current interval.

Channels (Bundles) Interval Statistics Table.

IP Interval Statistics per bundle

The Interval index, which is actualy the Interval number.

Number of times that the sequence number of an incoming Frame causes a transition from the sync state to the out of sequence state in the selected interval.

Number of buffer underflows in the selected interval. This records the count of the number of times the Receive (Eth to TDM) buffer underflows in the selected interval. In the case of a continuous underflow caused by a loss of Frame flow, a single buffer underflow should be counted.

Number of buffer overflows in the selected interval. This records the count of the number of times the Receive (Eth to TDM) buffer overflows in the selected interval.

The maximum size of the buffer (in 10s of usec) in the selected interval.

This parameter defines whether all Jitter Buffer and Sequence Number events will enter to Log File, or enter those events to Log file in one minute steps.

This parameter defines whether Eth Switch is in VLAN Tagged mode.

The value of this object determines the VOIP card configuration. Bit 0 (LSB): if 1 - a GK exists. If 0 - no GK exists in this card. The other bits may be used in the future.

General parameters for the VOIP GateKeeper.

An entry in table gkGenTable.

This parameters shows whether the calls will go through the GK (routed) or whether the calls will be direct from Endpoint to Endpoint without involving the GK (direct).

MAX no. of connections enabled by the GK to take place simultaneously. If the MAX no. of calls is exceeded, a busy signal will be returned.

The Distance allowed for endpoints that are registered dynamically.

The Distance allowed for an out of zone endpoint that is making a call through the gatekeeper.

Defines the policy concerning the incoming phone calls. The importance of this parameter is for bidding and security matters. Accept All - all the incoming calls are accepted. Registered Only - the calls are accepted from the predefined endpoints only, which are endpoints that have previously registered with the gatekeeper. Predefined Only - with this policy only the calls from the statically registered endpoints can be accepted.

In order for the Gatekeeper to determine if an endpoint is turned off, or has otherwise entered a failure mode, the Gatekeeper may use the Information Request (IRQ) to poll the endpoints at the certain interval (in seconds). THE IRQ INTERVAL controls the frequency the gk sends IRQ messages. This message is sent to all on-line endpoints registered as dynamic in order to verify they are really on-line. This is done to detect terminals that shut off without sending the required URQ message that notifies the gk that they are no longer on-line. Endpoints failing to respond too many times have their dynamic properties unregistered. Choosing the desired interval should take into account the following factors : IRQ messages add to the traffic already present over the network and the shorter the interval the more IRQ messages will be sent. On the other hand the longer the delay the longer it will take for the gk to detect dynamic registrations that have ceased to actually be on-line. Note that the IRQ interval relates to each endpoint and the actual number of the IRQ messages the gk will create should be multiplied by the number of endpoints registered dynamically.

Q.931 Port no.

RAS Port no.

Policy of dynamic registrations in the Gatekeeper. The GK will act according to the following policies: Accept All - The GK will enable all requesting endpoints to register dynamically. Predefined Only - The GK will enable registration of endpoints that were registered previously via static registration. Registration Reject - No endpoint may register dynamically.

Zone Identifier: 1 or 2 digits, (0-9)(1-9).

Table containing the Endpoints that are registered (statically & Dynamically) with the current GK.

An entry in table gkEndpTable.

Alias Tag of the Endpoint.

Alias of the Endpoint.

The row status of the entry. This object is required to create or delete rows remotely by a manager.

Address Tag of Endpoint.

Address of Endpoint.

Endpoint Identifier.

This parameter shows whether the current endpoint is a GW or Terminal or any other type of H.323 endpoint.

Q.931 Port no.

Distance from the current endpoint to the GateKeeper with which it is Registered.

This parameter shows whether the Endpoint Registered Dynamically or Statically.

This parameter shows whether the endpoint will always be online or whether it will be on line upon Dynamic Registration only.

This parameter shows whether the endpoint is currently online.

Table of GateKeepers that are Neighbors of the current Gatekeeper.

An entry in table gkNeighbTable.

Tag of GK or GW address.

Address of GK or GW.

The row status of the entry. This object is required to create or delete rows remotely by a manager.

This is the Leading Alias Address (Zone Prefix) that will be dialed in order to reach the specific neighbor.

Distance between the local GateKeeper and the Neighbor GateKeeper.

ASCII String Description for identifying the Neighbor.

General parameters for the VOIP GateWay.

An entry in table gwGenTable.

A character string of up to 20 characters identifying the gateway.

The Q.931 port no. of the Gateway.

The RAS port no. of the Gateway.

GW Mode: disable - The GW is not activated. cvsIp - CVS is a Compressed Voice System. The GW will compress voice calls at a ratio of 16 to 1. 16 time slots of E1/T1 will be compressed into 1 E1/T1 time slot. When this mode is used the Gateway can communicate directly with another Gateway without a Gatekeeper. standard - This mode includes a Gateway & a Gatekeeper.

This is the extension number of the VOIP protocol. It is used for the Voice card to identify the calls made through the VoIP card. The user may choose an arbitrary value for this field, the only restriction is that there must be no other entity registered with the same extension number.

Defines the remote gateway address (IP + port). It is important for gateway to gateway connection.

MAX no. of connections enabled by the GW.

Type of Service. The BIT Format is consistent with the IP standard: +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ 0 1 2 3 4 5 6 7 At present, only 1 BYTE will be used, bits 0 (MSB) - 7 (LSB). The precedence consists of 3 BITS (0-2): 111 - Network Control 110 - Internetwork Control 101 - CRITIC/ECP 100 - Flash Override 011 - Flash 010 - Immediate 001 - Priority 000 - Routine The TOS values BITS (3-5): Bit 3 is the Delay: 0 = Normal Delay, 1 = Low Delay. Bit 4 is the Throughput: 0 = Normal Throughput, 1 = High Throughput. Bit 5:is the Reliability: 0 = Normal Reliability, 1 = High Reliability. Bits 6 & 7 are for future use and their current value is 0.

Defines the backup gatekeeper address (IP + port). When the backup GK is active, all the calls will be routed to it and it will be responsible for their address translation. The first GK address is defined in the standard H.341 MIB.

The GW should register every Time to Register seconds with the GK. The Time to Register range is from 0 to 900 seconds in intervals of 60 seconds. 0 means Never. When the GK becomes active the Gateways that are up can register so that the GK has an updated list of active Registered Gateways.

This table contains information about H.245 configuration parameters. It is a list of configuration parameter entries. The number of entries equals to the number of H.245 stacks in a system.

It contains objects that describe the H.245 configuration parameters.

Maximum peak to peak delivery (in miliseconds) of audio packets to the transport layer that the transmitter shall cause.

This variable enables or disables the usage of Tunneling.

RTP Multiplexing table. RTP Multiplexing: In IP telephony system, the addition of packet headers, including IP, UDP and RTP headers, increases the header overhead, decreasing efficient transmission. Also, because of large numbers of short voice packets flowing into the network, Internet load increases, eventually resulting in large delay and packet loss. RTP Multiplexing is a way to send multiple RTP packets between a pair of Gateways, with a single IP frame. This will reduces the header overhead and decreases delay by enabling voice transmission with fewer packets.

An entry in table rtpMultiplexTable.

RTP Multiplexing is a way to send multiple RTP packets with a single IP frame. This will reduce the header overhead and decrease the delay by enabling voice transmission with fewer packets. The option of this field are: Disable - No RTP Multiplexing. multiplexType1 - medium level of compression for RTP multiplexing. multiplexType2 - high level of compression for RTP multiplexing. Using the High Compression algorithm is more efficient but will cause the loss of some RTP header information. If RTP statistics are important, the medium compression must be selected.

Defines the maximum size in Bytes of the multiplexed frame. In some cases this must be limited to avoid IP fragmentation, which makes the multiplexing useless, and can also decrease the damage in case of the frame loss. At present the size is 1500.

Defines the maximum amout of time (msec.) between multiplexed frames that are sent. Legal values: 10-90 msec.

The events for Optimux.

The trap is sent every time there is a change in the state of one of the PS..

The trap is sent every time there is a change in the agnIndication variable. For Optimux XL family, from ver 4.1 and up, this trap should be sent upon any change in the agnNearFarConnection variable

optLineStatusChange trap is sent when the value of an instance dsx1LineStatus changes. It can be utilized by an NMS to trigger polls. When the line status change results from a higher level line status change (i.e. ds3), then no traps for the ds1 are sent.

This trap alerts the console if there is module enrollement/de-enrollement

This trap alerts the console if there is changes in the loopback status of some of the line.

optXlLineStatusChange trap is sent when the value of an instance dsx1LineStatus changes. It can be utilized by an NMS to trigger polls.

This table contains parameters of configuration for each member of the couple of Optimux.

An entry in the Optimux Config table.

optIndex = 1 is for local Optimux. optIndex = 2 is for remote Optimux.

HW Version of the device.

SW Version of the device.

The status of the primary Power Supply Unit.

The status of the secondary Power Supply Unit.

This object indicates which link is active. For Optimux-4 it may be: 5, 6 or 105, 106 For FOMi-E3/T3 it may be: 51, 61 or 151, 161. For Optimux-T3 it may be: 51 or 61. For Optimux-155/1 refer to product spec.

This object is used by Optimuxes. - For Optimux 4E1/T1 Old Look: This MIB object enables the user to force the device to use specific link. autoredundancy= Main (Link 1) is the default link. When it will fail, the device will use Backup (Link 2). If Main recovers, it automatically returns to Main. autoWoReturn = Automatic Without Return. Main (Link 1) is the default link. When it will fail, the device will use Backup (Link 2). If Main recovers, it will NOT return to Main. It will continue using Backup. This option is supported only by LRS cards. main = Forces the device to start immediately use of Main (Link 1), no matter what is its state and stay there. No Redundancy. back = Forces the device to start immediately use of Backup (Link 2), no matter what is its state and stay there. No Redundancy. - For Optimux-T3, Optimux-155, Optimux-XL and OP-4 (New Look): This MIB object is used to select which Link will be used as MAIN. Therefore: autoredundancy - not supported main = Link A is MAIN (=default). back = Link B is MAIN.

Performs payload loop ( remote loop) to 4 E1 channels at once.

For Optimux XL: If dsx3TransmitClockSource = localTiming(2), then the user can configure this field as: localInternal(2) = use the internal clock of the device localExternal(3) = use the external clock connected to the port dedicated to clock. For FomiE3/T3 this object is always applicable. localExternal(3) = station clock transparent(5) = the device takes the clock info from the data. For FomiE3/T3 with HSSI electrical interface, only the following are valid: localInternal(2) and transparent(5). For Optimux-T3 the applicable values are (2), (3), (4). For Optimux-155/1 the applicable values are (2), (3), (4), (5).

If there are two modules links, then this field should be set to available(2). If there is only one module link, this field should be set to notAvailable(3).

This object is used by Optimux-XL, FomiE3/T3, Optimux-T3 and Optimux-155. For Optimux-XL: If optRedundancyStatus = notAvailable(3), then this field can be off(2) or forcedBU(6). - off(2) = forcedMain: forces the device to start immediately use of Main (Link 1), no matter what is its state and stay there - forcedBU(6) = forces the device to start immediately use of Backup (Link 2), no matter what is its state and stay there. This value is not supported by Optimux-T3. Else, user can configure this field as: auto(3) = switch back to main link when valid. manual(4) = dont switch back to main link = automatic w/o return. For FomiE3/T3 all values are applicable unconditioned. For Optimux-T3 and OP-4 New Look, values off(2), auto(3), manual(4) are applicable unconditioned. For Optimux-155/1 values off (2) = Protection Lockout, auto (3) and manual (4)

Far-End type of product. This object is especially relevant for the local optimux. notApplicable - for devices that dont have a far-end unit.

Service Channel Enable/Disable for each Optimux (local/remote).

Mask Channel Alarm. This object is applicable only for Optimux cards. The value of this object is a sum of 2**n, where n is a bit assigned to a certain Channel. Bit=1 means masked. For Optimux-4: Bit0: CH1 ; Bit1: CH2 ; Bit2: CH3 ; Bit3: CH4 (Bit=1 means masked). Examples: - 15 : means that all Channels are masked. - 9 : means that Alarms of CH 1 and CH 4 are masked. For Optimux-T3: Bit0: CH1 ; Bit1: CH2 ; Bit2: CH3 ;.. Bit20: CH21 OR Bit27: CH28. For FDSL: Bit0..Bit12 : CH1..CH12; Bit13: ETH ; Bit14..Bit15: Uplink1..Uplink2.

AIS enable/disable. notApplicable - for devices that do not support this feature.

This object is used by Optimux-XL and FomiE3/T3. Is there possibility of Far-End Management (no/yes). This object is applicable only for the Local device. notApplicable - for Remote device and devices that do not support it. no - far-end device is NOT I-Type so it doesnt have a management link to its pair-device. yes - far-end device is I-Type so it has a management link to its pair-device.

This object is applicable only for FomiE3/T3 having an HSSI Electrical interface. It gives the possibility of Clock Division, so that Clock Rate will be less than T3/E3. notApplicable - for a device that does not support it noDivision - Clock stays as is (Internal or Transparent) half - Clock will be half the original (divided by 2) quarter - Clock will be a quarter of the original (divided by 4).

DTE Loop enable/disable (for example loop command requested by router). This object is applicable only for products having HSSI interface. notApplicable - for devices that do not support this feature.

This object is applicable for Optimux-T3, when optGrpClockSource=localExternal. It enables the user to select the Channel or Station Clock from which the Clock is received. Valid values: 0 = notApplicable 1..28 (= CH1..CH28). 73 = Station Clock. Only T1 Channels can be used as Clock Source. For Optimux-155/1 refer to product spec for port indexing.

State of the Incoming Alarm (On/Off), via Alarm Relay connector. This object is applicable only for Optimux-T3.

Default configuration for all Optimux Channels: T1 or E1. This object is applicable only for Optimux-T3.

This parameter defines the time (sec) device has to wait in the redundant state until it goes back to the default Link.

This parameter is not applicable when optRedundancyCnf = off. It enables user to enforce a Link in spite of the redundancy mechanism. Selecting the noEnforcement(2) value cause return to the usual rules of the redundancy mechanism. main (3) and backup (4) are unconditional (force).

This object allows user to define if Flip to the other port will be performed (or not), for certain possible events. Each event is represented by a bit. The value of the object is a sum of 2**n, according to the bits having 1 value. 1 - means that Flip should occur due to this event. Bit 0 (LSB) = SD (Signal Degraded).

Mask Channel Alarm done by the HW dip-switches. This object is applicable only for Optimux cards. The value of this object is a sum of 2**n, where n is a bit assigned to a certain Channel. For Optimux-16E1: Bit0: CH1 ; Bit1: CH2 ; Bit2: CH3 ;.. Bit15: CH16 (Bit=1 means masked). Examples: - 9 : means that Alarms of CH 1 and CH 4 are masked.

Service Channel Existence indication for each Optimux (local/remote).

This table defines the type of the module enrolled in each slot.

An entry in the Optimux Module table.

optMdIdx = 1 is for local Optimux. optMdIdx = 2 is for remote Optimux.

For Optimux XL: Slot A = 1, Slot B = 2, Slot C = 3, Slot D = 4, Slot Link = 5, Slot BU = 6 . For FomiE3/R3: Slot of Station Clock = 3, Slot of Electrical Link = 4, Slot of Optical Main Link = 5, Slot of Optical Backup Link = 6 . For Optimux-T3: Slot of Station Clock (internal card)= 3, Slot A = 5, Slot B = 6. For Optimux-155/1: E1/T1 Slot A - 1, E1/T1 Slot B- 2, LINK-A - 5, LINK-B - 6 I/O-1 - 11, I/O-2 -12 ...I/O-6 - 16 For Optimux-155 DS3: Common Logic+E3/T3 Slot A - 1, Common Logic+E3/T3 Slot B- 2, LINK-A - 5, LINK-B - 6

Module Type and number of connectors.

HW Version of the module.

The meaning of each bit depends on the module type.

Wave Length of T3/E3 Optical Links in [nm] and specification if Laser or not.

The Module Timing mode.

Indication of Alarm and test status of all interfaces served by a module. For Optimux155, Each interface will be represented by 2 bits where the 1st bit (right) will specify alarm status and the 2nd bit will specify test status. e.g 00 - normal 01 - alarm active 11 - alarm active + testing 10 - testing For bits assignment per interface refer to product spec.

This table defines the connection of every ch of the framer.

An entry in the Optimux Framer port Connections table.

The channel of the Framer. Valid values:1..31.

This parameter defines the Framer channel connection. The values will be as follows: Loop(1),Ch1(2),Ch2(3)....,Ch28(29).

This parameter defines the Framer port (E1 or T1).

The IP Address of the opposite optimux in the ring,which this channel connected to.

The number of changes in Framer connection table that occured since last time there was a reset to this parameter

Indication about Optimux special behavior: pointToPoint(2): regular operation mode (Point to Point). ring(3): this optimux is part of a ring. operations made on this device may affect other optimuxes in the Ring and vice versa. drop(4): enables connection between T3 tributary channel and physical E1/T1 port. In this mode there may be no connection between this Optimux and another Optimux While working in this mode optimux CANNOT be in PTP or Ring topology.

This table defines which optimuxes are in the ring and the IP Address of each one.

An entry in the Optimux Ring Connections table.

The index of the optimux, starting with next optimux to the current optimux. Valid values:1..28. The index is according to the order of optimux connections in the ring. Example: 1=next optimux to the current, in the ring 2=next optimux in the ring, after the one having index=1 etc.. Last index will be the current optimux, that close the ring.

The IP Address of each optimux in the ring, according to optRingNeIdx.

The trap is sent whenever there is a transition from a no alarm state to a state with at least one active alarm.

This trap alerts of major problems in the device.

This trap indicates Loss Of Signal.

This trap indicates Loss Of Frame.

This trap is sent upon any change in one or more channels.

This trap indicates AIS.

This trap indicates RDI.

This trap indicates FEBE.

This trap is sent upon a change in Local connectivity of Bundle connection.

This trap is sent upon a change in Remote connectivity of Bundle connection.

This trap is sent upon any change in the connectivity status of a Bundle (ip2IfOperStatus). The ifAlias index is the ifIndex of the bundle that its status has been changed.

This parameter is a command to the webranger CPU. It enables blocking or forwarding broadcast frames, which may cause a trigger to a connection. block (1) - blocks the broadcast frames. forward (2) - forwards the broadcast frames. blockLinkPropagation (3) - blocks the broadcast frames to the links, tx to the LAN.

This parameter enables the webranger to learn the DLCis configuration and maintanance protocol. off - will get the configuration by setting it. on - disables configuration and start self learning.

This parameter enables/disables the Gratuitous ARP feature. When enabled, the feature means: when receiving ARP with senders Source IP Address that already exists in the ARP table - replace MAC Address with senders Source MAC Address.

Activating (disable/enable) DHCP server operation. Since DHCP Server and DHCP Relay cannot reside in same device, DHCP Relay may be enabled (per interface), only if server action is disabled. For some devices, this object is used in order to enable/disable the DHCP Client. See device SDS.

A list of DHCP entries. The number of entries is up to DHCP current entries, according to the WEBRANger model.

DHCP parameters per entry of the DHCP table.

DHCP Low Ip Address.

DHCP High Ip Address.

IP mask Address.

Default Gateways IP Address.

Primary DNS.

Secondary DNS.

The IP addresse allocation is done according to the interface type from which the DHCP request arrives.

This attribute allows to create/delete a row in this table. For creating a row, the NMS should set wrDhcpRowStatus.id = active(1). For destroying a row, the NMS should set: wrDhcpStatus.id = destroy(6). Only rows with status active(1) are relevant. The only possible supported RowStatus vaules are active (1) and destroy (6).

Allocated IP Address lease time in seconds. A zero value specifies no time limitation.

DHCP pool name - string with max length of 10 characters

A list of DHCP Pool Allocation entries. Each entry (row) consist of a single IP Address belonging to DHCP pool whose lowest IP address is dhcpPoolAllocLowIpAddress. This IP address may be offered for leasing, or may already be leased (in use) by Host its MacAddress is dhcpPoolAllocMacAddress. Time left for leasing period is indicated by dhcpPoolAllocTimeLeft. All posible statuses of IP address are indicated and controlled by dhcpPoolAllocFlags

DHCP Pool Allocation parameters per entry of the DHCP Pool Allocation table.

Lowest IP address of this pool, value eqaul to wrDhcpLowIpAddress for the pool.

Single IP Address belonging to dhcp pool whose Lowest Ip Address is dhcpPoolAllocLowIpAddress. This IP address may be offered for leasing or may be leased by Host its MacAddress is dhcpPoolAllocMacAddress. All posible statuses of IP address are indicated by dhcpPoolAllocFlags

MAC Address to which the IP address has been leased

IP address leasing time left in seconds

These flags indicates status of each IP address. User may change value to free, via dhcpPoolAllocFreeCmd

Setting this attribute to On (3), will enforce the agent to Free this entry. The Agent will change the value of this MIB object to off(2) automatically, after performing the command. Setting this object to off(2), will do nothing

A list of DHCP relay entries.

DHCP Relay parameters per entry of the DHCP relay table.

Setting this attribute to enable (3), will enable DHCP Relay action for this interface (Only if DHCP Server is disabled for device - wrDhcpAction=disable). dhcpRelayServerIpAddressaddress should not be 0.0.0.0 when enable is set

DHCP Server IP Address.

Maximum number of hops till DHCP Server. upper limit is 16 hops

This parameter defines the port that DHCP flow will be actiavted.

A list of DHCP client entries.

DHCP Client parameters per entry of the DHCP Client table.

This parameter default value is enable(3). Setting this attribute to disable (2), will disable DHCP Client action for this interface. This parameter can be changed to disable (2) only (it cannot be changed from disable to enable).

DHCP Server IP Address.

This parameter holds the time (in minutes) left until lease expiration.

This parametr displays the DHCP status.

DHCP client entries for each Interface.

DHCP Clients per entry of the DHCP Interface Client table.

DHCP Client IP Address.

The row status used for creating, modifying, and deleting instances of the columnar objects in the dhcpIfClientTable. For Vmux Devices, it will be possible only to Delete instances. The addition of Clients will be done automatically by the Server according to Network messages that are sent by the Clients; not via SNMP. In order to Delete a Client, this MIB object should be set to: destroy (6).

This variable enables the operator to perform one of the specified actions on the Server. deleteAllClients (3) is an option that is used for a device functioning as a server. It will remove all the clients from all the interfaces of the device. When the operation is complete, the agent will return a noOp (2) value.

When Enabled, device will act as a DNS Relay: whenever the device receives a DNS request from its host, it will forward it to the DNS server as if the request was initiated by the device itself. The reply from the DNS server is forwarded by the device to the host as if the device was answering the request.

Activating (disable/enable) the auto-learn operation.

Lan IPX nets Table.

IPX Nets per frame type & LAN port. The table entries will be created by the agent

LAN port ifIndex.

Frame Type

Net address per Frame Type & LAN port.

Net address through a link.

A list of Interfaces which require separate configuration in RIP/SAP.

A Single Routing Domain in a single Subnet.

The interface ifIndex.

The ifIndex RIP/SAP mode.

This attribute allows to create/delete a row in this table. For creating a row, the NMS should set ripSapIfConfStatus.id1 = active(1). For destroying a row, the NMS should set: ripSapIfConfStatus.id1 = destroy(6). Only rows with status active(1) are relevant. The only possible supported RowStatus vaules are active (1) and destroy (6).

Link IP addresses Table.

Ip Address per Link

Port interface index.

Link IP Address.

Link IP mask Address.

This attribute allows to create/delete a row in this table. For creating a row, the NMS should set wrIpRowStatus.id1 = active(1). For destroying a row, the NMS should set: wrIpRowStatus.id1 = destroy(6). Only rows with status active(1) are relevant. The only possible supported RowStatus vaules are active (1) and destroy (6).

Spoofing Table.

Spoofing per Link

Port interface index.

Spoofing action is applied by bit code: enable : bit 0 set (disable: bit 0 is 0) keepAlive : bit 1 ... : bit 2 and so on. For the above example, to set spoofing to keepAlive action, the objects value will be 3 = [ 2**0 + 2**1 ] Only the Remote WEBRANger will accept this object ! -------

Aging time of stations list, in min. The agent translates the time entered in minutes, to 10 min. resolution, as follows: 1..10 min - 10 min 11..20 min - 20 min and so on... 0 is not a valid value. Only the Remote WEBRANger will accept this object ! ----------------

This attribute allows to create/delete a row in this table. For creating a row, the NMS should set wrSpoofingRowStatus.id1 = active(1). For destroying a row, the NMS should set: wrSpoofingRowStatus.id1 = destroy(6). Only rows with status active(1) are relevant. The only possible supported RowStatus vaules are active (1) and destroy (6).

Link IP addresses Table.

Ip Address per Link

Port interface index.

This parameter indicates whether the link is Bridge or Router and specifies the Routers type.

The LAN is disabled or enabled. For LAN 2 it can be also redundancy.

LAN Redundancy Timeout in seconds. Applicable when wrLanIfState=redundancy.

Configuration table for Async interface.

Configuration table

Sync interface index.

Clock Mode.

Clock Rate in. Rate can be changed if Clock Mode is Program only.

Configuration table for Fr parameters that do not exist in RFC2115.

Configuration entry for Fr parameters that do not exist in RFC2115.

This parameter enables the webranger to learn the DLCis configuration and maintanance protocol for the current interface. off - the WR will read the users configuration for this interface. on - the WR will begin self learning of the current interfaces maintanance protocol and DLCIs.

This parameter enables/disables the Webranger to Tx/Rx CLLM (Consolidated Link Layer Management) messages via DLCI 1023. The CLLM messages are link layer control messages. They can be used for example in cases of congestion. The CLLM message contains a code for cause of congestion and list of all DLCIs that should act to reduce data transmission.

According to this mode the packets will be forwarded. If disable (2) is selected, there will be no multicast.