eqptHolderPlannedType

ASAM-EQUIP-MIB · .1.3.6.1.4.1.637.61.1.23.2.1.3
Commands MIB view Table view

Object

column mandatory r/w SNMPv2-TCDisplayString 
A string representing the planned type of equipment holder.
If the equipment holder is planned, the string consists of a
mnemonic, identifying the holder type.
This object is only writable for the entries that represent a shelf.
Other entries get a value corresponding to the detected equipment
practice type.
              
Following values are valid:
              
System-types:
=============
LAUS          Large ASAM US market (6 racks, 3 shelves per rack)
LAEU          Large ASAM EU market (6 racks, 3 shelves per rack)
LEEU          Large ESAM EU market (7 racks, 4 shelves per rack)
LEUS          Large ESAM US market (7 racks, 4 shelves per rack)
LNEU          Large New EquipmentPractise EU market(7 racks, 4 shelves
              per rack)
LEWW          Large ESAM World Wide (7 racks, 4 shelves per rack)
LNWW    Large ESAM World Wide (7 racks, 4 shelves per rack)
              
Rack-types:
===========
ALTR-A        ADSL Line Termination Rack version A (US)
ALTR-E        ADSL Line Termination Rack version E (ETSI 2200mm)
              
Shelf-types:
============
<SHELF_MNEMONIC>  A shelf of a specific type.  Refer to the ETSI
                  Configurations and US Configurations documents
                  for the list of shelf types that are supported
                  in a given system release.
              
NOT_PLANNED       The shelf is not planned.
              
NOT_ALLOWED       Shelf planning is not allowed in this position.
              
ALCATEL NOTE:
   SUPPORT: YES   INSRVMOD: NO              RANGE: See above
   PERSIST: YES   DEFVALUE: 'NOT_PLANNED'   UNITS: -

Context

MIB
ASAM-EQUIP-MIB
OID
.1.3.6.1.4.1.637.61.1.23.2.1.3
Type
column
Access
readwrite
Status
mandatory
Parent
eqptHolderEntry

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ASAM-EQUIP-MIB' -M '/opt/observium/mibs/alcatel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ASAM-EQUIP-MIB::eqptHolderPlannedType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ASAM-EQUIP-MIB' -M '/opt/observium/mibs/alcatel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ASAM-EQUIP-MIB::eqptHolderPlannedType.<eqptHolderId>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ASAM-EQUIP-MIB' -M '/opt/observium/mibs/alcatel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ASAM-EQUIP-MIB::eqptHolderPlannedType'

Syntax

SNMPv2-TCDisplayString
Source
SNMPv2-TCDisplayString
Base type
OctetString
Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
          
character set, as defined in pages 4, 10-11 of RFC 854.
          
To summarize RFC 854, the NVT ASCII repertoire specifies:
          
  - the use of character codes 0-127 (decimal)
          
  - the graphics characters (32-126) are interpreted as
    US ASCII
          
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854
          
  - the other 25 codes have no standard interpretation
          
  - the sequence 'CR LF' means newline
          
  - the sequence 'CR NUL' means carriage-return
          
  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.
          
  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)
          
Any object defined using this syntax may not exceed 255
characters in length.

Values & Constraints

Type Constraints
range: 0..255