BIANCA-BRICK-PPP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for BIANCA-BRICK-PPP-MIB.
199
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
199 total| Object Name |
|---|
org OBJECT IDENTIFIER .1.3 |
RFC1155-SMI Unknown .1.3 |
dod OBJECT IDENTIFIER .1.3.6 |
internet OBJECT IDENTIFIER .1.3.6.1 |
private OBJECT IDENTIFIER .1.3.6.1.4 |
enterprises OBJECT IDENTIFIER .1.3.6.1.4.1 |
bintec OBJECT IDENTIFIER .1.3.6.1.4.1.272 |
bibo OBJECT IDENTIFIER .1.3.6.1.4.1.272.4 |
ppp OBJECT IDENTIFIER .1.3.6.1.4.1.272.4.3 |
biboPPPTableThe 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'. SEQUENCE OF BiboPPPEntry .1.3.6.1.4.1.272.4.3.1 |
biboPPPEntry BiboPPPEntry .1.3.6.1.4.1.272.4.3.1.1 |
biboPPPIfIndexCorrelating PPP interface index. This value is
assigned automatically by the system.ro INTEGER .1.3.6.1.4.1.272.4.3.1.1.1 |
biboPPPTypeThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.2 |
biboPPPEncapsulationThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.3 |
biboPPPKeepaliveWhen 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.4 |
biboPPPTimeoutThe number of milliseconds waiting before
retransmitting a PPP configure packet.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.5 |
biboPPPCompressionThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.6 |
biboPPPAuthenticationThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.7 |
biboPPPAuthIdentThe 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').rw DisplayString .1.3.6.1.4.1.272.4.3.1.1.8 |
biboPPPAuthSecretThe authentication secret, which is used symmetrically
for both local and remote sides of the PPP link.rw DisplayString .1.3.6.1.4.1.272.4.3.1.1.9 |
biboPPPIpAddressThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.10 |
biboPPPRetryTimeTime in seconds to wait before retrying a call;
currently not used.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.11 |
biboPPPBlockTimeTime 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.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.12 |
biboPPPMaxRetriesThe number of dialup retries before changing to
the blocked state.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.13 |
biboPPPShortHoldThe 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.rw INTEGER (-1..3600) .1.3.6.1.4.1.272.4.3.1.1.14 |
biboPPPInitConnThe number of channels to initially set up for this
interface.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.15 |
biboPPPMaxConnThe maximum number of channels bundled for this interface.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.16 |
biboPPPMinConnThe minimum number of channels bundled for this interface.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.17 |
biboPPPCallbackIf 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.18 |
biboPPPLayer1ProtocolThis entry is used to select the layer 1 protocol settings
for this partner. Normally the correct entry is hdlc-64.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.19 |
biboPPPLoginStringA 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.rw DisplayString .1.3.6.1.4.1.272.4.3.1.1.20 |
biboPPPVJHeaderCompThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.21 |
biboPPPLayer2ModeThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.22 |
biboPPPDynShortHoldOptimizes 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.)rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.23 |
biboPPPLocalIdentThis is the local identification string used for PPP
authentication(PAP/CHAP). If this entry is empty the
variable biboAdmLocalPPPIdent will be used.rw DisplayString .1.3.6.1.4.1.272.4.3.1.1.24 |
biboPPPDNSNegotiationThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.25 |
biboPPPEncryptionThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.26 |
biboPPPLQMonitoringThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.1.1.27 |
biboPPPIpPoolIdPool ID value to select an IP address pool for dynamic IP
address assignment via IPCP. See also PPPIpAssignTable
for further details.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.28 |
biboPPPSessionTimeoutMaximum 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.rw INTEGER .1.3.6.1.4.1.272.4.3.1.1.29 |
biboPPPStatTableThe 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. SEQUENCE OF BiboPPPStatEntry .1.3.6.1.4.1.272.4.3.2 |
biboPPPStatEntry BiboPPPStatEntry .1.3.6.1.4.1.272.4.3.2.1 |
biboPPPConnIfIndexCorrelating PPP interface index.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.1 |
biboPPPConnActiveThe actual number of bundled channels.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.2 |
biboPPPConnProtocolsThe 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.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.3 |
biboPPPConnStateThe physical state of the link. This field is obsolete
and will not be supported in a future release.ro Enumeration .1.3.6.1.4.1.272.4.3.2.1.4 |
biboPPPConnDurationThe current link duration on this interface in seconds.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.5 |
biboPPPConnUnitsThe current costs on this interface for all member links.ro Counter .1.3.6.1.4.1.272.4.3.2.1.6 |
biboPPPConnTransmitOctetsThe octets transmitted on this interface since its last
change to the 'up' state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.7 |
biboPPPConnReceivedOctetsThe octets received since its last change to the `up'
state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.8 |
biboPPPConnOutgoingCallsThe number of outgoing calls on this interface since
its last change to the 'up' state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.9 |
biboPPPConnOutgoingFailsThe number of outgoing call failures on this interface
since its last change to the 'up' state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.10 |
biboPPPConnIncomingCallsThe number of incoming calls on this interface since
its last change to the up state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.11 |
biboPPPConnIncomingFailsThe number of incoming call failures on this interface since
its last change to the up state.ro Counter .1.3.6.1.4.1.272.4.3.2.1.12 |
biboPPPTotalDurationThe total link duration in seconds.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.13 |
biboPPPTotalUnitsThe total costs on this interface for all member links.ro Counter .1.3.6.1.4.1.272.4.3.2.1.14 |
biboPPPTotalTransmitOctetsThe total amount of octets transmitted.ro Counter .1.3.6.1.4.1.272.4.3.2.1.15 |
biboPPPTotalReceivedOctetsThe total amount of octets received.ro Counter .1.3.6.1.4.1.272.4.3.2.1.16 |
biboPPPTotalOutgoingCallsThe total number of outgoing calls.ro Counter .1.3.6.1.4.1.272.4.3.2.1.17 |
biboPPPTotalOutgoingFailsThe total number of outgoing call failures.ro Counter .1.3.6.1.4.1.272.4.3.2.1.18 |
biboPPPTotalIncomingCallsThe total number of incoming calls.ro Counter .1.3.6.1.4.1.272.4.3.2.1.19 |
biboPPPTotalIncomingFailsThe total number of incoming call failures.ro Counter .1.3.6.1.4.1.272.4.3.2.1.20 |
biboPPPThroughputThe actual thoughput of the interface; updated every
5 seconds.ro Counter .1.3.6.1.4.1.272.4.3.2.1.21 |
biboPPPCompressionModeThis object describes wether data compression is active
for this interface. 42bis or Stac LZS compression
algorithm can be enabled in the biboPPPTable.ro Enumeration .1.3.6.1.4.1.272.4.3.2.1.22 |
biboPPPChargeIntervalDescribes the measured interval between charging info
elements received from the ISDN network.ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.23 |
biboPPPIdleTimeThe currently measured connection inactivity time
(channel is silent).ro INTEGER .1.3.6.1.4.1.272.4.3.2.1.24 |
biboPPPConnChargeThe current charge on this interface as 1/1000 of the
respective currency.ro Counter .1.3.6.1.4.1.272.4.3.2.1.25 |
biboPPPTotalChargeThe total charge on this interface as 1/1000 of the
respective currency.ro Counter .1.3.6.1.4.1.272.4.3.2.1.26 |
biboPPPLinkTableThe 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. SEQUENCE OF BiboPPPLinkEntry .1.3.6.1.4.1.272.4.3.3 |
biboPPPLinkEntry BiboPPPLinkEntry .1.3.6.1.4.1.272.4.3.3.1 |
biboPPPLinkIfIndexCorrelating PPP interface index.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.1 |
biboPPPLinkEstablishedTime when the link was established.ro Date .1.3.6.1.4.1.272.4.3.3.1.2 |
biboPPPLinkDirectionDirection of link, incoming(1) or outgoing(2). In case
of permanent links, the meaning is dce(1) or dte(2).ro Enumeration .1.3.6.1.4.1.272.4.3.3.1.3 |
biboPPPLinkProtocolsThe 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.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.4 |
biboPPPLinkStateThe 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.ro Enumeration .1.3.6.1.4.1.272.4.3.3.1.5 |
biboPPPLinkUnitsThe costs for this link in units.ro Counter .1.3.6.1.4.1.272.4.3.3.1.6 |
biboPPPLinkRetriesThe amount of retries taken to establish the link.ro Counter .1.3.6.1.4.1.272.4.3.3.1.7 |
biboPPPLinkKeepaliveSentThe amount of keepalive packets sent on the link.ro Counter .1.3.6.1.4.1.272.4.3.3.1.8 |
biboPPPLinkKeepalivePendingThe amount of keepalive answer packets waiting for
since the last occurance of an echo reply packet.ro Counter .1.3.6.1.4.1.272.4.3.3.1.9 |
biboPPPLinkDeviceIndexThe underlying link device index.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.10 |
biboPPPLinkSpeedThe speed of the link.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.11 |
biboPPPLinkStkNumberThe stack number of the dialup link, correlating to
the isdnStkNumber field in the isdnCallTable.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.13 |
biboPPPLinkCallTypeThe call type of the dialup link, correlating to
the isdnCallType field in the isdnCallTable.ro Enumeration .1.3.6.1.4.1.272.4.3.3.1.14 |
biboPPPLinkCallReferenceThe call reference of the dialup link, correlating to
the isdnCallReference field in the isdnCallTable.ro INTEGER .1.3.6.1.4.1.272.4.3.3.1.15 |
biboPPPLinkChargeThe costs for this link as 1/1000 of the respective currency.ro Counter .1.3.6.1.4.1.272.4.3.3.1.16 |
biboPPPLinkAccm.ro OCTET STRING .1.3.6.1.4.1.272.4.3.3.1.17 |
biboPPPLinkLqmIndicates the successful negotiation of the Link Quality
Protocol (LQM).ro Enumeration .1.3.6.1.4.1.272.4.3.3.1.18 |
biboPPPLinkLcpCompAddress- and Protocol-Field compression.ro Enumeration .1.3.6.1.4.1.272.4.3.3.1.19 |
biboPPPLinkLocDiscrLocal LCP multilink endpoint discriminator.ro OCTET STRING .1.3.6.1.4.1.272.4.3.3.1.20 |
biboPPPLinkRemDiscrPeer's LCP multilink endpoint discriminator.ro OCTET STRING .1.3.6.1.4.1.272.4.3.3.1.21 |
biboPPPIpAssignTableThe 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. SEQUENCE OF BiboPPPIpAssignEntry .1.3.6.1.4.1.272.4.3.4 |
biboPPPIpAssignEntryPool of IP addresses for dynamic IP address assignment via IPCP.
See the biboPPPIpAddress field for further explanation. BiboPPPIpAssignEntry .1.3.6.1.4.1.272.4.3.4.1 |
biboPPPIpAssignAddressFirst IP address of this range.rw IpAddress .1.3.6.1.4.1.272.4.3.4.1.1 |
biboPPPIpAssignStateIf 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).rw Enumeration .1.3.6.1.4.1.272.4.3.4.1.2 |
biboPPPIpAssignPoolIdPool ID value.rw INTEGER .1.3.6.1.4.1.272.4.3.4.1.3 |
biboPPPIpAssignRangeNumber of IP addresses that will be assigned starting
from biboPPPIpAssignAddress. A range of 0 will disable
this entryrw INTEGER .1.3.6.1.4.1.272.4.3.4.1.4 |
biboPPPProfileTableThe 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. SEQUENCE OF BiboPPPProfileEntry .1.3.6.1.4.1.272.4.3.5 |
biboPPPProfileEntry BiboPPPProfileEntry .1.3.6.1.4.1.272.4.3.5.1 |
biboPPPProfileNameThe name of the PPP profile. Three profiles are available.ro Enumeration .1.3.6.1.4.1.272.4.3.5.1.1 |
biboPPPProfileAuthProtocolThe type of authentication used on the point-to-point
link as described in RFC 1334. See biboPPPAuthentication
for further details.rw Enumeration .1.3.6.1.4.1.272.4.3.5.1.2 |
biboPPPProfileAuthRadiusThis 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).rw Enumeration .1.3.6.1.4.1.272.4.3.5.1.3 |
biboPPPProfileLQMonitoringThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.5.1.4 |
biboPPPProfilePPPoEDevIfIndexSpecifies the device to be used for PPP over Ethernet (PPPoE)
according RFC 2516.rw INTEGER .1.3.6.1.4.1.272.4.3.5.1.5 |
biboPPPProfileCallbackNegotiationSpecifies 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.rw Enumeration .1.3.6.1.4.1.272.4.3.5.1.7 |
pppLqmTableThe 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. SEQUENCE OF PppLqmEntry .1.3.6.1.4.1.272.4.3.6 |
pppLqmEntry PppLqmEntry .1.3.6.1.4.1.272.4.3.6.1 |
pppLqmIfIndexCorrelating PPP interface index.ro INTEGER .1.3.6.1.4.1.272.4.3.6.1.1 |
pppLqmCallReferenceThe call reference of the dialup link, correlating to
the isdnCallReference field in the isdnCallTable.ro INTEGER .1.3.6.1.4.1.272.4.3.6.1.2 |
pppLqmReportingPeriodThe 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.ro INTEGER .1.3.6.1.4.1.272.4.3.6.1.3 |
pppLqmOutLQRsNumber of transmitted Link Quality Reports (LQR) on this
link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.4 |
pppLqmOutPacketsNumber of transmitted Packets on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.5 |
pppLqmOutOctetsNumber of transmitted Octets on this link, including framing
data.ro Counter .1.3.6.1.4.1.272.4.3.6.1.6 |
pppLqmInLQRsNumber of Link Quality Reports (LQR) received on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.7 |
pppLqmInPacketsNumber of Packets reveived on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.8 |
pppLqmInOctetsNumber of Octets reveived on this link, including framing
data.ro Counter .1.3.6.1.4.1.272.4.3.6.1.9 |
pppLqmInDiscardsNumber of Packets received on this link, but discarded.ro Counter .1.3.6.1.4.1.272.4.3.6.1.10 |
pppLqmInErrorsNumber of errorneous Packets received on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.11 |
pppLqmPeerOutLQRsNumber of Link Quality Reports (LQR) transmitted by remote
on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.12 |
pppLqmPeerOutPacketsNumber of Packets transmitted by remote on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.13 |
pppLqmPeerOutOctetsNumber of Octets transmitted by remote on this link,
including framing data.ro Counter .1.3.6.1.4.1.272.4.3.6.1.14 |
pppLqmPeerInLQRsNumber of Link Quality Reports (LQR) received by remote
on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.15 |
pppLqmPeerInPacketsNumber of Packets reveived by remote on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.16 |
pppLqmPeerInOctetsNumber of Octets reveived by remote on this link, including
framing data.ro Counter .1.3.6.1.4.1.272.4.3.6.1.17 |
pppLqmPeerInDiscardsNumber of Packets received by remote on this link, but
discarded.ro Counter .1.3.6.1.4.1.272.4.3.6.1.18 |
pppLqmPeerInErrorsNumber of errorneous Packets received by remote on this
link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.19 |
pppLqmLostOutLQRsNumber of lost Link Quality Reports (LQR) transmitted on
this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.20 |
pppLqmLostOutPacketsNumber of lost Packets transmitted on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.21 |
pppLqmLostOutOctetsNumber of lost Octets transmitted on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.22 |
pppLqmLostPeerOutLQRsNumber of lost Link Quality Reports (LQR) transmitted by
remote on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.23 |
pppLqmLostPeerOutPktsNumber of lost Packets transmitted by remote on this
link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.24 |
pppLqmLostPeerOutOctsNumber of lost Octets transmitted by remote on this link.ro Counter .1.3.6.1.4.1.272.4.3.6.1.25 |
pppIpInUseTableThe pppIpUseTable contains dynamically assigned IP addresses. SEQUENCE OF PppIpInUseEntry .1.3.6.1.4.1.272.4.3.7 |
pppIpInUseEntry PppIpInUseEntry .1.3.6.1.4.1.272.4.3.7.1 |
pppIpInUseAddressassigned IP addressro IpAddress .1.3.6.1.4.1.272.4.3.7.1.1 |
pppIpInUsePoolIdUnique IP address pool IDro INTEGER .1.3.6.1.4.1.272.4.3.7.1.2 |
pppIpInUseIfIndexUnique interface indexro INTEGER .1.3.6.1.4.1.272.4.3.7.1.3 |
pppIpInUseIdentThe remote authentication identification string.ro DisplayString .1.3.6.1.4.1.272.4.3.7.1.4 |
pppIpInUseStateIf 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).ro Enumeration .1.3.6.1.4.1.272.4.3.7.1.5 |
pppIpInUseAgeThis 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.ro INTEGER .1.3.6.1.4.1.272.4.3.7.1.6 |
pppExtIfTableThe 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'. SEQUENCE OF PppExtIfEntry .1.3.6.1.4.1.272.4.3.9 |
pppExtIfEntry PppExtIfEntry .1.3.6.1.4.1.272.4.3.9.1 |
pppExtIfIndexCorrelating PPP interface index.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.1 |
pppExtIfBodModeEnables 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.rw Enumeration .1.3.6.1.4.1.272.4.3.9.1.2 |
pppExtIfAlgorithmThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.9.1.3 |
pppExtIfIntervalThe time interval (in seconds) to use for sampling and
calculating of the average throughput of the interface.
See also: pppExtIfLoad.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.4 |
pppExtIfLoadThe actual throughput (in percent) of the total bandwidth
of this interface (load). This value is updated once every
second.ro INTEGER .1.3.6.1.4.1.272.4.3.9.1.5 |
pppExtIfMlpFragmentationThe 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.rw Enumeration .1.3.6.1.4.1.272.4.3.9.1.6 |
pppExtIfMlpFragSizeThe 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.7 |
pppExtIfPPPoEServiceThe 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.rw DisplayString .1.3.6.1.4.1.272.4.3.9.1.8 |
pppExtIfPPPoEAcServerThe PPPoE (PPP over Ethernet, RFC 2516) AC-Server name which
determines the access concentrator during PPPoE discovery
stage.rw DisplayString .1.3.6.1.4.1.272.4.3.9.1.9 |
pppExtIfEncKeyNegotiationThis 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.rw Enumeration .1.3.6.1.4.1.272.4.3.9.1.10 |
pppExtIfEncTxKeyStatic (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'.rw OCTET STRING .1.3.6.1.4.1.272.4.3.9.1.11 |
pppExtIfEncRxKeyStatic (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'.rw OCTET STRING .1.3.6.1.4.1.272.4.3.9.1.12 |
pppExtIfGearUpThresholdGear 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.13 |
pppExtIfGearDownThresholdGear 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.14 |
pppExtIfAodiDChanQlenUpper 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.15 |
pppExtIfAodiGearDownTxRateLower 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.16 |
pppExtIfGearUpPersistanceGear 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.17 |
pppExtIfGearDownPersistanceGear 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.18 |
pppExtIfL1SpeedThis 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.19 |
pppExtIfCurrentRetryTimeCurrent time in seconds to wait before retrying a call when
the smart retry algorithm is implemented.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.20 |
pppExtIfMaxRetryTimeMaximum time in seconds to wait before retrying a call when
the smart retry algorithm is implemented. When set to zero
this algorithm is disabled.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.21 |
pppExtIfMtuDetermines 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.rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.22 |
pppExtIfMruThe maximum length for the PPP information field, including
padding, but not including the protocol field, is termed
the Maximum Receive Unit (MRU).rw INTEGER .1.3.6.1.4.1.272.4.3.9.1.23 |
pppExtIfAuthMutualThis object enables mutual PPP authentication between the
peers.rw Enumeration .1.3.6.1.4.1.272.4.3.9.1.24 |
pppSessionTableThe 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. SEQUENCE OF PppSessionEntry .1.3.6.1.4.1.272.4.3.10 |
pppSessionEntry PppSessionEntry .1.3.6.1.4.1.272.4.3.10.1 |
pppSessionIfIndexCorrelating PPP interface index.ro INTEGER .1.3.6.1.4.1.272.4.3.10.1.1 |
pppSessionMlpIndicates negotiation of Multilink PPP.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.2 |
pppSessionMruPeer's MRU/MRRU LCP option.ro Counter .1.3.6.1.4.1.272.4.3.10.1.3 |
pppSessionLcpCallbackCallback option inside LCP negotiation.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.4 |
pppSessionAuthProtThe negotiated PPP authentication protocol.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.5 |
pppSessionCompressionThe negotiated CCP compression mode.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.6 |
pppSessionEncryptionThe negotiated CCP encryption mode.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.7 |
pppSessionCbcpModeThe negotiated Callback Control Protocol (CBCP) mode.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.8 |
pppSessionCbcpDelayThe negotiated (CBCP) callback delay in seconds.ro INTEGER .1.3.6.1.4.1.272.4.3.10.1.9 |
pppSessionLocIpAddrThe negotiated local IP Address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.10 |
pppSessionRemIpAddrThe negotiated remote IP Address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.11 |
pppSessionDNS1The negotiated first name server IP address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.12 |
pppSessionDNS2The negotiated second name server IP address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.13 |
pppSessionWINS1The negotiated first NetBIOS name server (WINS)
IP address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.14 |
pppSessionWINS2The negotiated second NetBIOS name server (WINS)
IP address.ro IpAddress .1.3.6.1.4.1.272.4.3.10.1.15 |
pppSessionVJHeaderCompThe negotiation of Van Jacobsen TCP/IP header compression
option (IPCP).ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.16 |
pppSessionIpxcpNodeNumberUnique IPX Node Id dynamically assigned the client.ro OCTET STRING .1.3.6.1.4.1.272.4.3.10.1.17 |
pppSessionBacpFavoredPeerThe result of the BACP Favored-Peer negotiation.ro Enumeration .1.3.6.1.4.1.272.4.3.10.1.18 |
dialmap OBJECT IDENTIFIER .1.3.6.1.4.1.272.4.4 |
biboDialTableThe 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. SEQUENCE OF BiboDialEntry .1.3.6.1.4.1.272.4.4.1 |
biboDialEntry BiboDialEntry .1.3.6.1.4.1.272.4.4.1.1 |
biboDialIfIndexThe correlating PPP interface index.rw INTEGER .1.3.6.1.4.1.272.4.4.1.1.1 |
biboDialTypeThe 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.rw Enumeration .1.3.6.1.4.1.272.4.4.1.1.2 |
biboDialDirectionThe 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.rw Enumeration .1.3.6.1.4.1.272.4.4.1.1.3 |
biboDialNumberThe 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.rw DisplayString .1.3.6.1.4.1.272.4.4.1.1.4 |
biboDialSubaddressThe defined dial subaddress, if any. Also, see the
biboDialNumber field.rw OCTET STRING .1.3.6.1.4.1.272.4.4.1.1.5 |
biboDialClosedUserGroupThe defined closed user group, if any. Also, see the
biboDialNumber field.rw INTEGER .1.3.6.1.4.1.272.4.4.1.1.6 |
biboDialStkMaskThe 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.rw BitValue .1.3.6.1.4.1.272.4.4.1.1.7 |
biboDialScreeningThe 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.rw Enumeration .1.3.6.1.4.1.272.4.4.1.1.8 |
biboDialCallingSubaddressThe defined calling dial subaddress, if any. Also, see the
biboDialNumber field.rw OCTET STRING .1.3.6.1.4.1.272.4.4.1.1.9 |
biboDialTypeOfCallingSubAddThe type of calling party subaddress.rw Enumeration .1.3.6.1.4.1.272.4.4.1.1.10 |
biboDialTypeOfCalledSubAddThe type of called party subaddress.rw Enumeration .1.3.6.1.4.1.272.4.4.1.1.11 |