wfPppLineLineNumber |
.1.3.6.1.4.1.18.3.5.9.2.1.1.4 |
Instance identifier. This is the line number assigned
to the driver PPP is running on top of
|
wfPppLineLLIndex |
.1.3.6.1.4.1.18.3.5.9.2.1.1.5 |
Instance identifier. This is the lower layer index
presented to PPP by the layer immediately below it
on the protocol stack. If the lower layer is a driver,
the index will be 0.
|
wfPppLineDelete |
.1.3.6.1.4.1.18.3.5.9.2.1.1.1 |
Create/Delete parameter
|
wfPppLineDisable |
.1.3.6.1.4.1.18.3.5.9.2.1.1.2 |
Enable/Disable parameter -- Generates
Open/Close events to the LCP FSM
|
wfPppLineState |
.1.3.6.1.4.1.18.3.5.9.2.1.1.3 |
PPP state variable, Not Present, Init, Down, Up
|
wfPppLineLcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.1.1.6 |
the current state of the LCP Finite State Machine
|
wfPppLineRestartTimer |
.1.3.6.1.4.1.18.3.5.9.2.1.1.7 |
value for Restart timer in seconds
|
wfPppLineEchoRequestFreq |
.1.3.6.1.4.1.18.3.5.9.2.1.1.8 |
value for Echo-Request frequency - number of seconds
between transmission of Echo-Request packets
|
wfPppLineEchoReplyLoss |
.1.3.6.1.4.1.18.3.5.9.2.1.1.9 |
value for Echo-Reply acceptable loss - number of
unacknowledged Echo-Reply packets counted before
declaring the link down
|
wfPppLineMaxConfReq |
.1.3.6.1.4.1.18.3.5.9.2.1.1.10 |
value for maximum Configure-Requests - number of
Configure-Request packets sent without receiving a
valid Configure-Ack, Configure-Nak or Configure-Reject
before assuming peer is unable to respond
|
wfPppLineMaxTermReq |
.1.3.6.1.4.1.18.3.5.9.2.1.1.11 |
value for maximum Terminate-Requests - number of
Terminate-Request packets sent without receiving a
Terminate-Ack before assuming peer is unable to respond
|
wfPppLineMaxConfFail |
.1.3.6.1.4.1.18.3.5.9.2.1.1.12 |
value for maximum configuration failure count - number of
Configure-Nak packets sent without sending a
Configure-Ack before assuming configuration is unable to
converge
|
wfPppLineMagicNumber |
.1.3.6.1.4.1.18.3.5.9.2.1.1.13 |
the Magic Number being used on this line
|
wfPppLineMru |
.1.3.6.1.4.1.18.3.5.9.2.1.1.14 |
this is the MRU being used on the line (in both
directions)
|
wfPppLineLocalAuthProtocol |
.1.3.6.1.4.1.18.3.5.9.2.1.1.15 |
this is the authorization protocol we require our peer
to use on our side of the link
|
wfPppLineRemoteAuthProtocol |
.1.3.6.1.4.1.18.3.5.9.2.1.1.16 |
this is the authorization protocol our peer requires us
to use on its side of the link
|
wfPppLineLocalPapId |
.1.3.6.1.4.1.18.3.5.9.2.1.1.17 |
our PAP id - our peer sends this to us in an
Authenticate-Request message
|
wfPppLineLocalPapPassword |
.1.3.6.1.4.1.18.3.5.9.2.1.1.18 |
our PAP password - our peer sends this to us in an
Authenticate-Request message
|
wfPppLineRemotePapId |
.1.3.6.1.4.1.18.3.5.9.2.1.1.19 |
our peer's PAP id - we send this to our
peer in an Authenticate-Request message
|
wfPppLineRemotePapPassword |
.1.3.6.1.4.1.18.3.5.9.2.1.1.20 |
our peer's PAP password - we send this to our
peer in an Authenticate-Request message
|
wfPppLineLQProtocol |
.1.3.6.1.4.1.18.3.5.9.2.1.1.21 |
the Link Quality protocol we want to use
|
wfPppLineDisableRemoteLQRTimer |
.1.3.6.1.4.1.18.3.5.9.2.1.1.22 |
enable/disable our peer's LQR timer - this allows
for one side to maintain the timer while the
other just responds to LQR packets
|
wfPppLineCfgLQRRptPrd |
.1.3.6.1.4.1.18.3.5.9.2.1.1.23 |
this is the value in seconds between transmission
of LQR packets (Reporting-Period) - it will be the
same on both sides
|
wfPppLineLQRRptPrd |
.1.3.6.1.4.1.18.3.5.9.2.1.1.24 |
this is the Reporting-Period, in seconds, agreed upon
during negotiation - we allow the peer to negotiate
down from our configured period, our maximum, but not
below 1 second
|
wfPppLineCfgInboundQuality |
.1.3.6.1.4.1.18.3.5.9.2.1.1.25 |
the percentage of packets sent by our peer that
we've successfully received (over the last 5 LQR
Reporting-Periods) - 100 indicates we won't tolerate
any loss
|
wfPppLineInboundQuality |
.1.3.6.1.4.1.18.3.5.9.2.1.1.26 |
the current inbound quality
|
wfPppLineCfgOutboundQuality |
.1.3.6.1.4.1.18.3.5.9.2.1.1.27 |
the percentage of packets sent by us that our
peer successfully received (over the last 5 LQR
Reporting-Periods) - 100 indicates we won't tolerate
any loss
|
wfPppLineOutboundQuality |
.1.3.6.1.4.1.18.3.5.9.2.1.1.28 |
the current inbound quality
|
wfPppLineOutLQRs |
.1.3.6.1.4.1.18.3.5.9.2.1.1.29 |
the number of Link-Quality-Report packets we've
transmitted
|
wfPppLineInLQRs |
.1.3.6.1.4.1.18.3.5.9.2.1.1.30 |
the number of Link-Quality-Report packets we've
received
|
wfPppLineChapSecret |
.1.3.6.1.4.1.18.3.5.9.2.1.1.31 |
this CHAP secret MUST be the same on both sides of
the link if CHAP is used as the Authentication
protocol
|
wfPppLinePapFallbackDisable |
.1.3.6.1.4.1.18.3.5.9.2.1.1.32 |
if an attempt to negotiate CHAP fails, enabling this
allows a fallback to PAP
|
wfPppLineChapLocalName |
.1.3.6.1.4.1.18.3.5.9.2.1.1.33 |
This attribute is used to assign a local CHAP Name
which is used to inform our peer of our identity,
during WHOAMI processing
|
wfPppLineChapRemoteName |
.1.3.6.1.4.1.18.3.5.9.2.1.1.34 |
This attribute is used to store our peer's CHAP Name
which is used to learn our peer's identity,
during WHOAMI processing
|
wfPppLineChapPeriodicTimer |
.1.3.6.1.4.1.18.3.5.9.2.1.1.35 |
Timer for periodic CHAP in seconds. A time of
0 disables Periodic CHAP. This timer value should
long enough to allow CHAP to complete one phase
before entering another.
|
wfPppLineBadPackets |
.1.3.6.1.4.1.18.3.5.9.2.1.1.36 |
These are packets not in correct PPP format
|
wfPppLineLastBadPacket |
.1.3.6.1.4.1.18.3.5.9.2.1.1.37 |
This is the first 16 bytes of the last bad packet
we received
|
wfPppLineLevelPktsIn |
.1.3.6.1.4.1.18.3.5.9.2.1.1.38 |
This is the count of PPP link-level packets
(such as Link Control Protocol or Compression
Control Protocl) which have been received.
|
wfPppLineAllowPapReject |
.1.3.6.1.4.1.18.3.5.9.2.1.1.39 |
There are some peers that don't want us asking to
be a PAP authenticator, so accept the Reject and
remove PAP from the LCP Configure-Request if this
is enabled.
|
wfPppLineActiveCct |
.1.3.6.1.4.1.18.3.5.9.2.1.1.40 |
This is the circuit number that this PPP line belongs to
For the any switched lines, this will initially be -1
|
wfPppLineCfgAsyncMap |
.1.3.6.1.4.1.18.3.5.9.2.1.1.41 |
This is the initial seed value of
Async-Control-Character-Map which will be used
for LCP negotiations with the peer.
|
wfPppLineActualAsyncMap |
.1.3.6.1.4.1.18.3.5.9.2.1.1.42 |
Async-Control-Character-Map used by the link to
escape control characters in the data packet. This
is the result of LCP negotiations with the peer.
|
wfPppLineAuthTimer |
.1.3.6.1.4.1.18.3.5.9.2.1.1.43 |
value for Authentication timer in seconds
|
wfPppLineConvergenceTimer |
.1.3.6.1.4.1.18.3.5.9.2.1.1.44 |
value for Convergence timer in seconds
|
wfPppLineMagicNumDisable |
.1.3.6.1.4.1.18.3.5.9.2.1.1.45 |
Allows Magic Numbers to be disabled on this interface.
|
wfPppLineMyLinkDiscr |
.1.3.6.1.4.1.18.3.5.9.2.1.1.46 |
value of Link Discriminator of this endpoint
|
wfPppLinePeerLinkDiscr |
.1.3.6.1.4.1.18.3.5.9.2.1.1.47 |
value of Link Discriminator of peer's endpoint
|
wfPppLineCfgMru |
.1.3.6.1.4.1.18.3.5.9.2.1.1.48 |
this is the Configured MRU being used on the line
|
wfPppLineRfc1661Compliance |
.1.3.6.1.4.1.18.3.5.9.2.1.1.49 |
Enable/Disable parameter for RFC 1661 compliance
|
wfPppLineLqmCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.1.1.50 |
Indicates whether LQM is running on the line.
|
wfPppCircuitID |
.1.3.6.1.4.1.18.3.5.9.2.2.1.11 |
cct number for this instance
|
wfPppCircuitDelete |
.1.3.6.1.4.1.18.3.5.9.2.2.1.1 |
Create/Delete parameter
|
wfPppCircuitState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.2 |
PPP state variable, Not Present, Init, Down, Up
|
wfPppCircuitIpcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.3 |
the current state of the IPCP Finite State Machine
|
wfPppCircuitOsinlcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.4 |
the current state of the OSINLCP Finite State Machine
|
wfPppCircuitXnscpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.5 |
the current state of the XNSCP Finite State Machine
|
wfPppCircuitDncpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.6 |
the current state of the DNCP Finite State Machine
|
wfPppCircuitAtcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.7 |
the current state of the ATCP Finite State Machine
|
wfPppCircuitIpxcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.8 |
the current state of the IPXCP Finite State Machine
|
wfPppCircuitBncpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.9 |
the current state of the BNCP Finite State Machine
|
wfPppCircuitVncpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.10 |
the current state of the VNCP Finite State Machine
|
wfPppCircuitIpDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.12 |
enable/disable IP Protocol - disabling generates
a Close event to the IPCP FSM and consequently disallows
IP traffic on this circuit
|
wfPppCircuitOsinlDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.13 |
enable/disable OSI Network Layer Protocol -
disabling generates a Close event to the OSINLCP FSM
and consequently disallows OSI traffic on this circuit
|
wfPppCircuitXnsDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.14 |
enable/disable XNS Protocol - disabling generates
a Close event to the XNSCP FSM and consequently
disallows XNS traffic on this circuit
|
wfPppCircuitDecnetDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.15 |
enable/disable DECnet Protocol - disabling generates
a Close event to the DNCP FSM and consequently
disallows DECnet traffic on this circuit
|
wfPppCircuitAppletalkDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.16 |
enable/disable AppleTalk Protocol - disabling generates
a Close event to the ATCP FSM and consequently
disallows AppleTalk traffic on this circuit
|
wfPppCircuitIpxDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.17 |
enable/disable IPX Protocol - disabling generates
a Close event to the IPXCP FSM and consequently
disallows IPX traffic on this circuit
|
wfPppCircuitBridgeDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.18 |
enable/disable the Bridge - disabling generates
a Close event to the BNCP FSM and consequently
disallows bridge traffic on this circuit
|
wfPppCircuitVinesDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.19 |
enable/disable Vines Protocol - disabling generates
a Close event to the VNCP FSM and consequently
disallows Vines traffic on this circuit
|
wfPppCircuitCfgLocalIpAddr |
.1.3.6.1.4.1.18.3.5.9.2.2.1.20 |
the IP address we're going to use
|
wfPppCircuitLocalIpAddr |
.1.3.6.1.4.1.18.3.5.9.2.2.1.21 |
the IP address our peer wants us to use
|
wfPppCircuitCfgRemoteIpAddr |
.1.3.6.1.4.1.18.3.5.9.2.2.1.22 |
the IP address we want our peer to use
|
wfPppCircuitRemoteIpAddr |
.1.3.6.1.4.1.18.3.5.9.2.2.1.23 |
the IP address our peer wants to use
|
wfPppCircuitCfgIpxNetworkNumber |
.1.3.6.1.4.1.18.3.5.9.2.2.1.24 |
the configured IPX Network Number to be used by
both us and our peer
|
wfPppCircuitIpxNetworkNumber |
.1.3.6.1.4.1.18.3.5.9.2.2.1.25 |
the result of IPX Network Number negotiation
|
wfPppCircuitIpxRemoteNodeNumber |
.1.3.6.1.4.1.18.3.5.9.2.2.1.26 |
this is what we'll tell our peer to use for node
number if it sends us a 0
|
wfPppCircuitCfgIpxRoutingProtocol |
.1.3.6.1.4.1.18.3.5.9.2.2.1.27 |
the desired IPX Routing Protocol to be used on
the link
|
wfPppCircuitIpxRoutingProtocol |
.1.3.6.1.4.1.18.3.5.9.2.2.1.28 |
the negotiated IPX Routing Protocol to be used on
the link
|
wfPppCircuitLocalIpxRouterName |
.1.3.6.1.4.1.18.3.5.9.2.2.1.29 |
our IPX Router Name
|
wfPppCircuitRemoteIpxRouterName |
.1.3.6.1.4.1.18.3.5.9.2.2.1.30 |
our peer's IPX Router Name
|
wfPppCircuitIpxConfigComplete |
.1.3.6.1.4.1.18.3.5.9.2.2.1.31 |
indicates whether or not IPXCP converged on all
required options
|
wfPppCircuitCfgAtNetwork |
.1.3.6.1.4.1.18.3.5.9.2.2.1.32 |
the configured AppleTalk network number - our
peer must use the same number
|
wfPppCircuitAtNetwork |
.1.3.6.1.4.1.18.3.5.9.2.2.1.33 |
the AppleTalk network number we agreed to use
|
wfPppCircuitCfgLocalAtNode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.34 |
the AppleTalk node number we're configured to use
|
wfPppCircuitLocalAtNode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.35 |
our AppleTalk node number after negotiation
|
wfPppCircuitCfgRemoteAtNode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.36 |
the AppleTalk node number we want our peer to use
|
wfPppCircuitRemoteAtNode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.37 |
our peer's AppleTalk node number after negotiation
|
wfPppCircuitCfgAtRoutingProtocol |
.1.3.6.1.4.1.18.3.5.9.2.2.1.38 |
the desired AppleTalk Routing Protocol to be used on
the link
|
wfPppCircuitAtRoutingProtocol |
.1.3.6.1.4.1.18.3.5.9.2.2.1.39 |
the negotiated AppleTalk Routing Protocol to be used on
the link
|
wfPppCircuitCfgBridgeEnet |
.1.3.6.1.4.1.18.3.5.9.2.2.1.40 |
allow/disallow Ethernet bridged frames
|
wfPppCircuitBridgeEnet |
.1.3.6.1.4.1.18.3.5.9.2.2.1.41 |
result of bridge MAC type negotiation for
Ethernet
|
wfPppCircuitCfgBridgeFddi |
.1.3.6.1.4.1.18.3.5.9.2.2.1.42 |
allow/disallow FDDI bridged frames
|
wfPppCircuitBridgeFddi |
.1.3.6.1.4.1.18.3.5.9.2.2.1.43 |
result of bridge MAC type negotiation for
FDDI
|
wfPppCircuitCfgBridgeTokenRing |
.1.3.6.1.4.1.18.3.5.9.2.2.1.44 |
allow/disallow Token Ring bridged frames
|
wfPppCircuitBridgeTokenRing |
.1.3.6.1.4.1.18.3.5.9.2.2.1.45 |
result of bridge MAC type negotiation for
Token Ring
|
wfPppCircuitBadPackets |
.1.3.6.1.4.1.18.3.5.9.2.2.1.46 |
these are packets not in correct PPP format
|
wfPppCircuitLastBadPacket |
.1.3.6.1.4.1.18.3.5.9.2.2.1.47 |
this is the first 16 bytes of the last bad packet
we received
|
wfPppCircuitCcpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.48 |
the current state of the CCP Finite State Machine
|
wfPppCircuitCcpDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.49 |
enable/disable compression - disabling generates
a Close event to the CCP FSM and consequently
disallows compression traffic on this circuit
|
wfPppCircuitPppMode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.50 |
Pre 9.0 multilines can only negotiate LCP over 1 line. The
exact line which LCP will occur on is unknown. So in order
to handle this situation we will wait until we receive an
LCP Request before we attempt to negotiate LCP by setting
the mode to PPP_MODE_PEER_SOLICITED_LCP_NEGO. If we are using
this line as a single PPP Line or we are sure our peer can
handle LCP on all the members of the multiline, PPP_MODE_NORMAL
should be selected.
Multilink is a PPP protocol extension which provides restoration
of packets which arrive out of sequence, a possibility with
multiple lines.
Multilink monitor, in conjunction with other configuration data
allows the throughput of a line to be monitored. Additional
lines can be brought into the bundle and taken down dynamically
in response to data traffic volume and other conditions.
|
wfPppCircuitMLFragPerm |
.1.3.6.1.4.1.18.3.5.9.2.2.1.51 |
This parameter allows interoperability with PPP Multilink
implementations which do not allow fragmentation.
|
wfPppCircuitExamPeriod |
.1.3.6.1.4.1.18.3.5.9.2.2.1.52 |
This indicates the interval that the Multilink bundle should
be polled for possible congestion. This value is in
tenths of a second
|
wfPppCircuitFullThreshold |
.1.3.6.1.4.1.18.3.5.9.2.2.1.53 |
This is the percentage of the theoretical maximum line
throughput that must be reached or exceeded before the line is
considered congested.
|
wfPppCircuitPeriodsCng |
.1.3.6.1.4.1.18.3.5.9.2.2.1.54 |
This is the number of consecutive periods where the line
throughput is above the congestion threshold required to declare
the line congested and attempt corrective action.
|
wfPppCircuitPrefBwSlot |
.1.3.6.1.4.1.18.3.5.9.2.2.1.55 |
This is the preferred bandwidth slot.
When lines are requested to be added to the Multilink bundle
this parameter denotes the slot which is asked first.
|
wfPppCircuitResvBwSlot |
.1.3.6.1.4.1.18.3.5.9.2.2.1.56 |
This is the reserve bandwidth slot.
When lines are requested to be added to the Multilink bundle
this parameter denotes the slot which is asked if the preferred
slot can not provide a line.
|
wfPppCircuitMLFragTriggerSize |
.1.3.6.1.4.1.18.3.5.9.2.2.1.57 |
This is the minimum size of a packet of which Multilink
will fragment.
|
wfPppCircuitMaxLinks |
.1.3.6.1.4.1.18.3.5.9.2.2.1.58 |
This is the maximum number of links allowed in the Multilink
bundle for this circuit at any one time.
|
wfPppCircuitRecoverThreshold |
.1.3.6.1.4.1.18.3.5.9.2.2.1.59 |
This is the recovery threshold expressed as a percentage of the
theoretical maximum bundle throughput. The actual throughput must fall
below this percentage in order for the BOD circuit to
begin to remove lines from the Multilink bundle.
|
wfPppCircuitPeriodsUnCng |
.1.3.6.1.4.1.18.3.5.9.2.2.1.60 |
This parameter is used for recovery. Once a Multilink bundle has
been declared as congested, this is the number of
consecutive examination periods where the queue depth is
below the recovery threshold value required to declare that the
bundle is no longer congested.
|
wfPppCircuitHistory |
.1.3.6.1.4.1.18.3.5.9.2.2.1.61 |
DEBUG parameter - This is the BOD history buffer.
|
wfPppCircuitDebugFlag |
.1.3.6.1.4.1.18.3.5.9.2.2.1.62 |
DEBUG parameter - This is the BOD Debug flag, used to control
debug code for BOD.
|
wfPppCircuitActualMode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.63 |
This attribute is the actual ppp mode of the circuit after
LCP has negotiated.
|
wfPppCircuitMaxBuffers |
.1.3.6.1.4.1.18.3.5.9.2.2.1.64 |
This is the maximum number of stored buffers allowed in the
Multilink Receive logic for this circuit at any one time.
|
wfPppCircuitLinksConfigured |
.1.3.6.1.4.1.18.3.5.9.2.2.1.65 |
This is the current number of lines configured for this
Multilink circuit.
|
wfPppCircuitBacpDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.66 |
enable/disable BACP Protocol - disabling generates
a Close event to the BACP FSM and consequently
disallows BAP traffic on this circuit
|
wfPppCircuitBacpCurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.67 |
the current state of the BACP Finite State Machine
|
wfPppCircuitBacpNoPhoneNum |
.1.3.6.1.4.1.18.3.5.9.2.2.1.68 |
enable/disable sending of the No-Phone-Number-Needed option
in BACP Call Request packets
|
wfPppCircuitIpv6Disable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.69 |
enable/disable IPv6 Protocol - disabling generates
a Close event to the IPv6CP FSM and consequently disallows
IPv6 traffic on this circuit
|
wfPppCircuitIpv6CurrentState |
.1.3.6.1.4.1.18.3.5.9.2.2.1.70 |
the current state of the Ipv6 Finite State Machine
|
wfPppCircuitCcpType |
.1.3.6.1.4.1.18.3.5.9.2.2.1.71 |
Specifies whether to use CCP or Individual Link CCP
|
wfPppCircuitCfgCcpOptions |
.1.3.6.1.4.1.18.3.5.9.2.2.1.72 |
Specifies the compression protocol options in 1st
config-request
|
wfPppCircuitCcpOptions |
.1.3.6.1.4.1.18.3.5.9.2.2.1.73 |
The negotiated compression protocol option
|
wfPppCircuitStacLZSCheckMode |
.1.3.6.1.4.1.18.3.5.9.2.2.1.74 |
Specifies the check mode for STAC LZS compression protocol. See
RFC 1974 for more information.
|
wfPppCircuitMLFragStrict |
.1.3.6.1.4.1.18.3.5.9.2.2.1.75 |
enable/disable strict fragmentation algorithm i.e. fragmenting a
packet when its size exceeds the threshold regardless of what the
average packet size is
|
wfPppCircuitLampreyCompDisable |
.1.3.6.1.4.1.18.3.5.9.2.2.1.76 |
enable/disable hardware compression, either from the compression
daugther card on the Lamprey or the old compression daugther
interface card on the link module, it tells you where the
compression hardware is
|
wfPppCircuitMsgLevel |
.1.3.6.1.4.1.18.3.5.9.2.2.1.77 |
PPP Circuit log messages level.
To control level of log messages
DBG_MSG_ALL 0x001f0000 - 2031616
DBG_MSG_DEBUG 0x00010000 - 65536
DBG_MSG_INFO 0x00020000 - 131072
DBG_MSG_WARNING 0x00040000 - 262144
DBG_MSG_FAULT 0x00080000 - 524288
DBG_MSG_TRACE 0x00100000 - 1048576
|
wfPppCircuitType |
.1.3.6.1.4.1.18.3.5.9.2.2.1.78 |
To differentiate between a Dial Up PPP circuit from L2TP and Leased Line
|
wfPppWhoamiName |
.1.3.6.1.4.1.18.3.5.9.2.3.1.2 |
Peer CHAP Name
|
wfPppWhoamiDelete |
.1.3.6.1.4.1.18.3.5.9.2.3.1.1 |
Create/Delete parameter
|
wfPppWhoamiCircuit |
.1.3.6.1.4.1.18.3.5.9.2.3.1.3 |
Circuit number to map to
|
wfPppWhoamiSecret |
.1.3.6.1.4.1.18.3.5.9.2.3.1.4 |
Peer CHAP Secret
|
wfPppWhoamiPapPassword |
.1.3.6.1.4.1.18.3.5.9.2.3.1.5 |
Peer Pap Password
|
wfPppWhoamiCctGrp |
.1.3.6.1.4.1.18.3.5.9.2.3.1.6 |
Unnumbered circuit group to map to
|
wfPppMlStatsCircuitID |
.1.3.6.1.4.1.18.3.5.9.2.4.1.2 |
cct number for this instance
|
wfPppMlStatsDelete |
.1.3.6.1.4.1.18.3.5.9.2.4.1.1 |
Create/Delete parameter
|
wfPppMlStatsHomeSlot |
.1.3.6.1.4.1.18.3.5.9.2.4.1.3 |
Slot on which this Multilink Control Subsystem exists
|
wfPppMlStatsLineCnt |
.1.3.6.1.4.1.18.3.5.9.2.4.1.4 |
Current count of lines in Multilink bundle
|
wfPppMlStatsBundleSpd |
.1.3.6.1.4.1.18.3.5.9.2.4.1.5 |
Current total bandwidth of Multilink bundle
|
wfPppMlStatsMrru |
.1.3.6.1.4.1.18.3.5.9.2.4.1.6 |
Current Maximum Receive Reconstructed Unit (MRRU)
in use for Multilink bundle
|
wfPppMlStatsEndptDisc |
.1.3.6.1.4.1.18.3.5.9.2.4.1.7 |
Current Endpoint Discriminator in use for
Multilink bundle
|
wfPppMlStatsTxOctets |
.1.3.6.1.4.1.18.3.5.9.2.4.1.8 |
Number of octets transmitted by Multilink
|
wfPppMlStatsTxPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.9 |
Number of packets transmitted by Multilink
|
wfPppMlStatsAvgTxListLen |
.1.3.6.1.4.1.18.3.5.9.2.4.1.10 |
Average number of packets received in the transient
list by the Multilink Transmit gate.
|
wfPppMlStatsRxOctets |
.1.3.6.1.4.1.18.3.5.9.2.4.1.11 |
Number of octets received without error
|
wfPppMlStatsRxPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.12 |
Number of packets received by Multilink
|
wfPppMlStatsReasmFails |
.1.3.6.1.4.1.18.3.5.9.2.4.1.13 |
Number of packet reassembly failures
|
wfPppMlStatsSeqNumberLost |
.1.3.6.1.4.1.18.3.5.9.2.4.1.14 |
Number of Multilink packets considered to be lost on
the wire
|
wfPppMlStatsSeqNumberArrivedLate |
.1.3.6.1.4.1.18.3.5.9.2.4.1.15 |
Number of Multilink packets which arrive
containing an old Sequence Number. IE: packets
with a more current Sequence Number have already
been sent up to NCP
|
wfPppMlStatsReSeqBufferCnt |
.1.3.6.1.4.1.18.3.5.9.2.4.1.16 |
Number of Multilink packets currently stored
in the ReSequencing buffer pool.
|
wfPppMlStatsReSeqBufferMax |
.1.3.6.1.4.1.18.3.5.9.2.4.1.17 |
The Maximum Number of Multilink packets stored
in the ReSequencing buffer pool.
|
wfPppMlStatsExceededBufferMax |
.1.3.6.1.4.1.18.3.5.9.2.4.1.18 |
The number of times a buffer needed to be stored by the
Multilink Receive logic when the count of buffers stored,
wfPppMlStatsReSeqBufferMax,was equal to the maximum allowable
for this circuit, wfPppCircuitMaxBuffers.
|
wfPppMlStatsLinkIdleEvents |
.1.3.6.1.4.1.18.3.5.9.2.4.1.19 |
The number of times the Multilink Receive logic detected a
stored buffer received on a line which has been declared idle.
|
wfPppMlStatsCalcPercent |
.1.3.6.1.4.1.18.3.5.9.2.4.1.20 |
enable/disable collection of Rx percentage line usage
|
wfPppMlStatsDebug |
.1.3.6.1.4.1.18.3.5.9.2.4.1.21 |
DEBUG parameter - this is used to control debug code for the Multilink subsystem
|
wfPppMlStatsReassmBufferCnt |
.1.3.6.1.4.1.18.3.5.9.2.4.1.22 |
Number of Multilink packets currently stored
in the Reassembling buffer pools.
|
wfPppMlStatsReassmBufferMax |
.1.3.6.1.4.1.18.3.5.9.2.4.1.23 |
The Maximum Number of Multilink packets stored
in the Reassembling buffer pools.
|
wfPppMlStatsNumPktsFragmented |
.1.3.6.1.4.1.18.3.5.9.2.4.1.24 |
The Number of Multilink packets that were
fragmented.
|
wfPppMlStatsPQHiXmits |
.1.3.6.1.4.1.18.3.5.9.2.4.1.25 |
High priority transmit count.
|
wfPppMlStatsPQNormalXmits |
.1.3.6.1.4.1.18.3.5.9.2.4.1.26 |
Normal priority transmit count.
|
wfPppMlStatsPQLoXmits |
.1.3.6.1.4.1.18.3.5.9.2.4.1.27 |
Low priority transmit count
|
wfPppMlStatsPQHiClippedPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.28 |
High priority transmit clip Count
|
wfPppMlStatsPQNormalClippedPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.29 |
Normal priority transmit clip Count
|
wfPppMlStatsPQLoClippedPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.30 |
Low priority transmit clip Count
|
wfPppMlStatsPQIntrQHighWaterPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.31 |
Interrupt-priority Queue high-water mark
|
wfPppMlStatsPQHiQHighWaterPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.32 |
High-priority Queue high-water mark
|
wfPppMlStatsPQNormalQHighWaterPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.33 |
Normal-priority Queue high-water mark
|
wfPppMlStatsPQLoQHighWaterPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.34 |
Low-priority Queue high-water mark
|
wfPppMlStatsPQHighWaterPktsClear |
.1.3.6.1.4.1.18.3.5.9.2.4.1.35 |
Attribute to clear the high-water marks. When the MIB
changes, Priority Queueing (if ENABLED) checks to see
if HighWaterPktsClear is different than the last time the MIB
was modified in any way. If it is different,
all the high water marks (see above) are set to zero.
|
wfPppMlStatsPQDroppedPkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.36 |
Packets which were filtered in Priority Queueing
|
wfPppMlStatsPQLargePkts |
.1.3.6.1.4.1.18.3.5.9.2.4.1.37 |
Large Packets which became an exception to latency rules
|
wfPppMlStatsPQHiTotalOctets |
.1.3.6.1.4.1.18.3.5.9.2.4.1.38 |
Running total of High Octets transmitted when
using Bandwidth Allocation dequeueing algorithm
|
wfPppMlStatsPQNormalTotalOctets |
.1.3.6.1.4.1.18.3.5.9.2.4.1.39 |
Running total of Normal Octets transmitted when
using Bandwidth Allocation dequeueing algorithm
|
wfPppMlStatsPQLoTotalOctets |
.1.3.6.1.4.1.18.3.5.9.2.4.1.40 |
Running total of Low Octets transmitted when
using Bandwidth Allocation dequeueing algorithm
|
wfPppMlStatsPQPktsNotQueued |
.1.3.6.1.4.1.18.3.5.9.2.4.1.41 |
Packets that were not Queued or Dropped by
Priority Queuing
|
wfPppBapStatsCircuitID |
.1.3.6.1.4.1.18.3.5.9.2.5.1.2 |
cct number for this instance
|
wfPppBapStatsDelete |
.1.3.6.1.4.1.18.3.5.9.2.5.1.1 |
Create/Delete parameter
|
wfPppBapCallReqTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.3 |
Number of Call Requests transmitted by BAP
|
wfPppBapCallRespAckTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.4 |
Number of Call Responses transmitted by BAP
with a Response Code of Request_Ack
|
wfPppBapCallRespNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.5 |
Number of Call Responses transmitted by BAP
with a Response Code of Request_Nak
|
wfPppBapCallRespFullNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.6 |
Number of Call Responses transmitted by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallRespRejTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.7 |
Number of Call Responses transmitted by BAP
with a Response Code of Request_Rej
|
wfPppBapCallbackReqTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.8 |
Number of Callback Requests transmitted by BAP
|
wfPppBapCallbackRespAckTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.9 |
Number of Callback Responses transmitted by BAP
with a Response Code of Request_Ack
|
wfPppBapCallbackRespNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.10 |
Number of Callback Responses transmitted by BAP
with a Response Code of Request_Nak
|
wfPppBapCallbackRespFullNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.11 |
Number of Callback Responses transmitted by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallbackRespRejTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.12 |
Number of Callback Responses transmitted by BAP
with a Response Code of Request_Rej
|
wfPppBapLdQueryReqTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.13 |
Number of LinkDrop Query Requests transmitted by BAP
|
wfPppBapLdQueryRespAckTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.14 |
Number of LinkDrop Query Responses transmitted by BAP
with a Response Code of Request_Ack
|
wfPppBapLdQueryRespNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.15 |
Number of LinkDrop Query Responses transmitted by BAP
with a Response Code of Request_Nak
|
wfPppBapLdQueryRespFullNakTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.16 |
Number of LinkDrop Query Responses transmitted by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallStatusIndFailTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.17 |
Number of Call_Status_Indications transmitted by BAP
with a non-zero Call Status
|
wfPppBapCallStatusIndSuccessTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.18 |
Number of Call_Status_Indications transmitted by BAP
with a zero Call Status
|
wfPppBapCallStatusRespTx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.19 |
Number of Call_Status_Response transmitted by BAP
|
wfPppBapCallReqRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.20 |
Number of Call Requests received by BAP
|
wfPppBapCallRespAckRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.21 |
Number of Call Responses received by BAP
with a Response Code of Request_Ack
|
wfPppBapCallRespNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.22 |
Number of Call Responses received by BAP
with a Response Code of Request_Nak
|
wfPppBapCallRespFullNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.23 |
Number of Call Responses received by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallRespRejRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.24 |
Number of Call Responses received by BAP
with a Response Code of Request_Rej
|
wfPppBapCallbackReqRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.25 |
Number of Callback Requests received by BAP
|
wfPppBapCallbackRespAckRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.26 |
Number of Callback Responses received by BAP
with a Response Code of Request_Ack
|
wfPppBapCallbackRespNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.27 |
Number of Callback Responses received by BAP
with a Response Code of Request_Nak
|
wfPppBapCallbackRespFullNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.28 |
Number of Callback Responses received by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallbackRespRejRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.29 |
Number of Callback Responses received by BAP
with a Response Code of Request_Rej
|
wfPppBapLdQueryReqRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.30 |
Number of LinkDrop Query Requests received by BAP
|
wfPppBapLdQueryRespAckRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.31 |
Number of LinkDrop Query Responses received by BAP
with a Response Code of Request_Ack
|
wfPppBapLdQueryRespNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.32 |
Number of LinkDrop Query Responses received by BAP
with a Response Code of Request_Nak
|
wfPppBapLdQueryRespFullNakRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.33 |
Number of LinkDrop Query Responses received by BAP
with a Response Code of Request_Full_Nak
|
wfPppBapCallStatusIndFailRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.34 |
Number of Call_Status_Indications received by BAP
with a non-zero Call Status
|
wfPppBapCallStatusIndSuccessRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.35 |
Number of Call_Status_Indications received by BAP
with a zero Call Status
|
wfPppBapCallStatusRespRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.36 |
Number of Call_Status_Response received by BAP
|
wfPppBapCallReqRespDiscardRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.37 |
Number of Call_Response received by BAP with an
old identifier.
|
wfPppBapCallbackReqRespDiscardRx |
.1.3.6.1.4.1.18.3.5.9.2.5.1.38 |
Number of Callback_Response received by BAP with an
old identifier.
|