OID repository
OID Repository
https://oid-base.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemprivate(4) Action itementerprise(1) Action item5591 Action itemscteHmsTree(1) Action iteminsidePlantIdent(11) Action itemheDigital(5) Action itemheManagedServer(6)   Navigating the OID tree
hmsScteSdvMib(1)
child OIDs: Child OID separator sdvServerMIBObjects(1) Child OID separator sdvServerEvents(2) Child OID separator sdvServerConformance(3) Child OID separator
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

hmsScteSdvMib MODULE-IDENTITY
LAST-UPDATED "200809241530Z"
ORGANIZATION
"SCTE HMS Working Group"
CONTACT-INFO
"SCTE HMS Subcommittee, Chairman
mailto: standards@SCTE.org"
DESCRIPTION
"The SCTE HMS MIB module to configure and monitor a
compliant Switched Digital Video server."
REVISION "200809241530Z"
DESCRIPTION
"ver 0.9
1. Changed objects with SYNTAX IpAddress to InetAddress.
2. Added objects for InetAddressType as required.
3. Changed enumerations starting with values of 0 to start with 1."
REVISION "200805221030Z"
DESCRIPTION
"ver 0.8
1. Removed extraneous comments and spacing.
2. Changed INTEGER to Integer32 per SMIv2
3. Moved SDV-MIB under heManagedServer under scteHmsTree
4. Renumbered nodes to remove gaps.
5. Changed sdvsmFreqPlanIndex and sdvsmAdZoneID from Integer32 to
Unsigned32 to prevent negative #'s
6. Added sdvsmProgramGroup and sdvsmClientConfigGroup to the
compliance statement"
REVISION "200704181730Z"
DESCRIPTION
"ver 0.2
1. Removed extraneous comments which described OID explicitly
(i.e. 1.3.6.1.4.1.5591.1.11.100).
2. Replaced SDB references w/ SDV.
3. Removed any SA or GQAM references.
4. Added unit and default clauses.
5. Changed indices to not-accessible and reordered objects so index
is first in table.
6. Added Compliance statement.
7. Used OBJECT-IDENTIFIER instead of OBJECT-IDENTITY for node
definitions that will not change.
8. Removed node definitions which had only one table defined under
it to avoid excessive layers.
9. Renamed node from sdvServerClientConfigParams to
sdvServerClientConfig.
10. There are several objects with ACCESS read-create; however,
comments indicate they are status only.
11. What does Alarm 209 mean?
12. Added alarm objects to eventTable instead of augmenting a
separate table.
13. Changed INT32 to UINT32 where descriptions indicated.
14. Changed INT32 to UINT32 where range was 1-2147483647.
15. Added/Removed objects from IMPORTS statement.
16. Updated organization and contact info.
17. Renamed sdvServerObjs as sdvServerMIBObjects.
18. Renumbered objects where there were gaps in numbering.
19. Changed SYNTAX from INTEGER to Integer32.
20. Removed not-accessible indices from conformance groups."


 
Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024
Tree display Parent OID: heManagedServer(6) First child OID: sdvServerMIBObjects(1)
Separation line
OID helper Webmaster Bullet 24 Apr 2023 Bullet Page top