All MIBs › BIANCA-BRICK-PPP-MIB
Category: IP and Core Protocols, Vendor: bintec
Description: Handles PPP link configuration, authentication, and statistics for bintec elmeg BIANCA/BRICK broadband routers.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is BIANCA-BRICK-PPP-MIB?
BIANCA-BRICK-PPP-MIB is a vendor-specific module from bintec elmeg (originally BinTec Communications GmbH) covering the BIANCA/BRICK family of ISDN and broadband routers, focused specifically on the Point-to-Point Protocol (PPP) subsystem used for WAN and dial-up connectivity. It exposes configuration data for PPP link setup and authentication method (PAP/CHAP) alongside per-link operational counters describing negotiated options and traffic. In practice it is used to monitor the software status of a router's WAN links — whether a PPP session is currently up, which authentication scheme was negotiated, and whether the link is passing traffic — which is essential for catching flapping ISDN backup circuits or failed CHAP/PAP logins. It builds on the conventions of the standard PPP MIBs (RFC 1471–1473) but adds BinTec/bintec-specific link and authentication objects rather than replacing them. It is typically deployed on small-office or branch routers where a central NMS polls PPP link state over a WAN uplink, and locating the BIANCA-BRICK-PPP-MIB OID branch on the router is the starting point for polling these link and authentication objects directly.
IPNetwork Monitor allows you to monitor SNMP objects defined in BIANCA-BRICK-PPP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- bintec elmeg BIANCA/BRICK ISDN/broadband router
Monitoring Examples
An administrator would poll the per-link PPP entry (indexed like a pppLinkTable) on a BIANCA/BRICK router to check the link's connection state and negotiated authentication protocol. Repeated link-down/link-up transitions on that entry would reveal a flapping ISDN backup line, while an authentication-state stuck at 'failed' would point to a misconfigured CHAP secret. No sample object names were available for this MIB, so exact table/column identifiers cannot be confirmed beyond this general PPP-link-and-authentication pattern.
What Can Be Monitored
- PPP link connection status
- negotiated authentication protocol (PAP/CHAP)
- link up/down transitions
- PPP link traffic statistics
This MIB depends on
Related MIBs
Imported Objects
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| bibo | 1.3.6.1.4.1.272.4 | |||
| OCT biboDialCallingSubaddress | 1.3.6.1.4.1.272.4.4.1.1.9 | OCTET STRING | read-write | The defined calling dial subaddress, if any. Also, see the biboDialNumber field. |
| INT biboDialClosedUserGroup | 1.3.6.1.4.1.272.4.4.1.1.6 | INTEGER | read-write | The defined closed user group, if any. Also, see the biboDialNumber field. |
| INT biboDialDirection | 1.3.6.1.4.1.272.4.4.1.1.3 | INTEGER | read-write | The allowed dial direction is either incoming(1), outgoing(2), or both(3) calls. No call is ever set up when set to incoming(1). Incoming calls will not be identified when set to outoing(2). Furthermore, once PPP authentication succeeds and there is at least one incoming number defined but for which none matches, the call will not be accepted for security reasons. |
| biboDialEntry | 1.3.6.1.4.1.272.4.4.1.1 | not-accessible | ||
| INT biboDialIfIndex | 1.3.6.1.4.1.272.4.4.1.1.1 | INTEGER | read-write | The correlating PPP interface index. |
| STR biboDialNumber | 1.3.6.1.4.1.272.4.4.1.1.4 | DisplayString | read-write | The defined dialing number. Used for either dialing or comparing to incoming calls or both, depending on the content of the biboDialDirection field. The wildcards '*', '?', '[', ']', '{', '}' may be used. |
| INT biboDialScreening | 1.3.6.1.4.1.272.4.4.1.1.8 | INTEGER | read-write | The screening indicator of the biboDialNumber. The biboDialScreening field can be used to gauge the `trustworthiness' of the biboDialNumber field. (See isdnCallScreening) Indicators are ordered from highest to lowest as follows: indicator: CPN assigned: verification: `network' by network none `user-verified' by user verification successful `user' by user none `user-failed' by user verification failed Set this field to `dont-care' to accept all calls. Otherwise calls are accepted only if the screening indicator matches or is higher than the set value. |
| BIT biboDialStkMask | 1.3.6.1.4.1.272.4.4.1.1.7 | BitValue | read-write | The defined stack mask. Each value of IsdnStkNumber represents a bit in this bitmask. A mask of 0 disables dialup completely, while a mask of -1 enables dialup on all available ISDN stacks. |
| OCT biboDialSubaddress | 1.3.6.1.4.1.272.4.4.1.1.5 | OCTET STRING | read-write | The defined dial subaddress, if any. Also, see the biboDialNumber field. |
| biboDialTable | 1.3.6.1.4.1.272.4.4.1 | not-accessible | The biboDialTable contains configuration information for incoming and outgoing ISDN telephone numbers. Creating entries: Entries are created by assigning a value to the biboDialIfIndex object. Deleting entries: An entry can be removed by assigning the value `delete' to its biboDialType object. | |
| INT biboDialType | 1.3.6.1.4.1.272.4.4.1.1.2 | INTEGER | read-write | The dialup type can be set to plain isdn(1), isdn-spv(2) semi-permanent links used by the German 1TR6 D-channel protocol, or to delete(3) to delete a biboDialTable entry. The types ppp-callback(4) and ppp-negotiated(5) are used for the LCP callback option. |
| INT biboDialTypeOfCalledSubAdd | 1.3.6.1.4.1.272.4.4.1.1.11 | INTEGER | read-write | The type of called party subaddress. |
| INT biboDialTypeOfCallingSubAdd | 1.3.6.1.4.1.272.4.4.1.1.10 | INTEGER | read-write | The type of calling party subaddress. |
| INT biboPPPAuthentication | 1.3.6.1.4.1.272.4.3.1.1.7 | INTEGER | read-write | The type of authentication used on the point-to-point link as described in RFC 1334. The authentication protocol supports pap(2) (Password Authentication Protocol), chap(3) (Challenge Handshake Authentication Protocol), or both(4). When set to both(4), the link must be successfully authenticated by either CHAP or PAP. The type ms-chap(6) and ms-chapv2(8) are Microsofts proprietary CHAP authentication procedures (using MD4 and DES encryption instead of MD5 encryption algorithm), all(7) includes PAP, CHAP and MS-CHAP. Another way to authenticate dial-in users is by using RADIUS (remote authentication dial in user service). Users can authenticate themselves either using PAP or CHAP (excluding MS-CHAP). In general the system creates PPP interfaces with this authentication itself, but it's also possible to take advance of the RADIUS dial-in services with pre-configured interfaces. See biboAdmRadiusServer for further details. |
| STR biboPPPAuthIdent | 1.3.6.1.4.1.272.4.3.1.1.8 | DisplayString | read-write | The remote authentication identification string. The local authentication identification string is taken from the contents of the sysName field, up to the appearance of the first dot (e.g., the remote name would be `brick' if the content of the sysName field was `brick.bintec.de'). |
| STR biboPPPAuthSecret | 1.3.6.1.4.1.272.4.3.1.1.9 | DisplayString | read-write | The authentication secret, which is used symmetrically for both local and remote sides of the PPP link. |
| INT biboPPPBlockTime | 1.3.6.1.4.1.272.4.3.1.1.12 | INTEGER | read-write | Time in seconds to wait after a connection failure (e.g. the number of biboPPPMaxRetries calls failed). When set to zero, the interface state is never set to blocked. |
| INT biboPPPCallback | 1.3.6.1.4.1.272.4.3.1.1.18 | INTEGER | read-write | If this object is enabled(1), and the call is recognized by the dialed number then calls are never accepted, and a callback is forced for incoming calls at once. The callback can be delayed for biboPPPRetryTime seconds by setting this entry to delayed(5). If the call is recognized by inband authentication (PAP or CHAP) then the actual connection is closed and a callback is performed at once. Setting this value to ppp-offered(4) allows a called peer to call back the calling site if offered by PPP negotiation. For PABX dialout a dialprefix is added to the number, if offered by the calling site (see isdnStkTable). If this object is set to expected(3), only one initial outgoing call is made expecting a callback. If this object is set to ppp-callback-optional(6), the CBCP option 'no callback' is also offered to the Windows client so that the user can decide wether he wants to be called back or not. |
| INT biboPPPChargeInterval | 1.3.6.1.4.1.272.4.3.2.1.23 | INTEGER | read-only | Describes the measured interval between charging info elements received from the ISDN network. |
| INT biboPPPCompression | 1.3.6.1.4.1.272.4.3.1.1.6 | INTEGER | read-write | The throughput can be enhanced up to factor three using the V42bis compression method or the Stac LZS compression algorithm. V42bis is currently supported with the ip-lapb and mpr-lapb encapsulation. Stac LZS compression algorithm is provided using PPP encapsulated links, stac(3) indicates support of Sequence checking, ms-stac(4) indicates support of Extended mode which is prefered by Microsoft. Both check modes are implemented according RFC 1974. When set to mppc(5), the Microsoft Point-to-Point Compression (MPPC) Protocol according RFC 2118 is negotiated. MPPC uses an LZ based algorithm with a sliding window history buffer. |
| INT biboPPPCompressionMode | 1.3.6.1.4.1.272.4.3.2.1.22 | INTEGER | read-only | This object describes wether data compression is active for this interface. 42bis or Stac LZS compression algorithm can be enabled in the biboPPPTable. |
| INT biboPPPConnActive | 1.3.6.1.4.1.272.4.3.2.1.2 | INTEGER | read-only | The actual number of bundled channels. |
| CTR biboPPPConnCharge | 1.3.6.1.4.1.272.4.3.2.1.25 | Counter | read-only | The current charge on this interface as 1/1000 of the respective currency. |
| INT biboPPPConnDuration | 1.3.6.1.4.1.272.4.3.2.1.5 | INTEGER | read-only | The current link duration on this interface in seconds. |
| INT biboPPPConnIfIndex | 1.3.6.1.4.1.272.4.3.2.1.1 | INTEGER | read-only | Correlating PPP interface index. |
| CTR biboPPPConnIncomingCalls | 1.3.6.1.4.1.272.4.3.2.1.11 | Counter | read-only | The number of incoming calls on this interface since its last change to the up state. |
| CTR biboPPPConnIncomingFails | 1.3.6.1.4.1.272.4.3.2.1.12 | Counter | read-only | The number of incoming call failures on this interface since its last change to the up state. |
| CTR biboPPPConnOutgoingCalls | 1.3.6.1.4.1.272.4.3.2.1.9 | Counter | read-only | The number of outgoing calls on this interface since its last change to the 'up' state. |
| CTR biboPPPConnOutgoingFails | 1.3.6.1.4.1.272.4.3.2.1.10 | Counter | read-only | The number of outgoing call failures on this interface since its last change to the 'up' state. |
| INT biboPPPConnProtocols | 1.3.6.1.4.1.272.4.3.2.1.3 | INTEGER | read-only | The bitwise ORed protocols successfully negotiated on this connection; currently the following protocols are supported: tcp/ip(1), ipx(2), bridge(4), bpdu(8), x25(16). These protocol values are most likely to change in future software releases. |
| CTR biboPPPConnReceivedOctets | 1.3.6.1.4.1.272.4.3.2.1.8 | Counter | read-only | The octets received since its last change to the `up' state. |
| INT biboPPPConnState | 1.3.6.1.4.1.272.4.3.2.1.4 | INTEGER | read-only | The physical state of the link. This field is obsolete and will not be supported in a future release. |
| CTR biboPPPConnTransmitOctets | 1.3.6.1.4.1.272.4.3.2.1.7 | Counter | read-only | The octets transmitted on this interface since its last change to the 'up' state. |
| CTR biboPPPConnUnits | 1.3.6.1.4.1.272.4.3.2.1.6 | Counter | read-only | The current costs on this interface for all member links. |
| INT biboPPPDNSNegotiation | 1.3.6.1.4.1.272.4.3.1.1.25 | INTEGER | read-write | The IP control protocol extensions as described in RFC 1877 has a means of negotiating primary and secondary Domain Name System (DNS) server addresses. When this option is disabled(1), no DNS negotiation will be performed. If enabled(2), DNS negotiation behavier depends on biboPPPIpAddress switch (client or server mode). Setting to dynamic-client(3), the remote system is asked to tell us the IP-address(es) of primary and/or secondary DNS. Setting to dynamic_server(4), primary and/or secondary DNS IP-address(es) found in biboAdmNameServer or biboAdmNameServ2, if asked, will be send to remote. |
| INT biboPPPDynShortHold | 1.3.6.1.4.1.272.4.3.1.1.23 | INTEGER | read-write | Optimizes idle time disconnects depending on the charging information received during the connection. This value specifies the minimum inactivity time (channel is silent) in percents of the current charging interval length and is only used for outgoing connections. Incoming connections are disconnected after idle time according to the value biboPPPShortHold. Please note that this only works if your ISDN port has the AOCD service enabled (advice of charging during the call). For instance in Germany this is an extra paid service. (Even the 'Komfortanschluss' does only include AOCE [advice of charge at the end of the call], so AOCD has to be ordered and paid extra.) |
| INT biboPPPEncapsulation | 1.3.6.1.4.1.272.4.3.1.1.3 | INTEGER | read-write | The layer 2 encapsulation of the link. The use of ppp(1) as described in RFC 1661 is the preferred encapsulation for point-to-point links. The encapsulation is set to x25(2) for X.25-only links and to x25-ppp(3) for concurrent use of X.25 and PPP. Mpr-lapb(7) and mpr-hdlc(8) are popular proprietary encapsulations. They both use the ethertype number for protocol multiplexing. The former is used when error correction or data compression (v42bis) is desired. The latter (mpr-hdlc) is compatible to Cisco's HDLC encapsulation. On IP-only links it is also possible to use the ISO LAPB protocol (ip-lapb(4)), also known as X.75, or raw hdlc framing (ip-hdlc(6)). The x75-ppp encapsulation provides a proprietary solution for using PPP encapsulation over X.75 (LAPB) framing, x75btx-ppp provides PPP over T.70 and LAPB framing including a BTX protocol header to access BTX services over ISDN links. The x25-nosig(13) encapsulation is used to establish X.25 connections over dialup links without specific signalling on the D-channel (pure data call). The x25-ppp-opt encapsulation provides a special kind of the x25-ppp encapsulation. Dialin partner will be authenticated either outband to establish an X.25 connection via ISDN or optional inband by using the point-to-point protocol (PPP). Concurrent use of X.25 and PPP encapsulation is excluded. The x25-noconfig(16) and x25-noconfig-nosig(17) encapsulations provide a solution fr establishing X.25 connections via ISDN. The dial number will be derived from X.25 destination address by using special rules. V42bis data compression can be enabled on LAPB links only, because v42bis requires an error free connection. Dialup links can be removed by setting this field to delete(5). This has no effect on permanent links. |
| INT biboPPPEncryption | 1.3.6.1.4.1.272.4.3.1.1.26 | INTEGER | read-write | This field specifies the data encryption scheme for en(de)crypting PPP encapsulated multi-protocol datagrams. Setting to mppe-40(2), mppe-128(3) or mppe-56(7) the Microsoft Point to Point Encryption Protocol (MPPE) will be enabled, using a 40 bit, 128 bit respectively 56 bit session key for initializing encryption tables. Setting to mppev2-40(8), mppev2-56(9) or mppev2-128(10) the Microsoft Point to Point Encryption Protocol (MPPE) 'stateless mode' will be enabled, using a 40 bit, 56 bit respectively 128 bit session key. |
| biboPPPEntry | 1.3.6.1.4.1.272.4.3.1.1 | not-accessible | ||
| INT biboPPPIdleTime | 1.3.6.1.4.1.272.4.3.2.1.24 | INTEGER | read-only | The currently measured connection inactivity time (channel is silent). |
| INT biboPPPIfIndex | 1.3.6.1.4.1.272.4.3.1.1.1 | INTEGER | read-only | Correlating PPP interface index. This value is assigned automatically by the system. |
| INT biboPPPInitConn | 1.3.6.1.4.1.272.4.3.1.1.15 | INTEGER | read-write | The number of channels to initially set up for this interface. |
| INT biboPPPIpAddress | 1.3.6.1.4.1.272.4.3.1.1.10 | INTEGER | read-write | The IP control protocol as described in RFC1332 has a means of negotiating IP-addresses. When this option is set to dynamic-server(2), an available IP-address found in biboPPPIpAddrTable is assigned as the remote IP-address and a temporary route is created during the uptime of the interface. When set to dynamic-client(3), the remote system is asked to tell us our own IP-address. A host route will be created during the uptime of the interface. In most cases this option will be set automatically by the network address translation option. In static(1) mode, address-negotiation is not forced. |
| IP biboPPPIpAssignAddress | 1.3.6.1.4.1.272.4.3.4.1.1 | IpAddress | read-write | First IP address of this range. |
| biboPPPIpAssignEntry | 1.3.6.1.4.1.272.4.3.4.1 | not-accessible | Pool of IP addresses for dynamic IP address assignment via IPCP. See the biboPPPIpAddress field for further explanation. | |
| INT biboPPPIpAssignPoolId | 1.3.6.1.4.1.272.4.3.4.1.3 | INTEGER | read-write | Pool ID value. |
| INT biboPPPIpAssignRange | 1.3.6.1.4.1.272.4.3.4.1.4 | INTEGER | read-write | Number of IP addresses that will be assigned starting from biboPPPIpAssignAddress. A range of 0 will disable this entry |
| INT biboPPPIpAssignState | 1.3.6.1.4.1.272.4.3.4.1.2 | INTEGER | read-write | If an entry is currently in use, the state is set to as- signed(1). Otherwise it is set to unused(2). You may also delete this entry by changing it to delete(3). |
| biboPPPIpAssignTable | 1.3.6.1.4.1.272.4.3.4 | not-accessible | The biboPPPIpAssignTable contains IP addresses used when dynamically assigning IP addresses; i.e. when the biboPPPIpAddress field is set to `dynamic'. Creating entries: Entries are created by assigning a value (IP address) to the biboPPPIpAssignAddress object. Deleting entries: An entry (address) can be removed by assigning the value `delete' to its biboPPPIpAssignState. | |
| INT biboPPPIpPoolId | 1.3.6.1.4.1.272.4.3.1.1.28 | INTEGER | read-write | Pool ID value to select an IP address pool for dynamic IP address assignment via IPCP. See also PPPIpAssignTable for further details. |
| INT biboPPPKeepalive | 1.3.6.1.4.1.272.4.3.1.1.4 | INTEGER | read-write | When set to on(1), keepalive packets are sent in regular intervals during the connection. Keepalive packets can not be sent using the ip-lapb or x25 encapsulation. |
| INT biboPPPLayer1Protocol | 1.3.6.1.4.1.272.4.3.1.1.19 | INTEGER | read-write | This entry is used to select the layer 1 protocol settings for this partner. Normally the correct entry is hdlc-64. |
| INT biboPPPLayer2Mode | 1.3.6.1.4.1.272.4.3.1.1.22 | INTEGER | read-write | This object specifies the layer 2 mode to be used for a connection. It is only relevant, if the Encapsulation involves an LAPB protocol. This is the case for x25, x25-ppp, ip-lapb, lapb, x31-bchan, x75-ppp, x75btx-ppp, x25-nosig. The Default value of this object is auto. For dialup connection, the layer 2 mode will than be DTE, on the calling side and DCE on the called side. For permanent connections, the layer 2 mode is set at lower layers (for example isdnChType in the isdnChTable). When this object is set to dte or dce, the layer 2 mode will always be DTE or DCE, regardless of the call direction or the settings at the lower layer. |
| OCT biboPPPLinkAccm | 1.3.6.1.4.1.272.4.3.3.1.17 | OCTET STRING | read-only | . |
| INT biboPPPLinkCallReference | 1.3.6.1.4.1.272.4.3.3.1.15 | INTEGER | read-only | The call reference of the dialup link, correlating to the isdnCallReference field in the isdnCallTable. |
| INT biboPPPLinkCallType | 1.3.6.1.4.1.272.4.3.3.1.14 | INTEGER | read-only | The call type of the dialup link, correlating to the isdnCallType field in the isdnCallTable. |
| CTR biboPPPLinkCharge | 1.3.6.1.4.1.272.4.3.3.1.16 | Counter | read-only | The costs for this link as 1/1000 of the respective currency. |
| INT biboPPPLinkDeviceIndex | 1.3.6.1.4.1.272.4.3.3.1.10 | INTEGER | read-only | The underlying link device index. |
| INT biboPPPLinkDirection | 1.3.6.1.4.1.272.4.3.3.1.3 | INTEGER | read-only | Direction of link, incoming(1) or outgoing(2). In case of permanent links, the meaning is dce(1) or dte(2). |
| biboPPPLinkEntry | 1.3.6.1.4.1.272.4.3.3.1 | not-accessible | ||
| DAT biboPPPLinkEstablished | 1.3.6.1.4.1.272.4.3.3.1.2 | Date | read-only | Time when the link was established. |
| INT biboPPPLinkIfIndex | 1.3.6.1.4.1.272.4.3.3.1.1 | INTEGER | read-only | Correlating PPP interface index. |
| CTR biboPPPLinkKeepalivePending | 1.3.6.1.4.1.272.4.3.3.1.9 | Counter | read-only | The amount of keepalive answer packets waiting for since the last occurance of an echo reply packet. |
| CTR biboPPPLinkKeepaliveSent | 1.3.6.1.4.1.272.4.3.3.1.8 | Counter | read-only | The amount of keepalive packets sent on the link. |
| INT biboPPPLinkLcpComp | 1.3.6.1.4.1.272.4.3.3.1.19 | INTEGER | read-only | Address- and Protocol-Field compression. |
| OCT biboPPPLinkLocDiscr | 1.3.6.1.4.1.272.4.3.3.1.20 | OCTET STRING | read-only | Local LCP multilink endpoint discriminator. |
| INT biboPPPLinkLqm | 1.3.6.1.4.1.272.4.3.3.1.18 | INTEGER | read-only | Indicates the successful negotiation of the Link Quality Protocol (LQM). |
| INT biboPPPLinkProtocols | 1.3.6.1.4.1.272.4.3.3.1.4 | INTEGER | read-only | The bitwise ORed protocols successfully negotiated on this link; currently the following protocols are supported: tcp/ip(1), ipx(2), bridge(4), bpdu(8), x25(16). These protocol values are most likely to change in future software releases. |
| OCT biboPPPLinkRemDiscr | 1.3.6.1.4.1.272.4.3.3.1.21 | OCTET STRING | read-only | Peer's LCP multilink endpoint discriminator. |
| CTR biboPPPLinkRetries | 1.3.6.1.4.1.272.4.3.3.1.7 | Counter | read-only | The amount of retries taken to establish the link. |
| INT biboPPPLinkSpeed | 1.3.6.1.4.1.272.4.3.3.1.11 | INTEGER | read-only | The speed of the link. |
| INT biboPPPLinkState | 1.3.6.1.4.1.272.4.3.3.1.5 | INTEGER | read-only | The actual state of each link in a bundle. The link is fully operational in the up(1) state, and not operational in the down(2) state. The starting(3) state is an inter- mediate state when the link is physically established but PPP or other link negotation has not finished yet. The loopbacked(4) state is entered when the PPP keepalive mechanism detects a loopbacked link. The dialing(5) state shows that a dialup link is in its link establishment phase, dialing. If there is no answer to the call, the link enters the retry-wait(6) state for biboPPPRetryTime seconds. After waiting that time either a call retry will occur, or the ifOperStatus will enter the blocked state, depending on the amount of retries already done (biboPPPLinkRetries) and the value of the biboPPPMaxRetries field. |
| INT biboPPPLinkStkNumber | 1.3.6.1.4.1.272.4.3.3.1.13 | INTEGER | read-only | The stack number of the dialup link, correlating to the isdnStkNumber field in the isdnCallTable. |
| biboPPPLinkTable | 1.3.6.1.4.1.272.4.3.3 | not-accessible | The biboPPPLinkTable contains statistical information for each current PPP link on the system. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP interface is created in the biboPPPTable. Deleting entries: Entries are removed by the system when the corresponding PPP interface is removed. | |
| CTR biboPPPLinkUnits | 1.3.6.1.4.1.272.4.3.3.1.6 | Counter | read-only | The costs for this link in units. |
| STR biboPPPLocalIdent | 1.3.6.1.4.1.272.4.3.1.1.24 | DisplayString | read-write | This is the local identification string used for PPP authentication(PAP/CHAP). If this entry is empty the variable biboAdmLocalPPPIdent will be used. |
| STR biboPPPLoginString | 1.3.6.1.4.1.272.4.3.1.1.20 | DisplayString | read-write | A textual string containing a login sequence (script) composed of fields in the format [expect send], comparable to chat scripts commonly used on other sytems. This script is required i.e. to establish an asynchronus PPP dialup connection to CompuServe. |
| INT biboPPPLQMonitoring | 1.3.6.1.4.1.272.4.3.1.1.27 | INTEGER | read-write | This parameter enables (2) or disables (1) PPP Link Quality Monitoring (LQM) according RFC 1989. When set to on(2) LQM is added to the list of parameters used in LCP negotiation. If LQM is acknowledged by peer link quality reports will be generated and send periodically. |
| INT biboPPPMaxConn | 1.3.6.1.4.1.272.4.3.1.1.16 | INTEGER | read-write | The maximum number of channels bundled for this interface. |
| INT biboPPPMaxRetries | 1.3.6.1.4.1.272.4.3.1.1.13 | INTEGER | read-write | The number of dialup retries before changing to the blocked state. |
| INT biboPPPMinConn | 1.3.6.1.4.1.272.4.3.1.1.17 | INTEGER | read-write | The minimum number of channels bundled for this interface. |
| INT biboPPPProfileAuthProtocol | 1.3.6.1.4.1.272.4.3.5.1.2 | INTEGER | read-write | The type of authentication used on the point-to-point link as described in RFC 1334. See biboPPPAuthentication for further details. |
| INT biboPPPProfileAuthRadius | 1.3.6.1.4.1.272.4.3.5.1.3 | INTEGER | read-write | This entry is used to configure possible RADIUS authentication on incoming calls. The default value is inband(2), only inband RADIUS requests (PAP, CHAP) are sent to the defined RADIUS server. Outband requests (CALLERID) are sent in outband(3) mode. If set to both(3), both requests are sent. To disable RADIUS requests in the profile set this value to none(1). To disable authentication attempts via the local data base set this value to radius-only(5). |
| INT biboPPPProfileCallbackNegotiation | 1.3.6.1.4.1.272.4.3.5.1.7 | INTEGER | read-write | Specifies wether callback negotiation (LCP/CBCP) is allowed or not. If set to disabled(1), no callback negotiation will be performed or accepted. If set to enabled(2), PPP callback negotation will be accepted on demand. If this object is set to cbcp-optional(3), the CBCP option 'no callback' is also offered to the Windows client so that the user can decide wether he wants to be called back or not. |
| biboPPPProfileEntry | 1.3.6.1.4.1.272.4.3.5.1 | not-accessible | ||
| INT biboPPPProfileLQMonitoring | 1.3.6.1.4.1.272.4.3.5.1.4 | INTEGER | read-write | This parameter enables (2) or disables (1) PPP Link Quality Monitoring (LQM) according RFC 1989. When set to on(2) LQM is added to the list of parameters acknowledged in LCP negotiation. Link quality reports (LQR) will be generated and send periodically. |
| INT biboPPPProfileName | 1.3.6.1.4.1.272.4.3.5.1.1 | INTEGER | read-only | The name of the PPP profile. Three profiles are available. |
| INT biboPPPProfilePPPoEDevIfIndex | 1.3.6.1.4.1.272.4.3.5.1.5 | INTEGER | read-write | Specifies the device to be used for PPP over Ethernet (PPPoE) according RFC 2516. |
| biboPPPProfileTable | 1.3.6.1.4.1.272.4.3.5 | not-accessible | The biboPPPProfileTable contains PPP default parameters used for PPP negotiation with unknown dialin partners. For PPP connections, PPP profiles are asigned to incoming connections via the isdnDispatchTable. Currently no entries can be created or deleted by user. | |
| INT biboPPPRetryTime | 1.3.6.1.4.1.272.4.3.1.1.11 | INTEGER | read-write | Time in seconds to wait before retrying a call; currently not used. |
| INT biboPPPSessionTimeout | 1.3.6.1.4.1.272.4.3.1.1.29 | INTEGER | read-write | Maximum number of seconds before termination the established PPP session, regardless there is any data throughput on the corresponding link(s). When set to 0, there no limit for the duration of the PPP session. |
| INT biboPPPShortHold | 1.3.6.1.4.1.272.4.3.1.1.14 | INTEGER | read-write | The time in seconds to wait, once the channel is silent, (that is, no data is being received or transmitted) before terminating the link. When set to zero the short hold mode is disabled, when set to -1 the short hold mode is disabled and the link will be reconnected when connection was lost. |
| biboPPPStatEntry | 1.3.6.1.4.1.272.4.3.2.1 | not-accessible | ||
| biboPPPStatTable | 1.3.6.1.4.1.272.4.3.2 | not-accessible | The biboPPPStatTable contains statistical connection- specific information. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP interface is created in the biboPPPTable. Deleting entries: Entries are removed by the system when the corresponding PPP interface is removed. | |
| biboPPPTable | 1.3.6.1.4.1.272.4.3.1 | not-accessible | The biboPPPTable contains configuration information for the PPP interfaces. Each time a new entry is made here, a corresponding entry is made in the ifTable. Creating entries: Entries are created by assigning a value to the biboPPPType object. Deleting entries: Entries are removed by setting an entry's biboPPPEncapsulation object to 'delete'. | |
| CTR biboPPPThroughput | 1.3.6.1.4.1.272.4.3.2.1.21 | Counter | read-only | The actual thoughput of the interface; updated every 5 seconds. |
| INT biboPPPTimeout | 1.3.6.1.4.1.272.4.3.1.1.5 | INTEGER | read-write | The number of milliseconds waiting before retransmitting a PPP configure packet. |
| CTR biboPPPTotalCharge | 1.3.6.1.4.1.272.4.3.2.1.26 | Counter | read-only | The total charge on this interface as 1/1000 of the respective currency. |
| INT biboPPPTotalDuration | 1.3.6.1.4.1.272.4.3.2.1.13 | INTEGER | read-only | The total link duration in seconds. |
| CTR biboPPPTotalIncomingCalls | 1.3.6.1.4.1.272.4.3.2.1.19 | Counter | read-only | The total number of incoming calls. |
| CTR biboPPPTotalIncomingFails | 1.3.6.1.4.1.272.4.3.2.1.20 | Counter | read-only | The total number of incoming call failures. |
| CTR biboPPPTotalOutgoingCalls | 1.3.6.1.4.1.272.4.3.2.1.17 | Counter | read-only | The total number of outgoing calls. |
| CTR biboPPPTotalOutgoingFails | 1.3.6.1.4.1.272.4.3.2.1.18 | Counter | read-only | The total number of outgoing call failures. |
| CTR biboPPPTotalReceivedOctets | 1.3.6.1.4.1.272.4.3.2.1.16 | Counter | read-only | The total amount of octets received. |
| CTR biboPPPTotalTransmitOctets | 1.3.6.1.4.1.272.4.3.2.1.15 | Counter | read-only | The total amount of octets transmitted. |
| CTR biboPPPTotalUnits | 1.3.6.1.4.1.272.4.3.2.1.14 | Counter | read-only | The total costs on this interface for all member links. |
| INT biboPPPType | 1.3.6.1.4.1.272.4.3.1.1.2 | INTEGER | read-write | The type of link. A new dialup link is created when this field is set to the value isdn-dialup(1), dialin-only(3) or multiuser(5). The maximum number of dialup links is limited by system memory. Each dialup link should have at least one corresponding entry in the biboDialTable to configure the remote ISDN telephone number(s). A leased line link, can not be created by setting this field to leased(2), but is automatically established when the IsdnChType field is set to either 'leased-dte' or 'leased-dce' (which doesn't make a difference for PPP, but must be set correctly for other encapsulation methods). Naturally, when the IsdnChType field is set to any other value, the biboPPPTable entry is removed. In both cases, a new entry in the biboPPPTable creates corre- corresponding entries in the ifTable (a new interface) and in the biboPPPStatTable (PPP statistics). Setting this object to multiuser(5), up to biboPPPMaxConn matching incoming connections (see biboPPPAuthentication, biboPPPAuthSecret, biboPPPAuthIdent) from different dialin partners will be accepted. |
| INT biboPPPVJHeaderComp | 1.3.6.1.4.1.272.4.3.1.1.21 | INTEGER | read-write | This entry is used to enable Van Jacobsen TCP/IP header compression, which reduces the size of TCP/IP packet headers and increases the efficiency of line utilization. |
| bintec | 1.3.6.1.4.1.272 | |||
| dialmap | 1.3.6.1.4.1.272.4.4 | |||
| dod | 1.3.6 | |||
| enterprises | 1.3.6.1.4.1 | |||
| internet | 1.3.6.1 | |||
| org | 1.3 | |||
| ppp | 1.3.6.1.4.1.272.4.3 | |||
| INT pppExtIfAlgorithm | 1.3.6.1.4.1.272.4.3.9.1.3 | INTEGER | read-write | The algorithm to use for weighting line utilization. Line utilization is determined by calculating the average load for each interface. When set to equal (1) all samples taken over the time interval (defined in pppExtIfInterval) will be given equal weight, when set to proportional (2) the weighting disproportional to the age of the sample. |
| INT pppExtIfAodiDChanQlen | 1.3.6.1.4.1.272.4.3.9.1.15 | INTEGER | read-write | Upper threshold for the amount of data (in octets) waiting to be sent across the 9.6Kbit/sec D-channel. If exceeded, additional bandwidth will be invoked at once. |
| INT pppExtIfAodiGearDownTxRate | 1.3.6.1.4.1.272.4.3.9.1.16 | INTEGER | read-write | Lower threshold for the amount of data in bits per second to be sent across the 64Kbit/sec B-channel. If the measured throughput becomes smaller than this value over a period of pppExtIfGearDownPersistance seconds, the remaining B-channel will be dropped. |
| INT pppExtIfAuthMutual | 1.3.6.1.4.1.272.4.3.9.1.24 | INTEGER | read-write | This object enables mutual PPP authentication between the peers. |
| INT pppExtIfBodMode | 1.3.6.1.4.1.272.4.3.9.1.2 | INTEGER | read-write | Enables bandwidth on demand (BOD) mode for leased line and dialup interfaces when setting to bod-active (3) respectively bod-passive (4) or backup only mode for leased line connections like X.21. When set to disabled (1), neither bandwidth on demand (as specified by the pppExtIfTable) or backup mode is enabled. Four modes (bap-active (5), bap-passive (6), bap-both(7) and bap-first (8)) are available for BAP (Bandwidth Allocation Protocol) support to specify wether BAP Call-Requests and BAP Callback-Requests should be initiated and/or accepted. |
| INT pppExtIfCurrentRetryTime | 1.3.6.1.4.1.272.4.3.9.1.20 | INTEGER | read-write | Current time in seconds to wait before retrying a call when the smart retry algorithm is implemented. |
| INT pppExtIfEncKeyNegotiation | 1.3.6.1.4.1.272.4.3.9.1.10 | INTEGER | read-write | This variable defines the specification of shared secrets (encryption keys) between the sender and receiver of encrypted data. If set to static (1), the keys specified in 'pppExtIfEncTxKey' and 'pppExtIfEncRxKey' will be used, if set to authentication (2), the key derivation is based on PPP authentication via CHAP or MS-CHAP. |
| OCT pppExtIfEncRxKey | 1.3.6.1.4.1.272.4.3.9.1.12 | OCTET STRING | read-write | Static (decryption) key used for decryption of encrypted data received on PPP connections. It's size depends on the used encryption algorithm and the corresponding key length, e.g. 'des_56' or 'blowfish_168'. |
| OCT pppExtIfEncTxKey | 1.3.6.1.4.1.272.4.3.9.1.11 | OCTET STRING | read-write | Static (encryption) key used for transmission of encrypted data via PPP. It's size depends on the used encryption algorithm and the corresponding key length, e.g. 'des_56' or 'blowfish_168'. |
| pppExtIfEntry | 1.3.6.1.4.1.272.4.3.9.1 | not-accessible | ||
| INT pppExtIfGearDownPersistance | 1.3.6.1.4.1.272.4.3.9.1.18 | INTEGER | read-write | Gear down persistence interval for decreasing current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with the current value of pppExtIfGearDownThreshold once per second. If exceeded longer than pppExtIfGearDownPersistance seconds, exactly one B-channel will be dropped. |
| INT pppExtIfGearDownThreshold | 1.3.6.1.4.1.272.4.3.9.1.14 | INTEGER | read-write | Gear down threshold for decreasing current bandwidth. The expected throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) after dropping a B-channel is compared with this threshold value once per second. If the needed bandwidth falls below this threshold longer than 10 seconds, exactly one B-channel will be dropped. |
| INT pppExtIfGearUpPersistance | 1.3.6.1.4.1.272.4.3.9.1.17 | INTEGER | read-write | Gear up persistence interval for invoking current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with the current value of the variable pppExtIfGearUpThreshold once per second. If exceeded longer than pppExtIfGearUpPersistance seconds an additional B-channel will be requested. |
| INT pppExtIfGearUpThreshold | 1.3.6.1.4.1.272.4.3.9.1.13 | INTEGER | read-write | Gear up threshold for invoking current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with this value once per second. If exceeded longer than 5 seconds an additional B-channel will be requested. |
| INT pppExtIfIndex | 1.3.6.1.4.1.272.4.3.9.1.1 | INTEGER | read-write | Correlating PPP interface index. |
| INT pppExtIfInterval | 1.3.6.1.4.1.272.4.3.9.1.4 | INTEGER | read-write | The time interval (in seconds) to use for sampling and calculating of the average throughput of the interface. See also: pppExtIfLoad. |
| INT pppExtIfL1Speed | 1.3.6.1.4.1.272.4.3.9.1.19 | INTEGER | read-write | This object contains the interface's nominal bandwidth in bits per second. Please note that this parameter may not represent the real available transmission rate. The current purpose is only informational for example for PPTP or PPPoE interfaces where no accurate information from the underlaying network is available. |
| INT pppExtIfLoad | 1.3.6.1.4.1.272.4.3.9.1.5 | INTEGER | read-only | The actual throughput (in percent) of the total bandwidth of this interface (load). This value is updated once every second. |
| INT pppExtIfMaxRetryTime | 1.3.6.1.4.1.272.4.3.9.1.21 | INTEGER | read-write | Maximum time in seconds to wait before retrying a call when the smart retry algorithm is implemented. When set to zero this algorithm is disabled. |
| INT pppExtIfMlpFragmentation | 1.3.6.1.4.1.272.4.3.9.1.6 | INTEGER | read-write | The multilink PPP fragmentation mode. When set to proportional (1) packets will be divided into fragments proportional to the transmission rate of each link, when set to equal (2) packets will be divided into multiple equal fragments (equal to MlpFragSize) such that the number sent on each link is proportional to the transmission rate. When set to interleave (3), large datagrams will be fragmentated (maximum size determined by MlpFragSize) to reduce transmission delay of high-priority traffic on slower links. |
| INT pppExtIfMlpFragSize | 1.3.6.1.4.1.272.4.3.9.1.7 | INTEGER | read-write | The multilink PPP fragment size. If MlpFragmentation is set to proportional (1) this value specifies the minimum size of the fragment in bytes. If MlpFragmentation is set to equal (2) this value specifies the maximum fragment size in bytes. |
| INT pppExtIfMru | 1.3.6.1.4.1.272.4.3.9.1.23 | INTEGER | read-write | The maximum length for the PPP information field, including padding, but not including the protocol field, is termed the Maximum Receive Unit (MRU). |
| INT pppExtIfMtu | 1.3.6.1.4.1.272.4.3.9.1.22 | INTEGER | read-write | Determines size of the largest datagram which can be sent on the interface, specified in octets (see ifMtu). When set to zero (default), the value of the variable ifMtu depends on the received LCP MRU/MRRU option. |
| STR pppExtIfPPPoEAcServer | 1.3.6.1.4.1.272.4.3.9.1.9 | DisplayString | read-write | The PPPoE (PPP over Ethernet, RFC 2516) AC-Server name which determines the access concentrator during PPPoE discovery stage. |
| STR pppExtIfPPPoEService | 1.3.6.1.4.1.272.4.3.9.1.8 | DisplayString | read-write | The PPPoE (PPP over Ethernet, RFC 2516) service name which indicates the requested service during PPPoE discovery stage. Examples of the use of the service name are to indicate an ISP name or a class or a quality of service. |
| pppExtIfTable | 1.3.6.1.4.1.272.4.3.9 | not-accessible | The pppExtIfTable contains extended configuration and information related to the PPP interfaces on the system. Entries are optional for each interface and can be added or deleted by the user. Deleting entries: Entries are removed by setting an entry's pppExtIfBodMode object to 'delete'. | |
| IP pppIpInUseAddress | 1.3.6.1.4.1.272.4.3.7.1.1 | IpAddress | read-only | assigned IP address |
| INT pppIpInUseAge | 1.3.6.1.4.1.272.4.3.7.1.6 | INTEGER | read-only | This object specifies the age of the entry after creation or after changing into state reserved(2). After expiration the IP address (see pppIpInUseAddress) is no longer reserved for peer specified by pppIpInUseIdent and this entry will be deleted. |
| pppIpInUseEntry | 1.3.6.1.4.1.272.4.3.7.1 | not-accessible | ||
| STR pppIpInUseIdent | 1.3.6.1.4.1.272.4.3.7.1.4 | DisplayString | read-only | The remote authentication identification string. |
| INT pppIpInUseIfIndex | 1.3.6.1.4.1.272.4.3.7.1.3 | INTEGER | read-only | Unique interface index |
| INT pppIpInUsePoolId | 1.3.6.1.4.1.272.4.3.7.1.2 | INTEGER | read-only | Unique IP address pool ID |
| INT pppIpInUseState | 1.3.6.1.4.1.272.4.3.7.1.5 | INTEGER | read-only | If an IP address is currently assigned, the state of this entry is set to assigned(1). Otherwise, after disconnect, it is set to reserved(2) until the same peer reconnects or this entry expires (see pppIpInUseAge). |
| pppIpInUseTable | 1.3.6.1.4.1.272.4.3.7 | not-accessible | The pppIpUseTable contains dynamically assigned IP addresses. | |
| INT pppLqmCallReference | 1.3.6.1.4.1.272.4.3.6.1.2 | INTEGER | read-only | The call reference of the dialup link, correlating to the isdnCallReference field in the isdnCallTable. |
| pppLqmEntry | 1.3.6.1.4.1.272.4.3.6.1 | not-accessible | ||
| INT pppLqmIfIndex | 1.3.6.1.4.1.272.4.3.6.1.1 | INTEGER | read-only | Correlating PPP interface index. |
| CTR pppLqmInDiscards | 1.3.6.1.4.1.272.4.3.6.1.10 | Counter | read-only | Number of Packets received on this link, but discarded. |
| CTR pppLqmInErrors | 1.3.6.1.4.1.272.4.3.6.1.11 | Counter | read-only | Number of errorneous Packets received on this link. |
| CTR pppLqmInLQRs | 1.3.6.1.4.1.272.4.3.6.1.7 | Counter | read-only | Number of Link Quality Reports (LQR) received on this link. |
| CTR pppLqmInOctets | 1.3.6.1.4.1.272.4.3.6.1.9 | Counter | read-only | Number of Octets reveived on this link, including framing data. |
| CTR pppLqmInPackets | 1.3.6.1.4.1.272.4.3.6.1.8 | Counter | read-only | Number of Packets reveived on this link. |
| CTR pppLqmLostOutLQRs | 1.3.6.1.4.1.272.4.3.6.1.20 | Counter | read-only | Number of lost Link Quality Reports (LQR) transmitted on this link. |
| CTR pppLqmLostOutOctets | 1.3.6.1.4.1.272.4.3.6.1.22 | Counter | read-only | Number of lost Octets transmitted on this link. |
| CTR pppLqmLostOutPackets | 1.3.6.1.4.1.272.4.3.6.1.21 | Counter | read-only | Number of lost Packets transmitted on this link. |
| CTR pppLqmLostPeerOutLQRs | 1.3.6.1.4.1.272.4.3.6.1.23 | Counter | read-only | Number of lost Link Quality Reports (LQR) transmitted by remote on this link. |
| CTR pppLqmLostPeerOutOcts | 1.3.6.1.4.1.272.4.3.6.1.25 | Counter | read-only | Number of lost Octets transmitted by remote on this link. |
| CTR pppLqmLostPeerOutPkts | 1.3.6.1.4.1.272.4.3.6.1.24 | Counter | read-only | Number of lost Packets transmitted by remote on this link. |
| CTR pppLqmOutLQRs | 1.3.6.1.4.1.272.4.3.6.1.4 | Counter | read-only | Number of transmitted Link Quality Reports (LQR) on this link. |
| CTR pppLqmOutOctets | 1.3.6.1.4.1.272.4.3.6.1.6 | Counter | read-only | Number of transmitted Octets on this link, including framing data. |
| CTR pppLqmOutPackets | 1.3.6.1.4.1.272.4.3.6.1.5 | Counter | read-only | Number of transmitted Packets on this link. |
| CTR pppLqmPeerInDiscards | 1.3.6.1.4.1.272.4.3.6.1.18 | Counter | read-only | Number of Packets received by remote on this link, but discarded. |
| CTR pppLqmPeerInErrors | 1.3.6.1.4.1.272.4.3.6.1.19 | Counter | read-only | Number of errorneous Packets received by remote on this link. |
| CTR pppLqmPeerInLQRs | 1.3.6.1.4.1.272.4.3.6.1.15 | Counter | read-only | Number of Link Quality Reports (LQR) received by remote on this link. |
| CTR pppLqmPeerInOctets | 1.3.6.1.4.1.272.4.3.6.1.17 | Counter | read-only | Number of Octets reveived by remote on this link, including framing data. |
| CTR pppLqmPeerInPackets | 1.3.6.1.4.1.272.4.3.6.1.16 | Counter | read-only | Number of Packets reveived by remote on this link. |
| CTR pppLqmPeerOutLQRs | 1.3.6.1.4.1.272.4.3.6.1.12 | Counter | read-only | Number of Link Quality Reports (LQR) transmitted by remote on this link. |
| CTR pppLqmPeerOutOctets | 1.3.6.1.4.1.272.4.3.6.1.14 | Counter | read-only | Number of Octets transmitted by remote on this link, including framing data. |
| CTR pppLqmPeerOutPackets | 1.3.6.1.4.1.272.4.3.6.1.13 | Counter | read-only | Number of Packets transmitted by remote on this link. |
| INT pppLqmReportingPeriod | 1.3.6.1.4.1.272.4.3.6.1.3 | INTEGER | read-only | The LQMReportingPeriod field indicates the maximum time in hundredths of seconds between transmission of Link Quality Reports (LQR). The peer may transmit packets at a faster rate than that which was negotiated. |
| pppLqmTable | 1.3.6.1.4.1.272.4.3.6 | not-accessible | The pppLqmTable contains statistical information for each current PPP link on the system. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP link was established and LQM negotiated successful. Deleting entries: Entries are removed by the system when the corresponding PPP link is disconnected. | |
| INT pppSessionAuthProt | 1.3.6.1.4.1.272.4.3.10.1.5 | INTEGER | read-only | The negotiated PPP authentication protocol. |
| INT pppSessionBacpFavoredPeer | 1.3.6.1.4.1.272.4.3.10.1.18 | INTEGER | read-only | The result of the BACP Favored-Peer negotiation. |
| INT pppSessionCbcpDelay | 1.3.6.1.4.1.272.4.3.10.1.9 | INTEGER | read-only | The negotiated (CBCP) callback delay in seconds. |
| INT pppSessionCbcpMode | 1.3.6.1.4.1.272.4.3.10.1.8 | INTEGER | read-only | The negotiated Callback Control Protocol (CBCP) mode. |
| INT pppSessionCompression | 1.3.6.1.4.1.272.4.3.10.1.6 | INTEGER | read-only | The negotiated CCP compression mode. |
| IP pppSessionDNS1 | 1.3.6.1.4.1.272.4.3.10.1.12 | IpAddress | read-only | The negotiated first name server IP address. |
| IP pppSessionDNS2 | 1.3.6.1.4.1.272.4.3.10.1.13 | IpAddress | read-only | The negotiated second name server IP address. |
| INT pppSessionEncryption | 1.3.6.1.4.1.272.4.3.10.1.7 | INTEGER | read-only | The negotiated CCP encryption mode. |
| pppSessionEntry | 1.3.6.1.4.1.272.4.3.10.1 | not-accessible | ||
| INT pppSessionIfIndex | 1.3.6.1.4.1.272.4.3.10.1.1 | INTEGER | read-only | Correlating PPP interface index. |
| OCT pppSessionIpxcpNodeNumber | 1.3.6.1.4.1.272.4.3.10.1.17 | OCTET STRING | read-only | Unique IPX Node Id dynamically assigned the client. |
| INT pppSessionLcpCallback | 1.3.6.1.4.1.272.4.3.10.1.4 | INTEGER | read-only | Callback option inside LCP negotiation. |
| IP pppSessionLocIpAddr | 1.3.6.1.4.1.272.4.3.10.1.10 | IpAddress | read-only | The negotiated local IP Address. |
| INT pppSessionMlp | 1.3.6.1.4.1.272.4.3.10.1.2 | INTEGER | read-only | Indicates negotiation of Multilink PPP. |
| CTR pppSessionMru | 1.3.6.1.4.1.272.4.3.10.1.3 | Counter | read-only | Peer's MRU/MRRU LCP option. |
| IP pppSessionRemIpAddr | 1.3.6.1.4.1.272.4.3.10.1.11 | IpAddress | read-only | The negotiated remote IP Address. |
| pppSessionTable | 1.3.6.1.4.1.272.4.3.10 | not-accessible | The pppSessionTable contains statistical information for the PPP protocol. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP connection is created. Deleting entries: Entries are removed by the system when the corresponding PPP connection is terminated. | |
| INT pppSessionVJHeaderComp | 1.3.6.1.4.1.272.4.3.10.1.16 | INTEGER | read-only | The negotiation of Van Jacobsen TCP/IP header compression option (IPCP). |
| IP pppSessionWINS1 | 1.3.6.1.4.1.272.4.3.10.1.14 | IpAddress | read-only | The negotiated first NetBIOS name server (WINS) IP address. |
| IP pppSessionWINS2 | 1.3.6.1.4.1.272.4.3.10.1.15 | IpAddress | read-only | The negotiated second NetBIOS name server (WINS) IP address. |
| private | 1.3.6.1.4 |
RFC description
Manages PPP link configuration, authentication, and statistics on bintec elmeg BIANCA/BRICK broadband routers.
Start monitoring bintec BIANCA/BRICK ISDN/VPN routers (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.