ERICSSON-TC-MIB
- Registered at
- 1.3.6.1.4.1.193.183.1
- Last updated
- 2021-02-04 00:00
- Organization
- Ericsson AB
- Revisions
- 2021-02-04 00:00, 2017-08-11 00:00, 2017-04-13 00:00, 2016-06-24 00:00, 2008-10-17 00:00
- Namespace
- ericsson
- Source file
ERICSSON-TC-MIB- Digest
sha256:6ffa0c21019be8183703c427213a9aff58f45a2be888b14820a21cc6e21e9d12
Description
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.
Contact
IMF
Imports
| From | Symbols |
|---|---|
| ERICSSON-TOP-MIB | ericssonModules |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION |
Imported by
2 module(s) in this corpus import this one.
Load order
Every file a consumer needs in order to load this module, dependencies first.
ERICSSON-TC-MIB ERICSSON-TOP-MIB SNMPv2-CONF SNMPv2-SMI SNMPv2-TC
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| EriMO TEXTUAL-CONVENTION 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. | current | |||
| EriPath TEXTUAL-CONVENTION An abridged instance-identifier in YANG that references a resource within the Managed Element. 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. | current |