smilint output for ./PW-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 25 |
| error | 10 |
| minor error | 18 |
| warning | 25 |
| fyi | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 9 |
| identifier-external-case-match (warning) | 1 |
| internal-flushing (warning) | 24 |
| internal-other (severe) | 25 |
| object-identifier-not-prefix (error) | 1 |
| previous-definition (fyi) | 1 |
| revision-after-update (minor error) | 1 |
| scalar-not-creatable (minor error) | 17 |
Messages:
/home/fenner/mibindex/latest2/PW-TC-MIB
1: -- extracted from draft-ietf-pwe3-pw-tc-mib-02.txt
2: -- at Thu Oct 23 06:15:14 2003
3:
4: PW-TC-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, Unsigned32, Integer32, experimental
8: FROM SNMPv2-SMI
9:
10: TEXTUAL-CONVENTION, TruthValue
11: FROM SNMPv2-TC;
12:
13: pwTCMIB MODULE-IDENTITY
14: LAST-UPDATED "200307281200Z" -- 28 July 2003 12:00:00 GMT
15: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
16: Group"
17: CONTACT-INFO
18: " Thomas D. Nadeau
19: Postal: Cisco Systems, Inc.
20: 250 Apollo Drive
21: Chelmsford, MA 01824
22: Tel: +1-978-497-3051
23: Email: tnadeau@cisco.com
24:
25: Dave Danenberg
26: Postal: Litchfield Communications, Inc.
27: 76 Westbury Park Rd
28: Princeton Building East
29: Watertown, CT 06795
30: Tel: +1-860-945-1573 x3180
31: Email: dave_danenberg@litchfieldcomm.com
32:
33: David Zelig
34: Postal: Corrigent Systems.
35: 126, Yigal Alon St.
36: Tel Aviv, ISRAEL
37: Phone: +972-3-6945273
38: E-mail: davidz@corrigent.com
39:
40: Andrew G. Malis
41: Postal: Tellabs, Inc.
42: 2730 Orchard Parkway
43: San Jose, CA 95134
44: Email: Andy.Malis@tellabs.com
45:
46: PWE3 Working Group Mailing List: pwe3@ietf.org"
47:
48: DESCRIPTION
49: "This MIB Module provides Textual Conventions
50: and OBJECT-IDENTITY Objects to be used PW services."
51:
52: -- Revision history.
53:
54: REVISION "200307281200Z" -- 28 July 2003 12:00:00 GMT
55: DESCRIPTION "Adding objects to cover new control draft.
56: Adapt VC types for current values in WG documents."
57:
58: REVISION "200305011200Z" -- 1 May 2003 12:00:00 GMT
59: DESCRIPTION "Adding PwVcAttachmentIdentifierType,
60: Adapt VC types for current values in WG documents."
61:
62: REVISION "0205281200Z" -- 28 May 2002 12:00:00 GMT
63: DESCRIPTION "Adding PwVcType, and enhance some descriptions."
64:
65: REVISION "0201301200Z" -- 30 January 2002 12:00:00 GMT
66: DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and
67: PwOperStatus."
68:
69: REVISION "200112201200Z" -- 20 Dec 2001 12:00:00 GMT
70: DESCRIPTION "Remove PwVcInstance"
71:
72: REVISION "200107121200Z" -- 12 July 2001 12:00:00 GMT
73: DESCRIPTION "Initial version."
74:
75: ::= { pwMIB 1 } -- pwMIB To Be Assigned by IANA
76:
77: pwMIB OBJECT IDENTIFIER
78: ::= { experimental 8888 } -- To be assigned by IANA
79:
80: -- Textual Conventions defined below are organized alphabetically
81:
82: PwGroupID ::= TEXTUAL-CONVENTION
83: STATUS current
84: DESCRIPTION
85: "An administrative identification mechanism for grouping a
86: set of service-specific pseudo-wire services. May only
87: have local significance."
88: SYNTAX Unsigned32
89:
90: PwVcIDType ::= TEXTUAL-CONVENTION
91: STATUS current
92: DESCRIPTION
93: "Virtual Circuit Identifier. Used to identify the VC
94: (together with some other fields) in the signaling
95: session. Zero if the VC is set-up manually."
96: SYNTAX Unsigned32
97:
98: PwVcIndexType ::= TEXTUAL-CONVENTION
99: STATUS current
100: DESCRIPTION
101: "Virtual Circuit Index. Locally unique index for indexing
102: several MIB tables associated with a particular VC."
103: SYNTAX Unsigned32
104:
105: PwVcVlanCfg ::= TEXTUAL-CONVENTION
106: STATUS current
107: DESCRIPTION
108: "VLAN configuration for Ethernet PW.
109: Values between 0 to 4095 indicate the actual VLAN field
110: value.
111: A value of 4096 indicates that the object refer to
112: untagged frames, i.e. frames without 802.1Q field.
113: A value of 4097 indicates that the object is not
114: relevant."
115: SYNTAX Integer32 (0..4097)
116:
117: PwOperStatus ::= TEXTUAL-CONVENTION
118: STATUS current
119: DESCRIPTION
120: "Indicate the operational status of the PW VC.
121:
122: - up: Ready to pass packets.
123: - down: If PW signaling has not yet finished, or
124: indications available at the service
125: level indicate that the VC is not
126: passing packets.
127: - testing: If AdminStatus at the PW level is set to
128: test.
129: - dormant: The PW is not available because of the
130: required resources are occupied PW with
131: higher priority PWs .
132: - notPresent: Some component is missing to accomplish
133: the set up of the PW.
134: - lowerLayerDown: The underlying PSN or outer tunnel is not
135: in OperStatus 'up'.
136: "
137: SYNTAX INTEGER {
138: up(1),
139: down(2),
140: testing(3),
141: unknown(4),
142: dormant(5),
143: notPresent(6),
144: lowerLayerDown(7)
145: }
146:
147: PwVcType ::= TEXTUAL-CONVENTION
147: fyi -
info: previous definition of `PwVcType'
148: STATUS current
149: DESCRIPTION
150: "Indicate the VC type (i.e. the carried service).
151: Note: the exact set of VC types is yet to be worked
152: out by the WG.
153: "
154: SYNTAX INTEGER {
155: other(0),
156: frameRelayDlci(1),
157: atmAal5SduVcc(2),
158: atmTransparent(3),
159: ethernetTagged(4),
160: ethernet(5),
161: hdlc(6),
162: ppp(7),
163: cem(8), -- old format
164: atmCellNto1Vcc(9),
165: atmCellNto1Vpc(10),
166: ipLayer2Transport(11),
167: atmCell1to1Vcc(12),
168: atmCell1to1Vpc(13),
169: atmAal5PduVcc(14),
170: frameRelayPortMode(15),
171: cep(16)
172: }
173:
174: PwVcAttachmentIdentifierType ::= TEXTUAL-CONVENTION
175:
176: STATUS current
177: DESCRIPTION
178: "An octet string used in the generalized FEC element for
179: identifying attachment forwarder and groups. The NULL
180: identifier is of zero length.
181: "
182: SYNTAX OCTET STRING (SIZE (0..255))
183:
184: PwVcCw ::= TEXTUAL-CONVENTION
185:
186: STATUS current
187: DESCRIPTION
188: "If true, indicate the existence or configuration
189: of control word.
190: "
191: SYNTAX TruthValue
192:
193: PwVcRemoteCwStatus ::= TEXTUAL-CONVENTION
194:
195: STATUS current
196: DESCRIPTION
197: "Indicate the status of the control word as advertized by
198: the remote.
199: notApplicable is set by the agent for manulaly configured PW.
200:
201: waitingForNextMsg indicate that the node is waiting for
202: another
203: label mapping from the remote.
204: sentWrongBitErrorCode indicate that the local node has
205: notified the
206: peer about mismatch in the C bit.
207: rxWithdrawWithWrongBitErrorCode indicate that a withdraw
208: message
209: has been recieved with wrong C-bit error code.
210: illegalRecievedBit indicate a C bit configuration with the
211: remote
212: which is not compatible with the PW type.
213: sameAsSent indicate consistent C bit setting between the
214: peers.
215: notYetKnown indicate that a label mapping has not yet
216: recieved
217: from the peer.
218: "
219: SYNTAX INTEGER {
220: notApplicable (0),
221: waitingForNextMsg (1),
222: sentWrongBitErrorCode (2),
223: rxWithdrawWithWrongBitErrorCode (3),
224: illegalRecievedBit (4),
225: sameAsSent (5),
226: notYetKnown(6)
227: }
228:
229: PwVcCapabilities ::= TEXTUAL-CONVENTION
230: STATUS current
231: DESCRIPTION
232: "Indicate the optional capabilities of the control protocol.
233: A value of zero indicate the basic LDP PW signaling.
234: Values may be added in the future based on
235: new capabilities introduced in IETF documents.
236: "
237: SYNTAX BITS {
238: pwStatusIndication (0)
239: }
240:
241: PwVcStatus ::= TEXTUAL-CONVENTION
242: STATUS current
243: DESCRIPTION
244: "The status of the PW and the interfaces affecting this PW.
245: "
246: SYNTAX BITS {
247: pwNotForwarding (0),
248: customerFacingPwRxFault (1),
249: customerFacingPwTxFault (2),
250: psnFacingPwRxFault (3),
251: psnFacingPwTxFault (4)
252: }
253:
254: PwVcFragSize ::= TEXTUAL-CONVENTION
255: STATUS current
256: DESCRIPTION
257: "If set to value other than zero, it indicates desired
258: fragmantation
259: to the value set. If set to zero, fragmantation is not desired
260: for
261: PSN bound packets.
262: "
263: SYNTAX Unsigned32
264:
265: PwVcFragStatus ::= TEXTUAL-CONVENTION
266: STATUS current
267: DESCRIPTION
268: "The status of the fragmantation process based on local
269: configuration
270: and the remote capability.
271:
272: noFragmantation bit indicate that local configuration is for no
273: fragmantation.
274: cfgFragGreaterThanPsnMtu bit indicate the local desire to
275: fragment, but the
276: fragamentation size desired is greater than the MTU available at
277: the PSN between
278: peers. Fragmantation is not done in this case.
279: cfgFragButRemoteIncapable bit
280: indicate local configuration indicate the desire for
281: fragmantation but the remote
282: is not capable of fragmantation. remoteFragCapable bit indicate
283: that the remote
284: has advertized it's fragmantation capability.
285: fragmantationEnabled bit indicate that both the local was
286: configured for
287: fragmantation and the remote has the cabability
288: to accept fragmented packets.
289: "
290: SYNTAX BITS {
291: noFragmantation (0),
292: cfgFragGreaterThanPsnMtu (1),
293: cfgFragButRemoteIncapable (2),
294: remoteFragCapable (3),
295: fragmantationEnabled (4)
296: }
297:
298: END
299:
300: --
301: -- Copyright (C) The Internet Society (2000). All Rights Reserved.
302: -- This document and translations of it may be copied and furnished to
303: -- others, and derivative works that comment on or otherwise explain
304: -- it or assist in its implementation may be prepared, copied,
305: -- published and distributed, in whole or in part, without restriction
306: -- of any kind, provided that the above copyright notice and this
307: -- paragraph are included on all such copies and derivative works.
308: -- However, this document itself may not be modified in any way, such
309: -- as by removing the copyright notice or references to the Internet
310: -- Society or other Internet organizations, except as needed for the
311: -- purpose of developing Internet standards in which case the
312: -- procedures for copyrights defined in the Internet Standards process
313: -- must be followed, or as required to translate it into languages
314: -- other than English.
315: -- The limited permissions granted above are perpetual and will not be
316: -- revoked by the Internet Society or its successors or assigns. This
317: -- document and the information contained herein is provided on an "AS
318: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
319: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
320: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
321: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
322: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
323:
PW-MIB
1: -- extracted from draft-ietf-pwe3-pw-mib-01.txt
2: -- at Fri May 14 06:21:09 2004
3:
4: PW-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: experimental, Integer32, Unsigned32,
9: Counter64, TimeTicks
10: FROM SNMPv2-SMI
11:
12: MODULE-COMPLIANCE, OBJECT-GROUP
13: FROM SNMPv2-CONF
14:
15: TruthValue, RowStatus, StorageType,
16: TimeStamp
17: FROM SNMPv2-TC
18:
19: SnmpAdminString
20: FROM SNMP-FRAMEWORK-MIB
21:
22: PwVcIndexType, PwGroupID, PwVcIDType, PwOperStatus,
23: PwVcType
24: FROM PW-TC-MIB
25:
26: InetAddressType, InetAddress
27: FROM INET-ADDRESS-MIB
28:
29: ;
30:
31: pwVcMIB MODULE-IDENTITY
32: LAST-UPDATED "200301301200Z" -- 30 January 2003 12:00:00 EST
33: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
34: Group"
35: CONTACT-INFO
36: "
37: David Zelig
38: Postal: Corrigent Systems
39: 126, Yigal Alon St.
40: Tel Aviv, ISRAEL
41: Phone: +972-3-6945273
42: E-mail: davidz@corrigent.com
43:
44: Thomas D. Nadeau
45: Postal: Cisco Systems, Inc.
46: 250 Apollo Drive
47: Chelmsford, MA 01824
48: Tel: +1-978-497-3051
49: Email: tnadeau@cisco.com
50:
51: Dave Danenberg
52: Postal: Litchfield Communications, Inc.
53: Pseudo Wire (PW) Management June 2003
54: Information Base
55:
56:
57: 76 Westbury Park Rd
58: Princeton Building East
59: Watertown, CT 06795
60: Tel: +1-860-945-1573 x3180
61: Email: dave_danenberg@litchfieldcomm.com
62:
63: Andrew G. Malis
64: Postal: Vivace Networks, Inc.
65: 2730 Orchard Parkway
66: San Jose, CA 95134
67: Email: Andy.Malis@vivacenetworks.com
68:
69: Sharon Mantin
70: Postal: AxONLink (Israel) Ltd
71: 9 Bareket St.
72: Petah Tikva 49517, Israel
73: Tel: +972-3-9263972
74: Email: sharon.mantin@axonlink.com
75:
76: The PWE3 Working Group (email distribution pwe3@ietf.org)
77: "
78:
79: DESCRIPTION
80: "This MIB contains managed object definitions for Pseudo
81: Wire operation as in: Pate, P., et al, <draft-ietf-pwe3-
82: framework>, Xiao, X., et al, <draft-ietf-pwe3-
83: requirements>, Martini, L., et al, <draft-martini-
84: l2circuit-trans-mpls>, and Martini, L., et al,
85: <draft-martini-l2circuit-encap-mpls>.
86:
87: The indexes for this MIB are also used to index the PSN-
88: specific tables and the VC-specific tables. The VC Type
89: dictates which VC-specific MIB to use. For example, a
90: 'cep' VC Type requires the use the configuration and status
91: tables within the CEP-MIB.
92:
93: This MIB enable the use of any underlying packet switched
94: network (PSN). Specific tables for the MPLS PSN is
95: currently defined in a separate PW-MPLS-MIB. Tables to
96: support other PSNs (IP, L2TP for example) will be added to
97: this MIB in future revisions.
98:
99: At the time of publication of this version, there are no
100: PWE3 WG documents for all features and objects in this MIB,
101: and the MIB is therefore subject to change based on the WG
102: progress."
103:
104: -- Revision history.
105: REVISION
106: "200305261200Z" -- 26 May 2002 12:00:00 EST
106: minor error -
revision date after last update
107: DESCRIPTION
108: Pseudo Wire (PW) Management June 2003
108: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
109: Information Base
110:
111:
112: "Moved to draft-ietf-00 status. Changes from previous draft:
113: 1) Change name of pwVcPriority to pwVcSetUpPriority and
114: added pwVcHoldingPriority.
115: 2) Add pwVcIdMappingTable and pwVcPeersMappingTable to help
116: ordered query of the MIB tables for EMS applications.
117: 3) Clarification to work in progress objects.
118: 4) Editorial and typos in descriptions.
119: 5) Added pwVcPerfTotalDiscontinuityTime and
120: pwVcPerfIntervalTimeElapsed.
121: 6) Remove 32 bit counters.
122: "
123: REVISION
124: "200201301200Z" -- 30 January 2002 12:00:00 EST
125: DESCRIPTION
126: " Changes from -01 draft:
127: 1) Inbound and outbound clarification and name changes.
128: 2) Removing pwVcPeerIpv4Addr and pwVcPeerIpv6Addr,
129: replacing them with pwVcPeerAddr and adding type for
130: address type selection.
131: 3) Adding type for VC OperStatus.
132: 4) Adding pwVcTimeElapsed and pwVcValidIntervals.
133:
134: "
135: REVISION
136: "200111071200Z" -- 7 November 2001 12:00:00 EST
137: DESCRIPTION
138: "Changes from -00 draft:
139: 1) Remove VcInstance from tables indexes in order to simplify
140: the MIB.
141: 2) Removing APS 1+1 table.
142: 3) Changing hdlcCisco to hdlc in pwVcType.
143: 4) Add description of VC label at pending PW signaling stage.
144: 5) Add interval valid object in interval performance tables.
145: 6) Remove VC APS notification.
146: 7) Change 'conservative'/'liberal' to 'strict'/'loose'.
147: 8) Add objects for interface MTU, use of control word,
148: interface string.
149: 9) Ordering of objects based on functionality.
150: 10) Update operation of pwVcOperStatus.
151: "
152:
153: REVISION
154: "200107111200Z" -- 11 July 2001 12:00:00 EST
155: DESCRIPTION
156: "draft-00 version"
157:
158: ::= { experimental xxx } -- To be assigned by IANA
158: warning -
warning: flushing recent incorrect declaration, see previous error(s)
159:
160: -- Top-level components of this MIB.
161:
162: -- Notifications
163: Pseudo Wire (PW) Management June 2003
163: error -
`Pseudo' should start with a lower case letter
163: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
164: Information Base
165:
166:
167:
168: -- Tables, Scalars
169: pwVcObjects OBJECT IDENTIFIER
170: ::= { pwVcMIB 1 }
170: warning -
warning: flushing recent incorrect declaration, see previous error(s)
171:
172: -- Conformance
173: pwVcConformance OBJECT IDENTIFIER
174: ::= { pwVcMIB 2 }
175:
176: -- PW Virtual Connection (VC) Table
177:
178: pwVcIndexNext OBJECT-TYPE
179: SYNTAX Unsigned32
180: MAX-ACCESS read-only
181: STATUS current
182: DESCRIPTION
183: "This object contains an appropriate value to be used
184: for pwVcIndex when creating entries in the
185: pwVcTable. The value 0 indicates that no
186: unassigned entries are available. To obtain the
187: value of pwVcIndex for a new entry in the
188: pwVcTable, the manager issues a management
189: protocol retrieval operation to obtain the current
190: value of pwVcIndex. After each retrieval
191: operation, the agent should modify the value to
192: reflect the next unassigned index. After a manager
193: retrieves a value the agent will determine through
194: its local policy when this index value will be made
195: available for reuse."
196: ::= { pwVcObjects 1 }
197:
198:
199: pwVcTable OBJECT-TYPE
200: SYNTAX SEQUENCE OF PwVcEntry
201: MAX-ACCESS not-accessible
202: STATUS current
203: DESCRIPTION
204: "This table specifies information for connecting various
205: emulated services to various tunnel type."
206: ::= { pwVcObjects 2 }
207:
208: pwVcEntry OBJECT-TYPE
209: SYNTAX PwVcEntry
210: MAX-ACCESS not-accessible
211: STATUS current
212: DESCRIPTION
213: "A row in this table represents an emulated virtual
214: connection (VC) across a packet network. It is indexed by
215: pwVcIndex, which uniquely identifying a singular
216: connection.
217: "
218: Pseudo Wire (PW) Management June 2003
218: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
219: Information Base
220:
221:
222: INDEX { pwVcIndex }
222: warning -
warning: flushing recent incorrect declaration, see previous error(s)
223:
224: ::= { pwVcTable 1 }
224: severe -
syntax error, unexpected COLON_COLON_EQUAL
224: warning -
warning: flushing recent incorrect declaration, see previous error(s)
225:
226: PwVcEntry ::= SEQUENCE {
227: pwVcIndex PwVcIndexType,
228: pwVcType PwVcType,
229: pwVcOwner INTEGER,
230: pwVcPsnType INTEGER,
231: pwVcSetUpPriority Integer32,
232: pwVcHoldingPriority Integer32,
233: pwVcInboundMode INTEGER,
234: pwVcPeerAddrType InetAddressType,
235: pwVcPeerAddr InetAddress,
236:
237: pwVcID PwVcIDType,
238: pwVcLocalGroupID PwGroupID,
239: pwVcControlWord TruthValue,
240: pwVcLocalIfMtu Unsigned32,
241: pwVcLocalIfString TruthValue,
242: pwVcRemoteGroupID PwGroupID,
243: pwVcRemoteControlWord INTEGER,
244: pwVcRemoteIfMtu Unsigned32,
245: pwVcRemoteIfString SnmpAdminString,
246: pwVcOutboundVcLabel Unsigned32,
247: pwVcInboundVcLabel Unsigned32,
248:
249: pwVcName SnmpAdminString,
250: pwVcDescr SnmpAdminString,
251: pwVcCreateTime TimeStamp,
252: pwVcUpTime TimeTicks,
253: pwVcAdminStatus INTEGER,
254: pwVcOperStatus PwOperStatus,
255: pwVcInboundOperStatus PwOperStatus,
256: pwVcOutboundOperStatus PwOperStatus,
257: pwVcTimeElapsed Integer32,
258: pwVcValidIntervals Integer32,
259: pwVcRowStatus RowStatus,
260: pwVcStorageType StorageType
261: }
262:
263: pwVcIndex OBJECT-TYPE
264: SYNTAX PwVcIndexType
265: MAX-ACCESS not-accessible
266: STATUS current
267: DESCRIPTION
268: "Index for the conceptual row identifying a VC within
269: this PW Emulation VC table."
270: ::= { pwVcEntry 1 }
271:
272: pwVcType OBJECT-TYPE
272: warning -
warning: identifier `pwVcType' differs from `PW-TC-MIB::PwVcType' only in case
273: Pseudo Wire (PW) Management June 2003
273: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
274: Information Base
275:
276:
277: SYNTAX PwVcType
278: MAX-ACCESS read-create
279: STATUS current
280: DESCRIPTION
281: "This value indicate the service to be carried over
282: this VC.
283: Note: the exact set of VC types is yet to be worked
284: out by the WG.
285: "
286: ::= { pwVcEntry 2 }
286: warning -
warning: flushing recent incorrect declaration, see previous error(s)
287:
288: pwVcOwner OBJECT-TYPE
289: SYNTAX INTEGER {
290: manual (1),
291: maintenanceProtocol (2), -- PW signaling
292: other (3)
293: }
294: MAX-ACCESS read-create
295: STATUS current
296: DESCRIPTION
297: "Set by the operator to indicate the protocol responsible
298: for establishing this VC. Value 'manual' is used in all
299: cases where no maintenance protocol (PW signaling) is used
300: to set-up the VC, i.e. require configuration of entries in
301: the VC tables including VC labels, etc. The value
302: 'maintenanceProtocol' is used in case of standard
303: signaling of the VC for the specific PSN, for example LDP
304: for MPLS PSN as specified in <draft- draft-martini-
305: l2circuit-trans-mpls> or L2TP control protocol.
306: Value 'other' is used for other types of signaling."
307: ::= { pwVcEntry 3 }
307: minor error -
scalar object must not have a `read-create' access value
308:
309:
310: pwVcPsnType OBJECT-TYPE
311: SYNTAX INTEGER {
312: mpls (1),
313: l2tp (2),
314: ip (3),
315: mplsOverIp (4), -- May be combined with 'mpls' in the future
316: gre (5),
317: other (6)
318: }
319: MAX-ACCESS read-create
320: STATUS current
321: DESCRIPTION
322: "Set by the operator to indicate the PSN type on which this
323: VC will be carried. Based on this object, the relevant PSN
324: table entries are created in the in the PSN specific MIB
325: modules. For example, if mpls(1) is defined, the agent
326: create an entry in pwVcMplsTable, which further define the
327: MPLS PSN configuration.
328: Pseudo Wire (PW) Management June 2003
329: Information Base
330:
331:
332: Note: the exact set of PSN types is yet to be worked
333: out by the WG.
334: "
335: ::= { pwVcEntry 4 }
335: minor error -
scalar object must not have a `read-create' access value
336:
337: pwVcSetUpPriority OBJECT-TYPE
338: SYNTAX Integer32 (0..7)
339: MAX-ACCESS read-create
340: STATUS current
341: DESCRIPTION
342: "This object define the relative set-up priority of the VC
343: in a lowest-to-highest fashion, where 0 is the highest
344: priority. VCs with the same priority are treated with
345: equal priority. Dropped VC will be set 'dormant' (as
346: indicated in pwVcOperStatus).
347: This value is significant if there are competing resources
348: between VCs and the implementation support this feature.
349: If not supported or not relevant, the value of zero MUST
350: be used."
351: DEFVAL
352: { 0 }
353: ::= { pwVcEntry 5 }
353: minor error -
scalar object must not have a `read-create' access value
354:
355: pwVcHoldingPriority OBJECT-TYPE
356: SYNTAX Integer32 (0..7)
357: MAX-ACCESS read-create
358: STATUS current
359: DESCRIPTION
360: "This object define the relative holding priority of the VC
361: in a lowest-to-highest fashion, where 0 is the highest
362: priority. VCs with the same priority are treated with
363: equal priority. Dropped VC will be set 'dormant' (as
364: indicated in pwVcOperStatus).
365: This value is significant if there are competing resources
366: between VCs and the implementation support this feature.
367: If not supported or not relevant, the value of zero MUST
368: be used."
369: DEFVAL
370: { 0 }
371: ::= { pwVcEntry 6 }
371: minor error -
scalar object must not have a `read-create' access value
372:
373: pwVcInboundMode OBJECT-TYPE
374: SYNTAX INTEGER {
375: loose (1),
376: strict (2)
377: }
378: MAX-ACCESS read-create
379: STATUS current
380: DESCRIPTION
381: "This object is used to enable greater security for
382: implementation that use per platform VC label space. In
383: Pseudo Wire (PW) Management June 2003
384: Information Base
385:
386:
387: strict mode, packets coming from the PSN are accepted only
388: from tunnels that are associated to the same VC via the
389: inbound tunnel table in the case of MPLS, or as identified
390: by the source IP address in case of L2TP or IP PSN. The
391: entries in the inbound tunnel table are either explicitly
392: configured or implicitly known by the maintenance protocol
393: used for VC set-up.
394:
395: If such association is not known, not configured or not
396: desired, loose mode should be configured, and the node
397: should accept the packet based on the VC label only
398: regardless of the outer tunnel used to carry the VC."
399: DEFVAL
400: { loose }
401: ::= { pwVcEntry 7 }
401: minor error -
scalar object must not have a `read-create' access value
402:
403: pwVcPeerAddrType OBJECT-TYPE
404: SYNTAX InetAddressType
405: MAX-ACCESS read-create
406: STATUS current
407: DESCRIPTION
408: "Denotes the address type of the peer node maintenance
409: protocol (signaling) address if PW maintenance protocol is
410: used for the VC creation. It should be set to
411: 'unknown' if PE/PW maintenance protocol is not used,
412: i.e. pwVcOwner is set to 'manual'. "
413: DEFVAL { ipv4 }
414: ::= { pwVcEntry 8 }
414: minor error -
scalar object must not have a `read-create' access value
415:
416: pwVcPeerAddr OBJECT-TYPE
417: SYNTAX InetAddress
418: MAX-ACCESS read-create
419: STATUS current
420: DESCRIPTION
421: "This object conatin the value of of the peer node address
422: of the PW/PE maintenance protocol entity. This object
423: should contain a value of 0 if not relevant (manual
424: configuration of the VC)."
425: ::= { pwVcEntry 9 }
425: minor error -
scalar object must not have a `read-create' access value
426:
427: pwVcID OBJECT-TYPE
428: SYNTAX PwVcIDType
429: MAX-ACCESS read-create
430: STATUS current
431: DESCRIPTION
432: "Used in the outgoing VC ID field within the 'Virtual
433: Circuit FEC Element' when LDP signaling is used or PW ID
434: AVP for L2TP."
435: REFERENCE
436: "Martini, et al, <draft-martini-l2circuit-trans-mpls>.
437: and So, et al, <draft-so-pwe3-ethernet>.
438: Pseudo Wire (PW) Management June 2003
439: Information Base
440:
441:
442: Note: as specified in l2circuit-trans: It is REQUIRED to
443: assign the same VC ID, and VC type for a given circuit in
444: both directions."
445: ::= { pwVcEntry 10 }
445: minor error -
scalar object must not have a `read-create' access value
446:
447: pwVcLocalGroupID OBJECT-TYPE
448: SYNTAX PwGroupID
449: MAX-ACCESS read-create
450: STATUS current
451: DESCRIPTION
452: "Used in the Group ID field sent to the peer PWES
453: within the maintenance protocol used for VC setup,
454: zero if not used."
455: REFERENCE
456: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
457: and So, et al, <draft-so-pwe3-ethernet.txt>."
458: ::= { pwVcEntry 11 }
458: minor error -
scalar object must not have a `read-create' access value
459:
460: pwVcControlWord OBJECT-TYPE
461: SYNTAX TruthValue
462: MAX-ACCESS read-create
463: STATUS current
464: DESCRIPTION
465: "Define if the control word will be sent with each packet by
466: the local node."
467: REFERENCE
468: "Martini, et al, <draft-martini-l2circuit-trans-mpls>"
469: DEFVAL
470: { false }
471: ::= { pwVcEntry 12 }
471: minor error -
scalar object must not have a `read-create' access value
472:
473: pwVcLocalIfMtu OBJECT-TYPE
474: SYNTAX Unsigned32 (0..65535)
475: MAX-ACCESS read-create
476: STATUS current
477: DESCRIPTION
478: "If not equal zero, the optional IfMtu object in the
479: maintenance protocol will be sent with this value,
480: representing the locally supported MTU size over the
481: interface (or the virtual interface) associated with the
482: VC."
483: REFERENCE
484: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
485: and So, et al, <draft-so-pwe3-ethernet>."
486:
487: DEFVAL
488: { 0 }
489: ::= { pwVcEntry 13 }
489: minor error -
scalar object must not have a `read-create' access value
490:
491: pwVcLocalIfString OBJECT-TYPE
492: SYNTAX TruthValue
493: Pseudo Wire (PW) Management June 2003
493: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
494: Information Base
495:
496:
497: MAX-ACCESS read-create
498: STATUS current
499: DESCRIPTION
500: "Each VC is associated to an interface (or a virtual
501: interface) in the ifTable of the node as part of the
502: service configuration. This object defines if the
503: maintenance protocol will send the interface's name as
504: appears on the ifTable in the name object as part of the
505: maintenance protocol. If set to false, the optional element
506: will not be sent."
507: REFERENCE
508: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
509: and So, et al, <draft-so-pwe3-ethernet.txt>."
510: DEFVAL
511: { false }
511: warning -
warning: flushing recent incorrect declaration, see previous error(s)
512: ::= { pwVcEntry 14 }
512: severe -
syntax error, unexpected COLON_COLON_EQUAL
512: warning -
warning: flushing recent incorrect declaration, see previous error(s)
513:
514: pwVcRemoteGroupID OBJECT-TYPE
515: SYNTAX PwGroupID
516: MAX-ACCESS read-only
517: STATUS current
518: DESCRIPTION
519: "Obtained from the Group ID field as received via the
520: maintenance protocol used for VC setup, zero if not used.
521: Value of 0xFFFF shall be used if the object is yet to be
522: defined by the VC maintenance protocol."
523: REFERENCE
524: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
525: and So, et al, <draft-so-pwe3-ethernet.txt>."
526: ::= { pwVcEntry 15 }
527:
528: pwVcRemoteControlWord OBJECT-TYPE
529: SYNTAX INTEGER {
530: noControlWord (1),
531: withControlWord (2),
532: notYetKnown(3)
533: }
534: MAX-ACCESS read-create
535: STATUS current
536: DESCRIPTION
537: "If maintenance protocol is used for VC establishment, this
538: parameter indicates the received status of the control word
539: usage, i.e. if packets will be received with control word
540: or not. The value of 'notYetKnown' is used while the
541: maintenance protocol has not yet received the indication
542: from the remote node.
543: In manual configuration of the VC this parameters indicate
544: to the local node what is the expected encapsulation for
545: the received packets.
546: "
547: Pseudo Wire (PW) Management June 2003
547: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
548: Information Base
549:
550:
551: REFERENCE
552: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
553: and So, et al, <draft-so-pwe3-ethernet.txt>."
554: ::= { pwVcEntry 16 }
554: warning -
warning: flushing recent incorrect declaration, see previous error(s)
555:
556: pwVcRemoteIfMtu OBJECT-TYPE
557: SYNTAX Unsigned32
558: MAX-ACCESS read-only
559: STATUS current
560: DESCRIPTION
561: "The remote interface MTU as (optionally) received from the
562: remote node via the maintenance protocol. Should be zero if
563: this parameter is not available or not used."
564: REFERENCE
565: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
566: and So, et al, <draft-so-pwe3-ethernet.txt>."
567: ::= { pwVcEntry 17 }
567: minor error -
scalar object must not have a `read-create' access value
568:
569: pwVcRemoteIfString OBJECT-TYPE
570: SYNTAX SnmpAdminString (SIZE (0..80))
571: MAX-ACCESS read-only
572: STATUS current
573: DESCRIPTION
574: "Indicate the interface description string as received by
575: the maintenance protocol, MUST be NULL string if not
576: applicable or not known yet."
577: REFERENCE
578: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
579: and So, et al, <draft-so-pwe3-ethernet>."
580: ::= { pwVcEntry 18 }
581:
582: pwVcOutboundVcLabel OBJECT-TYPE
583: SYNTAX Unsigned32
584: MAX-ACCESS read-create
585: STATUS current
586: DESCRIPTION
587: "The VC label used in the outbound direction (i.e. toward
588: the PSN). It may be set up manually if owner is 'manual' or
589: automatically otherwise. Examples: For MPLS PSN, it
590: represents the 20 bits of VC tag, for L2TP it represent the
591: 32 bits Session ID.
592: If the label is not yet known (signaling in process), the
593: object should return a value of 0xFFFF."
594: REFERENCE
595: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
596: Townsley, et al, <draft-ietf-l2tpext-l2tp-base.txt>"
597: ::= { pwVcEntry 19 }
597: minor error -
scalar object must not have a `read-create' access value
598:
599: pwVcInboundVcLabel OBJECT-TYPE
600: SYNTAX Unsigned32
601: MAX-ACCESS read-create
602: Pseudo Wire (PW) Management June 2003
602: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
603: Information Base
604:
605:
606: STATUS current
607: DESCRIPTION
608: "The VC label used in the inbound direction (i.e. packets
609: received from the PSN. It may be set up manually if owner
610: is 'manual' or automatically otherwise.
611: Examples: For MPLS PSN, it represents the 20 bits of VC
612: tag, for L2TP it represent the 32 bits Session ID.
613: If the label is not yet known (signaling in process), the
614: object should return a value of 0xFFFF."
615: REFERENCE
616: "Martini, et al, <draft-martini-l2circuit-trans-mpls>
617: Townsley, et al, <draft-ietf-l2tpext-l2tp-base.txt>"
618: ::= { pwVcEntry 20 }
618: warning -
warning: flushing recent incorrect declaration, see previous error(s)
619:
620: pwVcName OBJECT-TYPE
621: SYNTAX SnmpAdminString
622: MAX-ACCESS read-create
623: STATUS current
624: DESCRIPTION
625: "The canonical name assigned to the VC."
626: ::= { pwVcEntry 21 }
626: minor error -
scalar object must not have a `read-create' access value
627:
628: pwVcDescr OBJECT-TYPE
629: SYNTAX SnmpAdminString
630: MAX-ACCESS read-create
631: STATUS current
632: DESCRIPTION
633: "A textual string containing information about the VC.
634: If there is no description this object contains a zero
635: length string."
636: ::= { pwVcEntry 22 }
636: minor error -
scalar object must not have a `read-create' access value
637:
638: pwVcCreateTime OBJECT-TYPE
639: SYNTAX TimeStamp
640: MAX-ACCESS read-only
641: STATUS current
642: DESCRIPTION
643: "System time when this VC was created."
644: ::= { pwVcEntry 23 }
645:
646: pwVcUpTime OBJECT-TYPE
647: SYNTAX TimeTicks
648: MAX-ACCESS read-only
649: STATUS current
650: DESCRIPTION
651: "Number of consecutive ticks this VC has been 'up' in
652: both directions together (i.e. 'up' is observed in
653: pwVcOperStatus.)"
654: ::= { pwVcEntry 24 }
655:
656: pwVcAdminStatus OBJECT-TYPE
657: Pseudo Wire (PW) Management June 2003
657: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
658: Information Base
659:
660:
661: SYNTAX INTEGER {
662: up(1), -- ready to pass packets
663: down(2),
664: testing(3) -- in some test mode
665: }
665: warning -
warning: flushing recent incorrect declaration, see previous error(s)
666: MAX-ACCESS read-create
666: severe -
syntax error, unexpected MAX_ACCESS
667: STATUS current
668: DESCRIPTION
669: "The desired operational status of this VC."
670: ::= { pwVcEntry 25 }
670: warning -
warning: flushing recent incorrect declaration, see previous error(s)
671:
672: pwVcOperStatus OBJECT-TYPE
673: SYNTAX PwOperStatus
674: MAX-ACCESS read-only
675: STATUS current
676: DESCRIPTION
677: "Indicates the actual combined operational status of this
678: VC. It is 'up' if both pwVcInboundOperStatus and
679: pwVcOutboundOperStatus are in 'up' state. For all other
680: values, if the VCs in both directions are of the same
681: value it reflects that value, otherwise it is set to the
682: most severe status out of the two statuses. The order of
683: severance from most severe to less severe is: unknown,
684: notPresent, down, lowerLayerDown, dormant, testing, up.
685: The operator may consult the per direction OperStatus for
686: fault isolation per direction."
687: ::= { pwVcEntry 26 }
688:
689: pwVcInboundOperStatus OBJECT-TYPE
690: SYNTAX PwOperStatus
691: MAX-ACCESS read-only
692: STATUS current
693: DESCRIPTION
694: "Indicates the actual operational status of this VC in the
695: inbound direction.
696:
697: - down: if PW signaling has not yet finished, or
698: indications available at the service
699: level indicate that the VC is not
700: passing packets.
701: - testing: if AdminStatus at the VC level is set to
702: test.
703: - dormant: The VC is not available because of the
704: required resources are occupied VC with
705: higher priority VCs .
706: - notPresent: Some component is missing to accomplish
707: the set up of the VC.
708: - lowerLayerDown: The underlying PSN is not in OperStatus
709: 'up'.
710: "
711: ::= { pwVcEntry 27 }
712: Pseudo Wire (PW) Management June 2003
712: error -
`Pseudo' should start with a lower case letter
712: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
713: Information Base
714:
715:
716:
717: pwVcOutboundOperStatus OBJECT-TYPE
718: SYNTAX PwOperStatus
719: MAX-ACCESS read-only
720: STATUS current
721: DESCRIPTION
722: "Indicates the actual operational status of this VC in the
723: outbound direction
724: - down: if PW signaling has not yet finished, or
725: indications available at the service
726: level indicate that the VC is not
727: passing packets.
728: - testing: if AdminStatus at the VC level is set to
729: test.
730: - dormant: The VC is not available because of the
731: required resources are occupied VC with
732: higher priority VCs .
733: - notPresent: Some component is missing to accomplish
734: the set up of the VC.
735: - lowerLayerDown: The underlying PSN is not in OperStatus
736: 'up'.
737: "
738: ::= { pwVcEntry 28 }
738: warning -
warning: flushing recent incorrect declaration, see previous error(s)
739:
740: pwVcTimeElapsed OBJECT-TYPE
741: SYNTAX Integer32 (1..900)
742: MAX-ACCESS read-only
743: STATUS current
744: DESCRIPTION
745: "The number of seconds, including partial seconds,
746: that have elapsed since the beginning of the current
747: measurement period. If, for some reason, such as an
748: adjustment in the system's time-of-day clock, the
749: current interval exceeds the maximum value, the
750: agent will return the maximum value."
751: ::= { pwVcEntry 29 }
752:
753: pwVcValidIntervals OBJECT-TYPE
754: SYNTAX Integer32 (0..96)
755: MAX-ACCESS read-only
756: STATUS current
757: DESCRIPTION
758: "The number of previous 15-minute intervals
759: for which data was collected.
760: An agent with PW capability must be capable of supporting at
761: least n intervals. The minimum value of n is 4, The default
762: of n is 32 and the maximum value of n is 96.
763: The value will be <n> unless the measurement was (re-)
764: started within the last (<n>*15) minutes, in which case the
765: value will be the number of complete 15 minute intervals for
766: which the agent has at least some data. In certain cases
767: Pseudo Wire (PW) Management June 2003
768: Information Base
769:
770:
771: (e.g., in the case where the agent is a proxy) it is
772: possible that some intervals are unavailable. In this case,
773: this interval is the maximum interval number for which data
774: is available. "
775: ::= { pwVcEntry 30 }
776:
777: pwVcRowStatus OBJECT-TYPE
778: SYNTAX RowStatus
779: MAX-ACCESS read-create
780: STATUS current
781: DESCRIPTION
782: "For creating, modifying, and deleting this row."
783: ::= { pwVcEntry 31 }
783: minor error -
scalar object must not have a `read-create' access value
784:
785: pwVcStorageType OBJECT-TYPE
786: SYNTAX StorageType
787: MAX-ACCESS read-create
788: STATUS current
789: DESCRIPTION
790: "This variable indicates the storage type for this
791: object."
792: ::= { pwVcEntry 32 }
792: minor error -
scalar object must not have a `read-create' access value
793:
794: -- End of PW Virtual Connection (VC) Table
795:
796: -- Vc Performance Table.
797:
798: pwVcPerfCurrentTable OBJECT-TYPE
799: SYNTAX SEQUENCE OF PwVcPerfCurrentEntry
800: MAX-ACCESS not-accessible
801: STATUS current
802: DESCRIPTION
803: "This table provides per-VC performance information for the
804: current interval."
805: ::= { pwVcObjects 3 }
806:
807: pwVcPerfCurrentEntry OBJECT-TYPE
808: SYNTAX PwVcPerfCurrentEntry
809: MAX-ACCESS not-accessible
810: STATUS current
811: DESCRIPTION
812: "An entry in this table is created by the agent for
813: every VC."
814: INDEX { pwVcIndex }
815: ::= { pwVcPerfCurrentTable 1 }
816:
817: PwVcPerfCurrentEntry ::= SEQUENCE {
818: pwVcPerfCurrentInHCPackets Counter64,
819: pwVcPerfCurrentInHCBytes Counter64,
820: pwVcPerfCurrentOutHCBytes Counter64,
821: pwVcPerfCurrentOutHCPackets Counter64
822: Pseudo Wire (PW) Management June 2003
822: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting '}' or ','
823: Information Base
824:
825:
826: }
826: warning -
warning: flushing recent incorrect declaration, see previous error(s)
827:
828: pwVcPerfCurrentInHCPackets OBJECT-TYPE
829: SYNTAX Counter64
830: MAX-ACCESS read-only
831: STATUS current
832: DESCRIPTION
833: "High capacity counter for number of packets received
834: by the VC (from the PSN) in the current 15 minute
835: interval."
836: ::= { pwVcPerfCurrentEntry 1 }
837:
838: pwVcPerfCurrentInHCBytes OBJECT-TYPE
839: SYNTAX Counter64
840: MAX-ACCESS read-only
841: STATUS current
842: DESCRIPTION
843: "High capacity counter for number of bytes received
844: by the VC (from the PSN) in the current 15 minute
845: interval."
846: ::= { pwVcPerfCurrentEntry 2 }
847:
848: pwVcPerfCurrentOutHCPackets OBJECT-TYPE
849: SYNTAX Counter64
850: MAX-ACCESS read-only
851: STATUS current
852: DESCRIPTION
853: "High capacity counter for number of packets forwarded
854: by the VC (to the PSN) in the current 15 minute interval."
855: ::= { pwVcPerfCurrentEntry 3 }
856:
857: pwVcPerfCurrentOutHCBytes OBJECT-TYPE
858: SYNTAX Counter64
859: MAX-ACCESS read-only
860: STATUS current
861: DESCRIPTION
862: "High capacity counter for number of bytes forwarded
863: by the VC (to the PSN) in the current 15 minute interval."
864: ::= { pwVcPerfCurrentEntry 4 }
865:
866: -- End of Vc Perf current Table
867:
868: -- Vc Performance Interval Table.
869:
870: pwVcPerfIntervalTable OBJECT-TYPE
871: SYNTAX SEQUENCE OF PwVcPerfIntervalEntry
872: MAX-ACCESS not-accessible
873: STATUS current
874: DESCRIPTION
875: "This table provides per-VC performance information for
876: each interval."
877: Pseudo Wire (PW) Management June 2003
877: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
878: Information Base
879:
880:
881: ::= { pwVcObjects 4 }
881: warning -
warning: flushing recent incorrect declaration, see previous error(s)
882:
883: pwVcPerfIntervalEntry OBJECT-TYPE
884: SYNTAX PwVcPerfIntervalEntry
885: MAX-ACCESS not-accessible
886: STATUS current
887: DESCRIPTION
888: "An entry in this table is created agent for every VC."
889: INDEX { pwVcIndex, pwVcPerfIntervalNumber }
890: ::= { pwVcPerfIntervalTable 1 }
891:
892: PwVcPerfIntervalEntry ::= SEQUENCE {
893: pwVcPerfIntervalNumber Integer32,
894: pwVcPerfIntervalValidData TruthValue,
895: pwVcPerfIntervalTimeElapsed Integer32,
896:
897: pwVcPerfIntervalInHCPackets Counter64,
898: pwVcPerfIntervalInHCBytes Counter64,
899: pwVcPerfIntervalOutHCPackets Counter64,
900: pwVcPerfIntervalOutHCBytes Counter64
901: }
902:
903: pwVcPerfIntervalNumber OBJECT-TYPE
904: SYNTAX Integer32 (1..96)
905: MAX-ACCESS not-accessible
906: STATUS current
907: DESCRIPTION
908: "A number N, between 1 and 96, which identifies the
909: interval for which the set of statistics is available.
910: The interval identified by 1 is the most recently
911: completed 15 minute interval, and the interval identified
912: by N is the interval immediately preceding the one
913: identified by N-1.
914: The minimum range of N is 1 through 4. The default range
915: is 1 to 32. The maximum range of N is 1 through 96. "
916: REFERENCE
917: "Tesink, K. 'Definitions of Managed Objects for the
918: SONET/SDH Interface Type', RFC 2558"
919: ::= { pwVcPerfIntervalEntry 1 }
920:
921: pwVcPerfIntervalValidData OBJECT-TYPE
922: SYNTAX TruthValue
923: MAX-ACCESS read-only
924: STATUS current
925: DESCRIPTION
926: "This variable indicates if the data for this interval
927: is valid."
928: ::= { pwVcPerfIntervalEntry 2 }
929:
930: pwVcPerfIntervalTimeElapsed OBJECT-TYPE
931: SYNTAX Integer32
932: Pseudo Wire (PW) Management June 2003
932: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
933: Information Base
934:
935:
936: MAX-ACCESS read-only
937: STATUS current
938: DESCRIPTION
939: "The duration of a particular interval in seconds.
940: Adjustments in the system's time-of-day clock, may
941: cause the interval to be greater or less than the
942: normal value. Therefore this actual interval value
943: is provided."
944: ::= { pwVcPerfIntervalEntry 3 }
944: warning -
warning: flushing recent incorrect declaration, see previous error(s)
945:
946: pwVcPerfIntervalInHCPackets OBJECT-TYPE
947: SYNTAX Counter64
948: MAX-ACCESS read-only
949: STATUS current
950: DESCRIPTION
951: "High capacity counter for number of packets received by
952: the VC (from the PSN) in a particular 15-minute interval."
953: ::= { pwVcPerfIntervalEntry 4 }
954:
955: pwVcPerfIntervalInHCBytes OBJECT-TYPE
956: SYNTAX Counter64
957: MAX-ACCESS read-only
958: STATUS current
959: DESCRIPTION
960: "High capacity counter for number of bytes received by the
961: VC (from the PSN) in a particular 15-minute interval."
962:
963: ::= { pwVcPerfIntervalEntry 5 }
964:
965: pwVcPerfIntervalOutHCPackets OBJECT-TYPE
966: SYNTAX Counter64
967: MAX-ACCESS read-only
968: STATUS current
969: DESCRIPTION
970: "High capacity counter for number of packets forwarded by
971: the VC (to the PSN) in a particular 15-minute interval."
972: ::= { pwVcPerfIntervalEntry 6 }
973:
974: pwVcPerfIntervalOutHCBytes OBJECT-TYPE
975: SYNTAX Counter64
976: MAX-ACCESS read-only
977: STATUS current
978: DESCRIPTION
979: "High capacity counter for number of bytes forwarded by the
980: VC (to the PSN) in a particular 15-minute interval."
981:
982: ::= { pwVcPerfIntervalEntry 7 }
983:
984: -- End of VC Performance Interval Table
985:
986: -- VC Performance Total Table.
987: Pseudo Wire (PW) Management June 2003
987: error -
`Pseudo' should start with a lower case letter
987: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
988: Information Base
989:
990:
991:
992: pwVcPerfTotalTable OBJECT-TYPE
993: SYNTAX SEQUENCE OF PwVcPerfTotalEntry
994: MAX-ACCESS not-accessible
995: STATUS current
996: DESCRIPTION
997: "This table provides per-VC Performance information from VC
998: start time."
999: ::= { pwVcObjects 5 }
999: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1000:
1001: pwVcPerfTotalEntry OBJECT-TYPE
1002: SYNTAX PwVcPerfTotalEntry
1003: MAX-ACCESS not-accessible
1004: STATUS current
1005: DESCRIPTION
1006: "An entry in this table is created agent for every VC."
1007:
1008: INDEX { pwVcIndex }
1009: ::= { pwVcPerfTotalTable 1 }
1010:
1011: PwVcPerfTotalEntry ::= SEQUENCE {
1012: pwVcPerfTotalInHCPackets Counter64,
1013: pwVcPerfTotalInHCBytes Counter64,
1014: pwVcPerfTotalOutHCPackets Counter64,
1015: pwVcPerfTotalOutHCBytes Counter64,
1016: pwVcPerfTotalDiscontinuityTime TimeStamp
1017: }
1018:
1019: pwVcPerfTotalInHCPackets OBJECT-TYPE
1020: SYNTAX Counter64
1021: MAX-ACCESS read-only
1022: STATUS current
1023: DESCRIPTION
1024: "High capacity counter for number of packets received by the
1025: VC (from the PSN)."
1026: ::= { pwVcPerfTotalEntry 1 }
1027:
1028: pwVcPerfTotalInHCBytes OBJECT-TYPE
1029: SYNTAX Counter64
1030: MAX-ACCESS read-only
1031: STATUS current
1032: DESCRIPTION
1033: "High capacity counter for number of bytes received by the
1034: VC (from the PSN)."
1035: ::= { pwVcPerfTotalEntry 2 }
1036:
1037: pwVcPerfTotalOutHCPackets OBJECT-TYPE
1038: SYNTAX Counter64
1039: MAX-ACCESS read-only
1040: STATUS current
1041: DESCRIPTION
1042: Pseudo Wire (PW) Management June 2003
1042: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
1043: Information Base
1044:
1045:
1046: "High capacity counter for number of packets forwarded by
1047: the VC (to the PSN)."
1048: ::= { pwVcPerfTotalEntry 3 }
1048: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1049:
1050: pwVcPerfTotalOutHCBytes OBJECT-TYPE
1051: SYNTAX Counter64
1052: MAX-ACCESS read-only
1053: STATUS current
1054: DESCRIPTION
1055: "High capacity counter for number of bytes forwarded by the
1056: VC (to the PSN)."
1057: ::= { pwVcPerfTotalEntry 4 }
1058:
1059: pwVcPerfTotalDiscontinuityTime OBJECT-TYPE
1060: SYNTAX TimeStamp
1061: MAX-ACCESS read-only
1062: STATUS current
1063: DESCRIPTION
1064: "The value of sysUpTime on the most recent occasion at
1065: which any one or more of this row Counter32 or
1066: Counter64 suffered a discontinuity. If no such
1067: discontinuities have occurred since the last re-
1068: initialization of the local management subsystem, then
1069: this object contains a zero value."
1070: ::= { pwVcPerfTotalEntry 5 }
1071:
1072: -- End of VC Perf Total Table
1073:
1074: -- Error counter scalar
1075:
1076: pwVcPerfTotalErrorPackets OBJECT-TYPE
1077: SYNTAX Counter64
1078: MAX-ACCESS read-only
1079: STATUS current
1080: DESCRIPTION
1081: "Counter for number of error at VC level processing, for
1082: example packets received with unknown VC label."
1083: ::= { pwVcObjects 6 }
1084:
1085: -- Reverse mapping tables
1086:
1087: pwVcIdMappingTable OBJECT-TYPE
1088: SYNTAX SEQUENCE OF PwVcIdMappingEntry
1089: MAX-ACCESS not-accessible
1090: STATUS current
1091: DESCRIPTION
1092: "This table provides reverse mapping of the existing VCs
1093: based on vc type and VC ID ordering. This table is
1094: typically useful for EMS ordered query of existing VCs."
1095: ::= { pwVcObjects 7 }
1096: Pseudo Wire (PW) Management June 2003
1096: error -
`Pseudo' should start with a lower case letter
1096: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1097: Information Base
1098:
1099:
1100: pwVcIdMappingEntry OBJECT-TYPE
1101: SYNTAX PwVcIdMappingEntry
1102: MAX-ACCESS not-accessible
1103: STATUS current
1104: DESCRIPTION
1105: "An entry in this table is created by the agent for every
1106: VC configured by the pwVcTable."
1107:
1108: INDEX { pwVcIdMappingVcType, pwVcIdMappingVcID,
1109: pwVcIdMappingPeerAddrType, pwVcIdMappingPeerAddr,
1110: pwVcIdMappingVcIndex}
1110: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1111: ::= { pwVcIdMappingTable 1 }
1111: severe -
syntax error, unexpected COLON_COLON_EQUAL
1111: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1112:
1113: PwVcIdMappingEntry ::= SEQUENCE {
1114: pwVcIdMappingVcType PwVcType,
1115: pwVcIdMappingVcID PwVcIDType,
1116: pwVcIdMappingPeerAddrType InetAddressType,
1117: pwVcIdMappingPeerAddr InetAddress,
1118: pwVcIdMappingVcIndex PwVcIndexType
1119: }
1120:
1121: pwVcIdMappingVcType OBJECT-TYPE
1122: SYNTAX PwVcType
1123: MAX-ACCESS not-accessible
1124: STATUS current
1125: DESCRIPTION
1126: "The VC type (indicate the service) of this VC."
1127: ::= { pwVcIdMappingEntry 1 }
1128:
1129: pwVcIdMappingVcID OBJECT-TYPE
1130: SYNTAX PwVcIDType
1131: MAX-ACCESS not-accessible
1132: STATUS current
1133: DESCRIPTION
1134: "The VC ID of this VC. Zero if the VC is configured
1135: manually."
1136: ::= { pwVcIdMappingEntry 2 }
1137:
1138: pwVcIdMappingPeerAddrType OBJECT-TYPE
1139: SYNTAX InetAddressType
1140: MAX-ACCESS not-accessible
1141: STATUS current
1142: DESCRIPTION
1143: "IP address type of the peer node."
1144: ::= { pwVcIdMappingEntry 3 }
1145:
1146: pwVcIdMappingPeerAddr OBJECT-TYPE
1147: SYNTAX InetAddress
1148: MAX-ACCESS not-accessible
1149: STATUS current
1150: DESCRIPTION
1151: Pseudo Wire (PW) Management June 2003
1151: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
1152: Information Base
1153:
1154:
1155: "IP address type of the peer node."
1156: ::= { pwVcIdMappingEntry 4 }
1156: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1157:
1158: pwVcIdMappingVcIndex OBJECT-TYPE
1159: SYNTAX PwVcIndexType
1160: MAX-ACCESS read-only
1161: STATUS current
1162: DESCRIPTION
1163: "The value that represent the VC in the pwVcTable."
1164: ::= { pwVcIdMappingEntry 5 }
1165:
1166: pwVcPeerMappingTable OBJECT-TYPE
1167: SYNTAX SEQUENCE OF PwVcPeerMappingEntry
1168: MAX-ACCESS not-accessible
1169: STATUS current
1170: DESCRIPTION
1171: "This table provides reverse mapping of the existing VCs
1172: based on vc type and VC ID ordering. This table is
1173: typically useful for EMS ordered query of existing VCs."
1174: ::= { pwVcObjects 8 }
1175:
1176: pwVcPeerMappingEntry OBJECT-TYPE
1177: SYNTAX PwVcPeerMappingEntry
1178: MAX-ACCESS not-accessible
1179: STATUS current
1180: DESCRIPTION
1181: "An entry in this table is created by the agent for every
1182: VC configured in pwVcTable."
1183:
1184: INDEX { pwVcPeerMappingPeerAddrType, pwVcPeerMappingPeerAddr,
1185: pwVcPeerMappingVcType, pwVcPeerMappingVcID,
1186: pwVcPeerMappingVcIndex}
1187:
1188: ::= { pwVcPeerMappingTable 1 }
1189:
1190: PwVcPeerMappingEntry ::= SEQUENCE {
1191: pwVcPeerMappingPeerAddrType InetAddressType,
1192: pwVcPeerMappingPeerAddr InetAddress,
1193: pwVcPeerMappingVcType PwVcType,
1194: pwVcPeerMappingVcID PwVcIDType,
1195: pwVcPeerMappingVcIndex PwVcIndexType
1196: }
1197:
1198: pwVcPeerMappingPeerAddrType OBJECT-TYPE
1199: SYNTAX InetAddressType
1200: MAX-ACCESS not-accessible
1201: STATUS current
1202: DESCRIPTION
1203: "IP address type of the peer node."
1204: ::= { pwVcPeerMappingEntry 1 }
1205: Pseudo Wire (PW) Management June 2003
1205: error -
`Pseudo' should start with a lower case letter
1205: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1206: Information Base
1207:
1208:
1209: pwVcPeerMappingPeerAddr OBJECT-TYPE
1210: SYNTAX InetAddress
1211: MAX-ACCESS not-accessible
1212: STATUS current
1213: DESCRIPTION
1214: "IP address type of the peer node."
1215: ::= { pwVcPeerMappingEntry 2 }
1215: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1216:
1217: pwVcPeerMappingVcType OBJECT-TYPE
1218: SYNTAX PwVcType
1219: MAX-ACCESS not-accessible
1220: STATUS current
1221: DESCRIPTION
1222: "The VC type (indicate the service) of this VC."
1223: ::= { pwVcPeerMappingEntry 3 }
1224:
1225: pwVcPeerMappingVcID OBJECT-TYPE
1226: SYNTAX PwVcIDType
1227: MAX-ACCESS not-accessible
1228: STATUS current
1229: DESCRIPTION
1230: "The VC ID of this VC. Zero if the VC is configured
1231: manually."
1232: ::= { pwVcPeerMappingEntry 4 }
1233:
1234: pwVcPeerMappingVcIndex OBJECT-TYPE
1235: SYNTAX PwVcIndexType
1236: MAX-ACCESS read-only
1237: STATUS current
1238: DESCRIPTION
1239: "The value that represent the VC in the pwVcTable."
1240: ::= { pwVcPeerMappingEntry 5 }
1241:
1242:
1243: -- End of reverse mapping tables
1244:
1245: -- Notifications - PW VCs
1246:
1247: -- No notifications are defined. Notifications are generated in
1248: -- the per service MIB modules and/or PSN specific modules.
1249: -- Notification related to the maintenance protocol are FFS.
1250:
1251: -- End of notifications.
1252:
1253: -- conformance information
1254:
1255:
1256: -- Note: Conformance at the object access and values level is
1257: -- still FFS, therefore current conformance is defined at the
1258: -- object existence level only.
1259: Pseudo Wire (PW) Management June 2003
1259: error -
`Pseudo' should start with a lower case letter
1259: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1260: Information Base
1261:
1262:
1263: pwVcGroups OBJECT IDENTIFIER ::= { pwVcConformance 1 }
1263: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1264: pwVcCompliances OBJECT IDENTIFIER ::= { pwVcConformance 2 }
1265:
1266:
1267: pwModuleCompliance MODULE-COMPLIANCE
1268: STATUS current
1269: DESCRIPTION
1270: "The compliance statement for agent that support PW
1271: operation."
1272:
1273: MODULE -- this module
1274: MANDATORY-GROUPS { pwVcGroup,
1275: pwVcPeformanceGroup }
1276:
1277: ::= { pwVcCompliances 1 }
1278:
1279: -- Units of conformance.
1280:
1281: pwVcGroup OBJECT-GROUP
1282: OBJECTS {
1283: pwVcIndexNext,
1284: pwVcType,
1285: pwVcOwner,
1286: pwVcPsnType,
1287: pwVcSetUpPriority,
1288: pwVcHoldingPriority,
1289: pwVcInboundMode,
1290: pwVcPeerAddrType,
1291: pwVcPeerAddr,
1292: pwVcID,
1293: pwVcLocalGroupID,
1294: pwVcControlWord,
1295: pwVcLocalIfMtu,
1296: pwVcLocalIfString,
1297: pwVcRemoteGroupID,
1298: pwVcRemoteControlWord,
1299: pwVcRemoteIfMtu,
1300: pwVcRemoteIfString,
1301: pwVcOutboundVcLabel,
1302: pwVcInboundVcLabel,
1303: pwVcName,
1304: pwVcDescr,
1305: pwVcCreateTime,
1306: pwVcUpTime,
1307: pwVcAdminStatus,
1308: pwVcOperStatus,
1309: pwVcOutboundOperStatus,
1310: pwVcInboundOperStatus,
1311: pwVcTimeElapsed,
1312: pwVcValidIntervals,
1313: pwVcRowStatus,
1314: Pseudo Wire (PW) Management June 2003
1314: error -
`Pseudo' should start with a lower case letter
1314: error -
`Wire' should start with a lower case letter
1314: error -
Object identifier element `Wire' name only allowed as first element
1314: severe -
syntax error, unexpected '(', expecting '}' or ','
1315: Information Base
1316:
1317:
1318: pwVcStorageType
1319: }
1319: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1320:
1321: STATUS current
1321: severe -
syntax error, unexpected STATUS
1322: DESCRIPTION
1323: "Collection of objects needed for PW VC
1324: configuration."
1325: ::= { pwVcGroups 1 }
1325: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1326:
1327:
1328:
1329: pwVcPeformanceGroup OBJECT-GROUP
1330: OBJECTS {
1331: pwVcPerfCurrentInHCPackets,
1332: pwVcPerfCurrentInHCBytes,
1333: pwVcPerfCurrentOutHCPackets,
1334: pwVcPerfCurrentOutHCBytes,
1335:
1336: pwVcPerfIntervalValidData,
1337: pwVcPerfIntervalTimeElapsed,
1338: pwVcPerfIntervalInHCPackets,
1339: pwVcPerfIntervalInHCBytes,
1340: pwVcPerfIntervalOutHCPackets,
1341: pwVcPerfIntervalOutHCBytes,
1342:
1343: pwVcPerfTotalInHCPackets,
1344: pwVcPerfTotalInHCBytes,
1345: pwVcPerfTotalOutHCPackets,
1346: pwVcPerfTotalOutHCBytes,
1347: pwVcPerfTotalDiscontinuityTime,
1348:
1349: pwVcPerfTotalErrorPackets
1350: }
1351:
1352: STATUS current
1353: DESCRIPTION
1354: "Collection of objects needed for PW VC
1355: performance."
1356: ::= { pwVcGroups 2 }
1357:
1358: pwVcMappingTablesGroup OBJECT-GROUP
1359: OBJECTS {
1360: pwVcIdMappingVcIndex,
1361: pwVcPeerMappingVcIndex
1362: }
1363:
1364: STATUS current
1365: DESCRIPTION
1366: "Collection of objects contained in the reverse
1367: mapping tables."
1368: ::= { pwVcGroups 3 }
1369: Pseudo Wire (PW) Management June 2003
1369: error -
`Pseudo' should start with a lower case letter
1369: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1370: Information Base
1371:
1372:
1373:
1374: -- END of PW-MIB
1375:
1376: END
1377:
1378: --
1379: -- Copyright (C) The Internet Society (2000). All Rights Reserved.
1380: -- This document and translations of it may be copied and furnished to
1381: -- others, and derivative works that comment on or otherwise explain
1382: -- it or assist in its implementation may be prepared, copied,
1383: -- published and distributed, in whole or in part, without restriction
1384: -- of any kind, provided that the above copyright notice and this
1385: -- paragraph are included on all such copies and derivative works.
1386: -- However, this document itself may not be modified in any way, such
1387: -- as by removing the copyright notice or references to the Internet
1388: -- Society or other Internet organizations, except as needed for the
1389: -- purpose of developing Internet standards in which case the
1390: -- procedures for copyrights defined in the Internet Standards process
1391: -- must be followed, or as required to translate it into languages
1392: -- other than English.
1393: -- The limited permissions granted above are perpetual and will not be
1394: -- revoked by the Internet Society or its successors or assigns. This
1395: -- document and the information contained herein is provided on an "AS
1396: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1397: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1398: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1399: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1400: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1401: