smilint output for ./PW-DRAFT04-MIB


Message Severities
SeverityCount
severe1
error3
Message Types
TypeCount
import-failed (error)3
internal-other (severe)1

Messages:

PW-DRAFT04-MIB

   1: -- extracted from draft-ietf-pwe3-pw-mib-04.txt
   2: -- at Tue Feb 17 06:17:14 2004
   3: 
   4:    PW-DRAFT04-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-DRAFT04-MIB 
  24: error - identifier `PwVcAttachmentIdentifierType' cannot be imported from module `PW-TC-DRAFT04-MIB'
  24: error - identifier `PwVcCwStatus' cannot be imported from module `PW-TC-DRAFT04-MIB'

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