Reference record for OID 1.3.6.1.4.1.231.2.60.6.3.1.34.1

Parent
1.3.6.1.4.1.231.2.60.6.3.1.34 (hpiAnnouncementTable)
Node code
1
Node name
hpiAnnouncementEntry
Numeric OID
1.3.6.1.4.1.231.2.60.6.3.1.34.1
URN notation
urn:oid:1.3.6.1.4.1.231.2.60.6.3.1.34.1
ASN.1 notation

{1 3 6 1 4 1 231 2 60 6 3 1 34 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) sni(231) sniProductMibs(2) fscHpi(60) fscHpiBMIB(6) hpiEvents(3) events(1) hpiAnnouncementTable(34) hpiAnnouncementEntry(1)}
OID-IRI notation
  • /1/3/6/1/4/1/231/2/60/6/3/1/34/1
  • /ISO/Identified-Organization/6/1/4/1/231/2/60/6/3/1/34/1
  • /ISO/3/6/1/4/1/231/2/60/6/3/1/34/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/identified-organization/dod/internet/private/enterprises/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/org/dod/internet/private/enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/org/dod/internet/private/enterprises/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/org/dod/internet/private/ldap-enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/org/dod/internet/private/vendor-objects/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-organization/dod/internet/private/enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-organization/dod/internet/private/enterprises/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry
  • /iso/iso-organization/dod/internet/private/vendor-objects/sni/sniProductMibs/fscHpi/fscHpiBMIB/hpiEvents/events/hpiAnnouncementTable/hpiAnnouncementEntry

Descriptions

hpiAnnouncementEntry — Reviewed vendor MIB copies in Fujitsu ServerView, Fujitsu / Siemens native MIB archives

