-
Notifications
You must be signed in to change notification settings - Fork 651
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
10f54a3
commit f40cd54
Showing
10 changed files
with
2,504 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN | ||
|
||
IMPORTS | ||
Integer32, MODULE-IDENTITY, mib-2 | ||
FROM SNMPv2-SMI | ||
TEXTUAL-CONVENTION | ||
FROM SNMPv2-TC; | ||
|
||
diffServDSCPTC MODULE-IDENTITY | ||
LAST-UPDATED "200205090000Z" | ||
ORGANIZATION "IETF Differentiated Services WG" | ||
CONTACT-INFO | ||
" Fred Baker | ||
Cisco Systems | ||
1121 Via Del Rey | ||
Santa Barbara, CA 93117, USA | ||
E-mail: [email protected] | ||
|
||
Kwok Ho Chan | ||
Nortel Networks | ||
600 Technology Park Drive | ||
Billerica, MA 01821, USA | ||
E-mail: [email protected] | ||
|
||
Andrew Smith | ||
Harbour Networks | ||
Jiuling Building | ||
21 North Xisanhuan Ave. | ||
Beijing, 100089, PRC | ||
E-mail: [email protected] | ||
|
||
Differentiated Services Working Group: | ||
[email protected]" | ||
DESCRIPTION | ||
"The Textual Conventions defined in this module should be used | ||
whenever a Differentiated Services Code Point is used in a MIB." | ||
REVISION "200205090000Z" | ||
DESCRIPTION | ||
"Initial version, published as RFC 3289." | ||
::= { mib-2 96 } | ||
|
||
Dscp ::= TEXTUAL-CONVENTION | ||
DISPLAY-HINT "d" | ||
STATUS current | ||
DESCRIPTION | ||
"A Differentiated Services Code-Point that may be used for | ||
marking a traffic stream." | ||
REFERENCE | ||
"RFC 2474, RFC 2780" | ||
SYNTAX Integer32 (0..63) | ||
|
||
DscpOrAny ::= TEXTUAL-CONVENTION | ||
DISPLAY-HINT "d" | ||
STATUS current | ||
DESCRIPTION | ||
"The IP header Differentiated Services Code-Point that may be | ||
|
||
used for discriminating among traffic streams. The value -1 is | ||
used to indicate a wild card i.e. any value." | ||
REFERENCE | ||
"RFC 2474, RFC 2780" | ||
SYNTAX Integer32 (-1 | 0..63) | ||
|
||
END |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,118 @@ | ||
HCNUM-TC DEFINITIONS ::= BEGIN | ||
|
||
IMPORTS | ||
MODULE-IDENTITY, mib-2, Counter64 | ||
FROM SNMPv2-SMI | ||
TEXTUAL-CONVENTION | ||
FROM SNMPv2-TC; | ||
|
||
hcnumTC MODULE-IDENTITY | ||
LAST-UPDATED "200006080000Z" | ||
|
||
ORGANIZATION "IETF OPS Area" | ||
CONTACT-INFO | ||
" E-mail: [email protected] | ||
Subscribe: [email protected] | ||
with msg body: subscribe mibs | ||
|
||
Andy Bierman | ||
Cisco Systems Inc. | ||
170 West Tasman Drive | ||
San Jose, CA 95134 USA | ||
+1 408-527-3711 | ||
[email protected] | ||
|
||
Keith McCloghrie | ||
Cisco Systems Inc. | ||
170 West Tasman Drive | ||
San Jose, CA 95134 USA | ||
+1 408-526-5260 | ||
[email protected] | ||
|
||
Randy Presuhn | ||
BMC Software, Inc. | ||
Office 1-3141 | ||
2141 North First Street | ||
San Jose, California 95131 USA | ||
+1 408 546-1006 | ||
[email protected]" | ||
DESCRIPTION | ||
"A MIB module containing textual conventions | ||
for high capacity data types. This module | ||
addresses an immediate need for data types not directly | ||
supported in the SMIv2. This short-term solution | ||
is meant to be deprecated as a long-term solution | ||
is deployed." | ||
REVISION "200006080000Z" | ||
DESCRIPTION | ||
"Initial Version of the High Capacity Numbers | ||
MIB module, published as RFC 2856." | ||
::= { mib-2 78 } | ||
|
||
CounterBasedGauge64 ::= TEXTUAL-CONVENTION | ||
STATUS current | ||
DESCRIPTION | ||
"The CounterBasedGauge64 type represents a non-negative | ||
integer, which may increase or decrease, but shall never | ||
exceed a maximum value, nor fall below a minimum value. The | ||
maximum value can not be greater than 2^64-1 | ||
(18446744073709551615 decimal), and the minimum value can | ||
|
||
not be smaller than 0. The value of a CounterBasedGauge64 | ||
has its maximum value whenever the information being modeled | ||
is greater than or equal to its maximum value, and has its | ||
minimum value whenever the information being modeled is | ||
smaller than or equal to its minimum value. If the | ||
information being modeled subsequently decreases below | ||
(increases above) the maximum (minimum) value, the | ||
CounterBasedGauge64 also decreases (increases). | ||
|
||
Note that this TC is not strictly supported in SMIv2, | ||
because the 'always increasing' and 'counter wrap' semantics | ||
associated with the Counter64 base type are not preserved. | ||
It is possible that management applications which rely | ||
solely upon the (Counter64) ASN.1 tag to determine object | ||
semantics will mistakenly operate upon objects of this type | ||
as they would for Counter64 objects. | ||
|
||
This textual convention represents a limited and short-term | ||
solution, and may be deprecated as a long term solution is | ||
defined and deployed to replace it." | ||
SYNTAX Counter64 | ||
|
||
ZeroBasedCounter64 ::= TEXTUAL-CONVENTION | ||
STATUS current | ||
DESCRIPTION | ||
"This TC describes an object which counts events with the | ||
following semantics: objects of this type will be set to | ||
zero(0) on creation and will thereafter count appropriate | ||
events, wrapping back to zero(0) when the value 2^64 is | ||
reached. | ||
|
||
Provided that an application discovers the new object within | ||
the minimum time to wrap it can use the initial value as a | ||
delta since it last polled the table of which this object is | ||
part. It is important for a management station to be aware | ||
of this minimum time and the actual time between polls, and | ||
to discard data if the actual time is too long or there is | ||
no defined minimum time. | ||
|
||
Typically this TC is used in tables where the INDEX space is | ||
constantly changing and/or the TimeFilter mechanism is in | ||
use. | ||
|
||
Note that this textual convention does not retain all the | ||
semantics of the Counter64 base type. Specifically, a | ||
Counter64 has an arbitrary initial value, but objects | ||
defined with this TC are required to start at the value | ||
|
||
zero. This behavior is not likely to have any adverse | ||
effects on management applications which are expecting | ||
Counter64 semantics. | ||
|
||
This textual convention represents a limited and short-term | ||
solution, and may be deprecated as a long term solution is | ||
defined and deployed to replace it." | ||
SYNTAX Counter64 | ||
|
||
END |
Oops, something went wrong.