ERICSSON-TC-MIB
Ericsson ABThis MIB document includes textual conventions
that can be used by all of the Ericsson group.
The intention is to have shared definitions such
that integration and SNMP development are made
easier.
Document number: 2/196 03-CXC 172 7549.snmptranslate -m ERICSSON-TC-MIB -Tpsnmpwalk -v2c -c <community> -m ERICSSON-TC-MIB <host> 1.3.6.1.4.1.193.183.1Imports
| ERICSSON-TOP-MIB | ericssonModules |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Bits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| IericssonTCMIB | 1.3.6.1.4.1.193.183.1 | |||
identity This MIB document includes textual conventions
that can be used by all of the Ericsson group.
The intention is to have shared definitions such
that integration and SNMP development are made
easier.
Document number: 2/196 03-CXC 172 7549. | ||||
Textual conventions
EriMOOCTET STRING (SIZE (4..150))Display hint:
1aThe 3GPP naming convention shall be used as the format for the managed object parameter. Note that the granularity MUST be sufficient to guarantee unique alarm states and relevant resource identification to the operator. NOTE: The DN should be *relative* to the Managed Element's *own* root.EriPathOCTET STRING (SIZE (4..150))Display hint:
1aAn Abridged YANG Instance-Identifier that references a resource within the Managed Element. Prefixes used MUST be the ones defined in the YANG module statement's prefix substatement. A prefix SHALL be omitted if it is the same as the previous prefix on the ancestor axis. For example: /ex:system/server[ip='192.0.2.1'][port='80'] See: YANG module ericsson-yang-types. See also: RFC 7950 Section 9.13. NOTE: The granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator.