smilint output for ./PW-DRAFT05-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 1 |
| error | 3 |
| Message Types |
|---|
| Type | Count |
|---|
| import-failed (error) | 3 |
| internal-other (severe) | 1 |
Messages:
PW-DRAFT05-MIB
1: -- extracted from draft-ietf-pwe3-pw-mib-05.txt
2: -- at Thu Jul 8 06:21:50 2004
3:
4: PW-DRAFT05-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
8: Integer32, Unsigned32, Counter32, Counter64, TimeTicks
9: FROM SNMPv2-SMI
10:
11: MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
12: FROM SNMPv2-CONF
13:
14: TruthValue, RowStatus, StorageType,
15: TimeStamp
16: FROM SNMPv2-TC
17:
18: SnmpAdminString
19: FROM SNMP-FRAMEWORK-MIB
20:
21: PwVcIndexType, PwGroupID, PwVcIDType, PwOperStatus, PwVcType,
22: PwVcAttachmentIdentifierType, PwVcCwStatus, PwVcCapabilities,
23: PwVcStatus, PwVcFragSize, PwVcFragStatus, pwStdMIB
24: FROM PW-TC-DRAFT05-MIB
24: error -
identifier `PwOperStatus' cannot be imported from module `PW-TC-DRAFT05-MIB'
24: error -
identifier `PwVcType' cannot be imported from module `PW-TC-DRAFT05-MIB'
24: error -
identifier `PwVcFragStatus' cannot be imported from module `PW-TC-DRAFT05-MIB'
25:
26: InterfaceIndexOrZero
27: FROM IF-MIB
28:
29: InetAddressType, InetAddress
30: Pseudo Wire (PW) Management June 2004
30: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting FROM or ','
31: Information Base
32:
33:
34: FROM INET-ADDRESS-MIB
35:
36: PerfCurrentCount, PerfIntervalCount
37: FROM PerfHist-TC-MIB
38:
39: HCPerfCurrentCount, HCPerfIntervalCount, HCPerfTimeElapsed,
40: HCPerfValidIntervals
41: FROM HC-PerfHist-TC-MIB
42: ;
43:
44: pwVcMIB MODULE-IDENTITY
45: LAST-UPDATED "200406021200Z" -- 2 June 2004 12:00:00 GMT
46: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
47: Group"
48: CONTACT-INFO
49: "
50: David Zelig
51: Postal: Corrigent Systems
52: 126, Yigal Alon St.
53: Tel Aviv, ISRAEL
54: Phone: +972-3-6945273
55: E-mail: davidz@corrigent.com
56:
57: Thomas D. Nadeau
58: Postal: Cisco Systems, Inc.
59: 250 Apollo Drive
60: Chelmsford, MA 01824
61: Tel: +1-978-497-3051
62: Email: tnadeau@cisco.com
63:
64: Dave Danenberg
65: Email: dave_danenberg@yahoo.com
66:
67: Sharon Mantin
68: Postal: AxONLink (Israel) Ltd
69: 9 Bareket St.
70: Petah Tikva 49517, Israel
71: Tel: +972-3-9263972
72: Email: sharon.mantin@axonlink.com
73:
74: The PWE3 Working Group (email distribution pwe3@ietf.org,
75: http://www.ietf.org/html.charters/pwe3-charter.html)
76: "
77:
78: DESCRIPTION
79: "This MIB module contains managed object definitions for
80: Pseudo Wire operation as in: Bryant., et al, 'PWE3
81: architecture', Martini, L., et al, 'Pseudowire Setup and
82: Maintenance using LDP', and Townsley, M., et al, 'Layer Two
83: Tunneling Protocol (Version 3)'.
84: Pseudo Wire (PW) Management June 2004
85: Information Base
86:
87:
88: -- Editor note: will add RFC numbers when available.
89: This MIB module enables the use of any underlying packet
90: switched network (PSN). MIB nodules that will support
91: PW operations over specific PSN types are defined in
92: separate memos.
93:
94: The indexes for this MIB module are also used to index the
95: PSN-specific tables and the PW-specific tables. The PW Type
96: dictates which PW-specific MIB module to use.
97:
98: Copyright (C) The Internet Society (date). This version
99: of this MIB module is part of RFC yyyy; see the RFC
100: itself for full legal notices.
101: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
102: "
103:
104: -- Revision history.
105:
106: REVISION
107: "200406021200Z" -- 2 June 2004 12:00:00 GMT
108: DESCRIPTION
109: " published as draft-ietf-pw-mib-05. Changes from previous
110: drafts:
111: - FCS retention includes FCS size mismatch error.
112: - Allow configuration of peer address when signaling
113: protocol is not in use.
114: - Adding DEFVAL to PwVcFragSize.
115: "
116:
117: REVISION
118: "200402031200Z" -- 3 February 2004 12:00:00 GMT
119: DESCRIPTION
120: " published as draft-ietf-pw-mib-04. Changes from previous
121: draft:
122: - Adding an option for PW stitching - pwVcAttachedPwIndex.
123: - Removing unnecessary index from pwVcPeerMappingTable.
124: - Adding 32 bit counter support across performance tables.
125: - Changing pwVcIndexMappingVcIndex to read-create in order
126: to enable an option for EMS control on pwVcIndex.
127: - Add optional mapping of a pwVcIndex to an ifIndex.
128: - remove RowStatus from mapping table.
129: - Change time elapsed items to HCPerfTimeElapsed TC
130: - Change current and interval counters to their respective
131: TC from existing TC modules.
132: - Add disable/enable control for pwVcDeletedNotification.
133: - Change pwVcRemoteCwStatus to pwVcCwStatus, and it now
134: represent both the signaling status whether CW is to be
135: present or not.
136: "
137:
138: REVISION
139: Pseudo Wire (PW) Management June 2004
140: Information Base
141:
142:
143: "200312101200Z" -- 10 December 2003 12:00:00 EST
144: DESCRIPTION
145: " re-published as draft-ietf-pw-mib-03. Changes from
146: previous
147: draft:
148: - Changing textual convention back to TruthValue where
149: required for correct compilation.
150: - Editing description clauses.
151: - Adapting main description clause to MIB boilerplate.
152: - Adapt MIB names to STD-MIB naming convention.
153: - Add pwVcRemoteStatusCapable.
154: - Add PW delete notification.
155: - Add pwVcLastChanged.
156: - Clarify usage of pwVcIndexMappingTable.
157: "
158:
159: REVISION
160: "200307211200Z" -- 21 July 2003 12:00:00 EST
161: DESCRIPTION
162: " published as draft-ietf-pw-mib-02. Changes from previous
163: draft:
164: 1) Aligned with draft-ietf-pwe3-control-protocol-02.txt
165: 2) Add support for Generalized ID FEC Element option.
166: 3) Add support for fragmentation status.
167: 3) Add notifications and notification control.
168: 4) Remove control word to service specific MIB modules.
169: "
170:
171: REVISION
172: "200205261200Z" -- 26 May 2002 12:00:00 EST
173: DESCRIPTION
174: "Moved to draft-ietf-00 status. Changes from previous draft:
175: 1) Change name of pwVcPriority to pwVcSetUpPriority and
176: added pwVcHoldingPriority.
177: 2) Add pwVcIdMappingTable and pwVcPeersMappingTable to help
178: ordered query of the MIB tables for EMS applications.
179: 3) Clarification to work in progress objects.
180: 4) Editorial and typos in descriptions.
181: 5) Added pwVcPerfTotalDiscontinuityTime and
182: pwVcPerfIntervalTimeElapsed.
183: 6) Remove 32 bit counters.
184: "
185: REVISION
186: "200201301200Z" -- 30 January 2002 12:00:00 EST
187: DESCRIPTION
188: " Changes from -01 draft:
189: 1) Inbound and outbound clarification and name changes.
190: 2) Removing pwVcPeerIpv4Addr and pwVcPeerIpv6Addr,
191: replacing them with pwVcPeerAddr and adding type for
192: address type selection.
193: 3) Adding type for VC OperStatus.
194: Pseudo Wire (PW) Management June 2004
195: Information Base
196:
197:
198: 4) Adding pwVcTimeElapsed and pwVcValidIntervals.
199:
200: "
201: REVISION
202: "200111071200Z" -- 7 November 2001 12:00:00 EST
203: DESCRIPTION
204: "Changes from -00 draft:
205: 1) Remove VcInstance from tables indexes in order to simplify
206: the MIB.
207: 2) Removing APS 1+1 table.
208: 3) Changing hdlcCisco to hdlc in pwVcType.
209: 4) Add description of VC label at pending PW signaling stage.
210: 5) Add interval valid object in interval performance tables.
211: 6) Remove VC APS notification.
212: 7) Change 'conservative'/'liberal' to 'strict'/'loose'.
213: 8) Add objects for interface MTU, use of control word,
214: interface string.
215: 9) Ordering of objects based on functionality.
216: 10) Update operation of pwVcOperStatus.
217: "
218:
219: REVISION
220: "200107111200Z" -- 11 July 2001 12:00:00 EST
221: DESCRIPTION
222: "draft-00 version"
223:
224: ::= { pwStdMIB x } -- To be assigned by IANA
225: -- the value 2 is requested for this
226: -- specific Module.
227:
228: -- Top-level components of this MIB.
229:
230: -- Notifications
231: pwVcNotifications OBJECT IDENTIFIER
232: ::= { pwVcMIB 0 }
233: -- Tables, Scalars
234: pwVcObjects OBJECT IDENTIFIER
235: ::= { pwVcMIB 1 }
236: -- Conformance
237: pwVcConformance OBJECT IDENTIFIER
238: ::= { pwVcMIB 2 }
239:
240: -- PW Virtual Connection (VC) Table
241:
242: pwVcIndexNext OBJECT-TYPE
243: SYNTAX Unsigned32
244: MAX-ACCESS read-only
245: STATUS current
246: DESCRIPTION
247: "This object contains an appropriate value to be used
248: for pwVcIndex when creating entries in the
249: Pseudo Wire (PW) Management June 2004
250: Information Base
251:
252:
253: pwVcTable. The value 0 indicates that no
254: unassigned entries are available. To obtain the
255: value of pwVcIndex for a new entry in the
256: pwVcTable, the manager issues a management
257: protocol retrieval operation to obtain the current
258: value of pwVcIndex. After each retrieval
259: operation, the agent should modify the value to
260: reflect the next unassigned index. After a manager
261: retrieves a value the agent will determine through
262: its local policy when this index value will be made
263: available for reuse."
264: ::= { pwVcObjects 1 }
265:
266:
267: pwVcTable OBJECT-TYPE
268: SYNTAX SEQUENCE OF PwVcEntry
269: MAX-ACCESS not-accessible
270: STATUS current
271: DESCRIPTION
272: "This table specifies information for configuring and
273: status monitoring which are common to all service types
274: and PSN types."
275:
276: ::= { pwVcObjects 2 }
277:
278: pwVcEntry OBJECT-TYPE
279: SYNTAX PwVcEntry
280: MAX-ACCESS not-accessible
281: STATUS current
282: DESCRIPTION
283: "A row in this table represents a pseudo wire (PW) virtual
284: connection (VC) across a packet network. It is indexed by
285: pwVcIndex, which uniquely identifying a singular
286: connection.
287: A row is created by the operator or by the agent if the PW
288: is created by non-SNMP application or due to autodiscovery
289: process.
290: None of the read-create objects values can be changed
291: when pwVcRowStatus is in the active(1) state. Changes are
292: allowed when the pwRowStatus is in notInService(2) or
293: notReady(3) states only.
294: If the operator need to change one of the values for an
295: active row (for example in order to fix a mismatch in
296: configuration between the local node and the peer), the
297: pwVcRowStatus should be first changed to notInService(2),
298: the objects may be changed now, and later to active(1)
299: in order to re-initiate the signaling process with the
300: new values in effect.
301: "
302: INDEX { pwVcIndex }
303: Pseudo Wire (PW) Management June 2004
304: Information Base
305:
306:
307: ::= { pwVcTable 1 }
308:
309: PwVcEntry ::= SEQUENCE {
310: pwVcIndex PwVcIndexType,
311: pwVcType PwVcType,
312: pwVcOwner INTEGER,
313: pwVcPsnType INTEGER,
314: pwVcSetUpPriority Integer32,
315: pwVcHoldingPriority Integer32,
316: pwVcPeerAddrType InetAddressType,
317: pwVcPeerAddr InetAddress,
318: pwVcAttachedPwIndex PwVcIndexType,
319: pwVcIfIndex InterfaceIndexOrZero,
320:
321: pwVcID PwVcIDType,
322: pwVcLocalGroupID PwGroupID,
323: pwVcGroupAttachmentID PwVcAttachmentIdentifierType,
324: pwVcLocalAttachmentID PwVcAttachmentIdentifierType,
325: pwVcPeerAttachmentID PwVcAttachmentIdentifierType,
326:
327: pwVcCwPreference TruthValue,
328: pwVcLocalIfMtu Unsigned32,
329: pwVcLocalIfString TruthValue,
330: pwVcLocalCapabAdvert PwVcCapabilities,
331: pwVcRemoteGroupID PwGroupID,
332: pwVcCwStatus PwVcCwStatus,
333: pwVcRemoteIfMtu Unsigned32,
334: pwVcRemoteIfString SnmpAdminString,
335: pwVcRemoteCapabilities PwVcCapabilities,
336:
337: pwVcFragmentCfgSize PwVcFragSize,
338: pwVcRmtFragCapability PwVcFragStatus,
339: pwVcFcsRetentioncfg INTEGER,
340: pwVcFcsRetentionStatus BITS,
341:
342: pwVcOutboundVcLabel Unsigned32,
343: pwVcInboundVcLabel Unsigned32,
344:
345: pwVcName SnmpAdminString,
346: pwVcDescr SnmpAdminString,
347: pwVcCreateTime TimeStamp,
348: pwVcUpTime TimeTicks,
349: pwVcLastChange TimeTicks,
350: pwVcAdminStatus INTEGER,
351: pwVcOperStatus PwOperStatus,
352: pwVcLocalStatus PwVcStatus,
353: pwVcRemoteStatusCapable INTEGER,
354: pwVcRemoteStatus PwVcStatus,
355:
356: pwVcTimeElapsed HCPerfTimeElapsed,
357: pwVcValidIntervals HCPerfValidIntervals,
358: Pseudo Wire (PW) Management June 2004
359: Information Base
360:
361:
362:
363: pwVcRowStatus RowStatus,
364: pwVcStorageType StorageType
365: }
366:
367: pwVcIndex OBJECT-TYPE
368: SYNTAX PwVcIndexType
369: MAX-ACCESS not-accessible
370: STATUS current
371: DESCRIPTION
372: "Index for the conceptual row identifying a PW within
373: this PW Emulation table."
374: ::= { pwVcEntry 1 }
375:
376: pwVcType OBJECT-TYPE
377: SYNTAX PwVcType
378: MAX-ACCESS read-create
379: STATUS current
380: DESCRIPTION
381: "This value indicate the service to be carried over
382: this PW.
383: "
384: ::= { pwVcEntry 2 }
385:
386: pwVcOwner OBJECT-TYPE
387: SYNTAX INTEGER {
388: manual (1),
389: pwIdFecSignaling (2), -- PW signaling with PW ID FEC
390: genFecSignaling (3), -- Generalized attachment FEC
391: l2tpControlProtocol (4),
392: other (5)
393: }
394: MAX-ACCESS read-create
395: STATUS current
396: DESCRIPTION
397: "Set by the operator to indicate the protocol responsible
398: for establishing this PW. Value 'manual' is used in all
399: cases where no maintenance protocol (PW signaling) is used
400: to set-up the PW, i.e. require configuration of entries in
401: the PW tables including PW labels, etc. The value
402: 'pwIdFecSignaling' is used in case of signaling with the
403: Pwid FEC element with LDP signaling, and
404: 'genFecSignaling' is used of the generalized FEC with LDP
405: is used for signaling purposes.
406: The value 'l2tpControlProtocol' indicate the use of L2TP
407: control protocol.
408: Value 'other' is used for other types of signaling."
409: ::= { pwVcEntry 3 }
410:
411:
412: pwVcPsnType OBJECT-TYPE
413: Pseudo Wire (PW) Management June 2004
414: Information Base
415:
416:
417: SYNTAX INTEGER {
418: mpls (1),
419: l2tp (2),
420: ip (3),
421: mplsOverIp (4),
422: gre (5),
423: other (6)
424: }
425: MAX-ACCESS read-create
426: STATUS current
427: DESCRIPTION
428: "Set by the operator to indicate the PSN type on which this
429: PW will be carried. Based on this object, the relevant PSN
430: table entries are created in the in the PSN specific MIB
431: modules. For example, if mpls(1) is defined, the agent
432: create an entry in pwVcMplsTable, which further define the
433: MPLS PSN configuration.
434: "
435: ::= { pwVcEntry 4 }
436:
437: pwVcSetUpPriority OBJECT-TYPE
438: SYNTAX Integer32 (0..7)
439: MAX-ACCESS read-create
440: STATUS current
441: DESCRIPTION
442: "This object define the relative set-up priority of the PW
443: in a lowest-to-highest fashion, where 0 is the highest
444: priority. PWs with the same priority are treated with
445: equal priority. Dropped VC will be set 'dormant' (as
446: indicated in pwVcOperStatus).
447: This value is significant if there are competing resources
448: between VCs and the implementation support this feature.
449: If not supported or not relevant, the value of zero MUST
450: be used."
451: DEFVAL
452: { 0 }
453: ::= { pwVcEntry 5 }
454:
455: pwVcHoldingPriority OBJECT-TYPE
456: SYNTAX Integer32 (0..7)
457: MAX-ACCESS read-create
458: STATUS current
459: DESCRIPTION
460: "This object define the relative holding priority of the PW
461: in a lowest-to-highest fashion, where 0 is the highest
462: priority. PWs with the same priority are treated with
463: equal priority. Dropped VC will be set 'dormant' (as
464: indicated in pwVcOperStatus).
465: This value is significant if there are competing resources
466: between PWs and the implementation support this feature.
467: If not supported or not relevant, the value of zero MUST
468: Pseudo Wire (PW) Management June 2004
469: Information Base
470:
471:
472: be used."
473: DEFVAL
474: { 0 }
475: ::= { pwVcEntry 6 }
476:
477:
478: pwVcPeerAddrType OBJECT-TYPE
479: SYNTAX InetAddressType
480: MAX-ACCESS read-create
481: STATUS current
482: DESCRIPTION
483: "Denotes the address type of the peer node. It should be
484: set to 'unknown' if PE/PW maintenance protocol is not used
485: and the address is unknown."
486: DEFVAL { ipv4 }
487: ::= { pwVcEntry 8 }
488:
489: pwVcPeerAddr OBJECT-TYPE
490: SYNTAX InetAddress
491: MAX-ACCESS read-create
492: STATUS current
493: DESCRIPTION
494: "This object contain the value of the peer node address
495: of the PW/PE maintenance protocol entity. This object
496: SHOULD contain a value of all zeroes if not applicable
497: (pwVcPeerAddrType is 'unknown')."
498: ::= { pwVcEntry 9 }
499:
500: pwVcAttachedPwIndex OBJECT-TYPE
501: SYNTAX PwVcIndexType
502: MAX-ACCESS read-create
503: STATUS current
504: DESCRIPTION
505: "If the PW is attached to another PW instead of a local
506: native service, this item indicates the pwVcIndex of the
507: attached PW, and the PW specific entry in the service MIB
508: module MUST not be created. Otherwise, this object MUST
509: be set to zero."
510: DEFVAL { 0 }
511: ::= { pwVcEntry 10 }
512:
513: pwVcIfIndex OBJECT-TYPE
514: SYNTAX InterfaceIndexOrZero
515: MAX-ACCESS read-create
516: STATUS current
517: DESCRIPTION
518: "If the PW is represented in the ifTable as an ifIndex, this
519: item holds the ifIndex of the PW in the ifTable, otherwise
520: it MUST be set to zero."
521: DEFVAL { 0 }
522: ::= { pwVcEntry 11 }
523: Pseudo Wire (PW) Management June 2004
524: Information Base
525:
526:
527:
528: pwVcID OBJECT-TYPE
529: SYNTAX PwVcIDType
530: MAX-ACCESS read-create
531: STATUS current
532: DESCRIPTION
533: "Used in the outgoing PW ID field within the 'Virtual
534: Circuit FEC Element'.
535: Applicable if pwVcOwner equal 'pwIdFecSignaling' or
536: 'l2tpControlProtocol', should be set to zero otherwise."
537: REFERENCE
538: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
539: ::= { pwVcEntry 12 }
540:
541: pwVcLocalGroupID OBJECT-TYPE
542: SYNTAX PwGroupID
543: MAX-ACCESS read-create
544: STATUS current
545: DESCRIPTION
546: "Used in the Group ID field sent to the peer PWES
547: within the maintenance protocol used for PW setup.
548: Applicable if pwVcOwner equal 'pwIdFecSignaling' or
549: 'l2tpControlProtocol', should be set to zero otherwise."
550: REFERENCE
551: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
552: ::= { pwVcEntry 13 }
553:
554: pwVcGroupAttachmentID OBJECT-TYPE
555: SYNTAX PwVcAttachmentIdentifierType
556: MAX-ACCESS read-create
557: STATUS current
558: DESCRIPTION
559: "This object is an octet string representing the attachment
560: group identifier (AGI) this PW belongs too, which typically
561: identifies the VPN ID.
562: Applicable if pwVcOwner equal 'genFecSignaling'. Should be
563: set to NULL (zero length) if not applicable."
564: REFERENCE
565: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
566: ::= { pwVcEntry 14 }
567:
568: pwVcLocalAttachmentID OBJECT-TYPE
569: SYNTAX PwVcAttachmentIdentifierType
570: MAX-ACCESS read-create
571: STATUS current
572: DESCRIPTION
573: "This object is an octet string representing the local
574: forwarder attachment individual identifier (AII) to be
575: used by this PW. It is used as the SAII for outgoing
576: signaling messages and the TAII in the incoming messages
577: from the peer.
578: Pseudo Wire (PW) Management June 2004
579: Information Base
580:
581:
582: Applicable if pwVcOwner equal 'genFecSignaling'. Should be
583: set to NULL (zero length) if not applicable. "
584: REFERENCE
585: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
586: ::= { pwVcEntry 15 }
587:
588: pwVcPeerAttachmentID OBJECT-TYPE
589: SYNTAX PwVcAttachmentIdentifierType
590: MAX-ACCESS read-create
591: STATUS current
592: DESCRIPTION
593: "This object is an octet string representing the peer
594: forwarder attachment individual identifier (AII) to be
595: used by this PW. It is used as the TAII for outgoing
596: signaling messages and the SAII in the incoming messages
597: from the peer.
598: Applicable if pwVcOwner equal 'genFecSignaling'. Should be
599: set to NULL (zero length) if not applicable. "
600: REFERENCE
601: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
602: ::= { pwVcEntry 16 }
603:
604: pwVcCwPreference OBJECT-TYPE
605: SYNTAX TruthValue
606: MAX-ACCESS read-create
607: STATUS current
608: DESCRIPTION
609: "Defines if the control word will be sent with each packet
610: by the local node. Some PW types mandate the use of
611: control word, and is such cases the value configured has
612: no effect on the existence of the control word."
613: REFERENCE
614: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
615: DEFVAL
616: { false }
617: ::= { pwVcEntry 17 }
618:
619: pwVcLocalIfMtu OBJECT-TYPE
620: SYNTAX Unsigned32 (0..65535)
621: MAX-ACCESS read-create
622: STATUS current
623: DESCRIPTION
624: "If not equal zero, the optional IfMtu object in the
625: signaling protocol will be sent with this value,
626: representing the locally supported MTU size over the
627: interface (or the virtual interface) associated with the
628: PW."
629: REFERENCE
630: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
631: DEFVAL
632: { 0 }
633: Pseudo Wire (PW) Management June 2004
634: Information Base
635:
636:
637: ::= { pwVcEntry 18 }
638:
639: pwVcLocalIfString OBJECT-TYPE
640: SYNTAX TruthValue
641: MAX-ACCESS read-create
642: STATUS current
643: DESCRIPTION
644: "Each PW is associated to an interface (or a virtual
645: interface) in the ifTable of the node as part of the
646: service configuration. This object defines if the
647: maintenance protocol will send the interface's name as
648: appears on the ifTable in the name object as part of the
649: maintenance protocol. If set to false, the optional
650: element will not be sent."
651: REFERENCE
652: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
653: DEFVAL
654: { false }
655: ::= { pwVcEntry 19 }
656:
657: pwVcLocalCapabAdvert OBJECT-TYPE
658: SYNTAX PwVcCapabilities
659: MAX-ACCESS read-create
660: STATUS current
661: DESCRIPTION
662: "Indicates the capabilities to be advertised by this node
663: to the peer."
664: REFERENCE
665: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
666: ::= { pwVcEntry 20 }
667:
668: pwVcRemoteGroupID OBJECT-TYPE
669: SYNTAX PwGroupID
670: MAX-ACCESS read-only
671: STATUS current
672: DESCRIPTION
673: "Obtained from the Group ID field as received via the
674: signaling protocol used for VC setup, zero if not used.
675: Value of 0xFFFF shall be used if the object is yet to be
676: defined by the PW maintenance protocol."
677: REFERENCE
678: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
679: ::= { pwVcEntry 21 }
680:
681: pwVcCwStatus OBJECT-TYPE
682: SYNTAX PwVcCwStatus
683: MAX-ACCESS read-only
684: STATUS current
685: DESCRIPTION
686: "If signaling is used for PW establishment, this object
687: indicates the status of the control word negotiation,
688: Pseudo Wire (PW) Management June 2004
689: Information Base
690:
691:
692: and in both signaling or manual configuration indicates
693: if CW is to be present or not for this PW.
694: "
695: REFERENCE
696: "Martini, et al, <draft-ietf-pwe3-control-protocol>.
697: "
698: ::= { pwVcEntry 22 }
699:
700: pwVcRemoteIfMtu OBJECT-TYPE
701: SYNTAX Unsigned32
702: MAX-ACCESS read-only
703: STATUS current
704: DESCRIPTION
705: "The remote interface MTU as (optionally) received from the
706: remote node via the maintenance protocol. Should be zero
707: if this parameter is not available or not used."
708: REFERENCE
709: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
710: ::= { pwVcEntry 23 }
711:
712: pwVcRemoteIfString OBJECT-TYPE
713: SYNTAX SnmpAdminString (SIZE (0..80))
714: MAX-ACCESS read-only
715: STATUS current
716: DESCRIPTION
717: "Indicates the interface description string as received by
718: the maintenance protocol, MUST be NULL string if not
719: applicable or not known yet."
720: REFERENCE
721: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
722: ::= { pwVcEntry 24 }
723:
724: pwVcRemoteCapabilities OBJECT-TYPE
725: SYNTAX PwVcCapabilities
726: MAX-ACCESS read-only
727: STATUS current
728: DESCRIPTION
729: "Indicates the capabilities as advertised by the peer."
730: REFERENCE
731: "Martini, et al, <draft-ietf-pwe3-control-protocol>."
732: ::= { pwVcEntry 25 }
733:
734: pwVcFragmentCfgSize OBJECT-TYPE
735: SYNTAX PwVcFragSize
736: MAX-ACCESS read-create
737: STATUS current
738: DESCRIPTION
739: "If set to value other than zero, indicates that
740: fragmentation is desired for this PW."
741: REFERENCE
742: "Malis A., Townsley M., 'PWE3 Fragmentation and Reassembly'
743: Pseudo Wire (PW) Management June 2004
744: Information Base
745:
746:
747: - work in progress"
748: DEFVAL
749: { 0 } -- I.e. fragmentation not desired
750: ::= { pwVcEntry 26 }
751:
752: pwVcRmtFragCapability OBJECT-TYPE
753: SYNTAX PwVcFragStatus
754: MAX-ACCESS read-only
755: STATUS current
756: DESCRIPTION
757: "The status of the fragmentation based on the local
758: configuration and the peer capabilities as advertised by
759: the peer if control protocol is used."
760: REFERENCE
761: "Malis A., Townsley M., 'PWE3 Fragmentation and Reassembly'
762: - work in progress"
763: ::= { pwVcEntry 27 }
764:
765: pwVcFcsRetentioncfg OBJECT-TYPE
766: SYNTAX INTEGER {
767: fcsRetentionDisable (1),
768: fcsRetentionEnable (2)
769: }
770: MAX-ACCESS read-create
771: STATUS current
772: DESCRIPTION
773: "The local configuration of FCS retention for this PW. FCS
774: retention can be configured for PW types HDLC, PPP and
775: Ethernet only. If the agent does not support FCS retention
776: the error should be configured in pwVcFcsRetentionStatus."
777: REFERENCE
778: "Malis A., et al., 'PWE3 Frame Check Sequence Retention'
779: - work in progress"
780: DEFVAL { fcsRetentionDisable }
781: ::= { pwVcEntry 28 }
782:
783: pwVcFcsRetentionStatus OBJECT-TYPE
784: SYNTAX BITS {
785: remoteIndicationUnknown (0),
786: remoteRequestFcsRetention (1),
787: fcsRetentionEnabled (2),
788: fcsRetentionDisabled (3),
789: localFcsRetentionCfgErr (4),
790: fcsRetentionFcsSizeMismatch (5)
791: }
792: MAX-ACCESS read-only
793: STATUS current
794: DESCRIPTION
795: "The status of the FCS retention negotiation process based on
796: local configuration and the remote advertisement.
797: remoteIndicationUnknown - set if a FEC has not been received
798: Pseudo Wire (PW) Management June 2004
799: Information Base
800:
801:
802: from the remote.
803: remoteRequestFcsRetention - indicates that the peer has
804: requested for FCS retention. FCS retention will be used if
805: the local node is capable and configured to use it for this
806: PW.
807: fcsRetentionEnabled - FCS retention is enabled (both peers
808: were configured for FCS retention for signaled PW, or the
809: local node is configured and capable for FCS retention.
810: fcsRetentionDisabled - FCS retention is disabled (not
811: configured locally or not advertised by the peer).
812: localFcsRetentionCfgErr - Set if the local node has been
813: configured for FCS retention but is not capable to support
814: it.
815: fcsRetentionFcsSizeMismatch - Set if there is a FCS size
816: mismatch between the loacl and the peer node.
817: "
818: REFERENCE
819: "Malis A., et al., 'PWE3 Frame Check Sequence Retention'
820: - work in progress"
821: ::= { pwVcEntry 29 }
822:
823: pwVcOutboundVcLabel OBJECT-TYPE
824: SYNTAX Unsigned32
825: MAX-ACCESS read-create
826: STATUS current
827: DESCRIPTION
828: "The PW label used in the outbound direction (i.e. toward
829: the PSN). It may be set up manually if owner is 'manual'
830: or automatically otherwise. Examples: For MPLS PSN, it
831: represents the 20 bits of PW tag, for L2TP it represent
832: the 32 bits Session ID.
833: If the label is not yet known (signaling in process), the
834: object should return a value of 0xFFFF."
835: ::= { pwVcEntry 30 }
836:
837: pwVcInboundVcLabel OBJECT-TYPE
838: SYNTAX Unsigned32
839: MAX-ACCESS read-create
840: STATUS current
841: DESCRIPTION
842: "The PW label used in the inbound direction (i.e. packets
843: received from the PSN. It may be set up manually if owner
844: is 'manual' or automatically otherwise.
845: Examples: For MPLS PSN, it represents the 20 bits of PW
846: tag, for L2TP it represent the 32 bits Session ID.
847: If the label is not yet known (signaling in process), the
848: object should return a value of 0xFFFF."
849: ::= { pwVcEntry 31 }
850:
851: pwVcName OBJECT-TYPE
852: SYNTAX SnmpAdminString
853: Pseudo Wire (PW) Management June 2004
854: Information Base
855:
856:
857: MAX-ACCESS read-create
858: STATUS current
859: DESCRIPTION
860: "The canonical name assigned to the PW."
861: ::= { pwVcEntry 32 }
862:
863: pwVcDescr OBJECT-TYPE
864: SYNTAX SnmpAdminString
865: MAX-ACCESS read-create
866: STATUS current
867: DESCRIPTION
868: "A textual string containing information about the PW.
869: If there is no description this object contains a zero
870: length string."
871: ::= { pwVcEntry 33 }
872:
873: pwVcCreateTime OBJECT-TYPE
874: SYNTAX TimeStamp
875: MAX-ACCESS read-only
876: STATUS current
877: DESCRIPTION
878: "System time when this PW was created."
879: ::= { pwVcEntry 34 }
880:
881: pwVcUpTime OBJECT-TYPE
882: SYNTAX TimeTicks
883: MAX-ACCESS read-only
884: STATUS current
885: DESCRIPTION
886: "Specifies the total time this PW operStatus has been
887: Up(1)."
888: ::= { pwVcEntry 35 }
889:
890: pwVcLastChange OBJECT-TYPE
891: SYNTAX TimeTicks
892: MAX-ACCESS read-only
893: STATUS current
894: DESCRIPTION
895: "The value of sysUpTime at the time the PW entered
896: its current operational state. If the current state was
897: entered prior to the last re-initialization of the local
898: network management subsystem, then this object contains a
899: zero value."
900: ::= { pwVcEntry 36 }
901:
902: pwVcAdminStatus OBJECT-TYPE
903: SYNTAX INTEGER {
904: up(1), -- ready to pass packets
905: down(2),
906: testing(3) -- in some test mode
907: }
908: Pseudo Wire (PW) Management June 2004
909: Information Base
910:
911:
912: MAX-ACCESS read-create
913: STATUS current
914: DESCRIPTION
915: "The desired operational status of this PW."
916: ::= { pwVcEntry 37 }
917:
918: pwVcOperStatus OBJECT-TYPE
919: SYNTAX PwOperStatus
920: MAX-ACCESS read-only
921: STATUS current
922: DESCRIPTION
923: "This object indicates the operational status of the PW, it
924: does not reflect however the status of the CE bound
925: interface.
926: It is set to down only if pwNotForwarding,
927: psnFacingPwRxFault, or psnFacingPwTxFault indications are
928: set in pwVcLocalStatus or pwVcRemoteStatus.
929: It indicates 'lowerLayerDown' if the only reason for
930: not being in the 'up' state is either outer tunnel
931: or physical layer down of the network side is in the down
932: state.
933: All other states are declared base on the description in
934: the textual convention.
935: "
936: ::= { pwVcEntry 38 }
937:
938: pwVcLocalStatus OBJECT-TYPE
939: SYNTAX PwVcStatus
940: MAX-ACCESS read-only
941: STATUS current
942: DESCRIPTION
943: "Indicates the status of the PW in the local node.
944: The various indications in this object should be
945: available independent of the ability of the local node to
946: advertise them or the remote node to accept these status
947: indications through the control protocol.
948: "
949: ::= { pwVcEntry 39 }
950:
951: pwVcRemoteStatusCapable OBJECT-TYPE
952: SYNTAX INTEGER {
953: notApplicable (1),
954: notYetKnown (2),
955: remoteCapable (3),
956: remoteNotCapable (4)
957:
958: }
959: MAX-ACCESS read-only
960: STATUS current
961: DESCRIPTION
962: "Indicates the remote node capability to advertise the
963: Pseudo Wire (PW) Management June 2004
964: Information Base
965:
966:
967: PW status notification.
968: notAppicable should be reported for manually set PW, or
969: if the local node is not capable of sending the status
970: notification object.
971: notYetKnown should be reported if the signaling protocol
972: has not yet finished the process of capability
973: determination.
974: remoteCapable and remoteNotcapable should be reported
975: based on the initial signaling exchange that has
976: determined the remote node capability.
977: "
978: ::= { pwVcEntry 40 }
979:
980: pwVcRemoteStatus OBJECT-TYPE
981: SYNTAX PwVcStatus
982: MAX-ACCESS read-only
983: STATUS current
984: DESCRIPTION
985: "Indicates the status of the PW as was advertised by the
986: remote. If the remote is not capable of advertising the
987: status object, or the local node is not able to accept
988: the status object through signaling, then the applicable
989: bit is 'pwNotForwarding' which is set if the remote has
990: sent label release or label withdraw for this PW.
991: "
992: ::= { pwVcEntry 41 }
993:
994: pwVcTimeElapsed OBJECT-TYPE
995: SYNTAX HCPerfTimeElapsed
996: MAX-ACCESS read-only
997: STATUS current
998: DESCRIPTION
999: "The number of seconds, including partial seconds,
1000: that have elapsed since the beginning of the current
1001: interval measurement period."
1002: ::= { pwVcEntry 42 }
1003:
1004: pwVcValidIntervals OBJECT-TYPE
1005: SYNTAX HCPerfValidIntervals
1006: MAX-ACCESS read-only
1007: STATUS current
1008: DESCRIPTION
1009: "The number of previous 15-minute intervals
1010: for which data was collected."
1011: ::= { pwVcEntry 43 }
1012:
1013: pwVcRowStatus OBJECT-TYPE
1014: SYNTAX RowStatus
1015: MAX-ACCESS read-create
1016: STATUS current
1017: DESCRIPTION
1018: Pseudo Wire (PW) Management June 2004
1019: Information Base
1020:
1021:
1022: "For creating, modifying, and deleting this row. None of the
1023: read-create objects in the conceptual rows may be changed
1024: when this object is in the active(1) state."
1025: ::= { pwVcEntry 44 }
1026:
1027: pwVcStorageType OBJECT-TYPE
1028: SYNTAX StorageType
1029: MAX-ACCESS read-create
1030: STATUS current
1031: DESCRIPTION
1032: "This variable indicates the storage type for this
1033: object."
1034: ::= { pwVcEntry 45 }
1035:
1036: -- End of PW Virtual Connection Table
1037:
1038: -- PW Performance Table.
1039:
1040: pwVcPerfCurrentTable OBJECT-TYPE
1041: SYNTAX SEQUENCE OF PwVcPerfCurrentEntry
1042: MAX-ACCESS not-accessible
1043: STATUS current
1044: DESCRIPTION
1045: "This table provides per-PW performance information for
1046: the current interval."
1047: ::= { pwVcObjects 3 }
1048:
1049: pwVcPerfCurrentEntry OBJECT-TYPE
1050: SYNTAX PwVcPerfCurrentEntry
1051: MAX-ACCESS not-accessible
1052: STATUS current
1053: DESCRIPTION
1054: "An entry in this table is created by the agent for
1055: every PW."
1056: INDEX { pwVcIndex }
1057: ::= { pwVcPerfCurrentTable 1 }
1058:
1059: PwVcPerfCurrentEntry ::= SEQUENCE {
1060: pwVcPerfCurrentInHCPackets HCPerfCurrentCount,
1061: pwVcPerfCurrentInHCBytes HCPerfCurrentCount,
1062: pwVcPerfCurrentOutHCPackets HCPerfCurrentCount,
1063: pwVcPerfCurrentOutHCBytes HCPerfCurrentCount,
1064: pwVcPerfCurrentInPackets PerfCurrentCount,
1065: pwVcPerfCurrentInBytes PerfCurrentCount,
1066: pwVcPerfCurrentOutPackets PerfCurrentCount,
1067: pwVcPerfCurrentOutBytes PerfCurrentCount
1068: }
1069:
1070: pwVcPerfCurrentInHCPackets OBJECT-TYPE
1071: SYNTAX HCPerfCurrentCount
1072: MAX-ACCESS read-only
1073: Pseudo Wire (PW) Management June 2004
1074: Information Base
1075:
1076:
1077: STATUS current
1078: DESCRIPTION
1079: "High capacity counter for number of packets received by
1080: the PW (from the PSN) in the current 15-minute interval.
1081: This is the 64 bit version of pwVcPerfCurrentInPackets,
1082: if pwVcPerfCurrentInHCPackets is supported according to
1083: the rules spelled out in RFC2863."
1084: ::= { pwVcPerfCurrentEntry 1 }
1085:
1086: pwVcPerfCurrentInHCBytes OBJECT-TYPE
1087: SYNTAX HCPerfCurrentCount
1088: MAX-ACCESS read-only
1089: STATUS current
1090: DESCRIPTION
1091: "High capacity counter for number of bytes received by the
1092: PW (from the PSN) in the current 15-minute interval.
1093: This is the 64 bit version of pwVcPerfCurrentInBytes, if
1094: pwVcPerfCurrentInHCBytes is supported according to the
1095: rules spelled out in RFC2863."
1096: ::= { pwVcPerfCurrentEntry 2 }
1097:
1098: pwVcPerfCurrentOutHCPackets OBJECT-TYPE
1099: SYNTAX HCPerfCurrentCount
1100: MAX-ACCESS read-only
1101: STATUS current
1102: DESCRIPTION
1103: "High capacity counter for number of packets forwarded by
1104: the PW (to the PSN) in the current 15-minute interval.
1105: This is the 64 bit version of pwVcPerfCurrentOutPackets,
1106: if pwVcPerfCurrentOutHCPackets is supported according to
1107: the rules spelled out in RFC2863."
1108: ::= { pwVcPerfCurrentEntry 3 }
1109:
1110: pwVcPerfCurrentOutHCBytes OBJECT-TYPE
1111: SYNTAX HCPerfCurrentCount
1112: MAX-ACCESS read-only
1113: STATUS current
1114: DESCRIPTION
1115: "High capacity counter for number of bytes forwarded by
1116: the PW (to the PSN) in the current 15-minute interval.
1117: This is the 64 bit version of pwVcPerfCurrentOutBytes,
1118: if pwVcPerfCurrentOutHCBytes is supported according to
1119: the rules spelled out in RFC2863."
1120: ::= { pwVcPerfCurrentEntry 4 }
1121:
1122: pwVcPerfCurrentInPackets OBJECT-TYPE
1123: SYNTAX PerfCurrentCount
1124: MAX-ACCESS read-only
1125: STATUS current
1126: DESCRIPTION
1127: "The counter for number of packets received by the PW (from
1128: Pseudo Wire (PW) Management June 2004
1129: Information Base
1130:
1131:
1132: the PSN) in the current 15-minute interval.
1133: This is the 32 bit version of pwVcPerfCurrentInHCPackets,
1134: if pwVcPerfCurrentInHCPackets is supported according to
1135: the rules spelled out in RFC2863."
1136: ::= { pwVcPerfCurrentEntry 5 }
1137:
1138: pwVcPerfCurrentInBytes OBJECT-TYPE
1139: SYNTAX PerfCurrentCount
1140: MAX-ACCESS read-only
1141: STATUS current
1142: DESCRIPTION
1143: "The counter for number of bytes received by the
1144: PW (from the PSN) in the current 15-minute interval.
1145: It MUST be equal to the least significant 32 bits of
1146: pwVcPerfCurrentInHCBytes, if pwVcPerfCurrentInHCBytes is
1147: supported according to the rules spelled out in RFC2863."
1148: ::= { pwVcPerfCurrentEntry 6 }
1149:
1150: pwVcPerfCurrentOutPackets OBJECT-TYPE
1151: SYNTAX PerfCurrentCount
1152: MAX-ACCESS read-only
1153: STATUS current
1154: DESCRIPTION
1155: "The counter for number of packets forwarded by
1156: the PW (to the PSN) in the current 15-minute interval.
1157: It MUST be equal to the least significant 32 bits of
1158: pwVcPerfCurrentOutHCPackets, if
1159: pwVcPerfCurrentOutHCPackets is supported according to the
1160: rules spelled out in RFC2863."
1161: ::= { pwVcPerfCurrentEntry 7 }
1162:
1163: pwVcPerfCurrentOutBytes OBJECT-TYPE
1164: SYNTAX PerfCurrentCount
1165: MAX-ACCESS read-only
1166: STATUS current
1167: DESCRIPTION
1168: "The counter for number of bytes forwarded by
1169: the PW (to the PSN) in the current 15-minute interval.
1170: It MUST be equal to the least significant 32 bits of
1171: pwVcPerfCurrentOutHCBytes, if pwVcPerfCurrentOutHCBytes is
1172: supported according to the rules spelled out in RFC2863."
1173: ::= { pwVcPerfCurrentEntry 8 }
1174:
1175: -- End of PW Perf current Table
1176:
1177: -- PW Performance Interval Table.
1178:
1179: pwVcPerfIntervalTable OBJECT-TYPE
1180: SYNTAX SEQUENCE OF PwVcPerfIntervalEntry
1181: MAX-ACCESS not-accessible
1182: STATUS current
1183: Pseudo Wire (PW) Management June 2004
1184: Information Base
1185:
1186:
1187: DESCRIPTION
1188: "This table provides per-PW performance information for
1189: each interval."
1190: ::= { pwVcObjects 4 }
1191:
1192: pwVcPerfIntervalEntry OBJECT-TYPE
1193: SYNTAX PwVcPerfIntervalEntry
1194: MAX-ACCESS not-accessible
1195: STATUS current
1196: DESCRIPTION
1197: "An entry in this table is created agent for every PW."
1198: INDEX { pwVcIndex, pwVcPerfIntervalNumber }
1199: ::= { pwVcPerfIntervalTable 1 }
1200:
1201: PwVcPerfIntervalEntry ::= SEQUENCE {
1202: pwVcPerfIntervalNumber Integer32,
1203: pwVcPerfIntervalValidData TruthValue,
1204: pwVcPerfIntervalTimeElapsed HCPerfTimeElapsed,
1205: pwVcPerfIntervalInHCPackets HCPerfIntervalCount,
1206: pwVcPerfIntervalInHCBytes HCPerfIntervalCount,
1207: pwVcPerfIntervalOutHCPackets HCPerfIntervalCount,
1208: pwVcPerfIntervalOutHCBytes HCPerfIntervalCount,
1209: pwVcPerfIntervalInPackets PerfIntervalCount,
1210: pwVcPerfIntervalInBytes PerfIntervalCount,
1211: pwVcPerfIntervalOutPackets PerfIntervalCount,
1212: pwVcPerfIntervalOutBytes PerfIntervalCount
1213: }
1214:
1215: pwVcPerfIntervalNumber OBJECT-TYPE
1216: SYNTAX Integer32 (1..96)
1217: MAX-ACCESS not-accessible
1218: STATUS current
1219: DESCRIPTION
1220: "A number N, between 1 and 96, which identifies the
1221: interval for which the set of statistics is available.
1222: The interval identified by 1 is the most recently
1223: completed 15 minute interval, and the interval identified
1224: by N is the interval immediately preceding the one
1225: identified by N-1.
1226: The minimum range of N is 1 through 4. The default range
1227: is 1 to 32. The maximum range of N is 1 through 96. "
1228: REFERENCE
1229: "Tesink, K. 'Definitions of Managed Objects for the
1230: SONET/SDH Interface Type', RFC 2558"
1231: ::= { pwVcPerfIntervalEntry 1 }
1232:
1233: pwVcPerfIntervalValidData OBJECT-TYPE
1234: SYNTAX TruthValue
1235: MAX-ACCESS read-only
1236: STATUS current
1237: DESCRIPTION
1238: Pseudo Wire (PW) Management June 2004
1239: Information Base
1240:
1241:
1242: "This variable indicates if the data for this interval
1243: is valid."
1244: ::= { pwVcPerfIntervalEntry 2 }
1245:
1246: pwVcPerfIntervalTimeElapsed OBJECT-TYPE
1247: SYNTAX HCPerfTimeElapsed
1248: MAX-ACCESS read-only
1249: STATUS current
1250: DESCRIPTION
1251: "The duration of this interval in seconds."
1252: ::= { pwVcPerfIntervalEntry 3 }
1253:
1254: pwVcPerfIntervalInHCPackets OBJECT-TYPE
1255: SYNTAX HCPerfIntervalCount
1256: MAX-ACCESS read-only
1257: STATUS current
1258: DESCRIPTION
1259: "High capacity counter for number of packets received by
1260: the PW (from the PSN) during the interval. This is the 64
1261: bit version of pwVcPerfIntervalInPackets, if
1262: pwVcPerfIntervalInHCPackets is supported according to the
1263: rules spelled out in RFC2863."
1264: ::= { pwVcPerfIntervalEntry 4 }
1265:
1266: pwVcPerfIntervalInHCBytes OBJECT-TYPE
1267: SYNTAX HCPerfIntervalCount
1268: MAX-ACCESS read-only
1269: STATUS current
1270: DESCRIPTION
1271: "High capacity counter for number of bytes received by the
1272: PW (from the PSN) during the interval.
1273: This is the 64 bit version of pwVcPerfIntervalInBytes, if
1274: pwVcPerfIntervalInHCBytes is supported according to the
1275: rules spelled out in RFC2863."
1276: ::= { pwVcPerfIntervalEntry 5 }
1277:
1278: pwVcPerfIntervalOutHCPackets OBJECT-TYPE
1279: SYNTAX HCPerfIntervalCount
1280: MAX-ACCESS read-only
1281: STATUS current
1282: DESCRIPTION
1283: "High capacity counter for number of packets forwarded by
1284: the PW (to the PSN) during the interval.
1285: This is the 64 bit version of pwVcPerfIntervalOutPackets,
1286: if pwVcPerfIntervalOutHCPackets is supported according to
1287: the rules spelled out in RFC2863."
1288: ::= { pwVcPerfIntervalEntry 6 }
1289:
1290: pwVcPerfIntervalOutHCBytes OBJECT-TYPE
1291: SYNTAX HCPerfIntervalCount
1292: MAX-ACCESS read-only
1293: Pseudo Wire (PW) Management June 2004
1294: Information Base
1295:
1296:
1297: STATUS current
1298: DESCRIPTION
1299: "High capacity counter for number of bytes forwarded by
1300: the PW (to the PSN) during the interval.
1301: This is the 64 bit version of pwVcPerfIntervalOutBytes,
1302: if pwVcPerfIntervalOutHCBytes is supported according to
1303: the rules spelled out in RFC2863."
1304: ::= { pwVcPerfIntervalEntry 7 }
1305:
1306: pwVcPerfIntervalInPackets OBJECT-TYPE
1307: SYNTAX PerfIntervalCount
1308: MAX-ACCESS read-only
1309: STATUS current
1310: DESCRIPTION
1311: "This value represents the number of packets received
1312: by this PW during the interval.
1313: It MUST be equal to the least significant 32 bits of
1314: pwVcPerfIntervalInHCPackets if pwVcPerfIntervalInHCPackets
1315: is supported according to the rules spelled out in
1316: RFC2863."
1317: ::= { pwVcPerfIntervalEntry 8 }
1318:
1319: pwVcPerfIntervalInBytes OBJECT-TYPE
1320: SYNTAX PerfIntervalCount
1321: MAX-ACCESS read-only
1322: STATUS current
1323: DESCRIPTION
1324: "This value represents the number of bytes received
1325: by this PW during the interval.
1326: It MUST be equal to the least significant 32 bits of
1327: if pwVcPerfIntervalInHCBytes is supported according to
1328: the rules spelled out in RFC2863."
1329: ::= { pwVcPerfIntervalEntry 9 }
1330:
1331: pwVcPerfIntervalOutPackets OBJECT-TYPE
1332: SYNTAX PerfIntervalCount
1333: MAX-ACCESS read-only
1334: STATUS current
1335: DESCRIPTION
1336: "This value represents the number of packets sent by this
1337: PW during the interval.
1338: It MUST be equal to the least significant 32 bits of
1339: pwVcPerfIntervalOutHCPackets if
1340: pwVcPerfIntervalOutHCPackets is supported according to the
1341: rules spelled out in RFC2863."
1342: ::= { pwVcPerfIntervalEntry 10 }
1343:
1344: pwVcPerfIntervalOutBytes OBJECT-TYPE
1345: SYNTAX PerfIntervalCount
1346: MAX-ACCESS read-only
1347: STATUS current
1348: Pseudo Wire (PW) Management June 2004
1349: Information Base
1350:
1351:
1352: DESCRIPTION
1353: "This value represents the number of bytes sent by this
1354: PW during the interval.
1355: It MUST be equal to the least significant 32
1356: bits of pwVcPerfIntervalOutHCBytes
1357: if pwVcPerfIntervalOutHCBytes is supported according to
1358: the rules spelled out in RFC2863."
1359: ::= { pwVcPerfIntervalEntry 11 }
1360:
1361: -- End of PW Performance Interval Table
1362:
1363: -- PW Performance Total Table.
1364:
1365: pwVcPerfTotalTable OBJECT-TYPE
1366: SYNTAX SEQUENCE OF PwVcPerfTotalEntry
1367: MAX-ACCESS not-accessible
1368: STATUS current
1369: DESCRIPTION
1370: "This table provides per-PW Performance information from
1371: PW start time or management application reset."
1372: ::= { pwVcObjects 5 }
1373:
1374: pwVcPerfTotalEntry OBJECT-TYPE
1375: SYNTAX PwVcPerfTotalEntry
1376: MAX-ACCESS not-accessible
1377: STATUS current
1378: DESCRIPTION
1379: "An entry in this table is created by the agent for every
1380: PW.
1381:
1382: pwVcPerfTotalDiscontinuityTime indicates the time of the
1383: last discontinuity in any of these objects."
1384:
1385: INDEX { pwVcIndex }
1386: ::= { pwVcPerfTotalTable 1 }
1387:
1388: PwVcPerfTotalEntry ::= SEQUENCE {
1389: pwVcPerfTotalInHCPackets Counter64,
1390: pwVcPerfTotalInHCBytes Counter64,
1391: pwVcPerfTotalOutHCPackets Counter64,
1392: pwVcPerfTotalOutHCBytes Counter64,
1393: pwVcPerfTotalInPackets Counter32,
1394: pwVcPerfTotalInBytes Counter32,
1395: pwVcPerfTotalOutPackets Counter32,
1396: pwVcPerfTotalOutBytes Counter32,
1397: pwVcPerfTotalDiscontinuityTime TimeStamp
1398: }
1399:
1400: pwVcPerfTotalInHCPackets OBJECT-TYPE
1401: SYNTAX Counter64
1402: MAX-ACCESS read-only
1403: Pseudo Wire (PW) Management June 2004
1404: Information Base
1405:
1406:
1407: STATUS current
1408: DESCRIPTION
1409: "High capacity counter for the total number of packets
1410: received by the PW (from the PSN).
1411: This is the 64 bit version of pwVcPerfTotalInPackets, if
1412: pwVcPerfTotalInHCPackets is supported according to the
1413: rules spelled out in RFC2863."
1414: ::= { pwVcPerfTotalEntry 1 }
1415:
1416: pwVcPerfTotalInHCBytes OBJECT-TYPE
1417: SYNTAX Counter64
1418: MAX-ACCESS read-only
1419: STATUS current
1420: DESCRIPTION
1421: "High capacity counter for the total number of bytes
1422: received by the PW (from the PSN).
1423: This is the 64 bit version of pwVcPerfTotalInBytes, if
1424: pwVcPerfTotalInHCBytes is supported according to the
1425: rules spelled out in RFC2863."
1426: ::= { pwVcPerfTotalEntry 2 }
1427:
1428: pwVcPerfTotalOutHCPackets OBJECT-TYPE
1429: SYNTAX Counter64
1430: MAX-ACCESS read-only
1431: STATUS current
1432: DESCRIPTION
1433: "High capacity counter for the total number of packets
1434: forwarded by the PW (to the PSN).
1435: This is the 64 bit version of pwVcPerfTotalOutPackets,
1436: if pwVcPerfTotalOutHCPackets is supported according to
1437: the rules spelled out in RFC2863."
1438: ::= { pwVcPerfTotalEntry 3 }
1439:
1440: pwVcPerfTotalOutHCBytes OBJECT-TYPE
1441: SYNTAX Counter64
1442: MAX-ACCESS read-only
1443: STATUS current
1444: DESCRIPTION
1445: "High capacity counter for the total number of bytes
1446: forwarded by the PW (to the PSN).
1447: This is the 64 bit version of pwVcPerfTotalOutBytes,
1448: if pwVcPerfTotalOutHCBytes is supported according to
1449: the rules spelled out in RFC2863."
1450: ::= { pwVcPerfTotalEntry 4 }
1451:
1452: pwVcPerfTotalInPackets OBJECT-TYPE
1453: SYNTAX Counter32
1454: MAX-ACCESS read-only
1455: STATUS current
1456: DESCRIPTION
1457: "This value represents the total number of packets received
1458: Pseudo Wire (PW) Management June 2004
1459: Information Base
1460:
1461:
1462: by this PW.
1463: It MUST be equal to the least significant 32 bits of
1464: pwVcPerfTotalInHCPackets if pwVcPerfTotalInHCPackets
1465: is supported according to the rules spelled out in
1466: RFC2863."
1467: ::= { pwVcPerfTotalEntry 5 }
1468:
1469: pwVcPerfTotalInBytes OBJECT-TYPE
1470: SYNTAX Counter32
1471: MAX-ACCESS read-only
1472: STATUS current
1473: DESCRIPTION
1474: "This value represents the total number of bytes received
1475: by this PW.
1476: It MUST be equal to the least significant 32 bits of
1477: if pwVcPerfTotalInHCBytes is supported according to
1478: the rules spelled out in RFC2863."
1479: ::= { pwVcPerfTotalEntry 6 }
1480:
1481: pwVcPerfTotalOutPackets OBJECT-TYPE
1482: SYNTAX Counter32
1483: MAX-ACCESS read-only
1484: STATUS current
1485: DESCRIPTION
1486: "This value represents the total number of packets sent by
1487: this PW.
1488: It MUST be equal to the least significant 32 bits of
1489: pwVcPerfTotalOutHCPackets if pwVcPerfTotalOutHCPackets
1490: is supported according to the rules spelled out in
1491: RFC2863."
1492: ::= { pwVcPerfTotalEntry 7 }
1493:
1494: pwVcPerfTotalOutBytes OBJECT-TYPE
1495: SYNTAX Counter32
1496: MAX-ACCESS read-only
1497: STATUS current
1498: DESCRIPTION
1499: "This value represents the total number of bytes sent by
1500: this PW.
1501: It MUST be equal to the least significant 32
1502: bits of pwVcPerfTotalOutHCBytes
1503: if pwVcPerfTotalOutHCBytes is supported according to
1504: the rules spelled out in RFC2863."
1505: ::= { pwVcPerfTotalEntry 8 }
1506:
1507: pwVcPerfTotalDiscontinuityTime OBJECT-TYPE
1508: SYNTAX TimeStamp
1509: MAX-ACCESS read-only
1510: STATUS current
1511: DESCRIPTION
1512: "The value of sysUpTime on the most recent occasion at
1513: Pseudo Wire (PW) Management June 2004
1514: Information Base
1515:
1516:
1517: which any one or more of this row Counter32 or
1518: Counter64 suffered a discontinuity. If no such
1519: discontinuities have occurred since the last re-
1520: initialization of the local management subsystem, then
1521: this object contains a zero value."
1522: ::= { pwVcPerfTotalEntry 9 }
1523:
1524: -- End of PW Perf Total Table
1525:
1526: -- Error counter scalar
1527:
1528: pwVcPerfTotalErrorPackets OBJECT-TYPE
1529: SYNTAX Counter32
1530: MAX-ACCESS read-only
1531: STATUS current
1532: DESCRIPTION
1533: "Counter for number of error at the PW processing level,
1534: for example packets received with unknown PW label."
1535: ::= { pwVcObjects 6 }
1536:
1537: -- Reverse mapping tables
1538:
1539: -- The PW ID mapping table
1540: pwVcIndexMappingTable OBJECT-TYPE
1541: SYNTAX SEQUENCE OF PwVcIndexMappingEntry
1542: MAX-ACCESS not-accessible
1543: STATUS current
1544: DESCRIPTION
1545: "This table enables the reverse mapping the unique PWid
1546: parameters <peer IP, PW type and PW ID> and the
1547: pwVcIndex. The table is not applicable for PW created
1548: manually or by using the generalized FEC."
1549: ::= { pwVcObjects 7 }
1550:
1551: pwVcIndexMappingEntry OBJECT-TYPE
1552: SYNTAX PwVcIndexMappingEntry
1553: MAX-ACCESS not-accessible
1554: STATUS current
1555: DESCRIPTION
1556: "An entry in this table MUST be created by the agent for
1557: every PW created by the pwVcTable for which pwVcOwner
1558: equals æpwIdFecSignalingÆ."
1559:
1560: INDEX { pwVcIndexMappingVcType, pwVcIndexMappingVcID,
1561: pwVcIndexMappingPeerAddrType, pwVcIndexMappingPeerAddr
1562: }
1563: ::= { pwVcIndexMappingTable 1 }
1564:
1565: PwVcIndexMappingEntry ::= SEQUENCE {
1566: pwVcIndexMappingVcType PwVcType,
1567: pwVcIndexMappingVcID PwVcIDType,
1568: Pseudo Wire (PW) Management June 2004
1569: Information Base
1570:
1571:
1572: pwVcIndexMappingPeerAddrType InetAddressType,
1573: pwVcIndexMappingPeerAddr InetAddress,
1574: pwVcIndexMappingVcIndex PwVcIndexType
1575: }
1576:
1577: pwVcIndexMappingVcType OBJECT-TYPE
1578: SYNTAX PwVcType
1579: MAX-ACCESS not-accessible
1580: STATUS current
1581: DESCRIPTION
1582: "The PW type (indicates the service) of this PW."
1583: ::= { pwVcIndexMappingEntry 1 }
1584:
1585: pwVcIndexMappingVcID OBJECT-TYPE
1586: SYNTAX PwVcIDType
1587: MAX-ACCESS not-accessible
1588: STATUS current
1589: DESCRIPTION
1590: "The PW ID of this PW. Zero if the PW is configured
1591: manually."
1592: ::= { pwVcIndexMappingEntry 2 }
1593:
1594: pwVcIndexMappingPeerAddrType OBJECT-TYPE
1595: SYNTAX InetAddressType
1596: MAX-ACCESS not-accessible
1597: STATUS current
1598: DESCRIPTION
1599: "IP address type of the peer node."
1600: ::= { pwVcIndexMappingEntry 3 }
1601:
1602: pwVcIndexMappingPeerAddr OBJECT-TYPE
1603: SYNTAX InetAddress
1604: MAX-ACCESS not-accessible
1605: STATUS current
1606: DESCRIPTION
1607: "IP address type of the peer node."
1608: ::= { pwVcIndexMappingEntry 4 }
1609:
1610: pwVcIndexMappingVcIndex OBJECT-TYPE
1611: SYNTAX PwVcIndexType
1612: MAX-ACCESS read-only
1613: STATUS current
1614: DESCRIPTION
1615: "The value that represents the PW in the pwVcTable."
1616: ::= { pwVcIndexMappingEntry 5 }
1617:
1618: -- End of the PW ID mapping table
1619:
1620: -- The peer mapping table
1621:
1622: pwVcPeerMappingTable OBJECT-TYPE
1623: Pseudo Wire (PW) Management June 2004
1624: Information Base
1625:
1626:
1627: SYNTAX SEQUENCE OF PwVcPeerMappingEntry
1628: MAX-ACCESS not-accessible
1629: STATUS current
1630: DESCRIPTION
1631: "This table provides reverse mapping of the existing PW
1632: based on PW type and PW ID ordering. This table is
1633: typically useful for EMS ordered query of existing PWs."
1634: ::= { pwVcObjects 8 }
1635:
1636: pwVcPeerMappingEntry OBJECT-TYPE
1637: SYNTAX PwVcPeerMappingEntry
1638: MAX-ACCESS not-accessible
1639: STATUS current
1640: DESCRIPTION
1641: "An entry in this table is created by the agent for every
1642: PW configured in pwVcTable."
1643:
1644: INDEX { pwVcPeerMappingPeerAddrType, pwVcPeerMappingPeerAddr,
1645: pwVcPeerMappingVcType, pwVcPeerMappingVcID }
1646:
1647: ::= { pwVcPeerMappingTable 1 }
1648:
1649: PwVcPeerMappingEntry ::= SEQUENCE {
1650: pwVcPeerMappingPeerAddrType InetAddressType,
1651: pwVcPeerMappingPeerAddr InetAddress,
1652: pwVcPeerMappingVcType PwVcType,
1653: pwVcPeerMappingVcID PwVcIDType,
1654: pwVcPeerMappingVcIndex PwVcIndexType
1655: }
1656:
1657: pwVcPeerMappingPeerAddrType OBJECT-TYPE
1658: SYNTAX InetAddressType
1659: MAX-ACCESS not-accessible
1660: STATUS current
1661: DESCRIPTION
1662: "IP address type of the peer node."
1663: ::= { pwVcPeerMappingEntry 1 }
1664:
1665: pwVcPeerMappingPeerAddr OBJECT-TYPE
1666: SYNTAX InetAddress
1667: MAX-ACCESS not-accessible
1668: STATUS current
1669: DESCRIPTION
1670: "IP address type of the peer node."
1671: ::= { pwVcPeerMappingEntry 2 }
1672:
1673: pwVcPeerMappingVcType OBJECT-TYPE
1674: SYNTAX PwVcType
1675: MAX-ACCESS not-accessible
1676: STATUS current
1677: DESCRIPTION
1678: Pseudo Wire (PW) Management June 2004
1679: Information Base
1680:
1681:
1682: "The PW type (indicates the service) of this PW."
1683: ::= { pwVcPeerMappingEntry 3 }
1684:
1685: pwVcPeerMappingVcID OBJECT-TYPE
1686: SYNTAX PwVcIDType
1687: MAX-ACCESS not-accessible
1688: STATUS current
1689: DESCRIPTION
1690: "The PW ID of this PW. Zero if the PW is configured
1691: manually."
1692: ::= { pwVcPeerMappingEntry 4 }
1693:
1694: pwVcPeerMappingVcIndex OBJECT-TYPE
1695: SYNTAX PwVcIndexType
1696: MAX-ACCESS read-only
1697: STATUS current
1698: DESCRIPTION
1699: "The value that represents the PW in the pwVcTable."
1700: ::= { pwVcPeerMappingEntry 5 }
1701:
1702: -- End of the peer mapping table
1703:
1704: -- End of reverse mapping tables
1705:
1706: pwVcUpDownNotifEnable OBJECT-TYPE
1707: SYNTAX TruthValue
1708: MAX-ACCESS read-write
1709: STATUS current
1710: DESCRIPTION
1711: "If this object is set to true(1), then it enables
1712: the emission of pwVcUp and pwVcDown
1713: notifications; otherwise these notifications are not
1714: emitted."
1715: REFERENCE
1716: "See also RFC3413 for explanation that
1717: notifications are under the ultimate control of the
1718: MIB module in this document."
1719: DEFVAL { false }
1720: ::= { pwVcObjects 9 }
1721:
1722: pwVcDeletedNotifEnable OBJECT-TYPE
1723: SYNTAX TruthValue
1724: MAX-ACCESS read-write
1725: STATUS current
1726: DESCRIPTION
1727: "If this object is set to true(1), then it enables the
1728: emission of pwVcDeleted notification; otherwise this
1729: notification is not emitted."
1730: REFERENCE
1731: "See also RFC3413 for explanation that
1732: notifications are under the ultimate control of the
1733: Pseudo Wire (PW) Management June 2004
1734: Information Base
1735:
1736:
1737: MIB module in this document."
1738: DEFVAL { false }
1739: ::= { pwVcObjects 10 }
1740:
1741: pwVcNotifRate OBJECT-TYPE
1742: SYNTAX Unsigned32
1743: MAX-ACCESS read-write
1744: STATUS current
1745: DESCRIPTION
1746: "This object defines the maximum number of PW notifications
1747: that can be emitted from the device per second."
1748: ::= { pwVcObjects 11 }
1749:
1750: -- Notifications - PW
1751:
1752: pwVcDown NOTIFICATION-TYPE
1753: OBJECTS { pwVcOperStatus, --start of range
1754: pwVcOperStatus --end of range
1755: }
1756: STATUS current
1757: DESCRIPTION
1758: "This notification is generated when the
1759: pwVcOperStatus object for one or more contiguous
1760: entries in pwVcTable are about to enter the
1761: down(2) state from some other state. The included values
1762: of pwVcOperStatus MUST all be set equal to this
1763: down(2) state. The two instances of pwVcOperStatus
1764: in this notification indicate the range of indexes
1765: that are affected. Note that all the indexes of the
1766: two ends of the range can be derived from the
1767: instance identifiers of these two objects. For
1768: cases where a contiguous range of cross-connects
1769: have transitioned into the down(2) state at roughly
1770: the same time, the device SHOULD issue a single
1771: notification for each range of contiguous indexes in
1772: an effort to minimize the emission of a large number
1773: of notifications. If a notification has to be
1774: issued for just a single cross-connect entry, then
1775: the instance identifier (and values) of the two
1776: pwVcOperStatus objects MUST be identical."
1777: ::= { pwVcNotifications 1 }
1778:
1779: pwVcUp NOTIFICATION-TYPE
1780: OBJECTS { pwVcOperStatus, --start of range
1781: pwVcOperStatus --end of range
1782: }
1783: STATUS current
1784: DESCRIPTION
1785: "This notification is generated when the
1786: pwVcOperStatus object for one or more contiguous
1787: entries in pwVcTable are about to enter the up(1)
1788: Pseudo Wire (PW) Management June 2004
1789: Information Base
1790:
1791:
1792: state from some other state. The included values of
1793: pwVcOperStatus MUST both be set equal to this
1794: new state (i.e: up(1)). The two instances of
1795: pwVcOperStatus in this notification indicate the range
1796: of indexes that are affected. Note that all the indexes
1797: of the two ends of the range can be derived from the
1798: instance identifiers of these two objects. For
1799: cases where a contiguous range of cross-connects
1800: have transitioned into the up(1) state at roughly
1801: the same time, the device SHOULD issue a single
1802: notification for each range of contiguous indexes in
1803: an effort to minimize the emission of a large number
1804: of notifications. If a notification has to be
1805: issued for just a single cross-connect entry, then
1806: the instance identifier (and values) of the two
1807: pwVcOperStatus objects MUST be the identical."
1808: ::= { pwVcNotifications 2 }
1809:
1810: pwVcDeleted NOTIFICATION-TYPE
1811: OBJECTS { pwVcType,
1812: pwVcID,
1813: pwVcPeerAddrType,
1814: pwVcPeerAddr
1815: }
1816: STATUS current
1817: DESCRIPTION
1818: "This notification is generated when the PW has been
1819: deleted, i.e. when the pwVcRowStatus has been set to
1820: destroy(6), the PW has been deleted by a non-MIB
1821: application or due to auto discovery process.
1822: "
1823: ::= { pwVcNotifications 3 }
1824:
1825: -- End of notifications.
1826:
1827: -- conformance information
1828:
1829: pwVcGroups OBJECT IDENTIFIER ::= { pwVcConformance 1 }
1830: pwVcCompliances OBJECT IDENTIFIER ::= { pwVcConformance 2 }
1831:
1832:
1833: -- Compliance requirement for fully compliant implementations.
1834:
1835: pwVcModuleFullCompliance MODULE-COMPLIANCE
1836: STATUS current
1837: DESCRIPTION
1838: "The compliance statement for agents that provide full
1839: support for PW MIB Module. Such devices can
1840: then be monitored and also be configured using
1841: this MIB module."
1842: Pseudo Wire (PW) Management June 2004
1843: Information Base
1844:
1845:
1846: MODULE -- this module
1847: MANDATORY-GROUPS { pwVcBasicGroup,
1848: pwVcPerformanceGeneralGroup,
1849: pwVcPeformanceTotalGroup }
1850:
1851: GROUP pwVcPwIdGroup
1852: DESCRIPTION "This group is only mandatory for implementations
1853: that support the PW ID FEC.
1854: "
1855:
1856: GROUP pwVcGeneralizedFecGroup
1857: DESCRIPTION "This group is only mandatory for implementations
1858: that support the generalized PW FEC.
1859: "
1860:
1861: GROUP pwVcFcsGroup
1862: DESCRIPTION "This group is only mandatory for implementations
1863: that support FCS retention."
1864:
1865: GROUP pwVcFragGroup
1866: DESCRIPTION "This group is only mandatory for implementations
1867: that support PW fragmentation.
1868: "
1869:
1870: GROUP pwVcPwStatusGroup
1871: DESCRIPTION "This group is only mandatory for implementations
1872: that support PW status notification.
1873: "
1874:
1875: GROUP pwVcGetNextGroup
1876: DESCRIPTION "This group is only mandatory for implementations
1877: where the pwVcIndex may be any arbitrary value
1878: and the EMS would require retrieval of the next
1879: free index."
1880:
1881: GROUP pwVcPriorityGroup
1882: DESCRIPTION "This group is only mandatory for implementations
1883: that support the controlling the PW setup and
1884: holding priority."
1885:
1886: GROUP pwVcAttachmentGroup
1887: DESCRIPTION "This group is only mandatory for implementations
1888: that support attachment of two PWs (PW stitching)."
1889:
1890: GROUP pwVcHCPeformanceTotalGroup
1891: DESCRIPTION "This group is only mandatory for implementations
1892: where at least one of the total performance
1893: counters wraps around too quickly based on the
1894: criteria specified in RFC 2863 for high-capacity
1895: counters."
1896: Pseudo Wire (PW) Management June 2004
1897: Information Base
1898:
1899:
1900: GROUP pwVcPerformanceIntervalGeneralGroup
1901: DESCRIPTION "This group is only mandatory for implementations
1902: that support PW performance gathering in 15
1903: minutes intervals."
1904:
1905: GROUP pwVcPeformanceIntervalGroup
1906: DESCRIPTION "This group is only mandatory for implementations
1907: that support PW performance gathering in 15
1908: minutes intervals."
1909:
1910: GROUP pwVcHCPeformanceIntervalGroup
1911: DESCRIPTION "This group is only mandatory for implementations
1912: where at least one of the interval performance
1913: counters wraps around too quickly based on the
1914: criteria specified in RFC 2863 for high-capacity
1915: counters."
1916:
1917: GROUP pwVcMappingTablesGroup
1918: DESCRIPTION "This group is only mandatory for implementations
1919: that support reverse mapping of PW indexes to
1920: the pwVcIndex and the peer mapping table."
1921:
1922: GROUP pwVcNotificationControlGroup
1923: DESCRIPTION "This group is only mandatory for implementations
1924: that support the PW notifications."
1925:
1926: OBJECT pwVcAdminStatus
1927: SYNTAX INTEGER { up(1), down(2) }
1928: DESCRIPTION "The support of the value testing(3) is not
1929: required."
1930:
1931: OBJECT pwVcOperStatus
1932: SYNTAX INTEGER { up(1), down(2), notPresent(6),
1933: lowerLayerDown(7) }
1934: DESCRIPTION "The support of the values testing(3), unknown(4),
1935: and dormant(5) is not required."
1936:
1937: OBJECT pwVcRowStatus
1938: SYNTAX RowStatus { active(1), notInService(2),
1939: notReady(3) }
1940: WRITE-SYNTAX RowStatus { active(1), notInService(2),
1941: createAndGo(4), destroy(6)
1942: }
1943: DESCRIPTION "Support for createAndWait is not required. Support
1944: of notReady is not required for implementations
1945: that do not support signaling, or if it is
1946: guaranteed that the conceptual row has all the
1947: required information to create the PW when the
1948: row has been created by the agent."
1949: Pseudo Wire (PW) Management June 2004
1950: Information Base
1951:
1952:
1953: OBJECT pwVcPeerAddrType
1954: SYNTAX InetAddressType { unknown(0), ipv4(1) }
1955: DESCRIPTION "Only unknown(0) and ipv4(1) is required."
1956:
1957: OBJECT pwVcPeerAddr
1958: SYNTAX InetAddress (SIZE(0|4))
1959: DESCRIPTION "An implementation is only required to support
1960: 0, 4 address sizes."
1961:
1962:
1963: ::= { pwVcCompliances 1 }
1964:
1965: -- Compliance requirement for read only compliant implementations.
1966:
1967: pwVcModuleReadOnlyCompliance MODULE-COMPLIANCE
1968: STATUS current
1969: DESCRIPTION
1970: "The compliance statement for agents that provide read
1971: only support for PW MIB Module. Such devices can
1972: then be monitored but cannot be configured using this
1973: MIB module."
1974:
1975: MODULE -- this module
1976: MANDATORY-GROUPS { pwVcBasicGroup,
1977: pwVcPeformanceTotalGroup }
1978:
1979: GROUP pwVcPwIdGroup
1980: DESCRIPTION "This group is only mandatory for implementations
1981: that support the PW ID FEC.
1982: "
1983:
1984: GROUP pwVcGeneralizedFecGroup
1985: DESCRIPTION "This group is only mandatory for implementations
1986: that support the generalized PW FEC.
1987: "
1988:
1989: GROUP pwVcFcsGroup
1990: DESCRIPTION "This group is only mandatory for implementations
1991: that support FCS retention."
1992:
1993: GROUP pwVcFragGroup
1994: DESCRIPTION "This group is only mandatory for implementations
1995: that support PW fragmentation.
1996: "
1997:
1998: GROUP pwVcPwStatusGroup
1999: DESCRIPTION "This group is only mandatory for implementations
2000: that support PW status notification.
2001: "
2002:
2003: GROUP pwVcGetNextGroup
2004: Pseudo Wire (PW) Management June 2004
2005: Information Base
2006:
2007:
2008: DESCRIPTION "This group is only mandatory for implementations
2009: where the pwVcIndex may be any arbitary value
2010: and the EMS would require retrieval of the next
2011: free index."
2012:
2013: GROUP pwVcPriorityGroup
2014: DESCRIPTION "This group is only mandatory for implementations
2015: that support the controling the PW setup and
2016: holding priority."
2017:
2018: GROUP pwVcAttachmentGroup
2019: DESCRIPTION "This group is only mandatory for implementations
2020: that support attachment of two PWs (PW stitching)."
2021:
2022: GROUP pwVcHCPeformanceTotalGroup
2023: DESCRIPTION "This group is only mandatory for implementations
2024: where at least one of the total performance
2025: counters wraps around too quickly based on the
2026: criteria specified in RFC 2863 for high-capacity
2027: counters."
2028:
2029: GROUP pwVcPerformanceIntervalGeneralGroup
2030: DESCRIPTION "This group is only mandatory for implementations
2031: that support PW performance gathering in 15
2032: minutes intervals."
2033:
2034: GROUP pwVcPeformanceIntervalGroup
2035: DESCRIPTION "This group is only mandatory for implementations
2036: that support PW performance gathering in 15
2037: minutes intervals."
2038:
2039: GROUP pwVcHCPeformanceIntervalGroup
2040: DESCRIPTION "This group is only mandatory for implementations
2041: where at least one of the interval performance
2042: counters wraps around too quickly based on the
2043: criteria specified in RFC 2863 for high-capacity
2044: counters."
2045:
2046: GROUP pwVcMappingTablesGroup
2047: DESCRIPTION "This group is only mandatory for implementations
2048: that support reverse mapping of PW indexes to
2049: the pwVcIndex and the peer mapping table."
2050:
2051: GROUP pwVcNotificationControlGroup
2052: DESCRIPTION "This group is only mandatory for implementations
2053: that support the PW notifications."
2054:
2055: OBJECT pwVcType
2056: MIN-ACCESS read-only
2057: DESCRIPTION "Write access is not required."
2058: Pseudo Wire (PW) Management June 2004
2059: Information Base
2060:
2061:
2062: OBJECT pwVcOwner
2063: MIN-ACCESS read-only
2064: DESCRIPTION "Write access is not required."
2065:
2066: OBJECT pwVcPsnType
2067: MIN-ACCESS read-only
2068: DESCRIPTION "Write access is not required."
2069:
2070: OBJECT pwVcSetUpPriority
2071: MIN-ACCESS read-only
2072: DESCRIPTION "Write access is not required."
2073:
2074: OBJECT pwVcHoldingPriority
2075: MIN-ACCESS read-only
2076: DESCRIPTION "Write access is not required."
2077:
2078: OBJECT pwVcPeerAddrType
2079: SYNTAX InetAddressType { unknown(0), ipv4(1) }
2080: MIN-ACCESS read-only
2081: DESCRIPTION "Write access is not required. Only unknown(0) and
2082: ipv4(1) is required."
2083:
2084: OBJECT pwVcPeerAddr
2085: SYNTAX InetAddress (SIZE(0|4))
2086: MIN-ACCESS read-only
2087: DESCRIPTION "Write access is not required. An implementation
2088: is only required to support 0, 4 address sizes."
2089:
2090: OBJECT pwVcAttachedPwIndex
2091: MIN-ACCESS read-only
2092: DESCRIPTION "Write access is not required."
2093:
2094: OBJECT pwVcIfIndex
2095: MIN-ACCESS read-only
2096: DESCRIPTION "Write access is not required."
2097:
2098: OBJECT pwVcID
2099: MIN-ACCESS read-only
2100: DESCRIPTION "Write access is not required."
2101:
2102: OBJECT pwVcLocalGroupID
2103: MIN-ACCESS read-only
2104: DESCRIPTION "Write access is not required."
2105:
2106: OBJECT pwVcGroupAttachmentID
2107: MIN-ACCESS read-only
2108: DESCRIPTION "Write access is not required."
2109:
2110: OBJECT pwVcLocalAttachmentID
2111: MIN-ACCESS read-only
2112: DESCRIPTION "Write access is not required."
2113: Pseudo Wire (PW) Management June 2004
2114: Information Base
2115:
2116:
2117:
2118: OBJECT pwVcPeerAttachmentID
2119: MIN-ACCESS read-only
2120: DESCRIPTION "Write access is not required."
2121:
2122: OBJECT pwVcCwPreference
2123: MIN-ACCESS read-only
2124: DESCRIPTION "Write access is not required."
2125:
2126: OBJECT pwVcLocalIfMtu
2127: MIN-ACCESS read-only
2128: DESCRIPTION "Write access is not required."
2129:
2130: OBJECT pwVcLocalIfString
2131: MIN-ACCESS read-only
2132: DESCRIPTION "Write access is not required."
2133:
2134: OBJECT pwVcLocalCapabAdvert
2135: MIN-ACCESS read-only
2136: DESCRIPTION "Write access is not required."
2137:
2138: OBJECT pwVcFragmentCfgSize
2139: MIN-ACCESS read-only
2140: DESCRIPTION "Write access is not required."
2141:
2142: OBJECT pwVcFcsRetentioncfg
2143: MIN-ACCESS read-only
2144: DESCRIPTION "Write access is not required."
2145:
2146: OBJECT pwVcOutboundVcLabel
2147: MIN-ACCESS read-only
2148: DESCRIPTION "Write access is not required."
2149:
2150: OBJECT pwVcInboundVcLabel
2151: MIN-ACCESS read-only
2152: DESCRIPTION "Write access is not required."
2153:
2154: OBJECT pwVcName
2155: MIN-ACCESS read-only
2156: DESCRIPTION "Write access is not required."
2157:
2158: OBJECT pwVcDescr
2159: MIN-ACCESS read-only
2160: DESCRIPTION "Write access is not required."
2161:
2162: OBJECT pwVcAdminStatus
2163: SYNTAX INTEGER { up(1), down(2) }
2164: MIN-ACCESS read-only
2165: DESCRIPTION "Write access is not required. The support of value
2166: testing(3) is not required."
2167: Pseudo Wire (PW) Management June 2004
2168: Information Base
2169:
2170:
2171: OBJECT pwVcOperStatus
2172: SYNTAX INTEGER { up(1), down(2), notPresent(6),
2173: lowerLayerDown(7) }
2174: DESCRIPTION "The support of the values testing(3), unknown(4),
2175: and is not required."
2176:
2177: OBJECT pwVcRowStatus
2178: SYNTAX RowStatus { active(1) }
2179: MIN-ACCESS read-only
2180: DESCRIPTION "Write access is not required."
2181:
2182:
2183: OBJECT pwVcStorageType
2184: MIN-ACCESS read-only
2185: DESCRIPTION "Write access is not required."
2186:
2187: OBJECT pwVcUpDownNotifEnable
2188: MIN-ACCESS read-only
2189: DESCRIPTION "Write access is not required."
2190:
2191: OBJECT pwVcDeletedNotifEnable
2192: MIN-ACCESS read-only
2193: DESCRIPTION "Write access is not required."
2194:
2195: OBJECT pwVcNotifRate
2196: MIN-ACCESS read-only
2197: DESCRIPTION "Write access is not required."
2198:
2199: ::= { pwVcCompliances 2 }
2200:
2201: -- Units of conformance.
2202:
2203: pwVcBasicGroup OBJECT-GROUP
2204: OBJECTS {
2205: pwVcType,
2206: pwVcOwner,
2207: pwVcPsnType,
2208: pwVcPeerAddrType,
2209: pwVcPeerAddr,
2210: pwVcIfIndex,
2211: pwVcID,
2212: pwVcLocalGroupID,
2213: pwVcCwPreference,
2214: pwVcLocalIfMtu,
2215: pwVcLocalIfString,
2216: pwVcLocalCapabAdvert,
2217: pwVcRemoteGroupID,
2218: pwVcCwStatus,
2219: pwVcRemoteIfMtu,
2220: pwVcRemoteIfString,
2221: pwVcOutboundVcLabel,
2222: Pseudo Wire (PW) Management June 2004
2223: Information Base
2224:
2225:
2226: pwVcInboundVcLabel,
2227: pwVcName,
2228: pwVcDescr,
2229: pwVcCreateTime,
2230: pwVcUpTime,
2231: pwVcLastChange,
2232: pwVcAdminStatus,
2233: pwVcOperStatus,
2234: pwVcLocalStatus,
2235: pwVcRowStatus,
2236: pwVcStorageType
2237: }
2238:
2239: STATUS current
2240: DESCRIPTION
2241: "Collection of objects that are required in all
2242: implementations that support the PW MIB module."
2243: ::= { pwVcGroups 1 }
2244:
2245: pwVcPwIdGroup OBJECT-GROUP
2246: OBJECTS {
2247: pwVcID
2248: }
2249:
2250: STATUS current
2251: DESCRIPTION
2252: "Collection of objects required for PW ID configuration
2253: and signaling."
2254: ::= { pwVcGroups 2 }
2255:
2256: pwVcGeneralizedFecGroup OBJECT-GROUP
2257: OBJECTS {
2258: pwVcGroupAttachmentID,
2259: pwVcLocalAttachmentID,
2260: pwVcPeerAttachmentID
2261: }
2262:
2263: STATUS current
2264: DESCRIPTION
2265: "Collection of objects required for generalized FEC
2266: configuration and signaling."
2267: ::= { pwVcGroups 3 }
2268:
2269: pwVcFcsGroup OBJECT-GROUP
2270: OBJECTS {
2271: pwVcFcsRetentioncfg,
2272: pwVcFcsRetentionStatus
2273: }
2274:
2275: STATUS current
2276: DESCRIPTION
2277: Pseudo Wire (PW) Management June 2004
2278: Information Base
2279:
2280:
2281: "Collection of objects required for FCS retention
2282: configuration and signaling."
2283: ::= { pwVcGroups 4 }
2284:
2285: pwVcFragGroup OBJECT-GROUP
2286: OBJECTS {
2287: pwVcFragmentCfgSize,
2288: pwVcRmtFragCapability
2289: }
2290:
2291: STATUS current
2292: DESCRIPTION
2293: "Collection of objects required for fragmentation
2294: configuration and signaling."
2295: ::= { pwVcGroups 5 }
2296:
2297: pwVcPwStatusGroup OBJECT-GROUP
2298: OBJECTS {
2299: pwVcRemoteCapabilities,
2300: pwVcRemoteStatusCapable,
2301: pwVcRemoteStatus
2302: }
2303:
2304: STATUS current
2305: DESCRIPTION
2306: "Collection of objects required for PW status configuration
2307: and signaling."
2308: ::= { pwVcGroups 6 }
2309:
2310: pwVcGetNextGroup OBJECT-GROUP
2311: OBJECTS {
2312: pwVcIndexNext
2313: }
2314:
2315: STATUS current
2316: DESCRIPTION
2317: "Collection of objects for getting the next available
2318: index."
2319: ::= { pwVcGroups 7 }
2320:
2321: pwVcPriorityGroup OBJECT-GROUP
2322: OBJECTS {
2323: pwVcSetUpPriority,
2324: pwVcHoldingPriority
2325: }
2326:
2327: STATUS current
2328: DESCRIPTION
2329: "Collection of objects for controlling the PW setup and
2330: holding priority."
2331: ::= { pwVcGroups 8 }
2332: Pseudo Wire (PW) Management June 2004
2333: Information Base
2334:
2335:
2336:
2337: pwVcAttachmentGroup OBJECT-GROUP
2338: OBJECTS {
2339: pwVcAttachedPwIndex
2340: }
2341:
2342: STATUS current
2343: DESCRIPTION
2344: "Collection of objects for PW configuration
2345: and signaling."
2346: ::= { pwVcGroups 9 }
2347:
2348: pwVcPerformanceGeneralGroup OBJECT-GROUP
2349: OBJECTS {
2350: pwVcPerfTotalDiscontinuityTime,
2351: pwVcPerfTotalErrorPackets
2352: }
2353:
2354: STATUS current
2355: DESCRIPTION
2356: "Collection of general objects needed for managing the
2357: total running performance parameters."
2358: ::= { pwVcGroups 10 }
2359:
2360: pwVcPeformanceTotalGroup OBJECT-GROUP
2361: OBJECTS {
2362: pwVcPerfTotalInPackets,
2363: pwVcPerfTotalInBytes,
2364: pwVcPerfTotalOutPackets,
2365: pwVcPerfTotalOutBytes
2366: }
2367:
2368: STATUS current
2369: DESCRIPTION
2370: "Collection of 32 bits objects needed for PW running total
2371: performance collection."
2372: ::= { pwVcGroups 11 }
2373:
2374: pwVcHCPeformanceTotalGroup OBJECT-GROUP
2375: OBJECTS {
2376: pwVcPerfTotalInHCPackets,
2377: pwVcPerfTotalInHCBytes,
2378: pwVcPerfTotalOutHCPackets,
2379: pwVcPerfTotalOutHCBytes
2380: }
2381:
2382: STATUS current
2383: DESCRIPTION
2384: "Collection of HC objects needed for PW running total
2385: performance collection."
2386: ::= { pwVcGroups 12 }
2387: Pseudo Wire (PW) Management June 2004
2388: Information Base
2389:
2390:
2391:
2392: pwVcPerformanceIntervalGeneralGroup OBJECT-GROUP
2393: OBJECTS {
2394: pwVcTimeElapsed,
2395: pwVcValidIntervals,
2396: pwVcPerfIntervalValidData,
2397: pwVcPerfIntervalTimeElapsed
2398: }
2399:
2400: STATUS current
2401: DESCRIPTION
2402: "Collection of general objects needed for managing the
2403: interval performance parameters."
2404: ::= { pwVcGroups 13 }
2405:
2406: pwVcPeformanceIntervalGroup OBJECT-GROUP
2407: OBJECTS {
2408: pwVcPerfCurrentInPackets,
2409: pwVcPerfCurrentInBytes,
2410: pwVcPerfCurrentOutPackets,
2411: pwVcPerfCurrentOutBytes,
2412:
2413: pwVcPerfIntervalInPackets,
2414: pwVcPerfIntervalInBytes,
2415: pwVcPerfIntervalOutPackets,
2416: pwVcPerfIntervalOutBytes
2417: }
2418:
2419: STATUS current
2420: DESCRIPTION
2421: "Collection of 32 bits objects needed for PW performance
2422: collection in 15 minutes intervals."
2423: ::= { pwVcGroups 14 }
2424:
2425: pwVcHCPeformanceIntervalGroup OBJECT-GROUP
2426: OBJECTS {
2427: pwVcPerfCurrentInHCPackets,
2428: pwVcPerfCurrentInHCBytes,
2429: pwVcPerfCurrentOutHCPackets,
2430: pwVcPerfCurrentOutHCBytes,
2431:
2432: pwVcPerfIntervalInHCPackets,
2433: pwVcPerfIntervalInHCBytes,
2434: pwVcPerfIntervalOutHCPackets,
2435: pwVcPerfIntervalOutHCBytes
2436: }
2437:
2438: STATUS current
2439: DESCRIPTION
2440: "Collection of HC objects needed for PW performance
2441: collection in 15 minutes intervals."
2442: Pseudo Wire (PW) Management June 2004
2443: Information Base
2444:
2445:
2446: ::= { pwVcGroups 15 }
2447:
2448: pwVcMappingTablesGroup OBJECT-GROUP
2449: OBJECTS {
2450: pwVcIndexMappingVcIndex,
2451: pwVcPeerMappingVcIndex
2452: }
2453:
2454: STATUS current
2455: DESCRIPTION
2456: "Collection of objects contained in the reverse
2457: mapping tables."
2458: ::= { pwVcGroups 16 }
2459:
2460: pwVcNotificationControlGroup OBJECT-GROUP
2461: OBJECTS {
2462: pwVcUpDownNotifEnable,
2463: pwVcDeletedNotifEnable,
2464: pwVcNotifRate
2465: }
2466:
2467: STATUS current
2468: DESCRIPTION
2469: "Collection of objects for controlling the PW
2470: notifications."
2471: ::= { pwVcGroups 17 }
2472:
2473: pwVcNotificationGroup NOTIFICATION-GROUP
2474: NOTIFICATIONS {
2475: pwVcUp,
2476: pwVcDown,
2477: pwVcDeleted
2478: }
2479:
2480: STATUS current
2481: DESCRIPTION
2482: "Collection PW notifications objects."
2483: ::= { pwVcGroups 18 }
2484:
2485: -- END of PW MIB module
2486:
2487: END
2488:
2489: --
2490: -- Copyright (C) The Internet Society (2000). All Rights Reserved.
2491: -- This document and translations of it may be copied and furnished
2492: -- to others, and derivative works that comment on or otherwise
2493: -- explain it or assist in its implementation may be prepared,
2494: -- copied, published and distributed, in whole or in part, without
2495: -- restriction of any kind, provided that the above copyright notice
2496: -- and this paragraph are included on all such copies and derivative
2497: -- Information Base
2498: --
2499: --
2500: -- works. However, this document itself may not be modified in any
2501: -- way, such as by removing the copyright notice or references to the
2502: -- Internet Society or other Internet organizations, except as needed
2503: -- for the purpose of developing Internet standards in which case the
2504: -- procedures for copyrights defined in the Internet Standards
2505: -- process must be followed, or as required to translate it into
2506: -- languages other than English.
2507: -- The limited permissions granted above are perpetual and will not
2508: -- be revoked by the Internet Society or its successors or assigns.
2509: -- This document and the information contained herein is provided on
2510: -- an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
2511: -- ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
2512: -- IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
2513: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
2514: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2515: --
2516: -- 13 Intellectual Property Notice
2517: --
2518: -- The IETF takes no position regarding the validity or scope of any
2519: -- intellectual property or other rights that might be claimed to
2520: -- pertain to the implementation or use of the technology described
2521: -- in this document or the extent to which any license under such
2522: -- rights might or might not be available; neither does it represent
2523: -- that it has made any effort to identify any such rights.
2524: -- Information on the IETF's procedures with respect to rights in
2525: -- standards-track and standards-related documentation can be found
2526: -- in BCP-11 [RFC2028].
2527: -- Copies of claims of rights made available for publication and any
2528: -- assurances of licenses to be made available, or the result of an
2529: -- attempt made to obtain a general license or permission for the use
2530: -- of such proprietary rights by implementors or users of this
2531: -- specification can be obtained from the IETF Secretariat.
2532: -- The IETF invites any interested party to bring to its attention
2533: -- any copyrights, patents or patent applications, or other
2534: -- proprietary rights that may cover technology that may be required
2535: -- to practice this standard. Please address the information to the
2536: -- IETF Executive Director.
2537: