-- extracted from draft-ietf-pwe3-pw-tc-mib-07.txt -- at Thu Feb 2 06:15:03 2006 PW-TC-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Unsigned32, transmission FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579] pwTcStdMIB MODULE-IDENTITY LAST-UPDATED "200507121200Z" -- 12 July 2005 12:00:00 GMT ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working Group" CONTACT-INFO " Thomas D. Nadeau Email: tnadeau@cisco.com David Zelig E-mail: davidz@corrigent.com The PWE3 Working Group (email distribution pwe3@ietf.org, http://www.ietf.org/html.charters/pwe3-charter.html) " DESCRIPTION "Copyright (C) The Internet Society (2006). The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC -- RFC Editor: Please replace XXXX with RFC number & remove this -- note. itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module defines TEXTUAL-CONVENTIONs PWE3 TC MIB February 2006 for concepts used in Pseudo Wire Edge-to-Edge networks. " -- Revision history. REVISION "200507121200Z" -- 12 July 2005 12:00:00 GMT DESCRIPTION "Initial version published as part of RFC YYYY." -- RFC Editor: please replace YYYY value, and -- delete this note. ::= { transmission XXXX } -- RFC Editor: please replace XXXX with IANA assigned value, and -- delete this note. PwGroupID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An administrative identification mechanism for grouping a set of service-specific pseudo-wire services. May only have local significance." SYNTAX Unsigned32 PwIDType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Pseudo-Wire Identifier. Used to identify the PW (together with some other fields) in the signaling session. Zero if the PW is set-up manually." SYNTAX Unsigned32 PwIndexType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Pseudo Wire Index. Locally unique index for indexing several MIB tables associated with a particular PW." SYNTAX Unsigned32 PwVlanCfg ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "VLAN configuration for Ethernet PW. Values between 0 to 4095 indicate the actual VLAN field value. A value of 4096 indicates that the object refer to untagged frames, i.e. frames without 802.1Q field. A value of 4097 indicates that the object is not relevant." SYNTAX Unsigned32 (0..4097) PwOperStatusTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION PWE3 TC MIB February 2006 "Indicates the operational status of the PW. - up(1): Ready to pass packets. - down(2): If PW signaling has not yet finished, or indications available at the service level indicate that the PW is not passing packets. - testing(3): If AdminStatus at the PW level is set to test. - dormant(4): The PW is not available because the required resources are occupied by higher priority PWs. - notPresent(5): Some component is missing to accomplish the set up of the PW. - lowerLayerDown(6):The underlying PSN or outer tunnel is not in OperStatus 'up' state. " SYNTAX INTEGER { up(1), down(2), testing(3), unknown(4), dormant(5), notPresent(6), lowerLayerDown(7) } PwAttachmentIdentifierType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An octet string used in the generalized FEC element for identifying attachment forwarder and groups. The NULL identifier is of zero length. " SYNTAX OCTET STRING (SIZE (0..255)) PwCwStatusTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the status of the control word negotiation based on the local configuration and the indications received from the peer node. waitingForNextMsg(1) indicates that the node is waiting for another label mapping from the peer. sentWrongBitErrorCode(2) indicates that the local node has notified the peer about mismatch in the C bit. rxWithdrawWithWrongBitErrorCode(3) indicates that a withdraw message has been received with the wrong C-bit error code. PWE3 TC MIB February 2006 illegalReceivedBit(4) indicates a C bit configuration with the peer which is not compatible with the PW type. cwPresent(5) indicates that the CW is present for this PW: if signaling is used - C bit is set and agreed between the nodes, and for manual configured PW the local configuration require the use of the CW. cwNotPresent(6) indicates that the CW is not present for this PW: if signaling is used - C bit is reset and agreed between the nodes, and for manual configured PW the local configuration requires that CW would not be used. notYetKnown(7) indicates that a label mapping has not yet received from the peer. " SYNTAX INTEGER { waitingForNextMsg (1), sentWrongBitErrorCode (2), rxWithdrawWithWrongBitErrorCode (3), illegalReceivedBit (4), cwPresent (5), cwNotPresent (6), notYetKnown(7) } PwCapabilities ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates the optional capabilities of the control protocol. A value of zero indicates the basic LDP PW signaling. Values may be added in the future based on new capabilities introduced in IETF documents. " SYNTAX BITS { pwStatusIndication (0) } PwStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The status of the PW and the interfaces affecting this PW. If none of the bits are set, it indicate no faults are reported. " SYNTAX BITS { pwNotForwarding (0), customerFacingPwRxFault (1), customerFacingPwTxFault (2), psnFacingPwRxFault (3), PWE3 TC MIB February 2006 psnFacingPwTxFault (4) } PwFragSize ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "If set to value other than zero, it indicates desired fragmentation to the value set. If set to zero, fragmentation is not desired for PSN bound packets. " SYNTAX Unsigned32 PwFragStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The status of the fragmentation process based on local configuration and the peer capability. noFrag(0) bit indicates that local configuration is for no fragmentation. cfgFragGreaterThanPsnMtu(1) bit indicates the local desire to fragment, but the fragmentation size desired is greater than the MTU available at the PSN between the nodes. Fragmentation is not done in this case. cfgFragButRemoteIncapable(2) bit indicates that the local configuration indicates the desire for fragmentation but the peer is not capable of fragmentation. cfgFragFcsLengthMismatch(3) bit indicates that there is a mismatch between the FCS size between the local configuration and the peer configuration. fragEnabled(4) bit indicates that both the local was configured for fragmentation and the peer has the cabability to accept fragmented packets, and the FCS size is equal in both peers. " SYNTAX BITS { noFrag (0), cfgFragGreaterThanPsnMtu (1), cfgFragButRemoteIncapable (2), remoteFragCapable (3), fragEnabled (4) } END -- Copyright (C) The Internet Society (2006). -- -- This document is subject to the rights, licenses and restrictions -- contained in BCP 78, and except as set forth therein, the authors -- retain all their rights. -- -- This document and the information contained herein are provided on -- an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE -- REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, -- EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT -- THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR -- ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A -- PARTICULAR PURPOSE. -- -- 0 Intellectual Property Notice -- -- The IETF takes no position regarding the validity or scope of any -- Intellectual Property or other rights that might be claimed to -- pertain to the implementation or use of the technology described in -- this document or the extent to which any license under such rights -- might or might not be available; neither does it represent that it -- has made any effort to identify any such rights. Information on -- the IETF's procedures with respect to rights in standards-track and -- standards-related documentation can be found in BCP-11 [RFC2028]. -- -- Copies of IPR disclosures made to the IETF Secretariat and any -- assurances of licenses to be made available, or the result of an -- attempt made to obtain a general license or permission for the use -- of such proprietary rights by implementers or users of this -- specification can be obtained from the IETF on-line IPR repository -- at http://www.ietf.org/ipr." -- -- The IETF invites any interested party to bring to its attention any -- copyrights, patents or patent applications, or other proprietary -- rights that may cover technology that may be required to implement -- this standard. Please address the information to the IETF -- Executive Director.