CIE1000-TC

File: CIE1000-TC.mib (18903 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC

Imported symbols

Integer32 Gauge32 TEXTUAL-CONVENTION

Defined Types

CIE1000Integer8  
Represents an 8-bit signed integer.
TEXTUAL-CONVENTION    
  INTEGER -128..127  

CIE1000Integer16  
Represents a 16-bit signed integer.
TEXTUAL-CONVENTION    
  INTEGER -32768..32767  

CIE1000Integer64  
Represents a 64-bit signed integer encoded as two's complement in network order.
TEXTUAL-CONVENTION    
  OCTET STRING Size(8)  

CIE1000Unsigned8  
Represents an 8-bit unsigned integer.
TEXTUAL-CONVENTION    
  Gauge32 0..255  

CIE1000Unsigned16  
Represents a 16-bit unsigned integer.
TEXTUAL-CONVENTION    
  Gauge32 0..65535  

CIE1000Unsigned64  
Represents a 64-bit unsigned integer encoded in network order.
TEXTUAL-CONVENTION    
  OCTET STRING Size(8)  

CIE1000TimeStamp  
Represents a timestamp in seconds since epoch. The data is encoded as a 64-bit unsigned integer in network order.
TEXTUAL-CONVENTION    
  OCTET STRING Size(8)  

CIE1000EtherType  
Represents a 16-bit Ethernet Type.
TEXTUAL-CONVENTION    
  Gauge32 0..65535  

CIE1000InterfaceIndex  
The interface index is a unique identification of an arbitrary interface in the system. Example of interfaces could be physical ports, aggregations, VLAN interfaces and others. The interface indexes used by the system is deterministic and is chosen using the schema below. NONE 0 - 0 (standalone/stacking) VLAN 1 - 4.095 (standalone/stacking) Usid1 /ports 1.000.001 - 1.000.999 (standalone/stacking) .. Usid16/ports 16.000.001 - 16.000.999 (stacking) Usid1 /llagr 1.005.001 - 1.005.999 (standalone/stacking) .. Usid16/llagr 16.005.001 - 16.005.999 (stacking) GLAG 100.000.001 - 100.000.999 (standalone/stacking) EVC 200.000.001 - 200.099.999 (standalone) MPLS links 300.000.001 - 300.009.999 (standalone) MPLS tunnels 400.000.001 - 400.099.999 (standalone) MPLS pseudo-wires 500.000.001 - 500.099.999 (standalone) MPLS lsp 600.000.001 - 600.099.999 (standalone)
TEXTUAL-CONVENTION    
  Integer32 0..2147483647  

CIE1000RowEditorState  
The RowEditorState is used both as a column in the dynamic tables, and as a object in the row editor. The meaning of the row editor state depends on the context where it is used. In either case it is used to implement actions related to add or delete columns in dynamic tables. When used as a column in a dynamic table ---------------------------------------- Read back of this value will always be zero. If the value 1 is written to this object the given row will be deleted. Values different from 0 and 1 are reserved for future use and should not be used. When used as an object in a row editor -------------------------------------- A value used to control the row editor protocol. The values 0-255 are reserved to be used in the row editor protocol, all other values tokes the manager can use to reserve the row editor. The values 0, 1 and 2 is currently use din the row editor protocol while the values 3-255 are reserved for future use. Following is the names of the values used in the row editor protocol: 0: IDLE STATE 1: CLEAR-ACTION 2: COMMIT-ACTION 256-4294967295: MANAGER-ID The following state machine defines the row editor protocol: +--------------+ +------------------+ | |<----------------| | | | CLEAR | | | IDLE |<----------------| RESERVED | | | COMMIT | | | |---------------->| | +--------------+ MANAGER-ID +------------------+ When the RowEditorState is being read one will either read the value zero: meaning that the row editor is in the idle state. Or a value between 256-4294967295: meaning that the row editor is reserved with the given ID. When the row editor is in the IDLE state the manager may try to reserve it by writing its own MANAGER-ID to the RowEditorState object. If the write succeeds the manager can read-back the MANAGER-ID. When the row editor is in the RESERVED state the manager can either clear the changes by writing CLEAR, or it can commit the changes by writing COMMIT. Both actions will cause the state to jump back to the IDLE state, but only the COMMIT will cause the row to be added.
TEXTUAL-CONVENTION    
  Gauge32  

CIE1000Percent  
An integer in the range 0..100 representing a percent value
TEXTUAL-CONVENTION    
  Gauge32 0..100  

CIE1000PortList  
A list of ports that may be distributed across more stack units. The type should be interpreted as a sequence of bits, each bit representing a port. If a bit is set (1) the represented port is included in the port list. If a bit is not set (0) the represented port is not included in the port list. Each switch in a stack is represented by an ID in the range [1-16] both included. Each switch in the stack has a reserved range of 64 bits or 8 bytes in this octet string. If the switch is not stackable it will be represented as 'Switch 1'. The switch with ID 1 owns the byte range 0-7, switch ID 2 owns the byte range 8-15, etc. The physical ports are represented by the bit index relative to the range owned by a given switch. Bit number zero is the least significant bit of the first entry in the byte sequence owned by the switch (port number 0 if such a port exists). Bit number one is the second least significant bit in the first byte of the range owned by the switch. This is illustrated below: Port 7 switch 1 Port 7 switch 2 ^ Port 0 switch 1 ^ Port 0 switch 2 | ^ Port 15 switch 1 | ^ Port 63 switch 2 | | ^ Port 8 switch 1 | | ^ Port 56 switch 2 | | | ^ Port 23 switch 1 | | ^ | | | | ^ Port 16 switch 1 | | | | | | | ^ Port 63 switch 1 | | | | | | | ^ Port 56 switch 1 | | | | | | | | ^ | | | | | | | | | | | | | v v v v v v v v v v v v +---------------------------------------------------------------+ |byte 0|byte 1|byte 2|...|byte 7|byte 8|...|byte 15|...|byte 127| +---------------------------------------------------------------+ \______________ ______________/ \________ ______/ \____ ____/ \/ \/ \/ Switch 1 Switch 2 Switch 3-16 IE1000-8P2S-LM fa1/8 fa1/7 fa1/6 fa1/5 fa 1/4 fa 1/3 fa 1/2 fa 1/1 x x x x x x gi1/10 1/9 0 0 0 1 0 0 0 0 1111 1110 0000 1001 F E 07 IE1000-4P2S-LM 6 port IE1000-4T1T 5 port IE100-6T2T 8 port The octet string is truncated at most significant byte which is not zero. An empty port list is encoded as [0x00]. Example: a non-stackable switch where 48 is the highest port number needs seven bytes to represent a complete port list. If the port list only contains port 1, 2 and 20 then the SNMP encoded port list is: [0x06, 0x00, 0x10]. NOTE: Even though port 0 does not exists in the port map it is still represented by a bit in this port list. The same is true for the higher indices. Configuring non-existing ports using the port list will have no effect on the target.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..128)  

