MIB Specifications
This chapter describes each Management Information Base (MIB) on the Cisco RFGW-10. Each description lists any constraints on how the MIB or its object identifiers (OIDs) are implemented on the Cisco RFGW-10.
Unless noted otherwise, the Cisco RFGW-10 implementation of a MIB follows the standard MIB that has been defined. Any MIB table or object not listed in the tables is implemented as defined in the standard MIB definition.
Note Not all MIBs included in a Cisco IOS or IOS-XE software release are fully supported by the Cisco RFGW-10. Some MIBs are not supported at all. Other MIBs might work, but they have not been tested on the Cisco RFGW-10. In addition, some MIBs are deprecated but cannot be removed from the software. When a MIB is included in the image, this does not necessarily mean it is supported by the Cisco RFGW-10 platform.
Overview of MIB Support
Support for a particular MIB is included as part of the Cisco IOS or IOS-XE software release. Each version of the Cisco IOS or IOS-XE software contains code that responds to SNMP requests for objects that are in the MIBs that are supported in that release for that particular software image.
Each new release of Cisco IOS or IOS-XE software typically changes that support to some extent, usually involving one or more of the following:
- Fixing a caveat or software defect that is preventing the proper use of the MIB
- Updating the software to support the latest version of the MIB or to support optional objects that were not supported previously
- Adding support for new MIBs that are part of a new feature that is being introduced
The fact that a MIB might be included in a Cisco IOS or IOS-XE software release does not imply that the MIB is fully supported on the Cisco RFGW-10. Similarly, the fact that you can access a particular object in a MIB does not imply that the object is fully supported either.
Note As a general rule, deprecated objects and MIBs should not be used, because they have been replaced by other, more functional objects and MIBs. Also, deprecated objects and MIBs can be removed in a future release without notice.
Note The exact MIB support depends on both the Cisco IOS or IOS-XE software image and the Cisco IOS or IOS-XE software release being used.
Table 3-1 lists the MIBs that are included in Cisco IOS Release 12.2(44) SQ for Cisco RFGW-10. Unless otherwise indicated, each MIB is included in all software images for the indicated release. In some cases, MIBs that are included in the software image are not actually supported or are only partially supported.
Table 3-1 Included MIBs on Cisco RFGW-10 in Cisco IOS Release 12.2(44)SQ.
Cisco RFGW-10
in Cisco IOS Release 12.2(44)SQ
|
|
CISCO-BULK-FILE-MIB |
|
CISCO-CDP-MIB |
|
CISCO-CLASS-BASED-QOS-MIB |
|
CISCO-CONFIG-COPY-MIB |
|
CISCO-CONFIG-MAN-MIB |
|
CISCO-ENTITY-EXT-MIB |
|
CISCO-ENTITY-FRU-CONTROL-MIB |
|
CISCO-ENTITY-SENSOR-MIB |
|
CISCO-ENVMON-MIB |
|
CISCO-FLASH-MIB |
|
CISCO-FTP-CLIENT-MIB |
|
CISCO-IMAGE-MIB |
|
CISCO-L2L3-INTERFACE-CONFIG-MIB |
|
CISCO-LAG-MIB |
|
CISCO-MAC-NOTIFICATION-MIB |
|
CISCO-PAGP-MIB |
|
CISCO-PING-MIB |
|
CISCO-PORT-SECURITY-MIB |
|
CISCO-PORT-STORM-CONTROL-MIB |
|
CISCO-PRIVATE-VLAN-MIB |
|
CISCO-PROCESS-MIB |
|
CISCO-RF-MIB |
|
CISCO-RTTMON-MIB |
|
CISCO-STP-EXTENSIONS-MIB |
|
CISCO-SYSLOG-MIB |
|
CISCO-VLAN-MEMBERSHIP-MIB |
|
CISCO-VTP-MIB |
|
DOCS-CABLE-DEVICE-MIB |
9908190000Z |
DOCS-IF-M-CMTS-MIB |
200511160000Z |
DOCS-IF-MIB |
200212200000Z |
DTI-MIB |
200606280000Z |
ENTITY-MIB |
9912070000Z |
ETHERLIKE-MIB |
|
IEEE8021-PAE-MIB |
|
IEEE8023-LAG-MIB |
|
IF-MIB |
9611031355Z |
RMON-MIB |
|
SCTE-HMS-MPEG-MIB |
200706051200Z |
SCTE-HMS-QAM-MIB |
200708231200Z |
SMON-MIB |
|
SNMP-COMMUNITY-MIB |
200003060000Z |
SNMP-FRAMEWORK-MIB |
9901190000Z |
SNMP-MPD-MIB |
9905041636Z |
SNMP-NOTIFICATION-MIB |
9808040000Z |
SNMP-PROXY-MIB |
|
SNMP-TARGET-MIB |
9808040000Z |
SNMP-USM-MIB |
9901200000Z |
SNMPv2-MIB |
9511090000Z |
SNMP-VACM-MIB |
9901200000Z |
TCP-MIB |
|
UDP-MIB |
|
Table 3-2 Included MIBs on Cisco RFGW-10 in Cisco IOS Release IOS-XE 3.2.0SQ
Cisco RFGW-10
in Cisco IOS-XE Release IOS-XE 3.2.0SQ
|
|
DOCS-DRF-MIB |
200812090000Z |
Table 3-3 Included MIBs on Cisco RFGW-10 in Cisco IOS Release IOS-XE 3.3.0SQ
Cisco RFGW-10
in Cisco IOS-XE Release IOS-XE 3.3.0SQ
|
|
SCTE-HMS-MPEG-MIB |
200810031700Z |
Table 3-4 Included MIBs on Cisco RFGW-10 in Cisco IOS Release IOS-XE 3.3.1SQ
Cisco RFGW-10
in Cisco IOS-XE Release IOS-XE 3.3.1SQ
|
|
CISCO-ENTITY-REDUNDANCY-MIB |
200510010000Z |
Table 3-5 Included MIBs on Cisco RFGW-10 in Cisco IOS Release IOS-XE 3.4.0SQ
Cisco RFGW-10
in Cisco IOS-XE Release IOS-XE 3.4.0SQ
|
|
SCTE-HMS-MPEG-MIB |
200810031700Z |
Table 3-6 Included MIBs on Cisco RFGW-10 in Cisco IOS Release IOS-XE 3.4.1SQ
Cisco RFGW-10
in Cisco IOS-XE Release IOS-XE 3.4.1SQ
|
|
SCTE-HMS-QAM-MIB |
200807160305Z |
MIB Specifications
This section gives a short summary of each MIB, along with the MODULE-IDENTITY and top-level object identifier (OID) that can be used to access the MIB when using an SNMP manager.
CISCO-ENTITY-REDUNDANCY-MIB
The CISCO-ENTITY-REDUNDANCY-MIB supports configuration, control, and monitoring of redundancy protection for various kinds of components on the managed devices.
Effective with Cisco IOS-XE Release 3.3.1SQ, the Cisco RFGW-10 supports the CISCO-ENTITY-REDUNDANCY-MIB. The Cisco RFGW-10 supports this MIB for Cisco DS-384 and Cisco DS-48 line card redundancy.
It is meant to be generic enough to handle basic redundancy control and monitoring for many types of redundant member components and redundancy architectures as long as there is an Entity MIB entPhysicalIndex and entPhysicalVendorType assigned to each member component. It is designed so that the tables can be augmented in other extension MIBS which build upon this MIB by adding additional objects that may be specific to a particular type of redundancy or member component. This MIB can also be used in cases where some types of redundancy groups and members do not require explicit user configuration. One example may be redundant fan assemblies. In those cases, the managed system should internally assign group and member indexes, so that it can provide read-only access to the group and member tables. This allows MIB monitoring for these types of redundant entities.
The CISCO-ENTITY-REDUNDANCY-MIB is implemented for read only objects. The OID for CISCO-ENTITY-REDUNDANCY-MIB is 1.3.6.1.4.1.9.9.498.
Version: 200510010000Z
MIB Objects
The table below shows the CISCO-ENTITY-REDUNDANCY-MIB table and objects:
Table 7 CISCO-ENTITY-REDUNDANCY-MIB Tables and Objects
|
|
|
Lists the basic types of redundancy groups supported on the managed device along with additional information about each group type. |
|
Lists all entPhysicalVendorTypes allowed as members for a specific ceRedunGroupTypeIndex on the managed device, inclusive for all configurable values for ceRedunType, ceRedunScope, ceRedunArch, and so on. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again. Note Although a specific ceRedunGroupTypeIndex may allow groups of different entPhysicalVendorTypes, managed devices typically enforce all members within a specific group to have the same entPhysicalVendorType. |
ceRedunInternalStatesTable
|
Allows the managed system to report a read-only list of internal state numbers and the corresponding descriptions which apply for the members of a particular redundancy group type. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again. |
ceRedunSwitchoverReasonTable
|
Allows the managed system to report a read-only list of switchover reason indexes and the corresponding descriptions. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again. |
|
Lists group configuration and status objects for a specific redundancy group. However, the members are configured separately in the ceRedunMbrTable. |
|
Lists the group members and generic redundancy objects which are associated with configuring redundancy group members. The switchover granularity should be for one member at a time. If a member is allowed to be an individual port, then switchovers on multi-port line cards would be expected to take place independently for each port on the line card. But if the members are full line cards, then all ports on the line card would be expected to switch at the same time. The Cisco RFGW-10 supports only full line card redundancy. |
|
Lists the redundancy status and other read-only redundancy objects which are associated with redundancy group members. Status associated with member alarm conditions should be reported separately using the CISCO-ENTITY-ALARM-MIB. |
|
Allows switchover commands to be sent to members of configured redundancy groups. |
ceRedunGroupTypesTable
The table below lists the MIB objects in ceRedunGroupTypesTable:
Table 8 MIB Objects in ceRedunGroupTypesTable
|
|
|
Contains an index assigned for each type of redundancy group supported on a managed system that requires its own table listing entPhysicalVendorTypes allowed as members for its groups. |
|
Indicates the textual name of the redundancy group type. The value of this object should be the name of the redundancy group type assigned by the local device as it appears for display commands entered in the device console. Examples are port-group, line card-group, fan-group, and so on. |
|
Indicates the current count of redundancy groups for a specific ceRedunGroupTypeIndex. This count indicates the number of rows in the ceRedunGroupTable for a specific ceRedunGroupTypeIndex. |
ceRedunNextUnusedGroupIndex
|
Indicates the next unused group index available for configuring a new redundancy group for this group type. For Cisco RFGW-10, there is no unused group index and this object returns the value 0. |
|
Contains the maximum number of primary plus secondary members allowed in a group for a specific ceRedunGroupTypeIndex. If only 1:1 or 1+1 is supported, this should be 2. If the maximum number is unknown or not determinable, the managed system should return 0. The Cisco RFGW-10 supports 1:1 and 1:N redundancy and the value of this object is set to 10. |
|
Contains a boolean object to indicate whether this type of redundancy group uses the ceRedunGroupString object as a group name identifier. If it is reported as 'true', the ceRedunGroupString name must contain no internal spaces. If it is reported as 'false', the ceRedunGroupString object is just used as an optional description for the group rather than as the group name. For Cisco RFGW-10, it is reported as ‘false’. |
ceRedunGroupDefinitionChanged
|
Contains the value of sysUpTime when there was the most recent change to any objects in the ceRedunGroupTypesTable except for ceRedunGroupCounts or ceRedunNextUnusedGroupIndex. The sysUpTime should also reflect changes to either the ceRedunVendorTypesTable, ceRedunInternalStatesTable, or ceRedunSwitchoverReasonTable. Normally these objects are static, but if there was an in service upgrade to the software image of the managed system then the tables may change and should be read again. If there has been no change since the last initialization of the local network management system, this object should contain the value 0. For Cisco RFGW-10, since the write objects are not supported, it returns the value 0. |
ceRedunGroupTable
The table below lists the MIB objects in ceRedunGroupTable:
Table 9 MIB Objects in ceRedunGroupTable
|
|
|
Contains the group number assigned to a particular redundancy group. A group consists of one or more primary members which are protected by one or more secondary members. |
|
Provides details of group string for corresponding group names. If ceRedunUsesGroupName is 'true' for this redundancy group type, this object is a group name identifier and the value of this object has to be specified and should contain no internal spaces when configuring this group entry. If ceRedunUsesGroupName is 'false', the ceRedunGroupString object is just used as an optional description for the group rather than as the group name. In that case it's allowed to have spaces in the string. |
|
Indicates the intended type of redundancy protection such as 'yCable' or 'aps' for this redundancy group. The line card redundancy type for Cisco RFGW-10 is internal switch. So, the value of this object is set to other(1) for Cisco RFGW-10. |
|
Determines the local/remote scope of the redundancy group. This object may not be modified if the associated ceRedunGroupRowStatus object is equal to active(1). For Cisco RFGW-10, the value of this object is set to local(2). |
|
The architecture of the redundancy group, such as 1:1 or 1:n, and so on. This object may not be modified if the associated ceRedunGroupRowStatus object is equal to active(1). |
|
Indicates the revertive mode of the redundancy group. nonrevertive(1)—The secondary member remains active until another switchable event takes place. revertive(2)—When the condition that caused a switch to the secondary member has been cleared, a switch is made back to the primary member after a configured delay. Switching should normally be revertive for the 1:n and load-sharing architectures. Switching may optionally be revertive with the 1:1 and 1+1 architectures. This object may not be modified if the associated ceRedunGroupRowStatus object is equal to active(1). |
ceRedunGroupWaitToRestore
|
Indicates the Wait To Restore period in seconds. This object is only applicable to groups which are configured as revertive and does not need to be instantiated for groups which are non-revertive. After clearing of a condition that necessitated an automatic switch, the wait to restore period must elapse before reverting. This is intended to avoid rapid switch oscillations. This object may not be modified if the associated ceRedunGroupRowStatus object is equal to active(1). |
|
Applicable only for those types of redundancy such as APS where switchovers can take place independently at near and far ends of a pair of interconnecting links and does not need to be instantiated for other redundancy types. unidirectional(1)—Switchovers are allowed to take place independently at protection equipment at the near and far ends of interconnecting links. bidirectional(2)—When a switchover happens at the near end protection equipment there is some form of signalling which should cause a corresponding switchover at the far end protection equipment. This object may not be modified if the associated ceRedunGroupRowStatus object is equal to active(1). |
|
Indicates the storage type for this conceptual row. By default, the row will not be saved into non-volatile memory unless this object is set to the value nonVolatile. Note Conceptual rows having the value 'readOnly' can be used for redundancy groups that cannot be configured and need not allow write-access to any columnar objects in the row. |
|
Provides the configuration status of this redundancy group entry. An entry may not exist in the active RowStatus state unless all configurable read-create objects in the entry have an appropriate value. No other read-create objects in this group may be modified if the ceRedunGroupRowStatus object is equal to active(1). When set to 'notInService', changes may be made to configurable read-create objects. Also, associated ceRedunMbrTable objects may be added, deleted and modified. After modifying a conceptual row in this table, the management client must set this object to 'active' in order for the changes to take effect. For Cisco RFGW-10, the value of this object is set to active(1). |
ceRedunMbrConfigTable
The table below lists the MIB objects in ceRedunMbrConfigTable:
Table 10 MIB Objects in ceRedunMbrConfigTable
|
|
|
Assigned as a unique member number within a redundancy group. The value 0 always indicates a secondary member. Primary members should have numbers which are higher than secondary members. Note This definition of member values, including the use of the value 0 for the secondary member allows compatibility with existing 1:n SONET APS channel numbering. Yet the numbering definition has also been expanded to allow support for the most general m:n redundancy architectures. |
|
Specifies the entity PhysicalIndex which is being configured as a redundancy member. It is the responsibility of the managed device to enforce any restrictions on matching entPhysicalVendorType, slot positions, and so on. among members of the same redundancy group. |
|
Sets the role to the 'primary' (working) or 'secondary' (protection) within the redundancy group. The designation as 'primary' or 'secondary' is configured and is static. It doesn't change due to a switchover. |
|
Specifies the type of address used for the ceRedunMbrAddress object. It does not need to be instantiated when the ceRedunGroupScope value is 'remoteSystem' or 'remoteChassis'. For Cisco RFGW-10, the value of this object is set to 0. |
|
Specifies the remote management address of the shelf or system where the peer member is expected to be configured. It does not need to be instantiated when the ceRedunGroupScope value is 'remoteSystem' or 'remoteChassis'. For Cisco RFGW-10, the value of this object is set to empty string. |
|
Indicates the priority of the member. For 1:n architectures if the secondary member has already become active for a primary member with a lower priority, it can instead take over for a different primary member if that member has higher priority. This field is only applicable if the member is to be included in a group using the 1:n architecture. It is not applicable if the member is to be included in a group using the 1:1 or 1+1 architecture, and is ignored in that case. For Cisco RFGW-10, the value of this object is set to 0. |
|
Indicates the storage type for this conceptual row. By default, the row will not be saved into non-volatile memory unless this object is set to the value nonVolatile. Note Conceptual rows having the value 'readOnly' can be used for redundancy groups that aren't configurable and need not allow write-access to any columnar objects in the row. For Cisco RFGW-10, the value of this object is set to ‘readOnly’(5). |
|
Indicates the configuration status of this member entry. A row in the ceRedunMbrConfigTable may not be created, deleted, or set to notInService if the associated ceRedunGroupRowStatus object is equal to active. However, if the ceRedunGroupRowStatus object is equal to notInService, a row may be created, deleted or modified. In other words, a member may not be added, deleted or modified if the including group is active. For Cisco RFGW-10, the value of this object is set to active(1). |
ceRedunMbrStatusTable
The table below lists the MIB objects in ceRedunMbrStatusTable:
Table 11 MIB Objects in ceRedunMbrStatusTable
|
|
|
Indicates the current status bit flags for the member. For Cisco RFGW-10, the following status bit flags are supported:
- failure(2)
- standby(3)
- protectionProvided(4)
|
|
Valid only for a secondary member. When the secondary member is active, this value indicates the primary member it has taken over for. When the secondary member is standby, it should return its own member number. Primary members should return their own member number. |
|
Indicates the current internal state index for a member. The corresponding state category and description can be found in the ceRedunInternalStatesTable. It may include any of the initialization or intermediate progression states necessary to reach a stable active or standby state. |
ceRedunMbrSwitchoverCounts
|
For Cisco RFGW-10, this object is not stored and returns the value 0. |
|
For Cisco RFGW-10, this object is not stored and returns the value 0. |
ceRedunMbrSwitchoverReason
|
For Cisco RFGW-10, this object is not stored and returns the value 0. |
ceRedunMbrSwitchoverSeconds
|
For Cisco RFGW-10, this object is not stored and returns the value 0. |
MIB Constraints
The table below lists the CISCO-ENTITY-REDUNDANCY-MIB constraints:
Table 12 CISCO-ENTITY-REDUNDANCY-MIB Constraints
|
|
ceRedunVendorTypesTable |
This table is not supported on the Cisco RFGW-10 and returns null. |
ceRedunInternalStatesTable |
This table is not supported on the Cisco RFGW-10 and returns null. |
ceRedunSwitchoverReasonTable
|
This table is not supported on the Cisco RFGW-10 and returns null. |
|
This table supports the addition, modification and deletion of members in entity redundancy groups.
- ceRedunMbrLastChanged—Not supported, returns zero.
- ceRedunMbrStatusLastChanged—Not supported, returns zero.
|
DOCS-CABLE-DEVICE-MIB
The DOCS-CABLE-DEVICE-MIB contains objects to configure and monitor DOCSIS-compliant Cisco RFGW-10 platforms. This MIB was released as RFC 2669.
The MODULE-IDENTITY for the DOCS-CABLE-DEVICE-MIB is docsDev, and its top-level OID is 1.3.6.1.2.1.69 (iso.org.dod.internet.mgmt-mib-2.docsDev).
MIB Constraints
Table 3-13 lists the constrainst on DOCS-CABLE-DEVICE-MIB.
.
Table 3-13 DOCS-CABLE-DEVICE-MIB Constraints
|
|
|
When the table is full and a new event occurs, the oldest event is removed and replaced by the new event. The docsDevEvIndex, however, continues incrementing, up to its maximum value of 2,147,483,647. |
|
This group of objects is not supported on the Cisco RFGW-10 |
|
This group of objects is not supported on the Cisco RFGW-10. |
|
|
|
This group of objects is not supported on the Cisco RFGW-10. |
|
This group of objects is not supported on the Cisco RFGW-10. |
|
This group of objects is not supported on the Cisco RFGW-10. |
|
This group of objects is not supported on the Cisco RFGW-10. |
DOCS-DRF-MIB
This MIB module contains the management objects for the management of the Downstream RF Interface specification. Copyright 1999-2008 Cable Television Laboratories, Inc. All rights reserved.
Version: 200812090000Z
Starting Cisco IOS Release 15.0(2)SQ, the DOCS-DRF-MIB is used to configure Downstream External Physical Interface (DEPI) on the Cisco RFGW-10. Querying these tables displays the QAM interfaces and channels for the Cisco RFGW-10 DS-384 line card.
MIB Objects
Table 3-14 lists the tables and objects.
Table 3-14 DOCS-DRF-MIB Tables and Objects
|
|
docsDrfDownstreamTable |
Contains extensions for the DOCSIS RFI Downstream docsIfDownstreamChannelTable. |
docsDrfDownstreamCapabilitiesTable |
Contains the QAM channel capabilities for the Downstream Interface PHY parameters. |
docsDrfGroupDependencyTable |
This table describes the rules that identify groups of QAM channels with PHY parameters dependencies. A PHY parameter dependency group means that a set to a QAM channel parameter may affect the value of other QAM Channels in the group. This module refers to TSID group as a PHY dependency Group. This table uses the ENTITY-MIB physical component structure to allows the managed system to describe the QAM channels’ PHY parameters dependencies. Examples of PHY dependencies could be usage of adjacent frequencies, or QAM channels of RF ports restricted, or same interleaver value, modulation and J.83 Annex value. Additional details and rules describe the PHY parameter dependency is indicated in docsDrfGroupDependencyType. |
docsDrfChannelBlockTable |
This table configure attributes of block channels and Controls channel Block Tests. A channel block is an ENTITY-MIB containment of PhysicalClass ‘module’ that represent an RF connector. |
Related Features
The DOCS-DRF-MIB object is associated with the M-CMTS DEPI feature.
DOCS-IF-M-CMTS-MIB
The DOCS-IF-M-CMTS-MIBprovides functionality to configure and manage the External PHY interface(DEPI) of the M-CMTS Architecture that is the PHY interface of Cisco RFGW-10 Router.
MIB Constraints
The objects of docsIfMCmtsBaseGroup and docsIfMCmtsCoreGroup are not supported. Table 3-15 lists the constraints on DOCS-IF-M-CMTS-MIB:
.
Table 3-15 DOCS-IF-M-CMTS-MIB Constraints
|
|
docsIfMCmtsEqamDownstreamTable
|
|
- docsIfMCmtsEqamDownstreamDeviceConfigPhyParamLock
|
Supported values are:
|
- docsIfMCmtsEqamDownstreamAllocationType
|
Supports only docsisOnly(1). |
- docsIfMCmtsEqamDownstreamAllocationTimeout
|
Supports only 0 as value. |
- docsIfMCmtsEqamDownstreamDRRPAdvertizing
|
Supports only false as value. |
docsIfMCmtsEqamGlobCfgDownBandwidth
|
Read-only. |
docsIfMCmtsEqamGlobCfgDownSymbolRateM
|
Read-only. |
docsIfMCmtsEqamGlobCfgDownTable
|
Read-write. |
docsIfMCmtsEqamGlobCfgDownSymbolRateN
|
Read-only. |
docsIfMCmtsChannelBlockTable
|
|
- docsIfMCmtsChannelBlockCfgNumberChannels
|
Supported values are:
|
- docsIfMCmtsChannelBlockTestType
|
Supported value are:
- noTest(1)
- offOthersNormal(2)
- allOff(3)
- onOthersOff(4)
- cwOnOthersOff(5)
|
DOCS-IF-MIB
The DOCS-IF-MIB contains objects to configure and monitor the radio frequency (RF) interfaces on DOCSIS-compliant Cisco RFGW-10 platforms. This MIB was released as RFC 2670. This MIB has been updated to draft-ietf-ipcdn-rfmibv2-05.txt.
The MODULE-IDENTITY for the DOCS-IF-MIB is docsIfMIB, and its top-level OID is 1.3.6.1.2.1.10.127 (iso.org.dod.internet.mgmt.mib-2.transmission.docsIfMIB).
MIB Constraints
Table 3-16 lists the constraint on DOCS-IF-MIB:
.
Table 3-16 DOCS-IF-MIB Constraints
|
|
|
Only docsIfDownstreamChannelTable is supported. |
|
Not supported. |
|
Not supported. |
|
Supported values are:
|
docsIfDownChannelModulation
|
Supported values are:
|
docsIfDownChannelInterleave
|
Supported values are:
- taps8Increment16(3)
- taps16Increment8(4)
- taps32Increment4(5)
- taps64Increment2(6)
- taps128Increment1(7)
|
DTI-MIB
The DTI-MIB supports the Cisco RFGW-10 with the following MIB attributes and values:
- dtiProtocolEntityType—Refer to Table 3-17 .
- dtiPathTraceabilityTable—Refer to Table 3-18 .
- entPhysicalTable—Refer to the following tables:
– Table 3-19 —entPhysicalTable Entries for the Cisco DTI Card
– Table 3-20 —entPhysicalTable Entries for Cisco DTI Ports
– Table 3-21 —entAliasMappingTable Entries for DTI Interfaces
Table 3-17 dtiProtocolEntityType Entries
|
|
|
dtiProtocolEntityType |
root(1), server(2), client(3) |
|
dtiProtocolClientClockType |
ituI(1), ituII(2), ituIII(3), st3(4), dtiClock(5) |
|
dtiProtocolServerStatusFlag |
unknown(0), warmup(1), freerun(2), fastTrackingMode(3), normalMode(4), holdoverMode(5), clientStable(6), testMode(7) |
Server status |
dtiProtocolClientStatusFlag |
unknown(0), warmup(1), freerun(2), fastTrackingMode(3), normalMode(4), holdoverMode(5), bridgingMode(6), testMode(7) |
Client status |
dtiProtocolServerToDState |
Valid(1) or Invalid(2) |
Validity of TOD |
dtiProtocolServerToDType |
Default(1), userTime(2), ntpv4(3), gps(4) |
Current TOD source for DTI connection |
dtiProtocolServerToDValue |
String |
Value of TOD in format DDDDD.YYYY/MM/DD.HH:MM:SS.SHH:F.D |
dtiProtocolServerCableAdvanceFlag |
Valid(1), invalid(2), manual(3) |
Cable advance status |
dtiProtocolServerCableAdvanceValue |
String |
Cable advance value |
dtiProtocolClientPhaseError |
Signed number |
Phase error counter |
dtiProtocolClientVersion |
Unsigned number |
Client DTI version |
dtiProtocolClientPathTraceability |
Unsigned number |
DTI tracibeality |
dtiProtocolServerClientStableFlag |
Valid(1) or Invalid(2) |
Client performance stable status of DTI server frame |
Table 3-18 dtiPathTraceabilityTable Entries
|
|
|
dtiPathTraceabilityIndex |
Unsigned number |
index |
dtiPathTraceabilityRootServerInetAddrType |
unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) |
Server address type |
dtiPathTraceabilityRootServerInetAddr |
<IP address> |
Server address |
dtiPathTraceabilityRootServerOutPhyIdx |
Physical index |
|
dtiPathTraceabilityServerInetAddrType |
unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) |
|
dtiPathTraceabilityServerInetAddr |
<IP address> |
|
dtiPathTraceabilityServerOutPhyIdx |
Physical index |
|
dtiPathTraceabilityRootServerProtVersion |
|
DTI version |
dtiPathTraceabilityServerProtVersion |
|
DTI protocol version |
MIB Constraints
There are no constraints on this MIB.
ENTITY-MIB
The ENTITY-MIB represents physical and logical entities (components) in the Cisco RFGW-10 and allows SNMP management of those entities. This MIB was released as RFC 2737, Entity MIB (Version 2).
The MIB table entPhysicalTable identifies the physical entities in the Cisco RFGW-10. The entPhysicalTable contains a single row for the chassis and a row for each entity in the chassis. A physical entity may contain other entities (for example, a fan-tray bay may contain a fan-tray module, which may contain one or more fans). The physical hierarchy of system components is determined at run time, based on the actual Cisco RFGW-10 configuration.
The ENTITY-MIB shows information only about hardware devices, not virtual devices.
The MODULE-IDENTITY for the ENTITY-MIB is entityMIB, and its top-level OID is 1.3.6.1.2.1.47 (iso.org.dod.internet.mgmt.mib-2.entityMIB).
MIB objects and related constraints introduced in Cisco IOS Release 12.2(44)SQ are included in Table 3-22 .
MIB Constraints
Table 3-19 lists the constraints on ENTITY-MIB:
Table 3-19 entPhysicalTable Entries for the DTI Line Card in Cisco IOS Release 12.2(33)SQ
|
|
|
entPhysicalIndex |
Physical index |
Set by Entity MIB when instance is created |
entPhysicalDescr |
Timing Clock card (2 DTI ports) |
|
entPhysicalVendorType |
cevRfgwDtcc |
Cisco IOS Release 12.2(44)SQ |
entPhysicalContainedIn |
Corresponding chassis index |
|
entPhysicalClass |
module |
|
entPhysicalParentRelPos |
A number denotes where the TCC w/ DTI card locates. |
|
entPhysicalName |
Linecard(slot slot#) |
|
entPhysicalHardwareRev |
Hardware revision |
Read from EEPROM |
entPhysicalFirmwareRev |
Firmware revision |
Read from EEPROM |
entPhysicalSoftwareRev |
Software revision |
Read from EEPROM |
entPhysicalSerialNum |
N/A |
Read from EEPROM |
entPhysicalMfgName |
Cisco |
|
entPhysicalModelName |
RFGW-TCC1 |
|
entPhysicalAlias |
|
Null by default, can be set. |
entPhysicalAssetID |
|
Null by default, can be set. |
entPhysicalIsFRU |
TRUE(1) |
|
Table 3-20 entPhysicalTable Entries for the DTI Ports in Cisco IOS Release 12.2(44)SQ
|
|
|
entPhysicalIndex |
Physical index |
Set when the port is enabled. |
entPhysicalDescr |
|
|
entPhysicalVendorType |
cevPortDti |
Cisco IOS Release 12.2(44)SQ |
entPhysicalContainedIn |
DTI card physical index |
e.g. Ge containedin SFP module |
entPhysicalClass |
Port(10) |
|
entPhysicalParentRelPos |
0 |
A number given when DTI is enabled, increasing from 0. |
entPhysicalName |
|
|
entPhysicalHardwareRev |
N/A |
|
entPhysicalFirmwareRev |
N/A |
|
entPhysicalSerialNum |
N/A |
|
entPhysicalMfgname |
Cisco |
|
entPhysicalModelname |
N/A |
|
entPhysicalAlias |
NA |
|
entPhysicalAssetID |
NA |
|
entPhysicalIsFRU |
False(2) |
|
Table 3-21 entAliasMappingTable Entries for DTI interfaces
|
|
|
entAliasLogicalIndexOrZero |
0 |
|
entAliasMappingIdentifier |
ifIndex.<ifIndex#> |
|
.
Table 3-22 ENTITY-MIB Constraints Prior to Cisco IOS Release 12.2(44)SQ
|
|
|
|
|
Not implemented. |
|
Not implemented. |
|
Not implemented. |
|
|
- entPhysicalHardwareRev
- entPhysicalModelName
- entPhysicalSerialNumber
|
|
|
- Supports the Cisco Unique Device Identifier (UDI).
- Contains the Version Identifier (VID).
|
|
- Supports the Cisco Unique Device Identifier (UDI).
- Contains the orderable Product Identifier (PID).
|
|
- Supports the Cisco unique device Identifier (UDI).
- Contains the hardware Serial Number (SN).
Note that for non-UDI compliant hardware, these fields might contain a NULL string. Currently, the UDI support is not implemented for the standby PRE. For standby PRE, both entPhysicalHardwareRev and entPhysicalSerialNumber will contain NULL string. |
|
|
|
|
|
This object accurately displays the location of the FastEthernet network management port on the active PRE-1 module. |
|
Not implemented. |
|
- On Cisco RFGW-10, this table does not contain entries for the TCC+ cards.
- On Cisco RFGW-10with two redundant PRE modules installed, the entPhysicalDesc entries in the entAliasMappingTable contain two sets of apparently identical references for each PRE module to “Forwarding Processor,” “Routing Processor,” and “Network Management Ethernet” (the Fast Ethernet port on the PRE modules). This occurs because two PRE modules are installed in the chassis, but only one is active. So the SNMP agent points both entries to the same PRE module.
- The entAliasMappingTable supports virtual interfaces only in Cisco IOS Release 12.2(44)SQ and later releases. The entries in this table show the logical upstream interface (as defined by ifIndex from the IF-MIB) that is using each physical upstream connector.
|
The entPhysicalTable and entAliasMappingTable objects are automatically updated whenever a card is removed or inserted into a slot or when you enter a command at the CLI prompt that affects the operation of the card. |
ENTITY-MIB UDI Support
The ENTITY-MIB supports the Cisco compliance effort for a Cisco unique device identifier (UDI) standard which is stored in IDPROM.
The Cisco UDI provides a unique identity for every Cisco product. The unique device identifier is comprised of an orderable product identifier (PID), the version identifier (VID), and the hardware Serial Number (SN). The UDI is stored in IDPROM. The PID, VID, and SN must be stored in the entPhysicalTable:
- PID shall be stored in the entPhysicalModelName object
- VID shall be stored in the entPhysicalHardwareRev object
- SN shall be stored in the entPhysicalSerialNum object
Note The Version ID returns NULL for those old or existing cards whose IDPROMs do not have the Version ID field. Therefore, corresponding entPhysicalHardwareRev returns NULL for cards that do not have the Version ID field in IDPROM. See Identifying Cisco Unique Device Identifiers for a complete description of the Cisco UDI feature.
Each product that is capable of MIB support is required to populate ENTITY-MIB v2 or later with PID, VID, and SN. This compliance is also a requirement of the Consistent Network Element Manageability initiative. If the product uses ENTITY-MIB the data in the following fields should be identical.
ENTITY-MIB v2 (RFC-2737) fields to be populated are:
- Entity-MIB.entPhysicalName (Product Name)
- Entity-MIB.entPhysicalDescr (Product Description)
- Entity-MIB.entPhysicalModelName (PID)
- Entity-MIB.entPhysicalHardwareRev (VID)
- Entity-MIB.entPhysicalSerialNumber (SN)
Overview of the ENTITY-MIB
The following are the most important objects in the ENTITY-MIB for the management of physical entities on the Cisco RFGW-10:
- entPhysicalTable—Describes each physical component (entity) in the Cisco RFGW-10. The table contains a row entry for the top-most entity (the chassis) and then for each entity in the chassis. Each entry provides the name and description of the entry, its type and vendor, and a description of the reason how the entity was first entered into the containment tree.
- entPhysicalIndex—Uniquely identifies each entry. This value is guaranteed to be unique across all equipment in this chassis and across all MIBs, allowing you to correlate the data from several MIBs for any particular entity.
- entAliasMappingTable—Maps each physical port’s entPhysicalIndex value to the corresponding ifIndex value in the ifTable in the IF-MIB. This provides a quick way of identifying a particular port with a particular interface.
In Cisco IOS Release 12.2(44)SQ releass, the entAliasMappingTable also shows the mapping of physical upstream connectors to logical upstream interface when virtual interfaces are configured on the Cisco RFGW-10 cable interface line cards. This support also changed the parent-child relationships of cable interface line cards and their ports. For more information, see the “Chassis Slot Layout” section.
- entPhysicalContainsTable—For each physical entity, lists the entPhysicalIndex value for any child objects of the entity. This provides an easy way of creating the container tree for the Cisco RFGW-10, which shows the relationship between physical entities in the chassis.
Typically, the container tree is organized as follows:
– The chassis is the top-most level and contains the processor card and chassis slots.
– Chassis slots contain the individual line cards and I/O controller (if installed).
– Line cards contain ports (interfaces).
Figure 3-1 shows an overview of the arrangement of objects in a Cisco RFGW-10, with one Fast Ethernet line card and two cable interface line cards.
Figure 3-1 ENTITY-MIB for Cisco RFGW-10 Chassis
Chassis Slot Layout
Table 3-23 provides information about the entities contained in chassis slots on the Cisco RFGW-10.
Table 3-23 Cisco RFGW-10 Chassis Slot Contents
|
|
|
Slots 1 to 10 |
One full-size line card per slot. |
For chassis slot containers:
- entPhysicalContainedIn is always 1 (which is the entPhysicalIndex of the chassis, which contains all chassis slots).
- entPhysicalParentRelPos is different for each chassis slot, to show its position in the chassis.
The Cisco RFGW-10 supports only full-size line cards in chassis slots:
- entPhysicalContainedIn is different for each line card (because each line card is installed in a different chassis slot).
- entPhysicalParentRelPos is always 1 (only one card per slot).
|
IF-MIB
The IF-MIB describes the attributes of physical and logical interfaces. The Cisco RFGW-10 supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, and ifConnectorPresent). This MIB was released as RFC 2233, The Interfaces Group MIB Using SMIv2.
In Cisco IOS Release 12.2(44)SQ release, the Cisco RFGW-10 implemented a cache to allow continuous polling of the ifTable interface counters, without creating spikes in the CPU usage. The cache is updated approximately every 10 seconds, which means that if you read the counter more quickly than that, the SNMP request might not return a new value.
The counters do continue to increment, however, to account for the actual traffic occurring on the interfaces, and another SNMP request in 10 seconds will show the new values. However, the use of the cache means that the counters displayed by the show interface command might not exactly match the values returned by the ifTable interface counters.
The MODULE-IDENTITY for the IF-MIB is ifMIB, and its top-level OID is 1.3.6.1.2.1.31 (iso.org.dod.internet.mgmt.mib-2.ifMIB).
IF-MIB Notes
Note It is expected that the interface counters displayed by the show interface command might not exactly match the values returned by the ifTable interface counters.
Table 3-24 lists the IF-MIB constraints and notes.
.
Table 3-24 IF-MIB Constraints
|
|
|
|
|
|
|
|
|
The first ifDescr object is typically “Ethernet0/0/0,” which is the internal backplane Ethernet interface that the PRE module uses to communicate with the line cards and the secondary PRE module (if installed). This interface cannot be configured or otherwise used, and therefore should be ignored. Note that ifDescr supports Virtual Interfaces only in Cisco IOS Release 12.2(44)SQ and later releases. Also see the ENTITY-MIB for entAliasMappingTable support. |
|
Always reports a value of 6 (Ethernet interface) for Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces. This conforms with the recommendations of RFC 2665, and accommodates 10/100/1000 interfaces that negotiate the link speed with the remote end. |
|
|
|
This object has valid values only for the upstream and downstream ifDescr entries. The ifSpeed for the MAC-layer cable interface entry is always 0. |
- ifInUcastPkts
- ifOutMulticast
|
These objects count both data packets and MAC-layer request packets from cable modems on an upstream, so as to conform to RFC 2670. |
- ifHCInUcastPkts
- ifHCInBroadcastPkts
- ifHCOutUcastPkts
|
|
|
|
SCTE-HMS-MPEG-MIB
This MIB module is for representing MPEG equipment present in the headend and is supported by a SNMP agent. It defines both the MPEG input and output MIB objects for managing MPEG input and output transport streams, programs and elementary streams.
It provides both input and output related statistics, as well as program mapping and video session information. All the tables, except mpegProgramMappingTable and mpegVideoSessionTable, capture and store the information related to active transport streams only. Optional MIB objects have default values defined in this MIB file.
Version: 200810031700Z
MIB Objects
The following table lists the tables and objects.
Table 3-25 SCTE-HMS-MPEG-MIB Tables and Objects
|
|
|
Specifies the attributes of video sessions or SPTSs. |
|
Describes the PSI of each incoming program. |
|
Provides information about the elementary streams in a program. |
|
Indicates the stream statistics, SPTS or MPTS. |
mpegInputUdpOriginationTable
|
Specifies the UDP unicast or multicast flows of an input transport stream. |
|
Describes the packet insertion information. Typical packets that are inserted at the RF output of a device are PSI, PSIP, and CVCT MPEG packets. These packets have their own PID. This table may be empty if the video device does not support packet insertion or do not have any packet insertion configured. |
|
Specifies the diagnostic statistics objects for the outputs transport stream of an MPEG device. |
|
Specifies the attributes of an outgoing transport stream SPTS or MPTS. |
|
Describes the PSI of each outgoing program. |
mpegOutputProgElemStatsTable
|
Provides information about the statistics associated with the elementary streams of an MPEG program. |
mpegOutputUdpDestinationTable
|
Specifies the UDP unicast or multicast of the output transport stream this entry references. |
|
Describes the program mappings such as the input destination to the output destination for every program active in the device. |
|
Stores the video session information. The session may be VOD, SDV or DB type. It captures logical information about a video stream, such as source and destination addresses, UDP port, and also ties it with its direct mapping of input and output programs. |
|
Provides a quick reference of the program mapping and input and output transport stream connection information associated with a video Session. |
mpegInputTSOutputSessionTable
|
Specifies the list of output session indexes that the Input transport stream entry. |
mpegInputTSTable
The mpegInputTSTable specifies the attributes of an incoming video session or SPTS.
The following table lists the MIB objects in mpegInputTSTable.
Table 3-26 MIB Objects in mpegInputTSTable
|
|
|
Indicates table index. |
|
Indicates the type of stream. Supported streams are:
|
mpegInputTSConnectionType
|
Indicates the type of input flow of the stream. The value udp indicates unicast or multicast udp origination flows. |
|
Specifies the start of the data source table that feeds the input stream. |
mpegInputTSActiveConnection
|
Specifies the instance of the data source that feeds the input stream. |
|
Indicates whether PSI is detected or not. |
|
Indicates the time MPEG device started receiving the stream (the time the entry was added to the table). |
mpegInputTSResourceAllocated
|
Indicates whether all resources have been allocated for the stream (true) or not (false). |
|
Indicates the number of programs in the input transport stream. |
|
Indicates the data rate of the incoming program or SPTS. |
|
Indicates the maximum data rate of the incoming VBR stream. |
|
Indicates the PAT version of the transport stream. |
|
Not supported. Indicates the CAT version number of transport stream. Set to zero. |
|
Indicates the NIT PID of the input transport stream. |
|
Indicates the number of EMMs in the input stream. The default value, 9999, indicates that the QAM does not support encryption. |
|
Indicates the input TSID of the transport stream. A valid TSID is 16 bits. If TSID is not supported all 32-bits are set to 1. |
|
Indicates whether the device is locked or not to the physical input. Currently this object is set to notLocked(2). Other supported values are:
- locked(1)
- intermittent(3)
- notIp(4)
- notMonitored(5)
|
mpegInputProgTable
The mpegInputProgTable describes the PSI of each incoming program. Each table entry is identified by ifIndex, mpegInputTSIndex, and mpegInputProgIndex.
The following table lists the MIB objects in mpeginputProgTable:
Table 3-27 MIB Objects in mpegInputProgTable
|
|
|
Specifies the third index of MIB table. The index should uniquely identify a program given a transport stream index. |
|
Specifies the identifier of the program present in the transport stream of the incoming video stream. This information is contained in the PAT table. |
|
Specifies the PMT version of the program. |
|
Specifies the PMT PID of the program. |
|
Specifies PCR PID of the program. |
|
Specifies ECM PID of the program. |
|
Specifies the number of elementary streams in the program. For the current implementation, it is 0. |
|
Specifies the number of ECMs for the program. The default value, 9999, indicates that the QAM does not support encryption. |
|
Not supported. Specifies the CA descriptor for the program. If the program does not have an associated CA descriptor, this object has a zero-length string (current implementation). Conditional access descriptor is used to specify system-wide conditional access management information (EMMS) and elementary stream-specific information (ECMs). If any elementary stream is scrambled, a CA descriptor is present for the program containing that elementary stream. |
|
Not supported. Specifies the SCTE 35 descriptor. If not present, a zero-length string is returned. For the current implementation, it is a zero-length string. |
|
Not supported. Specifies the SCTE 18 descriptor. If not present, a zero-length string is returned. For the current implementation, it is a zero-length string. |
mpegProgESTable
The mpegProgESTable contains information about the elementary streams in a program. This table is optional for devices that do not decode and store information such as the video server, encoder, or satellite or if mpegInputTSTransportType is pass-through type for the transport stream.
Each entry in the table is identified by ifIndex, mpegInputTSIndex, mpegInputProgIndex, and mpegProgElemStreamIndex.
The following table lists MIB objects for mpegProgESTable.
Table 3-28 MIB Objects in mpegProgESTable
|
|
|
Specifies the Table index. |
|
Specifies the PID for each transport stream packet that carries the program element. |
|
Specifies the type of elementary stream (video, audio, or data) of the incoming video session received from the video server. Supported values are:
- video(1)
- audio(2)
- data(3)
|
|
Specifies the CA descriptor associated with the elementary stream. If there is no CA descriptor for the elementary stream, this object has a zero-length string. |
|
Specifies the SCTE 35 descriptor. Returns a zero-length string if it is not supported or is not present. For the current implementation, it is zero-length string. |
|
Specifies the SCTE 18 descriptor. Returns a zero-length string if it is not supported or is not present. For the current implementation, it is zero-length string. |
mpegInputStatsTable
The mpegInputStatsTable contains stream statistics for SPTS or MPTS. Each table entry is identified by ifIndex and mpegInputTSIndex.
The following table lists MIB objects for mpegStatsStreamTable.
Table 3-29 MIB Objects in mpegInputStatsTable
|
|
|
Specifies the jitter difference between the actual value of the PCR and its expected value in nanoseconds. |
mpegInputStatsMaxPacketJitter
|
Specifies the measurement of the maximum variation in arrival time or delay between the individual packets in milliseconds. |
|
Specifies the number of MPEG transport packets, having PCR, received for the stream. |
mpegInputStatsNonPcrPackets
|
Specifies the number of MPEG transport packets, without PCR, received for the stream. |
mpegInputStatsUnexpectedPackets
|
Specifies the number of transport packets for which PIDs are not expected. |
mpegInputStatsContinuityErrors
|
Specifies the number of continuity counter errors. Transport packets have continuity counters. Successive packets have contiguous values in the continuity counter. Continuity counter error occurs when the successive packets do not have contiguous value and discontinuity indicator is not set. |
mpegInputStatsSyncLossPackets
|
Specifies the number of MPEG packets with missing sync byte per stream. When a sync byte is missing in a MPEG packet this value is incremented. |
mpegInputStatsPcrIntervalExceeds
|
Specifies the number of times that the interval between two successive PCR packets for any program in a transport stream exceeds 100 milliseconds. |
mpegInputUdpOriginationTable
The mpegInputUdpOriginationTable specifies the UDP unicast and multicast flows of an input transport stream. For unicast streams, it represents the UDP port and optionally destination IP address of the input TS origination UDP IP flow. For multicast streams, it represents the set of SSM multicast groups of the input TS origination UDP IP flow.
The following table lists the MIB objects for mpegInputUdpOriginationTable.
Table 3-30 MIB Objects in mpegInputUdpOriginationTable
|
|
mpegInputUdpOriginationIndex
|
Specifies the UDP transport stream origination information. |
mpegInputUdpOriginationId
|
Specifies each UDP IP flow associated with the input transport stream UDP origination. |
mpegInputUdpOriginationIfIndex
|
Specifies the interface index where the UDP flow is received. |
mpegInputUdpOriginationInetAddrType
|
Specifies the address associated with the input transport stream origination UDP IP flow. |
mpegInputUdpOriginationScrInetAddr
|
Specifies the source multicast IP address of the UDP IP flow for multicast transport streams. For unicast UDP IP flows, either the IP source address of the IP flow or all zeros address of known or irrelevant input transport streams are specified. |
mpegInputUdpOriginationDestInetAddr
|
Specifies the group address of the SSM origination input for multicast transport streams. For unicast UDP IP flows, either the IP destination address of the UDP flow or all zeros address for known or irrelevant input transport streams are specified. |
mpegInputUdpOriginationDestPort
|
Specifies the UDP destination port of the UDP IP flow of the input transport stream. |
mpedInputUdpOriginationActive
|
Specifies the activation state of the UDP flow. The value “true” for a UDP flow data stream indicates it is being sensed or buffered for the input transport stream independently of the flow being used by a video session. For multicast UDP origination flow, the value “true” indicates the UDP flow was successfully joined. |
mpegInputUdpOriginationPacketsDetected
|
Specifies whether the UDP flow packets are being detected. |
mpegInputUdpOriginationRank
|
Specifies the Rank priority used to determine the UDP flow selected for the input transport stream processing and the video session alignments. |
mpegInputUdpOriginationInputTSIndex
|
Specifies the association with the mpegInputTSIndex object. |
mpegInsertPacketTable
The mpegInsertPacketTable describes packet insertion information. A packet inserted at the RF output of a QAM is PSI, PSIP, or CVCT MPEG packet. Each packet has a unique PID.
This table is empty if the packet insertion is not supported or packet insertion is not configured on the video device.
The following table lists MIB objects for mpegInsertPacketTable.
Table 3-31 MIB Objects in mpegInsertPacketTable
|
|
|
Specifies the index of the list of packets inserted into all MPEG stream. |
|
Specifies the reference number of packets inserted into MPEG stream. |
mpegInsertPacketImmediateExecution
|
Indicates initialization of packet insertion. Always set to true. |
mpegInsertPacketStartTime
|
Specifies Unix epoch start time for insertions (if Immediate Execution is false). |
|
Specifies whether the insert packet is one-time or repetitive. |
mpegInsertPacketContinuousFlag
|
Indicates if the packets are sent periodically. |
|
Specifies the insertion rate for the packet list. |
mpedInsertPacketDeviceIfIndex
|
Specifies the IfIndex of the output device interface where the packet is inserted. |
mpegOutputStatsTable
The mpegOutputStatsTable specifies the diagnostic statistics objects for the RF outputs of an MPEG device designated by ifIndex and entPhysicalIndex.
The following table lists the MIB objects for mpegOutputStatsTable.
Table 3-32 MIB Objects in mpegOutputStatsTable
|
|
mpegOutputStatsDroppedPackets
|
Specifies the number of MPEG packets dropped on this output. |
mpegOutputStatsFifoOverflow
|
Specifies the number of FIFO overflows on this output. |
mpegOutputStats FifoUnderflow
|
Specifies the number of FIFO underflows on this output. |
|
Specifies the Data rate (bps) for the content on this output. |
mpegOutputStatsAvailableBandwidth
|
Specifies the unused bandwidth on this port. |
mpegOutputStatsChannelUtilization
|
Specifies the current utilization of a channel defined as (measured data rate / total bandwidth) * 100. Returns -1(default) as value if not applicable. |
mpegOutputStatsTotalPackets
|
Specifies the total number of packets sent out for the transport stream for the current the output stream. |
mpegOutputTSTable
The mpegoutputTSTable specifies the attributes of an outgoing transport stream SPTS or MPTS.
The following table lists MIB objects for mpegOutputTSTable.
Table 3-33 MIB Objects in mpegOutputTSTable
|
|
|
Specifies the table index. |
|
Specifies the type of stream:
|
mpegOutputTSConnectionType
|
Specifies the type of output flow of the stream.
- qam indicates a QAM output for the stream.
- udp indicates if it is either a unicast or multicast udp destination flow for the stream.
|
|
Specifies a reference to the instance of the output connection for the output stream.
- Connection type qam—contains the ifIndex of the identifier of the QAM channel of the output stream
- Connection type udp—contains the pointer to the UDP destination table used for the output stream.
|
|
Specifies the number of programs in the output transport stream. |
|
Specifies the TSID of the output transport stream. |
|
Not supported. Specifies the NIT PID of the outgoing transport stream. Default value is 65535. Note Effective with, Cisco IOS-XE Release 3.4.0SQ, this MIB object is supported on the Cisco RFGW-10. |
|
Not supported. Specifies the CA PID of the outgoing transport stream. Default value is 65535. |
mpegOutputTSCatInsertRate
|
Not supported. Specifies the CAT insertion rate, expressed in tables/ms. Default value is zero. |
mpegOutputTSPatInsertRate
|
Specifies the PAT insertion rate, expressed in tables/ms. |
mpegOutputTSPmtInsertRate
|
Specifies the PMT insertion rate, expressed in tables/ms. |
|
Specifies the time the MPEG device started transmitting the output stream. |
mpegOutputProgTable
The mpegOutputProgTable describes the PSI of each outgoing program. Each table entity is identified by ifIndex, mpegOutputTSIndex, and mpegOutputProgIndex.
The following table lists MIB objects for mpegOutputProgTable.
Table 3-34 MIB Objects in mpegOutputProgTable
|
|
|
Specifies the table index for output program. |
|
Specifies the identifier of the program present in the transport stream of the outgoing program. |
|
Specifies the PMT version of the outgoing program. |
|
Specifies the PMT PID of the outgoing program. |
|
Specifies the PCR PID of the outgoing program. |
|
Not supported. Specifies the ECM PID of the outgoing program. Default value is 65535. |
|
Specifies the number of elementary streams in the outgoing program. |
|
Specifies the number of ECMs for the outgoing program. The default value, 9999, indicates that the QAM does not support encryption. For the current implementation, the value is 9999. |
|
Not supported. Specifies the Conditional Access (CA) descriptor for this program. CA descriptor is used to specify the system-wide conditional access management information (EMMS) and elementary stream-specific information (ECMs). If an elementary stream is scrambled, a CA descriptor for the program contains the elementary stream information. If the outgoing program does not have an associated CA descriptor, this object has a zero-length string. For the current implementation, the value is zero-length string. |
mpegOutputProgScte35Descr
|
Not supported. Specifies the SCTE 35 descriptor in the outgoing program. Returns a zero-length string if it is not supported/not present. For the current implementation, it is zero-length string. |
mpegOutputProgScte18Descr
|
Not supported. Specifies the SCTE 18 descriptor. Returns a zero-length string if it is not supported/not present. For the current implementation, it is zero-length string. |
mpegOutputProgElemStatsTable
The mpegOutputProgElemStatsTable contains information associated with the elementary streams of an MPEG program.
This table is optional if mpegInputTSTransportType is pass-through type for the transport stream.
Each table entity is identified by ifIndex, mpegOutputTSIndex, mpegOutputProgIndex, and mpegOutputProgElemStatsIndex.
The following table lists the MIB objects for mpegOutputProgElemStatsTable
Table 3-35 MIB Objects in mpegOutputProgElemStatsTable
|
|
mpegOutputProgElemStatsIndex
|
Specifies the table index. |
mpegOutputProgElemStatsPid
|
Specifies the PID of output program elementary stream. |
mpegOutputProgElemStatsElemType
|
Specifies the type of elementary stream (video, audio, or data) of the program. For devices, such as QAM, that do not report exact stream type due to scalability issues, this object is set to unknown. Supported values are:
- unknown(6)
- video(1)
- audio(2)
- data(3)
- scte18(4)
- scte35(5)
|
mpegOutputProgElemStatsDataRate
|
Specifies the data rate of the elementary stream. Return -1 if not supported. For the current implementation, the value is -1. |
mpegOutputUdpDestinationTable
The mpegOutputUdpDestiantionTable specifies the UDP unicast or multicast of the output transport stream this entry references. For unicast it represents the UDP port and optionally, the destination IP address of the output transport stream destination UDP IP flow. For multicast streams, it represents the set of SSM multicast groups of the output transport stream destination UDP IP flow.
The following table lists the MIB objects for the mpegOutputUdpDestiantionTable.
Table 3-36 mpegOutputUdpDestiantionTable
|
|
mpegOutputUdpDestinationIndex
|
Specifies the unique identifier of the UDP output transport stream destination information. |
mpegOutputUdpDestinationId
|
Specifies the unique identifier of each UDP IP flow associated with the output transport stream UDP destination. |
mpegOutputUdpDestinationIfIndex
|
Specifies the interface index where the UDP flow is sent. |
mpegOutputUdpDestinationInetAddrType
|
Specifies the address type associated with the output transport stream destination UDP IP flow. |
mpegOutputUdpDestinationSrcInetAddr
|
Specifies the source specific multicast (SSM) IP address of the UDP IP flow for multicast transport streams. For unicast UDP IP flow, either the IP source address of the IP flow or all zeros address for known or irrelevant destination transport streams are specified. |
mpegOutputUdpDestinationDestInetAddr
|
Specifies the group address of the SSM destination output transport stream for multicast transport streams. For unicast UDP IP flow, either the IP source address of the IP flow or all zeros address for known or irrelevant destination transport streams are specified. |
mpegOutputUdpDestinationDestPort
|
Specifies the UDP port of the UDP IP flow of the output transport stream. |
mpegOutputUdpDestinationOutputTSIndex
|
Specifies the association with mpegOutputTSIndex entry. |
mpegProgramMappingTable
The mpegProgramMappingTable describes program mappings between the input destination and the output destination for every active program in the QAM. The objects of each entry should be read-only for a session-based QAM and read-write for a table-based QAM.
Note Cisco RFGW-10 supports up to 32 programs per QAM, and up to 32 PIDs per program.
Note Cisco RFGW-10 supports read-only for a session/table-based QAM.
The following table lists MIB objects for mpegProgramMappingTable.
Table 3-37 MIB Objects in mpegProgramMappingTable
|
|
|
Specifies the table index. |
mpegProgramMappingOutputProgIndex
|
Specifies the mpegOutputProgIndex of the corresponding entry in mpegOutputProgTable for a given output program. |
mpegProgramMappingOutputTSIndex
|
Specifies the mpegOutputTSIndex of the corresponding entry in mpegOutputProgTable for a given output program. |
mpegProgramMappingInputProgIndex
|
Specifies the value of mpegInputProgIndex for the corresponding entry in mpegInputProgTable for a given input program. |
mpegProgramMappingInputTSIndex
|
Specifies the value of mpegInputTSIndex of the entry in mpegInputProgTable for a given input program. |
mpegVideoSessionTable
The mpegVideoSessionTable stores the video session information. The session type is VOD, SDV or DB type. A session captures logical information such as source and destination addresses, and UDP port for a video stream and also ties this informationwith direct mapping of input and output programs.
Note The mpegVideoSessionTable captures video sessions provisioned by both session-based and table-based methods.
The following table lists MIB objects for mpegVideoSessionTable.
Table 3-38 MIB Objects in mpegVideoSessionTable
|
|
|
Specifies the table index. |
mpegVideoSessionPhyMappingIndex
|
Specifies the mpegProgramMappingIndex of the corresponding mpegProgrammingMappingEntry which contains physical mapping between the input and output program. |
|
Specifies if a session has PID remapping. A value “true” indicates session has PID remapping. |
|
Indicates if a transport stream is associated with a multiplexed session or is pass-through. For pass-through type of transport stream, all elementary stream level information is optional. |
|
Specifies the state of a session. Supported values are:
- active(1): Indicates in-use.
- provisioned(2): Indicates not-in-use
|
mpegVideoSessionProvMethod
|
Specifies the type of session, it can be QAM table-based or session-based. |
mpegVideoSessionEncryptionType
|
Indicates the encryption algorithm of the session. The value 8 indicates PowerKEY encryption and 7 indicates DVB scrambling. |
mpegVideoSessionEncryptionInfo
|
Indicates a reference to the information associated to the session encryption algorithm. |
|
Indicates a session throughput (bps). |
mpegVideoSessionSessionID
|
Specifies the session ID associated with the stream in the case of a session-based QAM. This is not applicable to a table-based QAM. This ID may be used by NMS system to uniquely identify an input program to output program mapping. |
mpegVideoSessionSelectedInput
|
Specifies a reference to the input flow currently used in the video session. |
mpegVideoSessionSelectedOutput
|
Specifies a reference to the output flow currently used in the video session. |
mpegVideoSessionPtrTable
The mpegVideoSessionPtrTable provides a quick reference of the program mapping and input and output transport stream connection information associated with a video session.
The following table lists the MIB objects for mpegVideoSessionPtrTable.
Table 3-39 mpegVideoSessionPtrTable
|
|
mpegVideoSessionPtrInputProgIndex
|
Indicates the input program index value of the video session. |
mpegVideoSessionPtrInputTSIndex
|
Indicates the input transport stream index value of the video session. |
mpegVideoSessionPtrInputTSConnType
|
Indicates the input transport stream connection type value of the video session. |
mpegVideoSessionPtrInputTSConnection
|
Indicates the input transport stream connection value of the video session. |
mpegVideoSessionPtrOutputProgIndex
|
Indicates the output program index value of the video session. |
mpegVideoSessionPtrOutputTSIndex
|
Indicates the output transport stream index value of the video session. |
mpegVideoSessionPtrOutputConnType
|
Indicates the output transport stream connection type value of the video session. |
mpegVideoSessionPtrOutputTSConnection
|
Indicates the output transport stream connection value of the video session. |
mpegVideoSessionPtrStatus
|
Indicates the status of the sessions. Only active sessions are reported. |
mpegInputTSOutputSessionTable
The mpegInputTSOutputSessionTable specifies the list of output session indexes that the input transport stream entry. For unicast sessions, this table points to just one output session. For multicast sessions, it points to all the output sessions using this internally replicated input transport stream.
The following table lists the MIB objects for mpegInputTSOutputSessionTable.
Table 3-40 mpegInputTSOutputSessionTable
|
|
mpegInputTSOutputSessionCreateTime
|
Indicates the creation time of the session. |
MIB Constraints
The following table lists the constraints that the router places on objects in the SCTE-HMS-MPEG-MIB.
Table 3-41 SCTE-HMS-MPEG-MIB Constraints
|
|
|
Not supported, always returns 0. |
|
Not supported, always returns 65535. Note Effective with, Cisco IOS-XE Release 3.4.0SQ, this MIB object is supported on the Cisco RFGW-10. |
|
Not supported, always returns 65535. |
|
Not supported, always returns 65535. |
|
Not supported, always returns 9999. |
|
Not supported, always returns 9999. |
|
Not supported, always returns 9999. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
|
Not supported, always returns zero-length string. |
mpegOutputProgScte35Descr
|
Not supported, always returns zero-length string. |
mpegOutputProgScte18Descr
|
Not supported, always returns zero-length string. |
mpegInsertPacketStartTime
|
Not supported. |
mpegOutputStatsChannelUtilization
|
Not supported, always returns -1. |
mpegOutputTSCatInsertRate
|
Not supported. |
mpegOutputProgElemStatsDataRate
|
No supported, always returns -1. |
|
Read-only. |
|
Read-only. |
mpegOutputProgElemStatsPid
|
Read-only. |
SCTE-HMS-QAM-MIB
The SCTE-HMS-QAM-MIB module is for representing Edge QAM equipment present in the headend (or indoor) and is supported by a SNMP agent. It defines QAM channel related configuration MIB objects associated with physical and logical characteristics of QAM channel.
The SCTE-HMS-QAM-MIB contains three read only tables:
- qamChannelTable
- qamChannelCommonTable
- qamConfigTable
Version: 200807160305Z
qamChannelTable
The qamChannelTable describes the configuration and attributes of each QAM channel designated by ifIndex.
Table 3-42 lists the Configuration and Attributes of QAM Channel.
Table 3-42 Configuration and Attributes of QAM Channels
|
|
|
Specifies the center frequency of the QAM channel (Hertz). |
qamChannelModulationFormat
|
Specifies the modulation format of the QAM channel. Supported values are:
- qam64(1)
- qam128(2)
- qam256(3)
- qam512(4)
- qam1024(5)
|
qamChannelInterleaverLevel
|
Specifies the interleaver level for FEC coding. This object is ignored when the AnnexMode has the value 'annexA' or 'annexC'. Supported values are:
|
qamChannelInterleaverMode
|
Specifies the interleaving depth or operation mode of the interleaver. When the qamChannelInterleaverLevel is set to level1, a single interleaving depth is supported(fecI128J1). When the qamChannelInterleaverLevel is set to level2, all the other interleaving depths are also supported. This object is ignored when AnnexMode has the value annexA or annexC. Supported values are:
- unknown(1)
- other(2)
- fecI8J16(3)
- fecI16J8(4)
- fecI32J4(5)
- fecI64J2(6)
- fecI128J1(7)
- fecI12J17(8)
- fecI128J2(9)
- fecI128J3(10)
- fecI128J4(11)
- fecI128J5(12)
- fecI128J6(13)
- fecI128J7(14)
- fecI128J8(15)
|
|
The output power of the QAM channel. If the QAM is muted, this object is set to 0. The output power is in 0.1 dBmV and the value depends on the number of max carriers. |
|
Indicates whether the QAM port is muted or not. Supported values are:
|
|
Indicates whether Continuous Wave mode is enabled or not for output. Supported values are:
|
|
Specifies the ITU-T standard supported by the QAM channel. Supported values are:
- unknown(1)
- other(2)
- annexA(3)
- annexB(4)
- annexC(5)
|
qamChannelCommonTable
The qamChannelCommonTable describes QAM channel output bandwidth and utilization information.
Table 3-43 lists MIB objects and description for qamChannelCommonTable.
Table 3-43 MIB Objects in qamChannelCommonTable
|
|
|
Specifies QAM channel output bandwidth or capacity. |
qamChannelCommonUtilization
|
Specifies the utilization of the QAM channel in 0.1 percentage. |
qamConfigTable
The qamConfigTable contains the following parameters:
- IP addresses configuration for the QAM channels.
- Program number range associated with QAM channels.
- UDP port range (optional).
Configuring these parameters is necessary when performing session-based provisioning. A session-based provisioning request must conform to the configurations in this table. The QAM channels within a QAM device may be partitioned to support multiple UDP, QAM, or ProgramNo ranges. You can also use this table to show the reserve UDP ports or program numbers for special purpose. The table entries are identified through qamConfigIndex.
Table 3-44 lists MIB objects for qamConfigTable.
Table 3-44 MIB Objects in qamConfigTable
|
|
|
Specifies table index. |
|
Contains entPhyIndex of RF linecard or 0 if there are no RF linecards. QAM channels are global to the QAM device. An RF linecard contains a number of RF/QAM channels. |
|
Specifies the minimum carrier ID among all the QAM channels associated with the corresponding QAM partition. QAM channel ID maybe within a line card or global depending on EntPhyIndex. |
|
Specifies the maximum carrier ID among all the QAM channels associated with the corresponding QAM partition. QAM channel ID maybe within a line card or global depending on EntPhyIndex. |
|
Specifies the type of the program destination address as defined by inetAddressType. The default value is 1 for ipv4(1). |
|
Specifies the IP address of the QAM channel. |
|
Specifies the lowest UDP port of the UDP port range that can be used on the QAM channel. |
|
Specifies the highest UDP port within the UDP port range that can be used on the QAM channel. |
|
Specifies the lowest MPEG output program number that can be used on the QAM channel. The default value is 1. |
|
Specifies the highest MPEG output program number that can be used on the QAM channel. The value ranges from 1 to 65535. The default value is 65535. |
MIB Constraints
There are no constraints for this MIB.
SNMP-FRAMEWORK-MIB
The SNMP-FRAMEWORK-MIB contains objects that describe the SNMP management architecture. This MIB was released as RFC 2571, An Architecture for Describing SNMP Management Frameworks.
The MODULE-IDENTITY for the SNMP-FRAMEWORK-MIB is snmpFrameworkMIB, and its top-level OID is 1.3.6.1.6.3.10 (iso.org.dod.internet.snmpv2.snmpModules.snmpFrameworkMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-MPD-MIB
The SNMP-MPD-MIB contains objects from the agent’s Message Processing and Dispatching (MPD) server that report on the the total number of packets received by the SNMP engine that were dropped because they referred to an unknown security model, were for an unknown application, or were otherwise invalid. This MIB was released as RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP).
The MODULE-IDENTITY for the SNMP-MPD-MIB is snmpMPDMIB, and its top-level OID is 1.3.6.1.6.3.11 (iso.org.dod.internet.snmpv2.snmpModules.snmpMPDMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-NOTIFICATION-MIB
The SNMP-NOTIFICATION-MIB contains objects to manage SNMP v3 notifications. This MIB was released as RFC 2573, SNMP Applications.
The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable). Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of SNMP notifications those entities are to receive.
The MODULE-IDENTITY for the SNMP-NOTIFICATION-MIB is snmpNotificationMIB, and its top-level OID is 1.3.6.1.6.3.13 (iso.org.dod.internet.snmpv2.snmpModules.snmpNotificationMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-TARGET-MIB
The SNMP-TARGET-MIB contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of entities to send SNMP notifications to, and contains a list of tag values that are used to filter the notifications sent to these entities (see the SNMP-NOTIFICATION-MIB). This MIB was defined as part of RFC 2573, SNMP Applications.
The MODULE-IDENTITY for the SNMP-TARGET-MIB is snmpTargetMIB, and its top-level OID is 1.3.6.1.6.3.12 (iso.org.dod.internet.snmpv2.snmpModules.snmpTargetMIB).
MIB Constraints
There are no constraints on this MIB.
SNMPv2-MIB
The SNMPv2-MIB contains objects to manage SNMPv2 entities on the Cisco RFGW-10. This MIB was released as RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2).
The MODULE-IDENTITY for the SNMPv2-MIB is snmpMIB, and its top-level OIDs are 1.3.6.1.6.3.1 (iso.org.dod.internet.snmpv2.snmpModules.snmpMIB) and 1.3.6.1.2.1.1 (iso.org.dod.internet.mgmt.mib-2.system).
MIB Constraints
There are no constraints on this MIB.