SHIVA-L2F-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for SHIVA-L2F-MIB.
82
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
82 total| Object Name |
|---|
l2fNetworkAccessServer OBJECT IDENTIFIER .1.3.6.1.4.1.166.1.26.1 |
RFC1213-MIB Unknown .1.3.6.1.4.1.166.1.26.1 |
l2fHomeGateway OBJECT IDENTIFIER .1.3.6.1.4.1.166.1.26.2 |
l2fHGConf OBJECT IDENTIFIER .1.3.6.1.4.1.166.1.26.2.1 |
l2fHGConfEnabledWhether L2F Home Gateway functionality is enabled
on this system.ro Enumeration .1.3.6.1.4.1.166.1.26.2.1.1 |
l2fHGConfMaximumCallsThe maximum number of incoming L2F calls that may be
active on this Home Gateway at any one time. Any attempt
to create a call in excess if this number will be
rejected.ro INTEGER .1.3.6.1.4.1.166.1.26.2.1.2 |
l2fHGConfUDPEnabledWhether L2F Home Gateway functionality is enabled
over the UDP protocol on port 1701 on this system.ro Enumeration .1.3.6.1.4.1.166.1.26.2.1.3 |
l2fHGConfNASDefinedIndicates the number of peer NASs which have been configured
on this Home Gateway. This value represents the number of
NAS entries in the configuration table (ie. number of
VPDNInterface sections).ro INTEGER .1.3.6.1.4.1.166.1.26.2.1.4 |
l2fHGConfInactivityRetriesIndicates the number of times this Home Gateway will send
L2F_ECHO packets without receiving a response, that is,
an L2F_ECHO_REPLY from the NAS peer before determining
the tunnel is no longer active.ro INTEGER .1.3.6.1.4.1.166.1.26.2.1.5 |
l2fHGConfInactivityRetryPeriodIndicates the number seconds that must elapse since the
last NAS peer packet was received by this Home Gateway
before an L2F_ECHO packet is generated.ro INTEGER .1.3.6.1.4.1.166.1.26.2.1.6 |
l2fHGConfTunnelTableTable of configuration information for each
incoming VPDN tunnel. The table is indexed by NAS name. SEQUENCE OF L2fHGConfTunnelEntry .1.3.6.1.4.1.166.1.26.2.1.8 |
l2fHGConfTunnelEntryConfiguration information for a particular VPDN tunnel. L2fHGConfTunnelEntry .1.3.6.1.4.1.166.1.26.2.1.8.1 |
l2fHGConfTunnelNASNameName of NAS that we are configured to receive L2F
tunnel connections from. Although this name may match
the peer's DNS host name, it is not required to. This
name corresponds to the PeerName entry in the associated
VPDNInterface section.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.1.8.1.1 |
l2fHGConfTunnelHGNameName of Home Gateway registered on this tunnel.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.1.8.1.2 |
l2fHGConfTunnelSectionNumberID that identifies this tunnel in the configuration table.ro INTEGER .1.3.6.1.4.1.166.1.26.2.1.8.1.3 |
l2fHGConfTunnelEnabledIndicates if this VPDN tunnel is enabled or not.ro Enumeration .1.3.6.1.4.1.166.1.26.2.1.8.1.4 |
l2fHGStat OBJECT IDENTIFIER .1.3.6.1.4.1.166.1.26.2.2 |
l2fHGStatCurrentCallsCurrent number of incoming L2F client calls to this
Home Gateway. Cannot ever be greater than
l2fHGConfMaximumCalls.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.1 |
l2fHGStatPeakCallsPeak number of incoming L2F client calls to this
Home Gateway. Cannot ever be greater than
l2fHGConfMaximumCalls.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.2 |
l2fHGStatTotalCallsTotal number of incoming L2F client calls to this
Home Gateway over time.ro Counter .1.3.6.1.4.1.166.1.26.2.2.3 |
l2fHGStatCallsOverMaxNumber of incoming L2F client calls to this
Home Gateway that were rejected because they were
in excess of l2fHGConfMaximumCalls.ro Counter .1.3.6.1.4.1.166.1.26.2.2.4 |
l2fHGStatCallsResourceFailureNumber of incoming L2F client calls to this
Home Gateway that were rejected because of
miscellaneous resource allocation failures.ro Counter .1.3.6.1.4.1.166.1.26.2.2.5 |
l2fHGStatCallsAuthFailedNumber of incoming L2F client calls to this
Home Gateway that were rejected because of
authentication or permission failures for the user.ro Counter .1.3.6.1.4.1.166.1.26.2.2.6 |
l2fHGStatCurrentTunnelsCurrent number of incoming L2F Network Access
Server peer tunnels to this Home Gateway.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.7 |
l2fHGStatPeakTunnelsPeak number of incoming L2F Network Access
Server peer tunnels to this Home Gateway at
any given time.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.8 |
l2fHGStatTotalTunnelsTotal number of incoming L2F Network Access
Server peer tunnels to this Home Gateway.ro Counter .1.3.6.1.4.1.166.1.26.2.2.9 |
l2fHGStatTunnelNoNameNumber of incoming L2F Network Access Server
peer tunnels to this Home Gateway that were
rejected because the NAS name was unknown.ro Counter .1.3.6.1.4.1.166.1.26.2.2.10 |
l2fHGStatTunnelAuthFailNumber of incoming L2F Network Access Server
peer tunnels to this Home Gateway that were
rejected because the NAS credentials could
not be authenticated.ro Counter .1.3.6.1.4.1.166.1.26.2.2.11 |
l2fHGStatTunnelResourceFailureNumber of incoming L2F Network Access Server
peer tunnels to this Home Gateway that were
rejected because of a miscellaneous resource
allocation failure.ro Counter .1.3.6.1.4.1.166.1.26.2.2.12 |
l2fHGPeerTableThis is a table of every L2F NAS tunnel peer that has
ever contacted this Home Gateway. This table is indexed
by the ifIndex of the 'primary' ifTable entry for the
tunnels for this peer. This information will remain in
the system until the next system restart. SEQUENCE OF L2fHGPeerEntry .1.3.6.1.4.1.166.1.26.2.2.13 |
l2fHGPeerEntryStatus and counter information about this
particular NAS tunnel peer. L2fHGPeerEntry .1.3.6.1.4.1.166.1.26.2.2.13.1 |
l2fHGPeerIfIndexThe ifIndex of the primary (permanent)
ifTable entry for tunnels from this peer.
This value is used to access the NAS peer entry
in the l2fHGPeerTable.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.13.1.1 |
l2fHGPeerEnabledIndicates if this particular NAS peer is configured
to create tunnels with this Home Gateway.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.13.1.2 |
l2fHGPeerNASNameName of the peer NAS server. The NAS name is also the
index into the l2fHGConfTunnelTable for this NAS peer.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.2.13.1.3 |
l2fHGPeerCurrentTunnelsCurrent number of incoming tunnels from this NAS.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.13.1.4 |
l2fHGPeerPeakTunnelsThe maximum number of incoming tunnels from this
NAS peer at any one time.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.5 |
l2fHGPeerTotalTunnelsTotal number of incoming tunnels that have been
created from this NAS. In this context, tunnels are
equivalent to the Client ID (CLID).ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.6 |
l2fHGPeerCurrentClientsCurrent number of clients that have established
a session on this tunnel.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.13.1.7 |
l2fHGPeerPeakClientsThe maximum number of clients which have established
a session on this tunnel at any one time.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.8 |
l2fHGPeerTotalClientsThe total number of clients that have established
a session on this tunnel since the tunnel was created.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.9 |
l2fHGPeerTunnelAuthFailedNumber of tunnels rejected by this Home Gateway
because NAS secret incorrect.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.10 |
l2fHGPeerTunnelMiscFailedNumber of tunnels that failed to open for other reasons.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.11 |
l2fHGPeerTunnelKeepAliveFailedNumber of tunnels torn down by this Home Gateway
due to failure of keep-alive monitoring. In the
context of this variable, the keep-alive mechanism
is an exchange of L2F_ECHO (sent by the HG) and
L2F_ECHO_REPLY (sent by NAS) packets.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.12 |
l2fHGPeerTunnelProtocolViolationsNumber of tunnels torn down by the Home Gateway
due to protocol violations.ro Counter .1.3.6.1.4.1.166.1.26.2.2.13.1.13 |
l2fHGPeerTunnelLastCloseTimeThe value of sysUpTime at the time a tunnel from
this NAS peer last closed. This is only an interesting
number if l2fHGPeerCurrentTunnels is zero. It is
kept here because the ifEntry for the tunnels are
volatile, and go away when they close. Therefore, one
cannot determine this information by looking at
ifLastChange.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.166.1.26.2.2.13.1.14 |
l2fHGTunnelTableTable consisting of all of the currently active NAS
tunnels. This table augments the ifTable. Each row in
this table has a row in the ifTable of ifType
'propVirtual'. The table is indexed by l2fHGTunnelCLID.
Note that rows in this table come and go as the tunnels
open and close. SEQUENCE OF L2fHGTunnelEntry .1.3.6.1.4.1.166.1.26.2.2.14 |
l2fHGTunnelEntryInformation concerning a particular active NAS tunnel. L2fHGTunnelEntry .1.3.6.1.4.1.166.1.26.2.2.14.1 |
l2fHGTunnelCLIDThe local client identifier for this tunnel.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.1 |
l2fHGTunnelPeerCLIDThe NAS peer's client identifier for this tunnel.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.2 |
l2fHGTunnelHGNameThis Home Gateway's name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.2.14.1.3 |
l2fHGTunnelNASNameThe name of the NAS peer on this tunnel.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.2.14.1.4 |
l2fHGTunnelReceiveChecksumIndicates if the NAS peer will be generating
checksums for the L2F payload received by this
Home Gateway.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.14.1.5 |
l2fHGTunnelGenerateChecksumIndicates if this Home Gateway will be generating
checksums for the L2F payload sent to the NAS peer.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.14.1.6 |
l2fHGTunnelIfIndexThe ifIndex of this tunnel in the ifTable.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.7 |
l2fHGTunnelPeerIndexThis is the index into the l2fHGPeerTable. This index
should be identical to the value in l2fHGTunnelIfIndex.
However, if it is not, then this indicates that the
NAS peer (using the same NAS name) has created multiple
tunnels to this Home Gateway.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.8 |
l2fHGTunnelTransportThe underlying transport interface which this
tunnel is communicating with the NAS peer.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.14.1.9 |
l2fHGTunnelIpAddressThe IP address of the NAS peer. This value is non-zero
if this tunnel is operating over UDP. Refer to
l2fHGTunnelTransport to determine which transport this
tunnel is communicating over.ro IpAddress .1.3.6.1.4.1.166.1.26.2.2.14.1.10 |
l2fHGTunnelCurrentStateCurrent tunnel state. These are the primary states that
have been defined for the Home Gateway side in the L2F
internet draft.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.14.1.13 |
l2fHGTunnelCurrentClientsCurrent number of clients accessing this tunnel.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.14 |
l2fHGTunnelPeakClientsPeak number of clients accessing this tunnel at
any given point in time.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.15 |
l2fHGTunnelTotalClientsTotal number of clients that have communicated over this
tunnel while the tunnel was active.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.16 |
l2fHGTunnelMaxLinkInactivityThe maximum amount of time that can elapse (in seconds)
since the last NAS peer packet was received before this
Home Gateway will tear down the tunnel.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.17 |
l2fHGTunnelCurrentLinkInactivityThe amount of time that has elapsed (in seconds)
since the last NAS peer packet was received. When the
Home Gateway has not heard from the NAS peer in a
period of time, it will generate L2F_ECHO packets to
determine if the NAS is still alive. Once the inactivity
reaches l2fHGTunnelMaxLinkInactivity, the Home Gateway
will tear down the link.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.14.1.18 |
l2fHGTunnelSequenceErrorsThe number of L2F control packets that were received
on this tunnel, by this Home Gateway out of sequence.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.19 |
l2fHGTunnelEchoSentNumber of L2F_ECHO packets sent. This typically occurs
when this Home Gateway has not received any data from
the NAS peer over a period of time on this tunnel.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.20 |
l2fHGTunnelEchoReceivedNumber of L2F_ECHO packets received. The NAS peer will
send this packet to determine if this Home Gateway is
still alive.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.21 |
l2fHGTunnelEchoReplySentNumber of L2F_ECHO_REPLY packets sent. The Home Gateway
sends this packets in response to the L2F_ECHO packet
sent by the NAS peer.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.22 |
l2fHGTunnelEchoReplyReceivedNumber of L2F_ECHO_REPLY packets received. The NAS
peer sends this packet in response to the L2F_ECHO
packet sent by this Home Gateway.ro Counter .1.3.6.1.4.1.166.1.26.2.2.14.1.23 |
l2fHGClientTableThis table contains status information concerning the
clients' currently operating over tunnels connected to
this Home Gateway. This table is indexed by the
Client ID (CLID) and the non-zero MID. This table
augments the ifTable. Each row in this table has a
corresponding row in the ifTable of ifType 'propVirtual'. SEQUENCE OF L2fHGClientEntry .1.3.6.1.4.1.166.1.26.2.2.15 |
l2fHGClientEntryStatus information for a particular client operating
over a tunnel connected to this Home Gateway. L2fHGClientEntry .1.3.6.1.4.1.166.1.26.2.2.15.1 |
l2fHGClientCLIDLocal Client Identifier for the NAS tunnel
underlying this entry. This is one of the
two indexes used to access this entry in the
table.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.15.1.1 |
l2fHGClientMIDThe Multiplex ID which identifies a particular
connection within the tunnel. This is one of
the two indexes used to access this entry in
the table.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.15.1.2 |
l2fHGClientPeerCLIDPeer Client Identifier for the NAS tunnel
underlying this entry.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.15.1.3 |
l2fHGClientTunnelStateCurrent client state. These are the primary states that
have been defined for the Home Gateway side in the L2F
internet draft.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.15.1.4 |
l2fHGClientIfIndexThe ifIndex of the NAS peer tunnel (L2F client connection)
in the ifTable.ro INTEGER .1.3.6.1.4.1.166.1.26.2.2.15.1.5 |
l2fHGClientOpenNameThe name received from the client in the L2F_OPEN_NAME
option.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.166.1.26.2.2.15.1.6 |
l2fHGClientReqLcp0Specifies a copy of the initial LCP CONFIGURE-REQUEST
packet sent from the PPP client, as sent by the NAS to
the HG in the L2F_REQ_LCP0 option. This request may
contain options that were negotiated away by the NAS.
The information starts after the length field in the LCP
header, and contains LCP options only.ro OCTET STRING .1.3.6.1.4.1.166.1.26.2.2.15.1.7 |
l2fHGClientAckLcp1Specifies a copy of the closing LCP CONFIGURE-ACK
packet sent by the PPP client, as sent by the NAS to
the HG in the L2F_ACK_LCP1 option. The information
starts after the length field in the LCP header, and
contains LCP options only.ro OCTET STRING .1.3.6.1.4.1.166.1.26.2.2.15.1.8 |
l2fHGClientAckLcp2Specifies a copy of the closing LCP CONFIGURE-ACK
packet sent to the PPP client, as sent by the NAS to
the HG in the L2F_ACK_LCP2 option. The information
starts after the length field in the LCP header, and
contains LCP options only.ro OCTET STRING .1.3.6.1.4.1.166.1.26.2.2.15.1.9 |
l2fHGClientOpenTypeSpecifies the type of authentication the NAS
exchanged with the client in detecting the client's
claimed identification.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.15.1.10 |
l2fHGClientSequenceEnabledIndicates if sequenced packet delivery is enabled
for DATA packets. Sequenced packets allow the receiver
to determine if a packet is a duplicate or is out of
order. Some PPP protocols assume that PPP will never
re-order packets, so enabling L2F data sequencing protects
against re-ordering between the NAS and HG network.ro Enumeration .1.3.6.1.4.1.166.1.26.2.2.15.1.11 |
l2fHGClientSequenceErrorsIf sequenced packet delivery is enabled for DATA
packets (see l2fHGClientSequenceEnabled), this value
indicates how many packets were received out of
sequence.ro Counter .1.3.6.1.4.1.166.1.26.2.2.15.1.12 |