MIB Browser

ERICSSON-TC-MIB

Ericsson AB
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.
Organization
Ericsson AB
Root OID
1.3.6.1.4.1.193.183.1
Last updated
Objects
1
Source
Show full MIB
snmptranslate -m ERICSSON-TC-MIB -Tp
snmpwalk -v2c -c <community> -m ERICSSON-TC-MIB <host> 1.3.6.1.4.1.193.183.1

Imports

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

OID tree

NameOIDTypeAccessStatus
IericssonTCMIB1.3.6.1.4.1.193.183.1

Textual conventions

EriMO OCTET STRING (SIZE (4..150))

Display hint: 1a

The 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.
EriPath OCTET STRING (SIZE (4..150))

Display hint: 1a

An 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.