CIE1000Vlan  
An integer representing a VLAN ID.
TEXTUAL-CONVENTION    
  Gauge32 1..4095  

CIE1000VlanOrZero  
An integer representing a VLAN ID or zero.
TEXTUAL-CONVENTION    
  Gauge32 0..4095  

CIE1000VlanListQuarter  
A list representing 1024 VLAN IDs. The type should be interpreted as a sequence of bits, each bit representing one VLAN ID. If a bit is set (1) the represented VLAN is included in the VLAN list. If a bit is not set (0) the represented VLAN is not included in the VLAN list. The least significant bit of each byte represents a smaller VLAN ID than a more significant bit of a byte. If for example the VLAN list represents VLAN IDs from 0 to 1023, bit 0 of the first byte represents VLAN ID 0, bit 1 of the first byte represents VLAN ID 1, and so on. The most significant bit of the 128th byte therefore represents VLAN ID 1023. An implementation that needs to represent all 4K VLANs will divide the VLAN list into four equally sized objects. VLAN ID 0 is included in the first object even though it is not used.
TEXTUAL-CONVENTION    
  OCTET STRING Size(128)  

CIE1000DisplayString  
Represents textual information taken from the ASCII character set, as defined in ANSI X3.4-1986 with some restrictions. The following rules apply: - only character codes 32-126 (decimal) are supported - the graphics characters (32-126) are interpreted as US ASCII Any object defined using this syntax may not exceed 255 characters in length.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..255)  

CIE1000InetAddress  
Represents an internet address. Following is the list of supported address types: IPv4 address, IPv6 address, Domain name or No-Address. The addresses are encoded as a human readable string as defined here: - IPv4 address is encoded as 'a.b.c.d' where a-d are integer numbers in the range from 0-255. - IPv6 address is encoded as defined in RFC5952. - Domain names are passed through in their native representation. - No-Address is encoded as the string literal: ''. This type is not allowed to be used as indices in tables.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..253)  

