Welcome,
Guest
|
Get quick Unbrowse SNMP help from Unleash Networks Engineers. The fastest way.
|
TOPIC: MIB will not load saying "seems to be SMIng"
MIB will not load saying "seems to be SMIng" 13 years 6 months ago #583
|
I can not add a MIB. It complains as follows:
Major Compiler Error: [2147500037] Unspecified error file `ETV-TSTV-RCS-MIB.mib' seems to be SMIng which is not supported OK : 0 Errors, 1 Warnings What in the world does that mean and how can I get it to load into unbrowse. I just want to print it. ssfbun |
The administrator has disabled public write access.
|
Re:MIB will not load saying "seems to be SMIng" 13 years 6 months ago #584
|
Can you send this MIB atleast a part of it by email to info at unleashnetworks dot com ? We will take a look at it.
|
The administrator has disabled public write access.
|
Re:MIB will not load saying "seems to be SMIng" 13 years 6 months ago #585
|
/* Ericsson Copyright notice:
(C) 2009-2010 Ericsson Television, Inc. All rights Reserved. The contents of this file may not be used for commercial purposes; copied; disclosed; reproduced; stored in a retrieval system or transmitted in any form or by any means, whether in whole or in part, without prior written agreement. */ -- Ericsson Television, Inc. Standard MIB disclaimer -- ########################################### -- SNMP MIBs for Ericsson products are developed -- primarily for use by Ericsson monitoring solutions. -- Where MIBs are provided to a Third Party or other -- non-Ericsson person, for the purposes of their -- development of a non-Ericsson monitoring solution, -- they are provided free of charge, and without obligation on the -- part of Ericsson to offer priority support, or changes -- to suit the third party. -- Ericsson Television -- This MIB defines the management objects and notification traps for the -- Time Shifted Television (TSTV) product - RCS. ETV-TSTV-RCS-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, enterprises, Integer32, IpAddress FROM SNMPv2-SMI OBJECT-GROUP, NOTIFICATION-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF DisplayString, DateAndTime FROM SNMPv2-TC; rcs MODULE-IDENTITY LAST-UPDATED "201004090000Z" -- April 9, 2010 ORGANIZATION "Ericsson Television" CONTACT-INFO "Amit Seth" DESCRIPTION "MIB for the TSTV Application (RCS Component)" REVISION "201004090000Z" DESCRIPTION "Updated the descriptions to give more clarity." REVISION "201003190000Z" DESCRIPTION "Added recording counters for each RM as well. Updated the descriptions to give more clarity." REVISION "201003180000Z" DESCRIPTION "Added more information for the RM and introduced severity levels for the traps. Also, included an error code and error description coming from RCS in the traps." REVISION "201003150000Z" DESCRIPTION "Added eventMessage (reason) to RM Online / Offline and RTC Online / Offline traps in order to include the reason for the change in status. Also, included asset life cycle details for captured recordings, capture failed recordings and provisioning failed recordings." REVISION "201003100000Z" DESCRIPTION "Initial version of this MIB" ::= { tstv 1 } ericsson OBJECT IDENTIFIER ::= { enterprises 11021 } tstv OBJECT IDENTIFIER ::= { ericsson 87 } -- Definition point for all notifications/traps from the RCS. rcsEvents OBJECT IDENTIFIER ::= { rcs 0 } -- Definition point for all the objects under RCS. rcsObjects OBJECT IDENTIFIER ::= { rcs 1 } -- Ericsson Television TSTV RCS MIB Objects tstvVersion OBJECT-TYPE SYNTAX DisplayString (SIZE(0..50)) MAX-ACCESS read-only STATUS current DESCRIPTION "The version of TSTV" ::= { rcsObjects 1 } -- Recording Counters pendingRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Pending State. This counter is a consolidation of all the pending recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 2 } capturingRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Capturing State. This counter is a consolidation of all the capturing recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 3 } provisioningRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Provisioning State. This counter is a consolidation of all the recordings being provisioned in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 4 } completedRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Completed State. This counter is a consolidation of all the completed recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording. And in case, the recording was completed on 1 RM but failed on the other RM, then the recording will be shown as a failed recording in this consolidated count." ::= { rcsObjects 5 } failedRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Failed State. This counter is a consolidation of all the failed recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording. And in case, the recording was completed on 1 RM but failed on the other RM, then the recording will be shown as a failed recording in this consolidated count." ::= { rcsObjects 6 } deletedRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Deleted State. This counter is a consolidation of all the deleted recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 7 } autoApprovedRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that were approved and created by an auto-approve right(s) or rule(s). This counter is a consolidation of all the auto-approved recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 8 } manualRecordings OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that were created manually from the UI. This counter is a consolidation of all the deleted recordings in the system. It is possible that the same recording has been scheduled on 2 or more RMs, but such a recording would be counted as one recording." ::= { rcsObjects 9 } -- EPG MIB Objects epgTable OBJECT-TYPE SYNTAX SEQUENCE OF EpgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "EPG Table." ::= { rcsObjects 10 } epgEntry OBJECT-TYPE SYNTAX EpgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The EPG Entry including the data described below." INDEX { epgIndex } ::= { epgTable 1 } EpgEntry ::= SEQUENCE { epgIndex Integer32, epgIngestSource OCTET STRING, lastEPGIngestDateTime DateAndTime, lastEPGIngestStatus INTEGER, daysEPGScheduleAvailable Integer32, nextEPGIngestDateTime DateAndTime } epgIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero that is equivalent to the sequence of every EPG Ingest in the TSTV system." ::= { epgEntry 1 } epgIngestSource OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The source/adapter that was used to ingest the EPG into the TSTV system. There are various adapters that could be used to generate the EPG Guide data into the ETV format. The filename that the adapter gives to the Guidedata is what is listed here." ::= { epgEntry 2 } lastEPGIngestDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The last Date/Time when the EPG was ingested. Once the Guide data is published on the TSTV system, it will be picked up and ingested. The ingestion process will include validation of the guide data, merging the current schedules with the new schedules which will take a few minutes. The Date and Time reported will be the time when the ingestion of the guide data is completed." ::= { epgEntry 3 } lastEPGIngestStatus OBJECT-TYPE SYNTAX INTEGER { success(1), failed(2), unknown(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The last EPG ingest status." ::= { epgEntry 4 } daysEPGScheduleAvailable OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of days for which the Schedule is available in the future as a result of the last EPG ingest. The days are calculated from the current date on the TSTV system when the EPG was ingested. For example, if the EPG Guide data listed was ingested on 4/19/2010 and the last schedule that was available was for 4/25/2010; the days available would be 6 days, even if you query on 4/23/2010. Hence, when you look at the days available it is in relation to the EPG Ingest Date." ::= { epgEntry 5 } nextEPGIngestDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The next estimated Date/Time when the EPG ingest will be attempted. Please note that this is only an estimate. The way the ingest would work is that it will pick up the Guide data files published within the TSTV system based on the configured time. But, the actual ingest time will vary based on the circumstances. For example, if 2 files are generated by the adapter(s) and published just before the scheduled ingest time, then both files will be picked for processing but will be processed sequentially. If the next scheduled time falls within the time that it takes for these 2 files to complete processing then the next file that is published will be picked up, but the actual ingest will happen only after the first 2 files are processed." ::= { epgEntry 6 } eventMessage OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The message that would be sent for every trap that is triggered. This message will include the complete exception that the TSTV application encountered which triggered the trap." ::= { rcsObjects 11 } rmTable OBJECT-TYPE SYNTAX SEQUENCE OF RmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "RM Table." ::= { rcsObjects 12 } rmEntry OBJECT-TYPE SYNTAX RmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RM Entry including the data described below." INDEX { rmIndex } ::= { rmTable 1 } RmEntry ::= SEQUENCE { rmIndex Integer32, rmName DisplayString, rmAddress IpAddress, rmStatus INTEGER, rmType INTEGER, rmRedundancyStatus INTEGER, rmRedundancyPartner DisplayString, pendingRecordingsRM Integer32, capturingRecordingsRM Integer32, provisioningRecordingsRM Integer32, completedRecordingsRM Integer32, failedRecordingsRM Integer32, deletedRecordingsRM Integer32 } rmIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero assigned to the RM in the TSTV system." ::= { rmEntry 1 } rmName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "The name that is assigned to the Recording Manager(RM)." ::= { rmEntry 2 } rmAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address that is assigned to the Recording Manager(RM)." ::= { rmEntry 3 } rmStatus OBJECT-TYPE SYNTAX INTEGER { online(1), offline(2), unknown(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current status of the RM." ::= { rmEntry 4 } rmType OBJECT-TYPE SYNTAX INTEGER { etv(1), isa(2), l2v(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of RM that represents how the RM interacts with RTC." ::= { rmEntry 5 } rmRedundancyStatus OBJECT-TYPE SYNTAX INTEGER { primary(1), secondary(2), nonredundant(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This defines if the RM is deployed in a redundant state or not. And if redundant, then this RM is either the Primary or the Secondary." ::= { rmEntry 6 } rmRedundancyPartner OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the redundancy partner, which would be the IP address of the Primary if this is the redundant RM, or the IP address of the Secondary if this is the primary RM or it can be empty in case the RM is non-redundant." ::= { rmEntry 7 } pendingRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Pending State. These are the recordings that have been scheduled till the date that the schedule is available. This number does not include any recordings that have been auto-approved, but the schedule for which is currently not available." ::= { rmEntry 8 } capturingRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Capturing State." ::= { rmEntry 9 } provisioningRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Provisioning State." ::= { rmEntry 10 } completedRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Completed State. These are the recordings that have been completely successful." ::= { rmEntry 11 } failedRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Failed State. These recordings number does not reflect the complete state of the recording, as we report a partial failure as a failure. It is possible that the recording was captured successfully, and while provisioning to 3 different dowstreams, one of the provisionings has failed. But, even then the recording would be reported as failed. Similarly, even if capture and provisioning were both successful and in cases where the content was supposed to get purged from the RTC and did not get purged, the recording would be marked as a failure." ::= { rmEntry 12 } deletedRecordingsRM OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of recordings that are currently in the Deleted State." ::= { rmEntry 13 } rtcTable OBJECT-TYPE SYNTAX SEQUENCE OF RtcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "RTC Table." ::= { rcsObjects 13 } rtcEntry OBJECT-TYPE SYNTAX RtcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The RTC Entry including the data described below." INDEX { rtcIndex } ::= { rtcTable 1 } RtcEntry ::= SEQUENCE { rtcIndex Integer32, rtcName DisplayString, rtcAddress IpAddress, rtcStatus INTEGER } rtcIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero assigned to the RTC in the TSTV system." ::= { rtcEntry 1 } rtcName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "The name that is assigned to the RTC." ::= { rtcEntry 2 } rtcAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address that is assigned to the RTC." ::= { rtcEntry 3 } rtcStatus OBJECT-TYPE SYNTAX INTEGER { online(1), offline(2), unknown(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current status of the RTC." ::= { rtcEntry 4 } capturedRecordingsTable OBJECT-TYPE SYNTAX SEQUENCE OF CapturedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table reflecting the current state in the asset life cycle for all recordings that have updated status within the last 1 hour and have completed capturing. Historical data about recordings that has an updated status earlier than 1 hour from the current time will not be available via SNMP." ::= { rcsObjects 14 } capturedRecordingsEntry OBJECT-TYPE SYNTAX CapturedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Entry for the recordings that completed capturing within the last 1 hour - including the data described below." INDEX { capturedRecordingsIndex } ::= { capturedRecordingsTable 1 } CapturedRecordingsEntry ::= SEQUENCE { capturedRecordingsIndex Integer32, capturedRecordingsAssetName OCTET STRING, capturedRecordingsFileName OCTET STRING, capturedRecordingsMinutes Integer32, provisioningStatus INTEGER, encodingInformation OCTET STRING } capturedRecordingsIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero assigned to the recordings object in the TSTV system." ::= { capturedRecordingsEntry 1 } capturedRecordingsAssetName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The asset name that is assigned to the captured recording." ::= { capturedRecordingsEntry 2 } capturedRecordingsFileName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The filename associated with the captured recording." ::= { capturedRecordingsEntry 3 } capturedRecordingsMinutes OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The length of the recording captured in minutes." ::= { capturedRecordingsEntry 4 } provisioningStatus OBJECT-TYPE SYNTAX INTEGER { successful(1), failed(2), unknown(3), inprogress(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current provisioning status of the recording captured. In cases where the provisioning is done to more than one downstreams, and if anyone fails, then the provisioning status is set to failed(2), but others may have been successful. You will need to look at the detailed recording information available on the RCS UI to verify provisioning to which downstream(s) failed." ::= { capturedRecordingsEntry 5 } encodingInformation OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The encoding / codec information associated with the captured recording." ::= { capturedRecordingsEntry 6 } captureFailedRecordingsTable OBJECT-TYPE SYNTAX SEQUENCE OF CaptureFailedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table reflecting the current state in the asset life cycle for all recordings that have failed capture within the last 1 hour. Historical data about recordings that failed capturing earlier than 1 hour from the current time will not be available via SNMP." ::= { rcsObjects 15 } captureFailedRecordingsEntry OBJECT-TYPE SYNTAX CaptureFailedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Entry for the recordings that failed capturing within the last 1 hour - including the data described below." INDEX { captureFailedRecordingsIndex } ::= { captureFailedRecordingsTable 1 } CaptureFailedRecordingsEntry ::= SEQUENCE { captureFailedRecordingsIndex Integer32, captureFailedRecordingsAssetName OCTET STRING } captureFailedRecordingsIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero assigned to the recordings object in the TSTV system." ::= { captureFailedRecordingsEntry 1 } captureFailedRecordingsAssetName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The asset name that is assigned to the recording that failed to capture." ::= { captureFailedRecordingsEntry 2 } provisionFailedRecordingsTable OBJECT-TYPE SYNTAX SEQUENCE OF ProvisionFailedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table reflecting the current state in the asset life cycle for all recordings that have completed capture, but failed during provisioning within the last 1 hour. Historical data about recordings that completed capturing earlier than 1 hour from the current time will not be available via SNMP." ::= { rcsObjects 16 } provisionFailedRecordingsEntry OBJECT-TYPE SYNTAX ProvisionFailedRecordingsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Entry for the recordings that completed capturing, but failed provisioning within the last 1 hour - including the data described below." INDEX { provisionFailedRecordingsIndex } ::= { provisionFailedRecordingsTable 1 } ProvisionFailedRecordingsEntry ::= SEQUENCE { provisionFailedRecordingsIndex Integer32, provisionFailedRecordingsAssetName OCTET STRING } provisionFailedRecordingsIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value greater than zero assigned to the recordings object in the TSTV system." ::= { provisionFailedRecordingsEntry 1 } provisionFailedRecordingsAssetName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The asset name that is assigned to the captured recording that failed to provision." ::= { provisionFailedRecordingsEntry 2 } errorCode OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "An error code that is defined in the TSTV system and is associated with the trap that is being sent out." ::= { rcsObjects 17 } errorDescription OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The error description defined for the associated trap that is triggered on an error condition." ::= { rcsObjects 18 } eventSeverity OBJECT-TYPE SYNTAX INTEGER { critical(1), major(2), minor(3), warning(4) } MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The severity level that would be sent for every trap that is triggered." ::= { rcsObjects 19 } -- TSTV Events / Alarms captureFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case of a capture failure. It will include the error code, error description, a detailed message, and the event severity as part of the trap. The AssetID is sent as part of the eventMessage for any recording capture that fails in order to help identify the recording that failed. Example eventMessage: 'Capture for CaptureName: BSPK7002000000015746__7002__2 failed with status description of:16588$Capture Ended. Result code is 1, Did not find an iframe in the multicast data stream, is data present?'" ::= { rcsEvents 1 } provisionFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case of a provisioning failure. It will include the error code, error description, a detailed message, and the event severity as part of the trap. The AssetID is sent as part of the eventMessage for any recording for which provisioning fails in order to help identify the recording for which provisioning failed." ::= { rcsEvents 2 } recordingTimedOut NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case the recording has been either in the capturing or provisioning state for longer than expected. It means that the recording will not complete and the system will mark the recording as Timed Out. The trap will include the error code, error description, a detailed message, and the event severity as part of the trap. The AssetID is included in the eventMessage for any recording which has timed out in order to help identify the recording which has failed as a result." ::= { rcsEvents 3 } recordingFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case of a recording failure. It will include the error code, error description, a detailed message, and the event severity as part of the trap. These are the recordings that have failed for reasons other than capture failure, provision failure, or recording timed out. The AssetID is included in the eventMessage in case of such a failure to help identify the recording that failed." ::= { rcsEvents 4 } rightExecutionFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case of a failure during rights execution. It will include the error code, error description, a detailed message, and the event severity as part of the trap. The name of the right along with a detailed description of what failure resulted from the execution of the particular right is included in the eventMessage." ::= { rcsEvents 5 } rulesExecutionFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent in case of a failure during rules execution. It will include the error code, error description, a detailed message, and the event severity as part of the trap. The name of the rule along with a detailed description of what failure resulted from the execution of the particular rule is included in the eventMessage." ::= { rcsEvents 6 } scheduleRecordingFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This trap is sent when a request to schedule the recording fails. The scheduled recording could be auto-approved or a manual recording. It will include the error code, error description, a detailed message and the event severity as part of the trap." ::= { rcsEvents 7 } rcsQueueManagerFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "This is the trap that is sent when any problem is detected with the RCS Queue Manager which is taking the schedules and sending it across to the right RM, which in turn will take care of allocating the RTC to be used for recording the content. It will include the error code, error description, a detailed message and the event severity as part of the trap. A description explaining what went wrong with the RCS queue manager is sent as a trap." ::= { rcsEvents 8 } epgAdapterFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "The EPG Adapter is responsible for getting the Guide data from the EPG provider and then translating the same to the ETV format. In the process if something goes wrong like the download failed, or incorrect data or a failure to translate, then this is the trap that will be sent. It will include the error code, error description, a detailed message and the event severity as part of the trap. A description explaining what went wrong with the EPG adapter, while downloading and then translating from the EPG source to the ETV format is included in the eventMessage." ::= { rcsEvents 9 } epgIngestFailed NOTIFICATION-TYPE OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "The Guide data that is translated by the EPG adapter is then ingested into the TSTV system. During this process of ingestion if there is an error, then this would be the trap that will be sent. It will include the error code, error description, a detailed message and the event severity as part of the trap. A description explaining what went wrong while the EPG was being ingested is included in the eventMessage." ::= { rcsEvents 10 } rmOnline NOTIFICATION-TYPE OBJECTS { rmName, rmAddress, rmStatus, eventMessage, rmRedundancyStatus, eventSeverity } STATUS current DESCRIPTION "A trap is sent whenever an RM changes its status to Online from any other state. This trap will include the name of the RM, I.P. address of the RM, the current status (online), an event message explaining any reason that may have been provided, the redundancy status of the RM and the event severity for the trap." ::= { rcsEvents 11 } rmOffline NOTIFICATION-TYPE OBJECTS { rmName, rmAddress, rmStatus, eventMessage, rmRedundancyStatus, eventSeverity } STATUS current DESCRIPTION "A trap is sent whenever an RM changes its status to Offline from an Online state. This trap will include the name of the RM, I.P. address of the RM, the current status (offline), an event message explaining any reason that may have been provided, the redundancy status of the RM and the event severity for the trap. The redundancy status should help understand the impact on the operations, as non-redundant status would mean that there is a probablity of loosing the status updates of recordings or a failure to schedule recordings while the RM is offline." ::= { rcsEvents 12 } rtcOnline NOTIFICATION-TYPE OBJECTS { rtcName, rtcAddress, rtcStatus, eventMessage, eventSeverity } STATUS current DESCRIPTION "A trap is sent whenever an RTC changes its status to Online from any other state. This trap will include the name of the RTC, I.P. address of the RTC, the current status (online), an event message explaining any reason that may have been provided and the event severity for the trap." ::= { rcsEvents 13 } rtcOffline NOTIFICATION-TYPE OBJECTS { rtcName, rtcAddress, rtcStatus, eventMessage, eventSeverity } STATUS current DESCRIPTION "A trap is sent whenever an RTC changes its status to Offline from an Online state. This trap will include the name of the RTC, I.P. address of the RTC, the current status (offline), an event message explaining any reason that may have been provided and the event severity for the trap." ::= { rcsEvents 14 } -- Groups rcsGeneralDetails OBJECT-GROUP OBJECTS { tstvVersion } STATUS current DESCRIPTION "Currently only version information is included." ::= { rcsGroups 1 } recordingsDetails OBJECT-GROUP OBJECTS { pendingRecordings, capturingRecordings, provisioningRecordings, completedRecordings, failedRecordings, deletedRecordings, autoApprovedRecordings, manualRecordings } STATUS current DESCRIPTION "A collection of recordings counters in the system currently based on their state or how they were created." ::= { rcsGroups 2 } epgDetails OBJECT-GROUP OBJECTS { epgIngestSource, lastEPGIngestDateTime, nextEPGIngestDateTime, lastEPGIngestStatus, daysEPGScheduleAvailable } STATUS current DESCRIPTION "A collection of EPG related information." ::= { rcsGroups 3 } rmDetails OBJECT-GROUP OBJECTS { rmName, rmAddress, rmStatus, rmType, rmRedundancyStatus, rmRedundancyPartner, pendingRecordingsRM, capturingRecordingsRM, provisioningRecordingsRM, completedRecordingsRM, failedRecordingsRM, deletedRecordingsRM } STATUS current DESCRIPTION "Information details for each RM." ::= { rcsGroups 4 } rtcDetails OBJECT-GROUP OBJECTS { rtcName, rtcAddress, rtcStatus } STATUS current DESCRIPTION "Information details for each RTC." ::= { rcsGroups 5 } rcsTraps NOTIFICATION-GROUP NOTIFICATIONS { captureFailed, provisionFailed, recordingTimedOut, recordingFailed, rightExecutionFailed, rulesExecutionFailed, scheduleRecordingFailed, rcsQueueManagerFailed, epgAdapterFailed, epgIngestFailed, rmOnline, rmOffline, rtcOnline, rtcOffline } STATUS current DESCRIPTION "All the traps generated from TSTV (RCS)." ::= { rcsGroups 6 } rcsEventVariable OBJECT-GROUP OBJECTS { errorCode, errorDescription, eventMessage, eventSeverity } STATUS current DESCRIPTION "Included only for conformance." ::= { rcsGroups 7 } capturedRecordingsDetails OBJECT-GROUP OBJECTS { capturedRecordingsAssetName, capturedRecordingsFileName, capturedRecordingsMinutes, provisioningStatus, encodingInformation } STATUS current DESCRIPTION "Details for all the recordings that completed capturing within the last 1 hour." ::= { rcsGroups 8 } captureFailedRecordingsDetails OBJECT-GROUP OBJECTS { captureFailedRecordingsAssetName } STATUS current DESCRIPTION "Details for all the recordings that failed capturing within the last 1 hour." ::= { rcsGroups 9 } provisionFailedRecordingsDetails OBJECT-GROUP OBJECTS { provisionFailedRecordingsAssetName } STATUS current DESCRIPTION "Details for all the recordings that completed capturing within the last 1 hour, but failed during provisioning." ::= { rcsGroups 10 } -- Conformance Information rcsConformance OBJECT IDENTIFIER ::= { rcs 2 } rcsGroups OBJECT IDENTIFIER ::= { rcsConformance 1 } rcsCompliances OBJECT IDENTIFIER ::= { rcsConformance 2 } -- Compliance Statement rcsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for TSTV SNMP entities." MODULE -- this module MANDATORY-GROUPS { rcsGeneralDetails, recordingsDetails, epgDetails, rmDetails, rtcDetails, capturedRecordingsDetails, captureFailedRecordingsDetails, provisionFailedRecordingsDetails, rcsTraps } GROUP rcsEventVariable DESCRIPTION "This group is mandatory only as a side-effect of the variables being used in most of the rcsTraps." ::= { rcsCompliances 1 } END |
The administrator has disabled public write access.
|
Re:MIB will not load saying "seems to be SMIng" 13 years 6 months ago #586
|
The C-style comment block is invalid. Remove that or change it into valid MIB (ASN.1) comment and it will load.
Ie. Remove this block /* Ericsson Copyright notice: (C) 2009-2010 Ericsson Television, Inc. .... */ or replace it with this -- Ericsson Copyright notice: -- (C) 2009-2010 Ericsson Television, Inc. -- All rights Reserved. -- -- etc |
The administrator has disabled public write access.
|
Re:MIB will not load saying "seems to be SMIng" 13 years 6 months ago #587
|
I agree the error message is off mark. Will fix it in next build.
|
The administrator has disabled public write access.
|
|
Moderators: vivek [unleash]
Time to create page: 0.246 seconds