The table of announcements is used to provide a common interface to varied mechanisms for announcing conditions. Each announcement in an Annunciator's current set contains a severity level, details describing the specific condition that is being reported, an Acknowledged flag, a timestamp indicating when the announcement was added to the set, and an EntryId that uniquely identifies the particular status item within the set. EntryIds are assigned to announcements as they are added to the set as well as a Timestamp. After an announcement is deleted from the current set, its EntryId may be reused for a newly added announcement as long as the new announcement will have a different timestamp than any previously deleted announcement using the same EntryId. Thus, the EntryId and Timestamp together will uniquely identify any announcement, which was ever present in the Annunciator's set. The actual meaning of the Acknowledged flag is arbitrary, and the actions taken by the platform when announcements are flagged as 'acknowledged' or 'unacknowledged' are implementation-specific. The intended use of the flag is to indicate whether a particular announcement in the current set has been recognized by whomever or whatever is inspecting the LEDs, displays, etc., that are being driven by the Annunciator management instrument. Thus, when announcements are added to the current set, generally the flag should be set to indicate that the condition is 'unacknowledged'. Later, either as the result of an HPI User function call, or due to some implementation-dependent action (such as pressing an 'acknowledge' button on a front-panel display), the flag can be changed to indicate that the announcement is now 'acknowledged.' The ability to acknowledge announcements is not controlled by the Annunciator 'mode' setting (Auto, User, or Shared). Any announcement may be acknowledged by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function call, regardless of the current mode setting for the Annunciator. Over time, announcements are added to and deleted from an Annunciator`s current set of announcements. This may be done automatically by the HPI implementation to reflect platform fault conditions, or by the HPI User via the HPI interface. When announcements are added or deleted automatically by the HPI implementation, it is implementation-specific which announcements are added or removed.

Source records

hpiAnnouncementEntry

Status in source: mandatory.

Names: hpiAnnouncementEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hpiAnnouncementEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "HpiAnnouncementEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The table of announcements is used to provide a common interface to varied mechanisms for announcing conditions. Each announcement in an Annunciator's current set contains a severity level, details describing the specific condition that is being reported, an Acknowledged flag, a timestamp indicating when the announcement was added to the set, and an EntryId that uniquely identifies the particular status item within the set. EntryIds are assigned to announcements as they are added to the set as well as a Timestamp. After an announcement is deleted from the current set, its EntryId may be reused for a newly added announcement as long as the new announcement will have a different timestamp than any previously deleted announcement using the same EntryId. Thus, the EntryId and Timestamp together will uniquely identify any announcement, which was ever present in the Annunciator's set. The actual meaning of the Acknowledged flag is arbitrary, and the actions taken by the platform when announcements are flagged as 'acknowledged' or 'unacknowledged' are implementation-specific. The intended use of the flag is to indicate whether a particular announcement in the current set has been recognized by whomever or whatever is inspecting the LEDs, displays, etc., that are being driven by the Annunciator management instrument. Thus, when announcements are added to the current set, generally the flag should be set to indicate that the condition is 'unacknowledged'. Later, either as the result of an HPI User function call, or due to some implementation-dependent action (such as pressing an 'acknowledge' button on a front-panel display), the flag can be changed to indicate that the announcement is now 'acknowledged.' The ability to acknowledge announcements is not controlled by the Annunciator 'mode' setting (Auto, User, or Shared). Any announcement may be acknowledged by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function call, regardless of the current mode setting for the Annunciator. Over time, announcements are added to and deleted from an Annunciator`s current set of announcements. This may be done automatically by the HPI implementation to reflect platform fault conditions, or by the HPI User via the HPI interface. When announcements are added or deleted automatically by the HPI implementation, it is implementation-specific which announcements are added or removed. \"",
    "INDEX",
    "{",
    "hpiDomainId",
    ",",
    "hpiResourceId",
    ",",
    "hpiEventSeverity",
    ",",
    "hpiEventTimeStamp",
    "}",
    "::=",
    "{",
    "hpiAnnouncementTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "HpiAnnouncementEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The table of announcements is used to provide a common interface to varied mechanisms for announcing conditions. Each announcement in an Annunciator's current set contains a severity level, details describing the specific condition that is being reported, an Acknowledged flag, a timestamp indicating when the announcement was added to the set, and an EntryId that uniquely identifies the particular status item within the set. EntryIds are assigned to announcements as they are added to the set as well as a Timestamp. After an announcement is deleted from the current set, its EntryId may be reused for a newly added announcement as long as the new announcement will have a different timestamp than any previously deleted announcement using the same EntryId. Thus, the EntryId and Timestamp together will uniquely identify any announcement, which was ever present in the Annunciator's set. The actual meaning of the Acknowledged flag is arbitrary, and the actions taken by the platform when announcements are flagged as 'acknowledged' or 'unacknowledged' are implementation-specific. The intended use of the flag is to indicate whether a particular announcement in the current set has been recognized by whomever or whatever is inspecting the LEDs, displays, etc., that are being driven by the Annunciator management instrument. Thus, when announcements are added to the current set, generally the flag should be set to indicate that the condition is 'unacknowledged'. Later, either as the result of an HPI User function call, or due to some implementation-dependent action (such as pressing an 'acknowledge' button on a front-panel display), the flag can be changed to indicate that the announcement is now 'acknowledged.' The ability to acknowledge announcements is not controlled by the Annunciator 'mode' setting (Auto, User, or Shared). Any announcement may be acknowledged by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function call, regardless of the current mode setting for the Annunciator. Over time, announcements are added to and deleted from an Annunciator`s current set of announcements. This may be done automatically by the HPI implementation to reflect platform fault conditions, or by the HPI User via the HPI interface. When announcements are added or deleted automatically by the HPI implementation, it is implementation-specific which announcements are added or removed."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "hpiDomainId"
        ],
        [
          0,
          "hpiResourceId"
        ],
        [
          0,
          "hpiEventSeverity"
        ],
        [
          0,
          "hpiEventTimeStamp"
        ]
      ]
    ],
    null
  ]
}
  • Fujitsu / Siemens native MIB archives · Publisher's source file: FSC-HPI-MIB — archive MIB indexed for Fujitsu

    Vendor MIB copy from the MibBrowser.online archive. Fujitsu support.

    Module: FSC-HPI-MIB

    Published definition
    hpiAnnouncementEntry 	OBJECT-TYPE
    	SYNTAX HpiAnnouncementEntry
    	ACCESS not-accessible
    	STATUS mandatory
    	DESCRIPTION
    		"The table of announcements is used to provide
    		 a common interface to varied mechanisms for announcing conditions.
    		 Each announcement in an Annunciator's current set contains a severity level,
    		 details describing the specific condition that is being reported, an
    		 Acknowledged flag, a timestamp indicating when the announcement was added
    		 to the set, and an EntryId that uniquely identifies the particular status
    		 item within the set.
    		 EntryIds are assigned to announcements as they are added to the set as well
    		 as a Timestamp.  After an announcement is deleted from the current set, its
    		 EntryId may be reused for a newly added announcement as long as the new
    		 announcement will have a different timestamp than any previously deleted
    		 announcement using the same EntryId.  Thus, the EntryId and Timestamp
    		 together will uniquely identify any announcement, which was ever present
    		 in the Annunciator's set.
    		 
    		 The actual meaning of the Acknowledged flag is arbitrary, and the actions
    		 taken by the platform when announcements are flagged as 'acknowledged' or
    		 'unacknowledged' are implementation-specific.  The intended use of the flag
    		 is to indicate whether a particular announcement in the current set has been
    		 recognized by whomever or whatever is inspecting the LEDs, displays, etc.,
    		 that are being driven by the Annunciator management instrument.  Thus, when
    		 announcements are added to the current set, generally the flag should be set
    		 to indicate that the condition is 'unacknowledged'.  Later, either as the
    		 result of an HPI User function call, or due to some implementation-dependent
    		 action (such as pressing an 'acknowledge' button on a front-panel display),
    		 the flag can be changed to indicate that the announcement is now 'acknowledged.'
    		 
    		 The ability to acknowledge announcements is not controlled by the Annunciator
    		 'mode' setting (Auto, User, or Shared).  Any announcement may be acknowledged
    		 by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function
    		 call, regardless of the current mode setting for the Annunciator.
    		 
    		 Over time, announcements are added to and deleted from an Annunciator`s
    		 current set of announcements. This may be done automatically by the HPI
    		 implementation to reflect platform fault conditions, or by the HPI User
    		 via the HPI interface.  When announcements are added or deleted automatically
    		 by the HPI implementation, it is implementation-specific which announcements
    		 are added or removed.
    		 "
    	INDEX {
    		hpiDomainId,
    		hpiResourceId,
    		hpiEventSeverity,
    		hpiEventTimeStamp
    	}
    	::= { hpiAnnouncementTable 1 }
    Module imports
    {'RFC1155-SMI': ['enterprises', 'Gauge', 'Counter', 'IpAddress', 'TimeTicks'], 'RFC1212-MIB': ['OBJECT-TYPE'], 'RFC1215-MIB': ['TRAP-TYPE']}
    · Download FSC-HPI-MIB — archive MIB indexed for Fujitsu

    Related source files and packages:

    • RFC1155-SMI — dependency MIB (MibBrowser.online)Native third-party archive dependency for Fujitsu MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:04 GMT; 3,067 bytes
    • RFC1212-MIB — dependency MIB (MibBrowser.online)Native third-party archive dependency for Fujitsu MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:03 GMT; 2,714 bytes
    • RFC1215-MIB — dependency MIB (MibBrowser.online)Native third-party archive dependency for Fujitsu MIB imports; authorship is not attributed to that manufacturer; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:10 GMT; 3,883 bytes

    Source location: FSC-HPI-MIB::hpiAnnouncementEntry.
    Source version and references

    Published package: Fujitsu archived MIB undated archived revision; file: FSC-HPI-MIB.mib.

    Native third-party archive copy; vendor association comes from the archive catalog and does not establish a current manufacturer release; Copy from MibBrowser.online; Publisher Last-Modified: Sun, 01 Oct 2023 19:21:19 GMT; 254,618 bytes

    Downloaded: 2026-10-27T05:14:00.089151+00:00.

  • Reviewed vendor MIB copies in Fujitsu ServerView · Publisher's source file: Source package: SNMPMIBs.zip

    Module: FSC-HPI-MIB

    Published definition
    hpiAnnouncementEntry 	OBJECT-TYPE
    	SYNTAX HpiAnnouncementEntry
    	ACCESS not-accessible
    	STATUS mandatory
    	DESCRIPTION
    		"The table of announcements is used to provide
    		 a common interface to varied mechanisms for announcing conditions.
    		 Each announcement in an Annunciator's current set contains a severity level,
    		 details describing the specific condition that is being reported, an
    		 Acknowledged flag, a timestamp indicating when the announcement was added
    		 to the set, and an EntryId that uniquely identifies the particular status
    		 item within the set.
    		 EntryIds are assigned to announcements as they are added to the set as well
    		 as a Timestamp.  After an announcement is deleted from the current set, its
    		 EntryId may be reused for a newly added announcement as long as the new
    		 announcement will have a different timestamp than any previously deleted
    		 announcement using the same EntryId.  Thus, the EntryId and Timestamp
    		 together will uniquely identify any announcement, which was ever present
    		 in the Annunciator's set.
    		 
    		 The actual meaning of the Acknowledged flag is arbitrary, and the actions
    		 taken by the platform when announcements are flagged as 'acknowledged' or
    		 'unacknowledged' are implementation-specific.  The intended use of the flag
    		 is to indicate whether a particular announcement in the current set has been
    		 recognized by whomever or whatever is inspecting the LEDs, displays, etc.,
    		 that are being driven by the Annunciator management instrument.  Thus, when
    		 announcements are added to the current set, generally the flag should be set
    		 to indicate that the condition is 'unacknowledged'.  Later, either as the
    		 result of an HPI User function call, or due to some implementation-dependent
    		 action (such as pressing an 'acknowledge' button on a front-panel display),
    		 the flag can be changed to indicate that the announcement is now 'acknowledged.'
    		 
    		 The ability to acknowledge announcements is not controlled by the Annunciator
    		 'mode' setting (Auto, User, or Shared).  Any announcement may be acknowledged
    		 by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function
    		 call, regardless of the current mode setting for the Annunciator.
    		 
    		 Over time, announcements are added to and deleted from an Annunciator`s
    		 current set of announcements. This may be done automatically by the HPI
    		 implementation to reflect platform fault conditions, or by the HPI User
    		 via the HPI interface.  When announcements are added or deleted automatically
    		 by the HPI implementation, it is implementation-specific which announcements
    		 are added or removed.
    		 "
    	INDEX {
    		hpiDomainId,
    		hpiResourceId,
    		hpiEventSeverity,
    		hpiEventTimeStamp
    	}
    	::= { hpiAnnouncementTable 1 }
    Module imports
    {'RFC1212': ['OBJECT-TYPE'], 'RFC1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'Gauge', 'Counter', 'IpAddress', 'TimeTicks']}

    Source data warning: MIB copy distributed by Fujitsu in its ServerView package. The original vendor distribution and applicability to a particular device or firmware have not been independently confirmed; consult the named file and IANA enterprise registration.

    · Download ServerView MIB copy — HPI-MIBV1.mib (saved edition 1)

    Related source files and packages:


    Source location: FSC-HPI-MIB::hpiAnnouncementEntry.
    Source version and references

    Module FSC-HPI-MIB; IANA enterprise number(s) 231. MIB copy distributed by Fujitsu in its ServerView package. The original vendor distribution and applicability to a particular device or firmware have not been independently confirmed; consult the named file and IANA enterprise registration.; Publisher path: prim_supportcd/SVSSoftware/Software/ServerView/MIBs/SNMPMIBs.zip; 254,610 bytes

    Downloaded: 2026-11-03T06:22:27.387034+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.231)

Rothe Detlef

Direct children (15)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.231.2.60.6.3.1.34.1.1 hpiAnnouncementEntryId00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.2 hpiAnnouncementTimestamp00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.3 hpiAnnouncementAddedByUser00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.4 hpiAnnouncementSeverity00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.5 hpiAnnouncementAcknowledged00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.6 hpiAnnouncementStatusCondType00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.7 hpiAnnouncementEntityPath00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.8 hpiAnnouncementSensorNum00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.9 hpiAnnouncementEventState00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.10 hpiAnnouncementName00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.11 hpiAnnouncementMid00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.12 hpiAnnouncementTextType00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.13 hpiAnnouncementTextLanguage00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.14 hpiAnnouncementText00
1.3.6.1.4.1.231.2.60.6.3.1.34.1.15 hpiAnnouncementDelete00