CIE1000IpAddress  
Represents an internet address. Following is the list of supported address types: IPv4 address, IPv6 address or No-Address. The addresses are encoded as a human readable string as defined here: - IPv4 address is encoded as 'a.b.c.d' where a-d are integer numbers in the range from 0-255. - IPv6 address is encoded as defined in RFC5952. - No-Address is encoded as the string literal: ''.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..46)  

CIE1000VclProtoEncap  
Represents a protocol encapsulation, needed by the Protocol part of the VCL module. The protocol encapsulation type, along with the respective encapsulation fields are encoded as an octet string of variable size ranging from 3 to 6. Currently, the VCL module only supports three protocol encapsulation types: - Ethernet II encapsulation, defined by setting the first octet to 1. Two more octets are used to describe the 'type' field. The type can range from 0x0600-0xffff. I.e. ETH2: 1 TYPE {byte 0} {byte 1 + byte 2} E.g. 1.2048 := ETH2, TYPE = 0x0800 - LLC SNAP encapsulation, defined by setting the first octet to 2. Three more octets are used for the 'OID' field and two for the 'PID' field. The OID can range from 0x000000-0xffffff and the PID from 0x0000-0xffff. Special case is when OID is 0x000000; then PID can only range from 0x0600-0xffff. I.e. LLC-SNAP: 2 OUI[0] OUI[1] OUI[2] PID {byte 0} {byte 1} {byte 2} {byte 3} {byte 4 + byte 5} E.g. 2.0.1.24.562 := SNAP, OUI = 0x00:01:18, PID = 0x0232 - LLC Other encapsulation, defined by setting the first octet to 3. Two more octets are used for the 'DSAP' and 'SSAP' fields respectively. Each of these two fields can range from 0-255 I.e. LLC-OTHER: 3 DSAP SSAP {byte 0} {byte 1} {byte 2} E.g. 3.42.85 := LLC, DSAP = 0x2A, SSAP = 0x55 Default, empty encapsulation is 0.0.0
TEXTUAL-CONVENTION    
  OCTET STRING Size(3..6)  

CIE1000BitType  
Represents a bit selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), zero(1), one(2)  

CIE1000DestMacType  
Represents a destination MAC type selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), unicast(1), multicast(2), broadcast(3)  

CIE1000VcapKeyType  
Represents a VCAP key type selector.
TEXTUAL-CONVENTION    
  INTEGER normal(0), doubleTag(1), ipAddr(2), macIpAddr(3)  

CIE1000VlanTagPriority  
VLAN priority.
TEXTUAL-CONVENTION    
  INTEGER any(0), value0(1), value1(2), value2(3), value3(4), value4(5), value5(6), value6(7), value7(8), range0to1(9), range2to3(10), range4to5(11), range6to7(12), range0to3(13), range4to7(14)  

CIE1000VlanTagType  
Represents a VLAN tag type selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), untagged(1), tagged(2), cTagged(3), sTagged(4)  

CIE1000ASRType  
Represents an Any/Specific/Range selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), specific(1), range(2)  

CIE1000AdvDestMacType  
Represents a destination MAC type selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), unicast(1), multicast(2), broadcast(3), specific(4)  

CIE1000ASType  
Represents an Any/Specific selector.
TEXTUAL-CONVENTION    
  INTEGER any(0), specific(1)  

CIE1000SfpTransceiver  
This enumerations show the SFP transceiver type.
TEXTUAL-CONVENTION    
  INTEGER none(0), notSupported(1), sfp100FX(2), sfp1000BaseT(7), sfp1000BaseCx(8), sfp1000BaseSx(9), sfp1000BaseLx(10), sfp1000BaseX(11), sfp2G5(12), sfp5G(13), sfp10G(14)  

CIE1000MepDmTimeUnit  
Calculation Delay Measurement time unit.
TEXTUAL-CONVENTION    
  INTEGER microSeconds(0), nanoSeconds(1)  

CIE1000MepInstanceDirection  
The MEP instance direction.
TEXTUAL-CONVENTION    
  INTEGER down(0), up(1)  

CIE1000MepTxRate  
MEP PDU transmission rate.
TEXTUAL-CONVENTION    
  INTEGER invalid(0), frames300PerSecond(1), frames100PerSecond(2), frames10PerSecond(3), frames1PerSecond(4), frames6PerMinute(5), frames1PerMinute(6), frames6PerHour(7)  

CIE1000PortStatusSpeed  
This enumerations show the current interface speed.
TEXTUAL-CONVENTION    
  INTEGER undefined(0), speed10M(1), speed100M(2), speed1G(3), speed2G5(4), speed5G(5), speed10G(6), speed12G(7)