The SAP table contains configuration information for each X.25 layer SAP
(service access point).
Service Access Points
Two types of SAPs exist:
- Upper: A SAP that exists at the upper interface of the X.25 layer and
serves an embedded application.
- Lower: A SAP that exists at the lower interface of the X.25 layer and
serves a single data link connection (LAPB) or multiple data link
connections (LAPD).
This data link connection, when attached to the sub-layer, can complete a
LAPB service, or can be one of many supported data link connections over a
LAPD service.
SAPs are identified by a SAP Number and CES (connection endpoint suffix).
X.25 LAPB service supports only one data link connection and thus only one
SAP is required. Its CES is irrelevant and is normally set to 0 at this
SAP. This SAP communicates with its 'companion' SAP at the sub-layer in a
one-to-one relationship.
X.25 LAPD service supports multiple data link connections, and thus
multiple SAPs are required. The CES for each must be unique and is
normally in the range of 0 to 63. Each of these SAPs (which are grouped
according to SAP Number) communicate with the same 'companion' SAP at the
sub-layer in a many-to-one relationship.
Facilities
This table contains numerous facilities subscription parameters. Each
facility subscription that is part of the standard, is referenced to the
appropriate section in the ITU(CCITT) X.25 (1988) blue book in the
REFERENCE section of the object.
Terms used in this table
Incoming calls: For lower SAPs, these are the X.25 calls received from the
sub-layer. For upper SAPs, these are the X.25 calls received from the
associated application.
Outgoing calls: Are the X.25 calls routed from other SAPs, which are to go
out this SAP.
Source side: The side that received an incoming call.
Destination side: The side that will send the outgoing call.
Parsed from file CXX25.MIB.txt
Company: None
Module: CXX25-MIB
The SAP table contains configuration information for each X.25 layer SAP
(service access point).
Service Access Points
Two types of SAPs exist:
- Upper: A SAP that exists at the upper interface of the X.25 layer and
serves an embedded application.
- Lower: A SAP that exists at the lower interface of the X.25 layer and
serves a single data link connection (LAPB) or multiple data link
connections (LAPD).
This data link connection, when attached to the sub-layer, can complete a
LAPB service, or can be one of many supported data link connections over a
LAPD service.
SAPs are identified by a SAP Number and CES (connection endpoint suffix).
X.25 LAPB service supports only one data link connection and thus only one
SAP is required. Its CES is irrelevant and is normally set to 0 at this
SAP. This SAP communicates with its 'companion' SAP at the sub-layer in a
one-to-one relationship.
X.25 LAPD service supports multiple data link connections, and thus
multiple SAPs are required. The CES for each must be unique and is
normally in the range of 0 to 63. Each of these SAPs (which are grouped
according to SAP Number) communicate with the same 'companion' SAP at the
sub-layer in a many-to-one relationship.
Facilities
This table contains numerous facilities subscription parameters. Each
facility subscription that is part of the standard, is referenced to the
appropriate section in the ITU(CCITT) X.25 (1988) blue book in the
REFERENCE section of the object.
Terms used in this table
Incoming calls: For lower SAPs, these are the X.25 calls received from the
sub-layer. For upper SAPs, these are the X.25 calls received from the
associated application.
Outgoing calls: Are the X.25 calls routed from other SAPs, which are to go
out this SAP.
Source side: The side that received an incoming call.
Destination side: The side that will send the outgoing call.
Parsed from file CXX25-MIB.mib
Module: CXX25-MIB
Vendor: Memotec Communications
Module: CXX25-MIB
[Automatically extracted from oidview.com]
x25SapTable OBJECT-TYPE SYNTAX SEQUENCE OF X25SapEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The SAP table contains configuration information for each X.25 layer SAP (service access point). Service Access Points Two types of SAPs exist: - Upper: A SAP that exists at the upper interface of the X.25 layer and serves an embedded application. - Lower: A SAP that exists at the lower interface of the X.25 layer and serves a single data link connection (LAPB) or multiple data link connections (LAPD). This data link connection, when attached to the sub-layer, can complete a LAPB service, or can be one of many supported data link connections over a LAPD service. SAPs are identified by a SAP Number and CES (connection endpoint suffix). X.25 LAPB service supports only one data link connection and thus only one SAP is required. Its CES is irrelevant and is normally set to 0 at this SAP. This SAP communicates with its 'companion' SAP at the sub-layer in a one-to-one relationship. X.25 LAPD service supports multiple data link connections, and thus multiple SAPs are required. The CES for each must be unique and is normally in the range of 0 to 63. Each of these SAPs (which are grouped according to SAP Number) communicate with the same 'companion' SAP at the sub-layer in a many-to-one relationship. Facilities This table contains numerous facilities subscription parameters. Each facility subscription that is part of the standard, is referenced to the appropriate section in the ITU(CCITT) X.25 (1988) blue book in the REFERENCE section of the object. Terms used in this table Incoming calls: For lower SAPs, these are the X.25 calls received from the sub-layer. For upper SAPs, these are the X.25 calls received from the associated application. Outgoing calls: Are the X.25 calls routed from other SAPs, which are to go out this SAP. Source side: The side that received an incoming call. Destination side: The side that will send the outgoing call." ::= { cxX25 21 }
x25SapTable OBJECT-TYPE SYNTAX SEQUENCE OF X25SapEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The SAP table contains configuration information for each X.25 layer SAP (service access point). Service Access Points Two types of SAPs exist: - Upper: A SAP that exists at the upper interface of the X.25 layer and serves an embedded application. - Lower: A SAP that exists at the lower interface of the X.25 layer and serves a single data link connection (LAPB) or multiple data link connections (LAPD). This data link connection, when attached to the sub-layer, can complete a LAPB service, or can be one of many supported data link connections over a LAPD service. SAPs are identified by a SAP Number and CES (connection endpoint suffix). X.25 LAPB service supports only one data link connection and thus only one SAP is required. Its CES is irrelevant and is normally set to 0 at this SAP. This SAP communicates with its 'companion' SAP at the sub-layer in a one-to-one relationship. X.25 LAPD service supports multiple data link connections, and thus multiple SAPs are required. The CES for each must be unique and is normally in the range of 0 to 63. Each of these SAPs (which are grouped according to SAP Number) communicate with the same 'companion' SAP at the sub-layer in a many-to-one relationship. Facilities This table contains numerous facilities subscription parameters. Each facility subscription that is part of the standard, is referenced to the appropriate section in the ITU(CCITT) X.25 (1988) blue book in the REFERENCE section of the object. Terms used in this table Incoming calls: For lower SAPs, these are the X.25 calls received from the sub-layer. For upper SAPs, these are the X.25 calls received from the associated application. Outgoing calls: Are the X.25 calls routed from other SAPs, which are to go out this SAP. Source side: The side that received an incoming call. Destination side: The side that will send the outgoing call." ::= { cxX25 21 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.495.2.1.6.29.21.1 | x25SapEntry | 70 | 70 | Defines a row in the x25SapTable. Each row contains the objects which define a service access point. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.495.2.1.6.29.1 | x25LowerPoolThreshold | 1 | 1 | Determines the minimum amount of system resources which are required by the X.25 layer. When system resources drop below this th… |
| 1.3.6.1.4.1.495.2.1.6.29.2 | x25ConfigErrorIndication, x25UpperPoolThreshold | 1 | 1 | Determines the amount of system resources which are required by the X.25 layer to avoid congestion. When system resources drop b… |
| 1.3.6.1.4.1.495.2.1.6.29.3 | x25RouteMask | 1 | 1 | Determines the number of digits to use for routing calls. If set to value '0', calls are routed normally, according to the calle… |
| 1.3.6.1.4.1.495.2.1.6.29.4 | x25BillingSegmentSize | 1 | 1 | Determines the size of billing data segments. Range of Values: 16 - 1024 bytes Default Value: 16 bytes Related Objects: x25Billing x… |
| 1.3.6.1.4.1.495.2.1.6.29.5 | x25Billing | 1 | 1 | Determines if this layer generates the x25BillingIndication trap. For switched virtual circuits the trap is generated each time … |
| 1.3.6.1.4.1.495.2.1.6.29.6 | x25NetworkType | 1 | 1 | Determines the format of the cause codes the X.25 layer adds to Reset, Restart, and Clear packets. Note: The X.25 layer will not … |
| 1.3.6.1.4.1.495.2.1.6.29.7 | x25HuntGroupRotation | 1 | 1 | Determines if hunt group members are rotated. Enabling rotation causes hunting to begin with a different hunt group member each … |
| 1.3.6.1.4.1.495.2.1.6.29.10 | x25Alarms | 1 | 1 | For future use. Determines if this layer generates the x25SapAlarm trap. Options: disabled (1): This layer does not generate the … |
| 1.3.6.1.4.1.495.2.1.6.29.11 | x25SapStatusEvent | 1 | 1 | For future use. Indicates the status reported by an x25SapAlarm trap when it occurs. This object always returns the value 'noEve… |
| 1.3.6.1.4.1.495.2.1.6.29.12 | x25ConfigErrorEvent | 1 | 1 | For future use. Indicates the status reported by an x25ConfigErrorIndication trap when it occurs. This object always returns the … |
| 1.3.6.1.4.1.495.2.1.6.29.19 | x25SoftwareVersions | 1 | 1 | Identifies the X.25 software revision number, which is displayed as a string of five numbers each separated by a period (1.2.3.4… |
| 1.3.6.1.4.1.495.2.1.6.29.20 | x25LogicalLinkTable | 1 | 7 | A logical link is a group of one or more lower service access points(SAPs) created for the purpose of route balancing. Two types… |
| 1.3.6.1.4.1.495.2.1.6.29.22 | x25SapStatsTable | 1 | 33 | A table containing statistical information about each service access point. |
| 1.3.6.1.4.1.495.2.1.6.29.23 | x25CugTable | 1 | 9 | This tables contains CUG (closed user group) definitions for the X.25 layer. Any service access point (upper or lower) can be pa… |
| 1.3.6.1.4.1.495.2.1.6.29.24 | x25RouteTable | 1 | 9 | The SVC Route table contains the definitions used to route all switched virtual circuits. A route entry consists of the called ad… |
| 1.3.6.1.4.1.495.2.1.6.29.25 | x25HuntGroupTable | 1 | 6 | This table contains Hunt Group definitions for the X.25 layer. A hunt group is a grouping of upper and lower SAPs (service acces… |
| 1.3.6.1.4.1.495.2.1.6.29.26 | x25HuntGroupOperTable | 1 | 5 | This table contains the current active Hunt Group (closed user group) definitions for the X.25 layer. Use the x25HuntGroupTable … |
| 1.3.6.1.4.1.495.2.1.6.29.27 | x25PvcTable | 1 | 21 | This table contains definitions used to route X.25 PVCs (permanent virtual circuits). A PVC is always routed between two lower S… |
| 1.3.6.1.4.1.495.2.1.6.29.28 | x25LcnStatusTable | 1 | 32 | A table containing current information about established virtual circuits (permanent or switched) within the layer. |
| 1.3.6.1.4.1.495.2.1.6.29.30 | x25MibLevel | 1 | 1 | Used to determine current MIB module release supported by the agent. Object is in decimal. |