App-Netsync
view release on metacpan or search on metacpan
share/mib/BGP4-MIB.txt view on Meta::CPAN
REFERENCE
"RFC 4271, Section 8."
::= { bgpPeerEntry 15 }
bgpPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This timer indicates how long (in
seconds) this peer has been in the
established state or how long
since this peer was last in the
established state. It is set to zero when
a new peer is configured or when the router is
booted."
REFERENCE
"RFC 4271, Section 8."
::= { bgpPeerEntry 16 }
bgpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval (in seconds) for the
ConnectRetry timer. The suggested value
for this timer is 120 seconds."
REFERENCE
"RFC 4271, Section 8.2.2. This is the value used
to initialize the 'ConnectRetryTimer'."
::= { bgpPeerEntry 17 }
bgpPeerHoldTime OBJECT-TYPE
SYNTAX Integer32 ( 0 | 3..65535 )
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
share/mib/BGP4-MIB.txt view on Meta::CPAN
"RFC 4271, Section 4.2."
::= { bgpPeerEntry 18 }
bgpPeerKeepAlive OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time interval (in seconds) for the KeepAlive
timer established with the peer. The value
of this object is calculated by this BGP
speaker such that, when compared with
bgpPeerHoldTime, it has the same proportion
that bgpPeerKeepAliveConfigured has,
compared with bgpPeerHoldTimeConfigured.
If the KeepAlive timer has not been established
with the peer, this object MUST have a value
of zero (0).
If the of bgpPeerKeepAliveConfigured object
has a value of (0), then this object MUST have
a value of (0)."
REFERENCE
"RFC 4271, Section 4.4."
::= { bgpPeerEntry 19 }
share/mib/BGP4-MIB.txt view on Meta::CPAN
peer. This value is placed in an OPEN
message sent to this peer by this BGP
speaker, and is compared with the Hold
Time field in an OPEN message received
from the peer when determining the Hold
Time (bgpPeerHoldTime) with the peer.
This value must not be less than three
seconds if it is not zero (0). If it is
zero (0), the Hold Time is NOT to be
established with the peer. The suggested
value for this timer is 90 seconds."
REFERENCE
"RFC 4271, Section 4.2.
RFC 4271, Section 10."
::= { bgpPeerEntry 20 }
bgpPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval (in seconds) for the
KeepAlive timer configured for this BGP
speaker with this peer. The value of this
object will only determine the
KEEPALIVE messages' frequency relative to
the value specified in
bgpPeerHoldTimeConfigured; the actual
time interval for the KEEPALIVE messages is
indicated by bgpPeerKeepAlive. A
reasonable maximum value for this timer
would be one third of that of
bgpPeerHoldTimeConfigured.
If the value of this object is zero (0),
no periodical KEEPALIVE messages are sent
to the peer after the BGP connection has
been established. The suggested value for
this timer is 30 seconds."
REFERENCE
"RFC 4271, Section 4.4.
RFC 4271, Section 10."
::= { bgpPeerEntry 21 }
bgpPeerMinASOriginationInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval (in seconds) for the
MinASOriginationInterval timer.
The suggested value for this timer is 15
seconds."
REFERENCE
"RFC 4271, Section 9.2.1.2.
RFC 4271, Section 10."
::= { bgpPeerEntry 22 }
bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval (in seconds) for the
MinRouteAdvertisementInterval timer.
The suggested value for this timer is 30
seconds for EBGP connections and 5
seconds for IBGP connections."
REFERENCE
"RFC 4271, Section 9.2.1.1.
RFC 4271, Section 10."
::= { bgpPeerEntry 23 }
bgpPeerInUpdateElapsedTime OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
share/mib/CISCO-TC.my view on Meta::CPAN
'peerFcipPortClosedConnection(47)' - port went down because
peer FCIP port closed TCP connection.
'peerFcipPortResetConnection(48)' - port went down because
the TCP connection was reset by the peer FCIP port.
'fcipPortMaxReTx(49)' - FCIP port went down due to maximum
TCP re-transmissions reached the configured limit.
'fcipPortKeepAliveTimerExpire(50)' - FCIP port went down
due to TCP keep alive timer expired.
'fcipPortPersistTimerExpire(51)' - FCIP port went down due
to TCP persist timer expired.
'fcipPortSrcLinkDown(52)' - FCIP port went down due to
Ethernet link down.
'fcipPortSrcAdminDown(53)' - FCIP port went down because
the source Ethernet link was administratively shutdown.
'fcipPortAdminCfgChange(54)' - FCIP port went down due to
configuration change.
share/mib/CISCO-VTP-MIB.my view on Meta::CPAN
--
-- Only one manager can edit the Edit Buffer at a time. So, a
-- request to copy the current VLAN information into the Edit Buffer
-- must fail if the Edit Buffer is already in use (i.e., is not empty).
-- Thus, concurrent attempts by multiple managers to gain use of the
-- Edit Buffer are resolved according to whichever of them succeeds
-- in performing a successful copy. An OwnerString object provides
-- information on which manager currently has access.
--
-- Ownership of the Edit Buffer terminates when a NMS explicitly
-- releases it, or when a deadman-timer expires. The deadman-timer
-- has a fixed expiry interval of 5 minutes. The deadman-timer is
-- automatically started on a successful copy operation. The
-- restartTimer operation allows an NMS to restart the deadman-timer
-- if it wishes to retain ownership of the Edit Buffer for longer
-- than 5 minutes. The deadman-timer ceases when the apply operation
-- is invoked, and is restarted when the apply operation terminates.
-- Restarting the deadman-timer after termination of the apply
-- operation allows the results of the apply operation to be retained
-- until the requesting manager has retrieved them, but for only a
-- limited amount of time.
--
-- When managementDomainVersionInUse is version1(1) or version2(2),
-- the local device with managementDomainLocalMode as server(2)
-- could change the global VLAN configuration by editing the VLAN
-- information in the edit buffer and then apply it. However,
-- when managementDomainVersionInUse is in version3(4), there
-- are two different VTP servers, the primary server and the
share/mib/CISCO-VTP-MIB.my view on Meta::CPAN
STATUS current
DESCRIPTION
"This object always has the value 'none' when read. When
written, each value causes the appropriate action:
'copy' - causes the creation of rows in the
vtpVlanEditTable exactly corresponding to the current global
VLAN information for this management domain. If the Edit
Buffer (for this management domain) is not currently empty,
a copy operation fails. A successful copy operation starts
the deadman-timer.
'apply' - first performs a consistent check on the the
modified information contained in the Edit Buffer, and if
consistent, then tries to instanciate the modified
information as the new global VLAN information. Note that
an empty Edit Buffer (for the management domain) would
always result in an inconsistency since the default VLANs
are required to be present.
'release' - flushes the Edit Buffer (for this management
domain), clears the Owner information, and aborts the
deadman-timer. A release is generated automatically if the
deadman-timer ever expires.
'restartTimer' - restarts the deadman-timer.
'none' - no operation is performed."
::= { vtpEditControlEntry 1 }
vtpVlanApplyStatus OBJECT-TYPE
SYNTAX INTEGER {
inProgress(1),
succeeded(2),
configNumberError(3),
inconsistentEdit(4),
share/mib/FDDI-SMT73-MIB.txt view on Meta::CPAN
-- due to the lower maximum value since they do not require
-- the full range.
--
-- Example: If fddimibMACTReq had a value of 8 ms, it would
-- be stored in ANSI TimerTwosComplement format as 0xFFFE7960
-- [8 ms is 100000 in 80 nsec units, which is then converted
-- to two's complement] but be reported as 8000000 in SNMP
-- since it is encoded here as FddiTimeNano.
FddiTimeMilli ::= INTEGER (0..2147483647)
-- This data type is used for some FDDI timers. It specifies
-- time in 1 millisecond units, in normal integer
-- representation.
FddiResourceId ::= INTEGER (0..65535)
-- This data type is used to refer to an instance of a MAC,
-- PORT, or PATH Resource ID. Indexing begins
-- at 1. Zero is used to indicate the absence of a resource.
FddiSMTStationIdType ::= OCTET STRING (SIZE (8))
-- The unique identifier for the FDDI station. This is a
share/mib/FDDI-SMT73-MIB.txt view on Meta::CPAN
rejectM-M 15 "
REFERENCE
"ANSI { fddiSMT 27 }"
::= { fddimibSMTEntry 14 }
fddimibSMTTNotify OBJECT-TYPE
SYNTAX INTEGER (2..30)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The timer, expressed in seconds, used in the
Neighbor Notification protocol. It has a range of
2 seconds to 30 seconds, and its default value is
30 seconds (refer to ANSI SMT 8.2)."
REFERENCE
"ANSI { fddiSMT 29 }"
::= { fddimibSMTEntry 15 }
fddimibSMTStatRptPolicy OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-write
share/mib/FOUNDRY-SN-SWITCH-GROUP-MIB.mib view on Meta::CPAN
DESCRIPTION
"
the Bridge-Identifier as used in the Spanning Tree
"
SYNTAX OCTET STRING (SIZE(8))
Timeout ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"
a STP timer in units of 1/100 seconds
"
SYNTAX Integer32
PortMask ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"
This data type is used to model port bitmask. The
maximum of ports are 32.
"
share/mib/FOUNDRY-SN-SWITCH-GROUP-MIB.mib view on Meta::CPAN
SYNTAX INTEGER (0..40)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"dot1dStpBridgeMaxAge: From RFC1493(Bridge MIB).
The value that all bridges use for MaxAge when
this bridge is acting as the root.
Note that 802.1D-1990 specifies that the
range for this parameter is related to the value of
dot1dStpBridgeHelloTime. The granularity of this
timer is specified by 802.1D-1990 to be 1 second.
An agent may return a badValue error if a set is
attempted to a value which is not a whole number
of seconds."
::= { snVLanByPortEntry 7 }
snVLanByPortStpGroupHelloTime OBJECT-TYPE
SYNTAX INTEGER (0..10)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"dot1dStpBridgeHelloTime: From RFC1493(Bridge MIB).
The value that all bridges use for HelloTime when
this bridge is acting as the root. The
granularity of this timer is specified by 802.1D-
1990 to be 1 second. An agent may return a
badValue error if a set is attempted to a value
which is not a whole number of seconds."
::= { snVLanByPortEntry 8 }
snVLanByPortStpGroupForwardDelay OBJECT-TYPE
SYNTAX INTEGER (0..30)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"dot1dStpBridgeForwardDelay : From RFC1493(Bridge MIB).
The value that all bridges use for ForwardDelay
when this bridge is acting as the root. Note that
802.1D-1990 specifies that the range for this
parameter is related to the value of
dot1dStpBridgeMaxAge. The granularity of this
timer is specified by 802.1D-1990 to be 1 second.
An agent may return a badValue error if a set is
attempted to a value which is not a whole number
of seconds."
::= { snVLanByPortEntry 9 }
snVLanByPortRowStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
valid(2),
delete(3),
share/mib/FOUNDRY-SN-SWITCH-GROUP-MIB.mib view on Meta::CPAN
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"dot1dStpBridgeMaxAge: From RFC1493(Bridge MIB).
The value that all bridges use for MaxAge when
this bridge is acting as the root.
Note that 802.1D-1990 specifies that the
range for this parameter is related to the value of
dot1dStpBridgeHelloTime. The granularity of this
timer is specified by 802.1D-1990 to be 1 second.
An agent may return a badValue error if a set is
attempted to a value which is not a whole number
of seconds.
Valid value betweek 6 and 40. Default is 20 seconds.
Value 0 is returned if no STP is not configured for this vlan."
::= { snVLanByPortCfgEntry 5 }
snVLanByPortCfgStpGroupHelloTime OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"dot1dStpBridgeHelloTime: From RFC1493(Bridge MIB).
The value that all bridges use for HelloTime when
this bridge is acting as the root. The
granularity of this timer is specified by 802.1D-
1990 to be 1 second. An agent may return a
badValue error if a set is attempted to a value
which is not a whole number of seconds.
Valid value betweek 1 and 10. Default is 2 seconds.
Value 0 is returned if no STP is not configured for this vlan."
::= { snVLanByPortCfgEntry 6 }
snVLanByPortCfgStpGroupForwardDelay OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"dot1dStpBridgeForwardDelay : From RFC1493(Bridge MIB).
The value that all bridges use for ForwardDelay
when this bridge is acting as the root. Note that
802.1D-1990 specifies that the range for this
parameter is related to the value of
dot1dStpBridgeMaxAge. The granularity of this
timer is specified by 802.1D-1990 to be 1 second.
An agent may return a badValue error if a set is
attempted to a value which is not a whole number
of seconds.
Valid value betweek 2 and 30. Default is 15 seconds.
Value 0 is returned if no STP is not configured for this vlan."
::= { snVLanByPortCfgEntry 7 }
snVLanByPortCfgBaseNumPorts OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
share/mib/POWER-ETHERNET-MIB.txt view on Meta::CPAN
::= { pethPsePortEntry 7 }
pethPsePortMPSAbsentCounter OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
transitions directly from the state POWER_ON to the
state IDLE due to tmpdo_timer_done being asserted."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.11
aPSEMPSAbsentCounter"
::= { pethPsePortEntry 8 }
pethPsePortType OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
share/mib/lldp.mib view on Meta::CPAN
is not recognized by the receiving LLDP agent. The TLV may
be from a later version of the basic management set.
This table should only contain TLVs that are found in
a single LLDP frame. Entries in this table, associated
with an MAC service access point (MSAP, the access point
for MAC services provided to the LCC sublayer, defined
in IEEE 100, which is also identified with a particular
lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with
most recently received unrecognized TLV from the same MSAP,
or they will naturally age out when the rxInfoTTL timer
(associated with the MSAP) expires."
REFERENCE
"IEEE 802.1AB-2005 10.3.2"
::= { lldpRemoteSystemsData 3 }
lldpRemUnknownTLVEntry OBJECT-TYPE
SYNTAX LldpRemUnknownTLVEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
( run in 1.142 second using v1.01-cache-2.11-cpan-49f99fa48dc )