MIB Browser

IANA-GMPLS-TC-MIB

Standards (IETF)
Copyright (C) The IETF Trust (2007).  The initial version
of this MIB module was published in RFC 4802.  For full legal
notices see the RFC itself.  Supplementary information
may be available on:
http://www.ietf.org/copyrights/ianamib.html
Organization
IANA
Root OID
1.3.6.1.2.1.152
Last updated
Objects
1
Source
Show full MIB
snmptranslate -m IANA-GMPLS-TC-MIB -Tp
snmpwalk -v2c -c <community> -m IANA-GMPLS-TC-MIB <host> 1.3.6.1.2.1.152

Imports

SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIBits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso, mib-2
SNMPv2-TCDisplayString, PhysAddress, TEXTUAL-CONVENTION

OID tree

NameOIDTypeAccessStatus
IianaGmpls1.3.6.1.2.1.152

Textual conventions

IANAGmplsAdminStatusInformationTC Bits

administrativelyDown(30) callControl(28) deleteInProgress(31) handover(25) inhibitAlarmCommunication(27) lockout(26) oamAlarmsEnabled(24) oamFlowsEnabled(23) reflect(0) reserved1(1) reserved10(10) reserved11(11) reserved12(12) reserved13(13) reserved14(14) reserved15(15) reserved16(16) reserved17(17) reserved18(18) reserved19(19) reserved2(2) reserved20(20) reserved21(21) reserved22(22) reserved3(3) reserved4(4) reserved5(5) reserved6(6) reserved7(7) reserved8(8) reserved9(9) testing(29)

This data type determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471.  Setting this object to a non-zero
value will result in the inclusion of the Admin Status

object or TLV on signaling messages.

This textual convention is strongly tied to the
Administrative Status Information Flags sub-registry of
the GMPLS Signaling Parameters registry managed by IANA.
Values should be assigned by IANA in step with the
Administrative Status Flags sub-registry and using the
same registry management rules.  However, the actual
values used in this textual convention are solely
within the purview of IANA and do not necessarily match
the values in the Administrative Status Information
Flags sub-registry.

The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.  (The
latest arrangements can be obtained by contacting the
IANA.)

Requests for new values should be made to IANA via
email (iana&iana.org).
IANAGmplsGeneralizedPidTC INTEGER

ansiEtsiPdh(38) asynchDS1T1(16) asynchDS2T2(10) asynchDS3T3(6) asynchE1(13) asynchE3(7) asynchE4(5) atm(32) bitsynchDS1T1(17) bitsynchDS2T2(11) bitsynchE3(8) bytesynch31ByDS0(15) bytesynchDS1T1(18) bytesynchE1(14) bytesynchE3(9) dVBASI(65) digitalwrapper(36) dqdb(42) ds1ESFAsynch(23) ds1SFAsynch(22) ds3CBitParityAsynch(25) ds3M23Asynch(24) ethernet(33) ethernet802dot3Only(46) ethernetV2DixOnly(45) fddi(41) fiberChannel3(43) framedGFP(59) g709BSNT(52) g709BSOT(51) g709CBRb(50) g709CBRorCBRa(49) g709ESCON(56) g709FICON(57) g709FiberChannel(58) g709ODU125G(66) g709ODUAny(67) g709ODUj(47) g709OTUk(48) gfpEthernetMAC(54) gfpEthernetPHY(55) gfpIPorPPP(53) hdlc(44) infiniBand(62) lambda(37) lapsSdh(40) nullTest(68) posNoScramble16BitCrc(28) posNoScramble32BitCrc(29) posScramble16BitCrc(30) posScramble32BitCrc(31) randomTest(69) reservedByRFC3471first(12) reservedByRFC3471second(20) reservedByRFC3471third(21) sDI(63) sDI1point001(64) sTM1(60) sTM4(61) sdhSonet(34) sixtyfourB66BGFPFEthernet(70) stsSpeHovc(27) unknown(0) vc1vc12(19) vtLovc(26)

This data type is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol.

This textual convention is strongly tied to the Generalized
PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
registry managed by IANA.  Values should be assigned by
IANA in step with the Generalized PIDs (G-PID) sub-registry
and using the same registry management rules.  However, the
actual values used in this textual convention are solely
within the purview of IANA and do not necessarily match the
values in the Generalized PIDs (G-PID) sub-registry.

The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.  (The
latest arrangements can be obtained by contacting the
IANA.)

Requests for new values should be made to IANA via
email (iana&iana.org).
IANAGmplsLSPEncodingTypeTC INTEGER

tunnelDigitalPath(12) tunnelLine(14) tunnelLspAnsiEtsiPdh(3) tunnelLspDigitalWrapper(7) tunnelLspEthernet(2) tunnelLspFiber(9) tunnelLspFiberChannel(11) tunnelLspLambda(8) tunnelLspNotGmpls(0) tunnelLspPacket(1) tunnelLspSdhSonet(5) tunnelOpticalChannel(13)

This type is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol.

This textual convention is strongly tied to the LSP
Encoding Types sub-registry of the GMPLS Signaling
Parameters registry managed by IANA.  Values should be
assigned by IANA in step with the LSP Encoding Types
sub-registry and using the same registry management rules.
However, the actual values used in this textual convention
are solely within the purview of IANA and do not
necessarily match the values in the LSP Encoding Types
sub-registry.

The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.  (The
latest arrangements can be obtained by contacting the
IANA.)

Requests for new values should be made to IANA via
email (iana&iana.org).
IANAGmplsSwitchingTypeTC INTEGER

dcsc(125) evpl(30) fsc(200) l2sc(51) lsc(150) otntdm(110) pbb(40) psc1(1) psc2(2) psc3(3) psc4(4) tdm(100) unknown(0) wsonlsc(151)

This type is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol.

This textual convention is strongly tied to the Switching
Types sub-registry of the GMPLS Signaling Parameters
registry managed by IANA.  Values should be assigned by
IANA in step with the Switching Types sub-registry and
using the same registry management rules.  However, the
actual values used in this textual convention are solely
within the purview of IANA and do not necessarily match
the values in the Switching Types sub-registry.

The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.  (The
latest arrangements can be obtained by contacting the
IANA.)

Requests for new values should be made to IANA via
email (iana&iana.org).