Reference record for OID 1.3.6.1.2.1.47.1.2.1.1.4

Parent
1.3.6.1.2.1.47.1.2.1.1 (entLogicalEntry)
Node code
4
Node name
entLogicalCommunity
Numeric OID
1.3.6.1.2.1.47.1.2.1.1.4
URN notation
urn:oid:1.3.6.1.2.1.47.1.2.1.1.4
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 2 1 47 1 2 1 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) entityMIB(47) entityMIBObjects(1) entityLogical(2) entLogicalTable(1) entLogicalEntry(1) entLogicalCommunity(4)}
OID-IRI notation
  • /1/3/6/1/2/1/47/1/2/1/1/4
  • /ISO/Identified-Organization/6/1/2/1/47/1/2/1/1/4
  • /ISO/3/6/1/2/1/47/1/2/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/identified-organization/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/org/dod/internet/mgmt/stdmib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-organization/dod/internet/mgmt/mib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-organization/dod/internet/mgmt/mib/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/entityMIB/entityMIBObjects/entityLogical/entLogicalTable/entLogicalEntry/entLogicalCommunity

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

entLogicalCommunity OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"An SNMPv1 or SNMPv2C community-string which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all managed
objects) and may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may return a community string with read-only
privileges, even if this object is accessed with a read-
write community string. However, the agent must take care
not to return a community string which allows more
privileges than the community string used to access this
object.
A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single default
naming scope. This is possible when the logical entities
represented by the same value of entLogicalCommunity have no
object instances in common. For example, ridge1 and

epeater1 may be part of the main naming scope, but at
least one additional community string is needed to represent
ridge2 and
epeater2.
Logical entities ridge1 and
epeater1 would be
represented by sysOREntries associated with the default
naming scope.
For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or no community string with
suitable access rights can be returned for a particular SNMP
request.
Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support)."

View at oid-base.com
Automatically extracted from RFC2737

Alternative description: Circitor

An SNMPv1 or SNMPv2C community-string, which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all managed
objects) and may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may return a community string with read-only
privileges, even if this object is accessed with a
read-write community string. However, the agent must take



care not to return a community string that allows more
privileges than the community string used to access this
object.

A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single 'default'
naming scope. This is possible when the logical entities,
represented by the same value of entLogicalCommunity, have
no object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but at
least one additional community string is needed to represent
'bridge2' and 'repeater2'.

Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'default'
naming scope.

For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or if no community string with
suitable access rights can be returned for a particular SNMP
request.

Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support).

Parsed from file ENTITY-MIB.mib
Module: ENTITY-MIB

Source file: Download ENTITY-MIB.mib

Publisher path: Mibs; 60,728 bytes

Alternative description: Cisco

An SNMPv1 or SNMPv2C community-string, which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all managed
objects) and may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may return a community string with read-only
privileges, even if this object is accessed with a
read-write community string. However, the agent must take


care not to return a community string that allows more
privileges than the community string used to access this
object.

A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single 'default'
naming scope. This is possible when the logical entities,
represented by the same value of entLogicalCommunity, have
no object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but at
least one additional community string is needed to represent
'bridge2' and 'repeater2'.

Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'default'
naming scope.

For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or if no community string with
suitable access rights can be returned for a particular SNMP
request.

Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support).

Source file: Download ENTITY-MIB.my · Publisher's file

S3200 Series Switches SNMP MIB Files; Models: S3200-8MG4S, S3200-8MG4S-U; Catalog updated: 2025-11-24 18:13:56; File: S3200 Series Switches SNMP MIB Files/ENTITY-MIB.my; Publisher path: mall/resource/s3200-series-switches-snmp-mib-files.zip; 59,499 bytes

Related source files and packages:

  • S3200 Series Switches SNMP MIB FilesS3200 Series Switches SNMP MIB Files; Models: S3200-8MG4S, S3200-8MG4S-U; Catalog updated: 2025-11-24 18:13:56; File: mall/resource/s3200-series-switches-snmp-mib-files.zip; Publisher Last-Modified: Mon, 24 Nov 2025 10:13:56 GMT; 14,370 bytes

Source file: Download rfc4133-entity.mib · Publisher's file

IES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: FS_MIB/rfc4133-entity.mib; Publisher path: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; 59,144 bytes

Related source files and packages:

  • IES5120-28TF Switch SNMP MIB FilesIES5120-28TF Switch SNMP MIB Files; Models: IES5120-28TF; Catalog updated: 2026-02-27 15:56:52; File: mall/resource/ies5120-28tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:14:36 GMT; 2.6 MiB
  • IES3220-8T4F Switch SNMP MIB FilesIES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:08:16 GMT; 2.6 MiB
  • IES5120-48T4S Switch SNMP MIB FilesIES5120-48T4S Switch SNMP MIB Files; Models: IES5120-48T4S; Catalog updated: 2026-02-27 16:10:26; File: mall/resource/ies5120-48t4s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:16:11 GMT; 2.6 MiB
Show all 10 related files and packages
  • TSN3220-10S Switch SNMP MIB FilesTSN3220-10S Switch SNMP MIB Files; Models: TSN3220-10S; Catalog updated: 2026-01-08 09:53:00; File: mall/resource/tsn3220-10s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:10:41 GMT; 2.6 MiB
  • IES5120-28TS-P Switch SNMP MIB FilesIES5120-28TS-P Switch SNMP MIB Files; Models: IES5120-28TS-P; Catalog updated: 2026-02-27 16:09:52; File: mall/resource/ies5120-28ts-p-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:40 GMT; 2.6 MiB
  • IES5220-30TS-3ES Switch SNMP MIB FilesIES5220-30TS-3ES Switch SNMP MIB Files; Models: IES5220-30TS-3ES; Catalog updated: 2025-08-19 16:17:18; File: mall/resource/ies5220-30ts-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:17:18 GMT; 2.6 MiB
  • IES5220-6S-3ES Switch SNMP MIB FilesIES5220-6S-3ES Switch SNMP MIB Files; Models: IES5220-6S-3ES; Catalog updated: 2026-02-27 16:11:15; File: mall/resource/ies5220-6s-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:32:47 GMT; 2.6 MiB
  • IES3220-8T4F-U Switch SNMP MIB FilesIES3220-8T4F-U Switch SNMP MIB Files; Models: IES3220-8T4F-U; Catalog updated: 2025-12-03 14:47:49; File: mall/resource/ies3220-8t4f-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:09:07 GMT; 2.6 MiB
  • IES5120-28TS Switch SNMP MIB FilesIES5120-28TS Switch SNMP MIB Files; Models: IES5120-28TS; Catalog updated: 2026-02-27 15:57:39; File: mall/resource/ies5120-28ts-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:08 GMT; 2.6 MiB
  • TSN3220-10S-U Switch SNMP MIB FilesTSN3220-10S-U Switch SNMP MIB Files; Models: TSN3220-10S-U; Catalog updated: 2025-12-16 18:11:48; File: mall/resource/tsn3220-10s-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:13:57 GMT; 2.6 MiB
Other official packages with the same file

tsn3220-10s-u-switch-snmp-mib-files.zip

tsn3220-10s-switch-snmp-mib-files.zip

ies5220-6s-3es-switch-snmp-mib-files.zip

ies5220-30ts-3es-switch-snmp-mib-files.zip

Source file: Download ENTITY-MIB.txt · Publisher's file

IES3110-8TFP-R Switch SNMP MIB Files; Models: IES3110-8TFP-R; Catalog updated: 2026-01-15 17:50:02; File: FSMIB/ENTITY-MIB.txt; Publisher path: mall/resource/ies3110-8tfp-r-switch-snmp-mib-files.zip; 59,262 bytes

Related source files and packages:

  • IES3110-8TFP-R Switch SNMP MIB FilesIES3110-8TFP-R Switch SNMP MIB Files; Models: IES3110-8TFP-R; Catalog updated: 2026-01-15 17:50:02; File: mall/resource/ies3110-8tfp-r-switch-snmp-mib-files.zip; Publisher Last-Modified: Thu, 15 Jan 2026 09:50:02 GMT; 682,112 bytes

Source file: Download stdent.mib · Publisher's file

Firmware > Magnum 5RX_10RX > 5RX_10RX MIB 2018-12-31 17:02:37; Publisher path: partner/sfc/servlet.shepherd/document/download/069Qp00000ju6teIAA; 59,144 bytes

Related source files and packages:

Source file: Download ENTITY-MIB.txt · Publisher's file

Hi-SCOM 2023-01-12 01:45:32; File: Hi-SCOM_MIB_BN_V01/public/ENTITY-MIB.txt; Publisher path: partner/sfc/servlet.shepherd/document/download/069Qp00000jtUdAIAU; 59,262 bytes

Related source files and packages:

Source file: Download ENTITY-MIB-V3-RFC4133.mib · Publisher's file

File: FS728TLP_FS526Tv2_FS726Tv2_MIB_File_20140110/ENTITY-MIB-V3-RFC4133.mib; Publisher path: files/GDC/FS526TV2/FS728TLP_FS526Tv2_FS726Tv2_MIB_File_1.0.1.21_20140110.zip; 61,238 bytes

Related source files and packages:

Other official packages with the same file

FS728TLP_FS526Tv2_FS726Tv2_MIB_File_20140110.zip

FS728TLP_FS526Tv2_FS726Tv2_MIB_File_20140110.zip

Source file: Download ENTITY-MIB.my · Publisher's file

File: MIB/Standard/ENTITY-MIB.my; Publisher path: RGS200-12P/mib_file/RGS200-12P_1.zip; 59,262 bytes

Related source files and packages:

Source file: Download ENTITY-MIB.mib · Publisher's file

File: DGS-1510_MIB_20150902/standardMIB/ENTITY-MIB.mib; Publisher path: pub/Switch/DGS-1510-20/SNMP/DGS-1510_Series_A1_FW_v1.30.007_MIB.zip; 60,558 bytes

Related source files and packages:

Show all 23 related files and packages
Other official packages with the same file

DXS-3610_A1_MIB_v1.01.zip

MIB.rar

MIB.rar

DXS-1210-R1.00-MIB-20200515.7z

Source file: Download rfc4133.mib · Publisher's file

File: DES-3200_MIB_20150731/public/rfc4133.mib; Publisher path: pub/Switch/DES-3200-10_C1/SNMP/DES-3200_MIB_20150731.zip; 60,924 bytes

Related source files and packages:

Show all 17 related files and packages
Other official packages with the same file

DES-3200_R4.46_MIB.zip

DES-3200_R4.46_MIB.zip

DES-3200_MIB_20150731.zip

DES-3200_R4.46_MIB.zip

Source file: Download rfc4133.txt · Publisher's file Junos OS Evolved 26.2R1

Junos OS Evolved 26.2R1; File: ./rfc4133.txt; Publisher path: mib-explorer/downloadArchive; 59,148 bytes

Other official packages with the same file

Junos OS 26.2R1

Alternative description: Cisco SMIv1

An SNMPv1 or SNMPv2C community-string, which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all managed
objects) and may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may return a community string with read-only
privileges, even if this object is accessed with a
read-write community string. However, the agent must take


care not to return a community string that allows more
privileges than the community string used to access this
object.

A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single 'default'
naming scope. This is possible when the logical entities,
represented by the same value of entLogicalCommunity, have
no object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but at
least one additional community string is needed to represent
'bridge2' and 'repeater2'.

Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'default'
naming scope.

For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or if no community string with
suitable access rights can be returned for a particular SNMP
request.

Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support).

Source file: Download ENTITY-MIB-V1SMI.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v1/ENTITY-MIB-V1SMI.my; 52,227 bytes

Source file: Download ENTITY-MIB-V1SMI.my.txt

File: cisco/ENTITY-MIB-V1SMI.my.txt; 53,599 bytes

Alternative description: MIBdepot

An SNMPv1 or SNMPv2C community-string, which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all managed
objects) and may also return a community string based on the
privileges of the request used to read this object. Note
that an agent may return a community string with read-only
privileges, even if this object is accessed with a
read-write community string. However, the agent must take



care not to return a community string that allows more
privileges than the community string used to access this
object.

A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single 'default'
naming scope. This is possible when the logical entities,
represented by the same value of entLogicalCommunity, have
no object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but at
least one additional community string is needed to represent
'bridge2' and 'repeater2'.

Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'default'
naming scope.

For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also
contain an empty string if a community string has not yet
been assigned by the agent, or if no community string with
suitable access rights can be returned for a particular SNMP
request.

Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent
support).

Source file: Download ENTITY-MIB.mib.txt

File: vmware/ENTITY-MIB.mib.txt; 59,268 bytes

Source file: Download ENTITY-MIB.txt

File: rittal/ENTITY-MIB.txt; 59,229 bytes

Source file: Download rfc4133-Entity-MIB-Version-3.mib.txt

File: ietf_rfcs/rfc4133-Entity-MIB-Version-3.mib.txt; 60,902 bytes

Source file: Download ENTITY-MIB.my.txt

File: cisco/ENTITY-MIB.my.txt; 60,965 bytes

Source file: Download ENTITY-MIB.mib.txt

File: avaya/ENTITY-MIB.mib.txt; 59,289 bytes

entLogicalCommunity — Huawei official enterprise MIB Query and object descriptions

This object indicates the community name of SNMPv2. The default value is 1.

Implementation notes: Get return NULL string

entLogicalCommunity — D-Link official switch MIBs, FS.COM official Documentation Hub native MIB packages, HPE Instant On official MIBs, LANCOM official release MIBs, MIBdepot, NETGEAR official product and EOL MIB downloads, RFC Editor

An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read- write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent, or no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents which implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object, or may continue to return a community string (e.g., tri-lingual agent support).

entLogicalCommunity — MIBdepot, RFC Editor

An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also choose to return a community string based on the privileges of the request used to read this object. Note that an agent may choose to return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'main' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'main' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty-string.

entLogicalCommunity — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Common and standard MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies, RFC Editor

An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object or may continue to return a community string (e.g., tri-lingual agent support).

entLogicalCommunity — Huawei official enterprise MIB Query and object descriptions

An SNMPv1 or SNMPv2C community-string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent, or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents which implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object, or may continue to return a community string (e.g., tri-lingual agent support).

entLogicalCommunity — Huawei official enterprise MIB Query and object descriptions

This object indicates the community name of SNMPv1/v2. The default value is 1.

Implementation notes: Get return NULL string

entLogicalCommunity — H3C official MIB documentation and object descriptions

SNMPv1 or SNMPv2C community string, used to access detailed management information for the logical entity.

Source records

entLogicalCommunity

Status in source: unspecified.

Names: entLogicalCommunity

Technical details
{
  "syntax": "OctetString min: 0 max: 255",
  "max_access": "read-only",
  "object_class": "table column",
  "implementation_notes": "Get return NULL string"
}

entLogicalCommunity

Status in source: deprecated.

Names: entLogicalCommunity

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "entLogicalCommunity",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read- write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent, or no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents which implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object, or may continue to return a community string (e.g., tri-lingual agent support).\"",
    "::=",
    "{",
    "entLogicalEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read- write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent, or no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents which implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object, or may continue to return a community string (e.g., tri-lingual agent support)."
    ],
    null,
    null,
    null,
    null
  ]
}
  • RFC Editor · RFC 2737 · RFC errata · Publisher's source file: Entity MIB (Version 2)

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download Entity MIB (Version 2)
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-19T00:19:03.887565+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download IETF_ENTITY.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:07.205143+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:07.521576+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:07.631031+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:07.948965+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.244245+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
            SYNTAX      OCTET STRING (SIZE (0..255))
            MAX-ACCESS  read-only
            STATUS      deprecated
            DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
            ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.250203+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737-entity.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.344516+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737-Entity-Version-2.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.581541+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX OCTET STRING (SIZE (0..255))
        MAX-ACCESS read-only
        STATUS deprecated
        DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string which can be used to
             access detailed management information for this logical
             entity.  The agent should allow read access with this
             community string (to an appropriate subset of all managed
             objects) and may also return a community string based on the
             privileges of the request used to read this object.  Note
             that an agent may return a community string with read-only
             privileges, even if this object is accessed with a read-
             write community string. However, the agent must take care
             not to return a community string which allows more
             privileges than the community string used to access this
             object.
    
             A compliant SNMP agent may wish to conserve naming scopes by
             representing multiple logical entities in a single 'default'
             naming scope.  This is possible when the logical entities
             represented by the same value of entLogicalCommunity have no
             object instances in common.  For example, 'bridge1' and
             'repeater1' may be part of the main naming scope, but at
             least one additional community string is needed to represent
             'bridge2' and 'repeater2'.
    
             Logical entities 'bridge1' and 'repeater1' would be
             represented by sysOREntries associated with the 'default'
             naming scope.
    
             For agents not accessible via SNMPv1 or SNMPv2C, the value
             of this object is the empty string.  This object may also
             contain an empty string if a community string has not yet
             been assigned by the agent, or no community string with
             suitable access rights can be returned for a particular SNMP
             request.
    
             Note that this object is deprecated. Agents which implement
             SNMPv3 access should use the entLogicalContextEngineID and
             entLogicalContextName objects to identify the context
             associated with each logical entity.  SNMPv3 agents may
             return a zero-length string for this object, or may continue
             to return a community string (e.g., tri-lingual agent
             support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'AutonomousType', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['OBJECT-TYPE'], 'RFC1213-MIB': ['mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download rfc2737.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:10.120142+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:11.198958+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:11.486326+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:11.876035+00:00.

  • HPE Instant On official MIBs · Publisher's source file: rfc2737.mib

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Published package: HPE Instant On 1960 3.4.0.6; file: rfc2737.mib.

    Same file in HPE Instant On 1960 2.6.0.73.

    Same file in HPE Instant On 1830 2.5.0.48.

    Same file in HPE Instant On 1960 2.7.0.103.

    Same file in HPE Instant On 1930 2.6.0.73.

    Downloaded: 2026-10-20T05:11:36.368638+00:00.

  • D-Link official switch MIBs · Publisher's source file: Source package: DES3028_R2.94_MIB.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib

    Related source files and packages:

    Show all 122 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in DXS-3610_A1_MIB_v1.01.zip.

    Same file in DXS-3600_Series_B1_MIB_forFW_v1.10.023.zip.

    Same file in DXS-3600-32S_A1_MIB_of_FW_v1.00.024.zip.

    Same file in DXS-3600_32S_MIB_R2.40.zip.

    Downloaded: 2026-10-23T18:11:51.595322+00:00.

  • D-Link official switch MIBs · Publisher's source file: Source package: DES6300 MIB(0131140909).zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMPv2-TC-v1': ['DisplayString'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download RFC2737.MIB

    Related source files and packages:


    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-23T18:17:42.753771+00:00.

  • D-Link official switch MIBs · Publisher's source file: Source package: 7200-MIB.rar

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY.mib

    Related source files and packages:

    Show all 32 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.

    Same file in DMS_DXS3130_RUN_1.20.003_mibs.tar.bz2.

    Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.

    Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.

    Downloaded: 2026-10-23T18:17:44.210758+00:00.

  • D-Link official switch MIBs · Publisher's source file: Source package: DGS-3100_FW_3.00.43_MIB.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib

    Related source files and packages:

    Show all 8 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in DGS-3100_series_FW_3.60.28_MIB.zip.

    Same file in DGS-3100_series_FW_3.60.28_MIB.zip.

    Same file in DGS-3100_series_FW_3.60.28_MIB.zip.

    Same file in DGS-3100_series_FW_3.60.28_MIB.zip.

    Downloaded: 2026-10-23T18:18:39.433275+00:00.

  • LANCOM official release MIBs · Publisher's source file: Source package: LC-CS-8132F-5.30.0202-Rel-MIB.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.mib

    Related source files and packages:

    Show all 123 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in LC-YS-7154CF-5.30.0363-RU2-MIB.zip.

    Same file in LC-XS-6128QF-5.20.0534-RU12-MIB.zip.

    Same file in LC-XS-5116QF-5.20.0534-RU12-MIB.zip.

    Same file in LC-XS-5110F-5.20.0534-RU12-MIB.zip.

    Downloaded: 2026-10-23T18:30:05.710341+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: FS728TPv2_V5.0.2.52-mibs.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.my

    Related source files and packages:

    • NETGEAR MIB package: M4250H-v13.0.4.14-mibs.zipMIB Version 13.0.4.14 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.4.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:23 GMT; 755,991 bytes
    • NETGEAR MIB package: fs728tp_5.0.2.50-mibs.zipMIB Version 5.0.2.50; Models: FS728TPv2; File: files/GDC/FS728TPv2/fs728tp_5.0.2.50-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:55:51 GMT; 327,192 bytes
    • NETGEAR MIB package: gs7xxts_tps-v5.3.0.36-mibs.zipMIB Version 5.3.0.36; Models: GS728TPS(B), GS728TS(B), GS752TPS(B), GS752TS(B); File: files/GDC/GS728TPS/gs7xxts_tps-v5.3.0.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:14 GMT; 458,806 bytes
    Show all 9 related files and packages
    • NETGEAR MIB package: M4250L-v13.0.4.14-mibs.zipMIB Version 13.0.4.14 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:14 GMT; 755,991 bytes
    • NETGEAR MIB package: gs7xxts_tps-v5.3.0.35-mibs.zipMIB Version 5.3.0.35; Models: GS728TPS(B), GS728TS(B), GS752TPS(B), GS752TS(B); File: files/GDC/GS728TPS/gs7xxts_tps-v5.3.0.35-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:14 GMT; 458,806 bytes
    • NETGEAR MIB package: M4250H-v13.0.4.13-mibs.zipMIB Version 13.0.4.13 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.4.13-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:22 GMT; 755,991 bytes
    • NETGEAR MIB package: GSM72xxP-mibs-fwv9.0.2.2.zip(GSM5212P, 7212F, 7212P, 7224P) GSM72xxP MIBs for Firmware 9.0.2.2; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/GSM5212P/GSM72xxP-mibs-fwv9.0.2.2.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:34 GMT; 518,601 bytes
    • NETGEAR MIB package: M4250L-v13.0.4.13-mibs.zipMIB Version 13.0.4.13 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.13-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:14 GMT; 755,991 bytes
    • NETGEAR MIB package: FS728TPv2_V5.0.2.52-mibs.zipMIB Version 5.0.2.52; Models: FS728TPv2; File: files/GDC/FS728TPv2/FS728TPv2_V5.0.2.52-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:55:51 GMT; 327,192 bytes

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in M4250H-v13.0.4.14-mibs.zip.

    Same file in M4250H-v13.0.4.13-mibs.zip.

    Same file in M4250L-v13.0.4.14-mibs.zip.

    Same file in M4250L-v13.0.4.13-mibs.zip.

    Downloaded: 2026-10-24T08:44:36.496814+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: GC108PP_V1.0.4.3_MIBs.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB.txt

    Related source files and packages:

    Show all 145 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in MS510TXM_TXUP_V1.1.1.9_MIBs.zip.

    Same file in MS510TXM_TXUP_V1.1.1.8_MIBs.zip.

    Same file in MS510TXM_TXUP_V1.1.1.11_MIBs.zip.

    Same file in MS510TXM_TXUP_V1.1.0.8_MIBs.zip.

    Downloaded: 2026-10-24T08:44:36.548813+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: GC728_GC752-V1.0.5.25-mibs.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.my

    Related source files and packages:

    • NETGEAR MIB package: GC728_GC752-v1.0.5.13-mibs.zipMIB Version 1.0.5.13; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.13-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,931 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.38-mibs.zipMIB Version 1.0.0.38; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.38-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:23 GMT; 503,593 bytes
    • NETGEAR MIB package: m4300v12.0.13.7-mibs.zipMIB Version 12.0.13.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.13.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 725,225 bytes
    Show all 62 related files and packages
    • NETGEAR MIB package: GC728_GC752-v1.0.5.35-mibs.zipMIB Version 1.0.5.35; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.35-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,971 bytes
    • NETGEAR MIB package: xs7xxtv7.0.0.24-mibs.zipMIB Version 7.0.0.24; Models: XS708T, XS712Tv2, XS716T; File: files/GDC/XS708T/xs7xxtv7.0.0.24-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:37 GMT; 537,488 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.27-mibs.zipMIB Version 1.0.0.27; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.27-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:22 GMT; 503,593 bytes
    • NETGEAR MIB package: GC728_GC752-V1.0.5.25-mibs.zipMIB Version 1.0.5.25; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-V1.0.5.25-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:07 GMT; 546,931 bytes
    • NETGEAR MIB package: gs418_510txp_v7.0.0.20-mibs.zipMIB Version 7.0.0.20; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v7.0.0.20-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:33 GMT; 548,135 bytes
    • NETGEAR MIB package: s3300v6.6.4.26-mibs.zipMIB Version 6.6.4.26; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300v6.6.4.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 551,003 bytes
    • NETGEAR MIB package: GS348T-v1.0.0.38-mibs.zipMIB Version 1.0.0.38; Models: GS348T; File: files/GDC/GS348T/GS348T-v1.0.0.38-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:26 GMT; 495,198 bytes
    • NETGEAR MIB package: m5300v11.0.0.40-mibs.zipM5300 MIB Version 11.0.0.40; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-28GF3 (GSM7328FSv2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.40-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 653,825 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.33-mibs.zipMIB Version 6.3.1.33; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.33-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 523,521 bytes
    • NETGEAR MIB package: m6100v11.0.0.40-mibs.zipM6100 MIB Version 11.0.0.40; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.40-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 724,059 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.30-mibs.zipMIB Version 1.0.0.30; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.30-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:22 GMT; 503,593 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.34-mibs.zipMIB Version 6.3.1.34; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.34-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 523,521 bytes
    • NETGEAR MIB package: m4300v12.0.17.10-mibs.zipMIB Version 12.0.17.10; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 726,136 bytes
    • NETGEAR MIB package: m4300v12.0.15.7-mibs.zipMIB Version 12.0.15.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.15.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 725,225 bytes
    • NETGEAR MIB package: GS348T-v1.0.0.17-mibs.zipMIB Version 1.0.0.17; Models: GS348T; File: files/GDC/GS348T/GS348T-v1.0.0.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:26 GMT; 495,198 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.26-mibs.zipMIB Version 1.0.0.26; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:22 GMT; 503,593 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.4.16-mibs.zipMIB Version 1.0.4.16; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.4.16-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 545,360 bytes
    • NETGEAR MIB package: GS7xxTvx-v6.3.1.47-mibs.zipMIB Version 6.3.1.47; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/GS7xxTvx-v6.3.1.47-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:47 GMT; 551,371 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.36-mibs.zipMIB Version 1.0.5.36; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,971 bytes
    • NETGEAR MIB package: GC728_GC752-V1.0.5.29-mibs.zipMIB Version 1.0.5.29; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-V1.0.5.29-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,931 bytes
    • NETGEAR MIB package: m4200v12.0.2.26-mibs.zipM4200 MIB Version 12.0.2.26; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 639,067 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.22-mibs.zipMIB Version 1.0.5.22; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.22-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,931 bytes
    • NETGEAR MIB package: m4300v12.0.11.16-mibs.zipMIB Version 12.0.11.16; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.16-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes
    • NETGEAR MIB package: GS348T-v1.0.0.26-mibs.zipMIB Version 1.0.0.26; Models: GS348T; File: files/GDC/GS348T/GS348T-v1.0.0.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:26 GMT; 495,198 bytes
    • NETGEAR MIB package: m4300v12.0.11.13-mibs.zipMIB Version 12.0.11.13; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.13-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes
    • NETGEAR MIB package: m4300v12.0.7.10-mibs.zipMIB Version 12.0.7.10; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 723,120 bytes
    • NETGEAR MIB package: s3300v6.6.4.21-mibs.zipMIB Version 6.6.4.21; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300v6.6.4.21-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 548,476 bytes
    • NETGEAR MIB package: m4300v12.0.17.13-mibs.zipMIB Version 12.0.17.13; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.13-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 726,136 bytes
    • NETGEAR MIB package: m4300v12.0.11.18-mibs.zipMIB Version 12.0.11.18; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.18-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes
    • NETGEAR MIB package: GS7xxT_v6.3.1.39-mib.zipMIB Version 6.3.1.39; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/GS7xxT_v6.3.1.39-mib.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:47 GMT; 523,523 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.12-mibs.zipMIB Version 1.0.5.12; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,931 bytes
    • NETGEAR MIB package: gs418_510txp_v7.0.0.11-mibs.zipMIB Version 7.0.0.11; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v7.0.0.11-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:33 GMT; 548,135 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.14-mibs.zipMIB Version 1.0.5.14; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,931 bytes
    • NETGEAR MIB package: m4100v10.0.2.31-mibs.zipM4100 MIB Version 10.0.2.31; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/m4100v10.0.2.31-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:00 GMT; 524,128 bytes
    • NETGEAR MIB package: m4200v12.0.2.36-mibs.zipM4200 MIB Version 12.0.2.36; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 639,067 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.32-mibs.zipMIB Version 1.0.5.32; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.32-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 546,971 bytes
    • NETGEAR MIB package: m4300v12.0.17.12-mibs.zipMIB Version 12.0.17.12; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 726,136 bytes
    • NETGEAR MIB package: xs7xxtv7.0.0.20-mibs.zipMIB Version 7.0.0.20; Models: XS708T, XS712Tv2, XS716T; File: files/GDC/XS708T/xs7xxtv7.0.0.20-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:37 GMT; 537,439 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.17-mibs.zipMIB Version 1.0.0.17; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:22 GMT; 503,593 bytes
    • NETGEAR MIB package: s3300v6.6.4.25-mibs.zipMIB Version 6.6.4.25; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300v6.6.4.25-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 551,003 bytes
    • NETGEAR MIB package: m7100-24xv11.0.0.40-mibs.zipM7100 MIB Version 11.0.0.40; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/m7100-24xv11.0.0.40-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:22 GMT; 543,465 bytes
    • NETGEAR MIB package: m4300v12.0.13.8-mibs.zipMIB Version 12.0.13.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.13.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 725,225 bytes
    • NETGEAR MIB package: m4300v12.0.17.8-mibs.zipMIB Version 12.0.17.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 725,886 bytes
    • NETGEAR MIB package: GC728_GC752-V1.0.5.27-mibs.zipMIB Version 1.0.5.27; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-V1.0.5.27-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:07 GMT; 546,931 bytes
    • NETGEAR MIB package: m4300v12.0.9.4-mibs.zipMIB Version 12.0.9.4; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.9.4-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 723,223 bytes
    • NETGEAR MIB package: m4300v12.0.11.15-mibs.zipMIB Version 12.0.11.15; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.15-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes
    • NETGEAR MIB package: m4300v12.0.7.12-mibs.zipMIB Version 12.0.7.12; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 723,120 bytes
    • NETGEAR MIB package: m4300v12.0.11.10-mibs.zipMIB Version 12.0.11.10; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes
    • NETGEAR MIB package: m4100v10.0.2.35-mibs.zipM4100 MIB Version 10.0.2.35; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/m4100v10.0.2.35-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:00 GMT; 524,128 bytes
    • NETGEAR MIB package: m4300v12.0.7.17-mibs.zipMIB Version 12.0.7.17; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 723,127 bytes
    • NETGEAR MIB package: m4300v12.0.7.15-mibs.zipMIB Version 12.0.7.15; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.15-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 723,127 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.34-mibs.zipMIB Version 1.0.0.34; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.34-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:23 GMT; 503,593 bytes
    • NETGEAR MIB package: GS348T-v1.0.0.33-mibs.zipMIB Version 1.0.0.33; Models: GS348T; File: files/GDC/GS348T/GS348T-v1.0.0.33-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:26 GMT; 495,198 bytes
    • NETGEAR MIB package: m4200v12.0.2.40-mibs.zipM4200 MIB Version 12.0.2.40; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.40-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 639,912 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.36-mibs.zipMIB Version 6.3.1.36; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 523,521 bytes
    • NETGEAR MIB package: gs7xxtxs-v6.1.0.39-mibs.zipMIB Version 6.1.0.39; Models: GS728TXS, GS752TXS; File: files/GDC/GS752TXS/gs7xxtxs-v6.1.0.39-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:31 GMT; 491,072 bytes
    • NETGEAR MIB package: m5300v11.0.0.37-mibs.zipM5300 MIB Version 11.0.0.37; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-28GF3 (GSM7328FSv2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.37-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 653,825 bytes
    • NETGEAR MIB package: gs418_510txp_v7.0.0.24-mibs.zipMIB Version 7.0.0.24; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v7.0.0.24-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:33 GMT; 548,184 bytes
    • NETGEAR MIB package: m4300v12.0.11.11-mibs.zipMIB Version 12.0.11.11; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.11-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 725,364 bytes

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in xs7xxtv7.0.0.24-mibs.zip.

    Same file in xs7xxtv7.0.0.20-mibs.zip.

    Same file in s3300v6.6.4.26-mibs.zip.

    Same file in s3300v6.6.4.25-mibs.zip.

    Downloaded: 2026-10-24T08:44:36.751810+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: GC728_GC752-v1.0.5.39-mibs.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.my

    Related source files and packages:

    • NETGEAR MIB package: m4300v12.0.2.9-mibs.zipMIB Version 12.0.2.9; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.2.9-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 742,727 bytes
    • NETGEAR MIB package: M6100v11.0.0.14-mibs.zipM6100 MIB Version 11.0.0.14; Models: M6100; File: files/GDC/M6100/M6100v11.0.0.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:11 GMT; 744,034 bytes
    • NETGEAR MIB package: m6100v11.0.0.25-mibs.zipM6100 MIB Version 11.0.0.25; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.25-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 744,034 bytes
    Show all 98 related files and packages
    • NETGEAR MIB package: gs418_510txp_v6.6.2.8-mibs.tar.bz2MIB Version 6.6.2.8; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v6.6.2.8-mibs.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:32 GMT; 386,811 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.39-mibs.zipMIB Version 1.0.5.39; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.39-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 602,239 bytes
    • NETGEAR MIB package: s3300-v6.4.0.19-mibs.zipMIB Version 6.4.0.19; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300-v6.4.0.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 545,351 bytes
    • NETGEAR MIB package: M4300v12.0.17.19-mibs.zipMIB Version 12.0.17.19; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300v12.0.17.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:07 GMT; 800,773 bytes
    • NETGEAR MIB package: M6100-Mibs-v11.0.0.10.zipM6100 MIB Version 11.0.0.10; Models: M6100; File: files/GDC/M6100/M6100-Mibs-v11.0.0.10.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:08 GMT; 729,815 bytes
    • NETGEAR MIB package: m4300v12.0.17.6-mibs.zipMIB Version 12.0.17.6; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.6-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 722,019 bytes
    • NETGEAR MIB package: m4300v12.0.2.17-mibs.zipMIB Version 12.0.2.17; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.2.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 734,189 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.19-mibs.zipMIB Version 6.3.1.19; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 535,378 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.11-mibs.zipMIB Version 6.3.1.11; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.11-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 528,612 bytes
    • NETGEAR MIB package: GS7xxT_v6.3.1.43-mib.zipMIB Version 6.3.1.43; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/GS7xxT_v6.3.1.43-mib.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:47 GMT; 516,155 bytes
    • NETGEAR MIB package: m4300v12.0.17.15-mibs.zipMIB Version 12.0.17.15; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.15-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 800,667 bytes
    • NETGEAR MIB package: M5300_V11.0.0.12.zipFirmware Version 11.0.0.12; Models: M5300-28GF3 (GSM7328FSv2); File: files/GDC/M5300/M5300_V11.0.0.12.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:04 GMT; 18.8 MiB
    • NETGEAR MIB package: M5300-mibs-v11.0.0.10.zipM5300 MIB Version 11.0.0.10; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/M5300-mibs-v11.0.0.10.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:58 GMT; 656,438 bytes
    • NETGEAR MIB package: m6100v11.0.0.18-mibs.zipM6100 MIB Version 11.0.0.18; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.18-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 744,034 bytes
    • NETGEAR MIB package: m4300v12.0.17.16-mibs.zipMIB Version 12.0.17.16; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.17.16-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 800,667 bytes
    • NETGEAR MIB package: M4100-mibs-v10.0.2.11.zipM4100 MIB Version 10.0.2.11; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/M4100-mibs-v10.0.2.11.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:00:58 GMT; 529,917 bytes
    • NETGEAR MIB package: GS324Tx_Mibs.zipMIB Version 1.0.0.44; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx_Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:24 GMT; 543,607 bytes
    • NETGEAR MIB package: m4100v10.0.2.26-mibs.zipM4100 MIB Version 10.0.2.26; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/m4100v10.0.2.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:00 GMT; 539,425 bytes
    • NETGEAR MIB package: m6100v11.0.0.12-mibs.zipM6100 MIB Version 11.0.0.12; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:15 GMT; 743,927 bytes
    • NETGEAR MIB package: xs712t-v6.1.0.34-mibs.zipMIB Version 6.1.0.34; Models: XS712T; File: files/GDC/XS712T/xs712t-v6.1.0.34-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:39 GMT; 491,073 bytes
    • NETGEAR MIB package: m4300-mibs-V12.0.17.7.zipMIB Version 12.0.17.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300-mibs-V12.0.17.7.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 722,019 bytes
    • NETGEAR MIB package: m4200-mibs-v12.0.0.15.zipM4200 MIB Version 12.0.0.15; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200-mibs-v12.0.0.15.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 658,204 bytes
    • NETGEAR MIB package: M4100_mibs-v10.0.2.13.zipM4100 MIB Version 10.0.2.13; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/M4100_mibs-v10.0.2.13.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:00:59 GMT; 529,162 bytes
    • NETGEAR MIB package: m7100-24xv11.0.0.24-mibs.zipM7100 MIB Version 11.0.0.24; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/m7100-24xv11.0.0.24-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:21 GMT; 558,647 bytes
    • NETGEAR MIB package: M7100-mibs-v11.0.0.10.zipM7100 MIB Version 11.0.0.10; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/M7100-mibs-v11.0.0.10.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:17 GMT; 547,127 bytes
    • NETGEAR MIB package: m4300v12.0.7.7-mibs.zipMIB Version 12.0.7.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 739,372 bytes
    • NETGEAR MIB package: m4300v12.0.8.8-mibs.zipMIB Version 12.0.8.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.8.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 747,765 bytes
    • NETGEAR MIB package: M6100-Mibs-v11.0.0.11.zipM6100 MIB Version 11.0.0.11; Models: M6100; File: files/GDC/M6100/M6100-Mibs-v11.0.0.11.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:08 GMT; 729,815 bytes
    • NETGEAR MIB package: M4300_v12.0.2.15_MIBs.zipMIB Version 12.0.2.15; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/M4300_v12.0.2.15_MIBs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:07 GMT; 734,437 bytes
    • NETGEAR MIB package: M5300-mibs-v11.0.0.11.zipM5300 MIB Version 11.0.0.11; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/M5300-mibs-v11.0.0.11.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:58 GMT; 656,438 bytes
    • NETGEAR MIB package: m4300v12.0.2.12-mibs.zipMIB Version 12.0.2.12; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.2.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 742,975 bytes
    • NETGEAR MIB package: m4300-mibs-v12.0.0.14.zipMIB Version 12.0.0.14; Models: M4300-12X12F (XSM4324S), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300-mibs-v12.0.0.14.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 743,231 bytes
    • NETGEAR MIB package: gs418_510txp-v7.0.0.31-MIBs.zipMIB Version 7.0.0.31; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp-v7.0.0.31-MIBs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:32 GMT; 606,619 bytes
    • NETGEAR MIB package: m4300v12.0.0.19-mibs.zipMIB Version 12.0.0.19; Models: M4300-12X12F (XSM4324S), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.0.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 742,983 bytes
    • NETGEAR MIB package: m4300v12.0.11.8-mibs.zipMIB Version 12.0.11.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.11.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 750,031 bytes
    • NETGEAR MIB package: m4300-mibs-v12.0.2.6.zipMIB Version 12.0.2.6; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300-mibs-v12.0.2.6.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 742,975 bytes
    • NETGEAR MIB package: gs7xxt-v6.3.1.16-mibs.zipMIB Version 6.3.1.16; Models: GS716Tv3, GS724Tv4, GS748Tv5; File: files/GDC/GS716TV3/gs7xxt-v6.3.1.16-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:48 GMT; 539,238 bytes
    • NETGEAR MIB package: m5300v11.0.0.18-mibs.zipM5300 MIB Version 11.0.0.18; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.18-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 669,172 bytes
    • NETGEAR MIB package: s3300v6.6.4.9-mibs.zipMIB Version 6.6.4.9; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300v6.6.4.9-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 560,746 bytes
    • NETGEAR MIB package: m4300v12.0.2.20-mibs.zipMIB Version 12.0.2.20; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.2.20-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 734,189 bytes
    • NETGEAR MIB package: M7100-24xv11.0.0.12-mibs.zipM7100 MIB Version 11.0.0.12; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/M7100-24xv11.0.0.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 558,542 bytes
    • NETGEAR MIB package: m5300v11.0.0.28-mibs.zipM5300 MIB Version 11.0.0.28; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-28GF3 (GSM7328FSv2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.28-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 672,030 bytes
    • NETGEAR MIB package: xs7xxt_6.6.3.2-mibs.zipMIB Version 6.6.3.2; Models: XS712Tv2; File: files/GDC/XS712Tv2/xs7xxt_6.6.3.2-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:39 GMT; 540,242 bytes
    • NETGEAR MIB package: m4300v12.0.6.7-mibs.zipMIB Version 12.0.6.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.6.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 736,891 bytes
    • NETGEAR MIB package: m4200v12.0.0.19-mibs.zipM4200 MIB Version 12.0.0.19; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.0.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 657,984 bytes
    • NETGEAR MIB package: m4300v12.0.7.9-mibs.zipMIB Version 12.0.7.9; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.9-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 660,317 bytes
    • NETGEAR MIB package: m4200v12.0.2.10-mibs.zipM4200 MIB Version 12.0.2.10; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 657,015 bytes
    • NETGEAR MIB package: m4300v12.0.7.8-mibs.zipMIB Version 12.0.7.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.7.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 734,537 bytes
    • NETGEAR MIB package: gs7xxtxs-v6.1.0.35-mibs.zipMIB Version 6.1.0.35; Models: GS728TXS, GS752TXS; File: files/GDC/GS752TXS/gs7xxtxs-v6.1.0.35-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:30 GMT; 506,496 bytes
    • NETGEAR MIB package: s3300-v6.6.1.4-mibs.tar.bz2MIB Version 6.6.1.4; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300-v6.6.1.4-mibs.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 391,491 bytes
    • NETGEAR MIB package: M4200v12.0.2.17-mibs.zipM4200 MIB Version 12.0.2.17; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/M4200v12.0.2.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:06 GMT; 649,196 bytes
    • NETGEAR MIB package: m4200v12.0.2.12-mibs.zipM4200 MIB Version 12.0.2.12; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 657,015 bytes
    • NETGEAR MIB package: m4300-mibs-v12.0.2.3.zipMIB Version 12.0.2.3; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300-mibs-v12.0.2.3.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 743,020 bytes
    • NETGEAR MIB package: s3300v6.6.4.28-mibs.zipMIB Version 6.6.4.28; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300v6.6.4.28-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 543,011 bytes
    • NETGEAR MIB package: xs712t-v6.1.0.36-mibs.zipMIB Version 6.1.0.36; Models: XS712T; File: files/GDC/XS712T/xs712t-v6.1.0.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:39 GMT; 497,364 bytes
    • NETGEAR MIB package: gs418_510txp_v6.6.2.9-mibs.tarMIB Version 6.6.2.9; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v6.6.2.9-mibs.tar; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:33 GMT; 386,551 bytes
    • NETGEAR MIB package: m4200v12.0.2.20-mibs.zipM4200 MIB Version 12.0.2.20; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.20-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 649,196 bytes
    • NETGEAR MIB package: m4200-mibs-v12.0.2.6.zipM4200 MIB Version 12.0.2.6; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200-mibs-v12.0.2.6.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 657,015 bytes
    • NETGEAR MIB package: m5300v11.0.0.23-mibs.zipM5300 MIB Version 11.0.0.23; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-28GF3 (GSM7328FSv2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.23-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 669,172 bytes
    • NETGEAR MIB package: M4200_V12.0.2.15_MIBs.zipM4200 MIB Version 12.0.2.15; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/M4200_V12.0.2.15_MIBs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:06 GMT; 649,416 bytes
    • NETGEAR MIB package: m4100v10.0.2.20-mibs.zipM4100 MIB Version 10.0.2.20; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/m4100v10.0.2.20-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:00 GMT; 539,425 bytes
    • NETGEAR MIB package: s3300-v6.6.0.14-mibs.zipMIB Version 6.6.0.14; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300-v6.6.0.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 569,223 bytes
    • NETGEAR MIB package: m4300v12.0.2.10-mibs.zipMIB Version 12.0.2.10; Models: M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300v12.0.2.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 742,975 bytes
    • NETGEAR MIB package: M5300-v11.0.0.14-mibs.zipM5300 MIB Version 11.0.0.14; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/M5300-v11.0.0.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:59 GMT; 669,172 bytes
    • NETGEAR MIB package: gs418_510txp_v6.6.2.7-mibs.tar.bz2MIB Version 6.6.2.7; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v6.6.2.7-mibs.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:32 GMT; 386,537 bytes
    • NETGEAR MIB package: m5300v11.0.0.31-mibs.zipM5300 MIB Version 11.0.0.31; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-28GF3 (GSM7328FSv2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/m5300v11.0.0.31-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:07 GMT; 672,030 bytes
    • NETGEAR MIB package: m4300v12.0.4.9_mib.zipMIB Version 12.0.4.9; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.4.9_mib.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 760,715 bytes
    • NETGEAR MIB package: m4200v12.0.2.9-mibs.zipM4200 MIB Version 12.0.2.9; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.2.9-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 656,795 bytes
    • NETGEAR MIB package: m4200-mibs-v12.0.0.12.zipM4200 MIB Version 12.0.0.12; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200-mibs-v12.0.0.12.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 658,204 bytes
    • NETGEAR MIB package: m4300v12.0.8.15-mibs.zipMIB Version 12.0.8.15; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.8.15-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 748,353 bytes
    • NETGEAR MIB package: m4300v12.0.6.6-mibs.zipMIB Version 12.0.6.6; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.6.6-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 736,891 bytes
    • NETGEAR MIB package: m6100v11.0.0.28-mibs.zipM6100 MIB Version 11.0.0.28; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.28-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 744,034 bytes
    • NETGEAR MIB package: m7100-24xv11.0.0.31-mibs.zipM7100 MIB Version 11.0.0.31; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/m7100-24xv11.0.0.31-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:21 GMT; 558,647 bytes
    • NETGEAR MIB package: gs7xxtxs-v6.1.0.36-mibs.zipMIB Version 6.1.0.36; Models: GS728TXS, GS752TXS; File: files/GDC/GS752TXS/gs7xxtxs-v6.1.0.36-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:30 GMT; 502,580 bytes
    • NETGEAR MIB package: M5300_V11.0.0.11.zipFirmware Version 11.0.0.11; Models: M5300-28GF3 (GSM7328FSv2); File: files/GDC/M5300/M5300_V11.0.0.11.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:03 GMT; 18.8 MiB
    • NETGEAR MIB package: M5300-v11.0.0.12-mibs.zipM5300 MIB Version 11.0.0.12; Models: M5300, M5300-28G (GSM7228S), M5300-28G-POE+ (GSM7228PSv1h2), M5300-28G3 (GSM7328Sv2h2), M5300-52G (GSM7252S), M5300-52G-POE+ (GSM7252PSv1h2), M5300-52G3 (GSM7352Sv2h2); File: files/GDC/M5300/M5300-v11.0.0.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:58 GMT; 669,287 bytes
    • NETGEAR MIB package: M7100-24xv11.0.0.14-mibs.zipM7100 MIB Version 11.0.0.14; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/M7100-24xv11.0.0.14-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 558,647 bytes
    • NETGEAR MIB package: s3300-v6.6.4.7-mibs.zipMIB Version 6.6.4.7; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300-v6.6.4.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 560,746 bytes
    • NETGEAR MIB package: m4300v12.0.9.3-mibs.zipMIB Version 12.0.9.3; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24XF (XSM4324FS), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/m4300v12.0.9.3-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:11 GMT; 748,105 bytes
    • NETGEAR MIB package: m4300-mibs-v12.0.0.15.zipMIB Version 12.0.0.15; Models: M4300-12X12F (XSM4324S), M4300-8X8F (XSM4316S); File: files/GDC/M4300/m4300-mibs-v12.0.0.15.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:10 GMT; 743,231 bytes
    • NETGEAR MIB package: GS324Tx-v1.0.0.43-Mibs.zipMIB Version 1.0.0.43; Models: GS324T, GS324TP; File: files/GDC/GS324T/GS324Tx-v1.0.0.43-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:24 GMT; 556,337 bytes
    • NETGEAR MIB package: xs7xxt-v6.6.1.7-mibs.zipMIB Version 6.6.1.7; Models: XS708T, XS716T; File: files/GDC/XS708T/xs7xxt-v6.6.1.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:37 GMT; 550,927 bytes
    • NETGEAR MIB package: xs7xxt6.6.3.3-mibs.zipMIB Version 6.6.3.3; Models: XS708T, XS712Tv2, XS716T; File: files/GDC/XS708T/xs7xxt6.6.3.3-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:37 GMT; 540,242 bytes
    • NETGEAR MIB package: m4200v12.0.17.6-mibs.zipM4200 MIB Version 12.0.17.6; Models: M4200-10MG-PoE+ (GSM4210P); File: files/GDC/M4200/m4200v12.0.17.6-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:07 GMT; 635,201 bytes
    • NETGEAR MIB package: m7100-24xv11.0.0.18-mibs.zipM7100 MIB Version 11.0.0.18; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/m7100-24xv11.0.0.18-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:21 GMT; 558,647 bytes
    • NETGEAR MIB package: GS348T-v1.0.0.43-Mibs.zipMIB Version 1.0.0.43; Models: GS348T; File: files/GDC/GS348T/GS348T-v1.0.0.43-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:26 GMT; 546,668 bytes
    • NETGEAR MIB package: M7100-mibs-v11.0.0.11.zipM7100 MIB Version 11.0.0.11; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/M7100-mibs-v11.0.0.11.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:17 GMT; 547,127 bytes
    • NETGEAR MIB package: m7100-24xv11.0.0.28-mibs.zipM7100 MIB Version 11.0.0.28; Models: M7100-24X (XSM7224); File: files/GDC/M7100-24X/m7100-24xv11.0.0.28-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:21 GMT; 558,647 bytes
    • NETGEAR MIB package: s3300-v6.6.1.7-mibs.zipMIB Version 6.6.1.7; Models: S3300-28X (GS728TX), S3300-28X-PoE+ (GS728TXP), S3300-52X (GS752TX), S3300-52X-PoE+ (GS752TXP); File: files/GDC/S3300/s3300-v6.6.1.7-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 565,325 bytes
    • NETGEAR MIB package: M4300_v12.0.4.8-mibs.zipMIB Version 12.0.4.8; Models: M4300, M4300-12X12F (XSM4324S), M4300-24X (XSM4324CS), M4300-48X (XSM4348CS), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.4.8-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:06 GMT; 735,393 bytes
    • NETGEAR MIB package: GC728_GC752-v1.0.5.40-mibs.zipMIB Version 1.0.5.40; Models: GC728X, GC728XP, GC752X, GC752XP; File: files/GDC/GC728X/GC728_GC752-v1.0.5.40-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:08 GMT; 601,887 bytes
    • NETGEAR MIB package: m6100v11.0.0.31-mibs.zipM6100 MIB Version 11.0.0.31; Models: M6100; File: files/GDC/M6100/m6100v11.0.0.31-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:05:16 GMT; 744,034 bytes
    • NETGEAR MIB package: m4100v10.0.2.30-mibs.zipM4100 MIB Version 10.0.2.30; Models: M4100, M4100-12G-POE+ (GSM7212P), M4100-12GF (GSM7212F), M4100-24G-POE+ (GSM7224P), M4100-26-POE (FSM7226Pv1h1), M4100-26G (GSM7224v2h2), M4100-26G-POE (GSM7226LPv1h1), M4100-50-POE (FSM7250Pv1h1), M4100-50G (GSM7248v2h2), M4100-50G-POE+ (GSM7248Pv1h1), M4100-D10-POE (FSM5210Pv1h1), M4100-D12G (GSM5212v1h1), M4100-D12G-POE+ (GSM5212P); File: files/GDC/M4100/m4100v10.0.2.30-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:00 GMT; 531,287 bytes
    • NETGEAR MIB package: gs418_510txp_v6.6.2.6-mibs.tar.bz2MIB Version 6.6.2.6; Models: GS418TPP, GS510TLP, GS510TPP; File: files/GDC/GS418TPP/gs418_510txp_v6.6.2.6-mibs.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:32 GMT; 386,617 bytes
    • NETGEAR MIB package: XS7xxT_V6.6.3.5-mibs.zipMIB Version 6.6.3.5; Models: XS708T, XS712Tv2, XS716T; File: files/GDC/XS708T/XS7xxT_V6.6.3.5-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:37 GMT; 519,645 bytes

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in xs7xxt_6.6.3.2-mibs.zip.

    Same file in xs712t-v6.1.0.36-mibs.zip.

    Same file in xs712t-v6.1.0.34-mibs.zip.

    Same file in xs7xxt6.6.3.3-mibs.zip.

    Downloaded: 2026-10-24T08:44:37.197805+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: GS108Tv2_GS110TP MIB_V5.4.2.16.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
    
    
    
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download entity.my

    Related source files and packages:

    Show all 99 related files and packages
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.0.7.tar.bz2MIB Version 7.0.0.7; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.0.7.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:53 GMT; 441,627 bytes
    • NETGEAR MIB package: M4300_v12.0.19.19-mibs.zipMIB Version 12.0.19.19; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.19-mibs.zip; Publisher Last-Modified: Thu, 12 Mar 2026 13:17:19 GMT; 809,789 bytes
    • NETGEAR MIB package: GS724Tv6-v7.0.0.8-Mibs.zipMIB Version 7.0.0.8; Models: GS724Tv6; File: files/GDC/GS724Tv6/GS724Tv6-v7.0.0.8-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:05 GMT; 618,928 bytes
    • NETGEAR MIB package: gs510tpp_v7.1.0.7-mibs.zipMIB Version 7.1.0.7; Models: GS510TPP; File: files/GDC/GS418TPP/gs510tpp_v7.1.0.7-mibs.zip; Publisher Last-Modified: Thu, 14 Aug 2025 07:21:12 GMT; 568,021 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.2.5.tar.zipMIB Version 7.0.2.5 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.2.5.tar.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 462,625 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.24-mibs.zipMIB Version 13.0.5.24 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.5.24-mibs.zip; Publisher Last-Modified: Fri, 13 Feb 2026 22:00:11 GMT; 849,576 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.16.tar.bz2MIB Version 7.0.1.16 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.16.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:50 GMT; 441,308 bytes
    • NETGEAR MIB package: M4250L-v13.0.6.8-mibs.zipMIB Version 13.0.6.8 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.6.8-mibs.zip; Publisher Last-Modified: Tue, 29 Sep 2026 11:11:33 GMT; 807,461 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.0.7.tar.bz2MIB Version 7.0.0.7; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.0.7.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:49 GMT; 441,075 bytes
    • NETGEAR MIB package: M4350-v14.0.2.17-Mibs.zipMIB Version 14.0.2.17; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.2.17-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:22 GMT; 935,929 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.4.23.tar.bz2MIB Version 7.0.4.23 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.4.23.tar.bz2; Publisher Last-Modified: Fri, 18 Apr 2025 11:21:45 GMT; 463,157 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.14-mibs.zipMIB Version 13.0.5.14 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.5.14-mibs.zip; Publisher Last-Modified: Thu, 17 Apr 2025 20:39:37 GMT; 850,520 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.3.12.tar.bz2.zipMIB Version 7.0.3.12 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.3.12.tar.bz2.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 462,971 bytes
    • NETGEAR MIB package: M4300_v12.0.19.21-mibs.zipMIB Version 12.0.19.21; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.21-mibs.zip; Publisher Last-Modified: Thu, 14 May 2026 13:54:53 GMT; 764,399 bytes
    • NETGEAR MIB package: M4300v12.0.19.7-mibs.zipMIB Version 12.0.19.7; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300v12.0.19.7-mibs.zip; Publisher Last-Modified: Tue, 18 Feb 2025 12:22:15 GMT; 806,987 bytes
    • NETGEAR MIB package: M4250H-v13.0.4.26-mibs.zipMIB Version 13.0.4.26 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.4.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:24 GMT; 825,798 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.14-mibs.zipMIB Version 13.0.5.14 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.14-mibs.zip; Publisher Last-Modified: Thu, 17 Apr 2025 21:43:40 GMT; 850,520 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.0.16.tar.bz2MIB Version 7.0.0.16; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.0.16.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:52 GMT; 441,334 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.20.tar.bz2MIB Version 7.0.1.20 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.20.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:53 GMT; 441,460 bytes
    • NETGEAR MIB package: M4250H-v13.0.4.23-mibs.zipMIB Version 13.0.4.23 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.4.23-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:24 GMT; 825,798 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.26-mibs.zipMIB Version 13.0.5.26 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.26-mibs.zip; Publisher Last-Modified: Wed, 29 Apr 2026 17:21:40 GMT; 804,070 bytes
    • NETGEAR MIB package: gs7xxts_tps-v5.3.0.29-mibs.zipMIB Version 5.3.0.29; Models: GS728TPS(B), GS728TS(B), GS752TPS(B), GS752TS(B); File: files/GDC/GS728TPS/gs7xxts_tps-v5.3.0.29-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:13 GMT; 472,238 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.10-mibs.zipMIB Version 13.0.5.10 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.10-mibs.zip; Publisher Last-Modified: Tue, 18 Feb 2025 10:52:33 GMT; 848,654 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.4.30.tar.bz2MIB Version 7.0.4.35; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.4.30.tar.bz2; Publisher Last-Modified: Wed, 22 Oct 2025 15:51:50 GMT; 462,959 bytes
    • NETGEAR MIB package: gs748tv6-v7.0.0.10-mibs.zipMIB Version 7.0.0.10; Models: GS748Tv6; File: files/GDC/GS748Tv6/gs748tv6-v7.0.0.10-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:26 GMT; 621,812 bytes
    • NETGEAR MIB package: M4350-v14.0.2.26-mibs.zipMIB Version 14.0.2.26; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.2.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:23 GMT; 936,064 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.24.tar.bz2MIB Version 7.0.1.24 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.24.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 441,318 bytes
    • NETGEAR MIB package: GS108Tv2_GS110TP MIB_V5.4.2.16.zipMIB Version (5.4.2.16 - 5.4.2.36); Models: GS108Tv2, GS110TPv2; File: files/GDC/GS110TP/GS108Tv2_GS110TP MIB_V5.4.2.16.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:57:43 GMT; 445,708 bytes
    • NETGEAR MIB package: gs748tv6-v7.0.0.12-mibs.zipMIB Version 7.0.0.12; Models: GS748Tv6; File: files/GDC/GS748Tv6/gs748tv6-v7.0.0.12-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:27 GMT; 597,940 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.10-mibs.zipMIB Version 13.0.5.10 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX); File: files/GDC/M4250/M4250L-v13.0.5.10-mibs.zip; Publisher Last-Modified: Tue, 18 Feb 2025 11:37:53 GMT; 848,654 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.16-mibs.zipMIB Version 13.0.5.16 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.16-mibs.zip; Publisher Last-Modified: Fri, 11 Jul 2025 20:37:04 GMT; 845,060 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.4.30.tar.bz2MIB Version 7.0.4.30; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.4.30.tar.bz2; Publisher Last-Modified: Wed, 22 Oct 2025 15:51:50 GMT; 463,317 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.4.35.tar.bz2MIB Version 7.0.4.35; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.4.35.tar.bz2; Publisher Last-Modified: Fri, 13 Feb 2026 21:59:15 GMT; 463,330 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.0.14.tar.bz2MIB Version 7.0.0.14; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.0.14.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:47 GMT; 441,540 bytes
    • NETGEAR MIB package: gs510tpp_v7.1.0.5-mibs.zipMIB Version 7.1.0.5; Models: GS510TPP; File: files/GDC/GS418TPP/gs510tpp_v7.1.0.5-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:33 GMT; 564,045 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.3.21.tar.bz2MIB Version 7.0.3.21 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.3.21.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 462,173 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.0.16.tar.bz2MIB Version 7.0.0.16; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.0.16.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:48 GMT; 441,085 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.24.tar.bz2MIB Version 7.0.1.24 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.24.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:54 GMT; 441,572 bytes
    • NETGEAR MIB package: XS508TM_XS516TM-v7.8.11.13-Mibs.zipMIB Version 7.8.11.13; Models: XS508TM, XS516TM; File: files/GDC/S3600_Switch/XS508TM_XS516TM-v7.8.11.13-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:40:15 GMT; 710,731 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.6.tar.bz2MIB Version 7.0.1.6 - Unsigned Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.6.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:54 GMT; 441,284 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.13.tar.bz2MIB Version 7.0.1.13 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.13.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:53 GMT; 441,656 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.5.6.tar.bz2MIB Version 7.0.5.6; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.5.6.tar.bz2; Publisher Last-Modified: Wed, 29 Apr 2026 19:45:52 GMT; 459,678 bytes
    • NETGEAR MIB package: M4250H-v13.0.4.17-mibs.zipMIB Version 13.0.4.17 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.4.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:24 GMT; 825,701 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.3.12.tar.bz2.zipMIB Version 7.0.3.12 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.3.12.tar.bz2.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:55 GMT; 462,937 bytes
    • NETGEAR MIB package: gs7xxts_tps-v5.3.0.31-mibs.zipMIB Version 5.3.0.31; Models: GS728TPS(B), GS728TS(B), GS752TPS(B), GS752TS(B); File: files/GDC/GS728TPS/gs7xxts_tps-v5.3.0.31-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:14 GMT; 467,842 bytes
    • NETGEAR MIB package: M4250H-v13.0.6.8-mibs.zipMIB Version 13.0.6.8 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.6.8-mibs.zip; Publisher Last-Modified: Tue, 29 Sep 2026 11:07:51 GMT; 807,461 bytes
    • NETGEAR MIB package: M4300v12.0.19.4-mibs.zipMIB Version 12.0.19.4; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300v12.0.19.4-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:07 GMT; 807,028 bytes
    • NETGEAR MIB package: M4350-v14.0.6.9-mibs.zipMIB Version 14.0.6.19; MIB Version 14.0.6.9; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24F4X (MSM4328F), M4350-24G4XF (GSM4328), M4350-24M4X4V (MSM4332), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40F4C (XSM4344FC), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8M2V (MSM4310), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.6.9-mibs.zip; Publisher Last-Modified: Fri, 11 Jul 2025 20:34:19 GMT; 935,235 bytes
    • NETGEAR MIB package: M4350-v14.0.0.17-mibs.zipMIB Version 14.0.0.17; Models: M4350, M4350-12X12F (XSM4324), M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-36X4V (XSM4340CV), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.0.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:21 GMT; 921,391 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.4.18.tar.bz2MIB Version 7.0.4.18; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.4.18.tar.bz2; Publisher Last-Modified: Wed, 19 Feb 2025 08:17:24 GMT; 463,370 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.20.tar.bz2MIB Version 7.0.1.20 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.20.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 441,253 bytes
    • NETGEAR MIB package: xsm72xxs-v9.0.1.46-mibs.zipMIB version v9.0.1.46; Models: M7300-24XF (XSM7224S); File: files/GDC/XSM7224S/xsm72xxs-v9.0.1.46-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 20:00:48 GMT; 619,274 bytes
    • NETGEAR MIB package: M4350-v14.0.4.14-mibs.zipMIB Version 14.0.4.14; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.4.14-mibs.zip; Publisher Last-Modified: Wed, 16 Apr 2025 16:07:58 GMT; 940,266 bytes
    • NETGEAR MIB package: M4350-v14.0.6.17-mibs.zipMIB Version 14.0.6.17; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24F4X (MSM4328F), M4350-24G4XF (GSM4328), M4350-24M4X4V (MSM4332), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40F4C (XSM4344FC), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8M2V (MSM4310), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.6.17-mibs.zip; Publisher Last-Modified: Fri, 13 Feb 2026 21:57:50 GMT; 940,583 bytes
    • NETGEAR MIB package: M4350-v14.0.2.18-Mibs.zipMIB Version 14.0.2.18; Models: M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-44M4X4V (MSM4352); File: files/GDC/M4350/M4350-v14.0.2.18-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:22 GMT; 940,575 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.6.tar.bz2MIB Version 7.0.1.6 - Unsigned Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.6.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 441,313 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.0.20.tar.bz2MIB Version 7.0.0.20; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.0.20.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:49 GMT; 441,193 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.4.18.tar.bz2MIB Version 7.0.4.18 - Signed Version; Models: M4500, M4500-32C (CSM4532), M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-32c-7.0.4.18.tar.bz2; Publisher Last-Modified: Wed, 19 Feb 2025 08:17:23 GMT; 463,010 bytes
    • NETGEAR MIB package: gs748tv6-v7.0.0.14-mibs.zipMIB Version 7.0.0.14; Models: GS748Tv6; File: files/GDC/GS748Tv6/gs748tv6-v7.0.0.14-mibs.zip; Publisher Last-Modified: Fri, 08 Aug 2025 11:48:45 GMT; 617,809 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.11.tar.bz2MIB Version 7.0.1.11 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.11.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:53 GMT; 441,323 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.10.tar.bz2MIB Version 7.0.1.10 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.10.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:50 GMT; 441,262 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.3.9.tar.zipMIB Version 7.0.3.9 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.3.9.tar.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:55 GMT; 462,590 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.1.16.tar.bz2MIB Version 7.0.1.16 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.1.16.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:53 GMT; 441,396 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.20-mibs.zipMIB Version 13.0.5.20 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.20-mibs.zip; Publisher Last-Modified: Thu, 23 Oct 2025 17:16:15 GMT; 804,427 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.4.12.tar.bz2MIB Version 7.0.4.12; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.4.12.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:55 GMT; 462,515 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.4.12.tar.bz2MIB Version 7.0.4.12; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.4.12.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:52 GMT; 462,188 bytes
    • NETGEAR MIB package: M4350-v14.0.2.23-mibs.zipMIB Version 14.0.2.23; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.2.23-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:23 GMT; 936,026 bytes
    • NETGEAR MIB package: M4350-v14.0.9.10-mibs.zipMIB Version 14.0.9.10; Models: M4350, M4350-12X12F (XSM4324), M4350-16C (CSM4316), M4350-16M4V (MSM4320), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24F4X (MSM4328F), M4350-24G4XF (GSM4328), M4350-24M4X4V (MSM4332), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40F4C (XSM4344FC), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8M2V (MSM4310), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.9.10-mibs.zip; Publisher Last-Modified: Thu, 13 Aug 2026 13:43:28 GMT; 949,526 bytes
    • NETGEAR MIB package: M4300_v12.0.19.10-mibs.zipMIB Version 12.0.19.10; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.10-mibs.zip; Publisher Last-Modified: Thu, 17 Apr 2025 20:07:52 GMT; 812,267 bytes
    • NETGEAR MIB package: M4250L-v13.0.4.17-mibs.zipMIB Version 13.0.4.17 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.17-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:15 GMT; 825,701 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.0.14.tar.bz2MIB Version 7.0.0.14; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.0.14.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:52 GMT; 441,306 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.13.tar.bz2MIB Version 7.0.1.13 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.13.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:50 GMT; 441,300 bytes
    • NETGEAR MIB package: M4250H-v13.0.4.19-mibs.zipMIB Version 13.0.4.19 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX); File: files/GDC/M4250W2/M4250H-v13.0.4.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:24 GMT; 825,701 bytes
    • NETGEAR MIB package: M4300_v12.0.19.23-mibs.zipMIB Version 12.0.19.23; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.23-mibs.zip; Publisher Last-Modified: Thu, 13 Aug 2026 07:39:54 GMT; 809,909 bytes
    • NETGEAR MIB package: GS510TPP_V7.1.0.4-mibs.zipMIB Version 7.1.0.4; Models: GS510TPP; File: files/GDC/GS418TPP/GS510TPP_V7.1.0.4-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:58:31 GMT; 564,045 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.2.5.tar.zipMIB Version 7.0.2.5 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.2.5.tar.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:54 GMT; 462,630 bytes
    • NETGEAR MIB package: GS724Tv6-v7.0.0.14-Mibs.zipMIB Version 7.0.0.14; Models: GS724Tv6; File: files/GDC/GS724Tv6/GS724Tv6-v7.0.0.14-Mibs.zip; Publisher Last-Modified: Tue, 29 Jul 2025 08:10:22 GMT; 615,213 bytes
    • NETGEAR MIB package: M4250L-v13.0.4.19-mibs.zipMIB Version 13.0.4.19 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.19-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:15 GMT; 825,701 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.4.23.tar.bz2MIB Version 7.0.4.23; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.4.23.tar.bz2; Publisher Last-Modified: Fri, 18 Apr 2025 11:21:48 GMT; 463,320 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.20-mibs.zipMIB Version 13.0.5.20 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.5.20-mibs.zip; Publisher Last-Modified: Thu, 23 Oct 2025 17:14:52 GMT; 804,427 bytes
    • NETGEAR MIB package: M4350-v14.0.6.13-mibs.zipMIB Version 14.0.6.13; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24F4X (MSM4328F), M4350-24G4XF (GSM4328), M4350-24M4X4V (MSM4332), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40F4C (XSM4344FC), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8M2V (MSM4310), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.6.13-mibs.zip; Publisher Last-Modified: Wed, 22 Oct 2025 22:10:49 GMT; 892,311 bytes
    • NETGEAR MIB package: M4350-v14.0.0.15-Mibs.zipMIB Version 14.0.0.15; Models: M4350, M4350-24F4V (XSM4328FV), M4350-24G4XF (GSM4328), M4350-24X4V (XSM4328CV), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352); File: files/GDC/M4350/M4350-v14.0.0.15-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:02:21 GMT; 926,129 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.26-mibs.zipMIB Version 13.0.5.26 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.5.26-mibs.zip; Publisher Last-Modified: Wed, 29 Apr 2026 14:07:35 GMT; 804,070 bytes
    • NETGEAR MIB package: GS724Tv6-v7.0.0.12-Mibs.zipMIB Version 7.0.0.12; Models: GS724Tv6; File: files/GDC/GS724Tv6/GS724Tv6-v7.0.0.12-Mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 18:59:04 GMT; 595,717 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.3.9.tar.zipMIB Version 7.0.3.9 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.3.9.tar.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:51 GMT; 462,384 bytes
    • NETGEAR MIB package: M4350-v14.0.6.19-mibs.zipMIB Version 14.0.6.19; Models: M4350, M4350-12X12F (XSM4324), M4350-16V4C (VSM4320C), M4350-24F4V (XSM4328FV), M4350-24F4X (MSM4328F), M4350-24G4XF (GSM4328), M4350-24M4X4V (MSM4332), M4350-24X4V (XSM4328CV), M4350-24X8F8V (XSM4340V), M4350-32F8V (XSM4340FV), M4350-36X4V (XSM4340CV), M4350-40F4C (XSM4344FC), M4350-40X4C (XSM4344C), M4350-44M4X4V (MSM4352), M4350-48G4XF (GSM4352), M4350-8M2V (MSM4310), M4350-8X8F (XSM4316); File: files/GDC/M4350/M4350-v14.0.6.19-mibs.zip; Publisher Last-Modified: Wed, 29 Apr 2026 18:34:10 GMT; 891,903 bytes
    • NETGEAR MIB package: M4250L-v13.0.4.26-mibs.zipMIB Version 13.0.4.26 for M4250 switches with 16-or-less ports; MIB Version 13.0.4.26 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.26-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:15 GMT; 825,798 bytes
    • NETGEAR MIB package: mibs-m4500-32c-7.0.1.11.tar.bz2MIB Version 7.0.1.11 - Signed Version; Models: M4500, M4500-32C (CSM4532); File: files/GDC/M4500/mibs-m4500-32c-7.0.1.11.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:50 GMT; 441,324 bytes
    • NETGEAR MIB package: M4300_v12.0.19.15-mibs.zipMIB Version 12.0.19.15; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.15-mibs.zip; Publisher Last-Modified: Wed, 22 Oct 2025 23:30:45 GMT; 764,507 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.5.6.tar.bz2MIB Version 7.0.5.6; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.5.6.tar.bz2; Publisher Last-Modified: Wed, 29 Apr 2026 19:46:04 GMT; 459,716 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.3.21.tar.bz2MIB Version 7.0.3.21 - Signed Version; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.3.21.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:55 GMT; 462,414 bytes
    • NETGEAR MIB package: M4250H-v13.0.5.24-mibs.zipMIB Version 13.0.5.24 for M4250 switches with 24-or-more ports; Models: M4250, M4250-26G4F-PoE+ (GSM4230P), M4250-26G4F-PoE++ (GSM4230UP), M4250-26G4XF-PoE+ (GSM4230PX), M4250-40G8F-PoE+ (GSM4248P), M4250-40G8XF-PoE+ (GSM4248PX), M4250-40G8XF-PoE++ (GSM4248UX); File: files/GDC/M4250W2/M4250H-v13.0.5.24-mibs.zip; Publisher Last-Modified: Fri, 13 Feb 2026 22:01:41 GMT; 849,576 bytes
    • NETGEAR MIB package: M4250L-v13.0.5.16-mibs.zipMIB Version 13.0.5.16 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.5.16-mibs.zip; Publisher Last-Modified: Fri, 11 Jul 2025 20:36:15 GMT; 845,060 bytes
    • NETGEAR MIB package: mibs-m4500-48xf8c-7.0.0.20.tar.bz2MIB Version 7.0.0.20; Models: M4500-48XF8C (XSM4556); File: files/GDC/M4500/mibs-m4500-48xf8c-7.0.0.20.tar.bz2; Publisher Last-Modified: Fri, 27 Dec 2024 19:04:52 GMT; 441,271 bytes
    • NETGEAR MIB package: M4300_v12.0.19.12-mibs.zipMIB Version 12.0.19.12; Models: M4300, M4300-12X12F (XSM4324S), M4300-16X (XSM4316PA), M4300-16X (XSM4316PB), M4300-24X (XSM4324CS), M4300-24X24F (XSM4348S), M4300-24XF (XSM4324FS), M4300-28G (GSM4328S), M4300-28G-PoE+ (GSM4328PA), M4300-28G-PoE+ (GSM4328PB), M4300-48X (XSM4348CS), M4300-48XF (XSM4348FS), M4300-52G (GSM4352S), M4300-52G-PoE+ (GSM4352PA), M4300-52G-PoE+ (GSM4352PB), M4300-8X8F (XSM4316S), M4300-96X (XSM4396K0 and XSM4396K1); File: files/GDC/M4300/M4300_v12.0.19.12-mibs.zip; Publisher Last-Modified: Thu, 07 Aug 2025 17:39:58 GMT; 805,588 bytes
    • NETGEAR MIB package: M4250L-v13.0.4.23-mibs.zipMIB Version 13.0.4.23 for M4250 switches with 16-or-less ports; MIB Version 13.0.4.23 for M4250 switches with 16-or-less ports; Models: M4250, M4250-10G2F-PoE+ (GSM4212P), M4250-10G2XF-PoE+ (GSM4212PX), M4250-10G2XF-PoE++ (GSM4212UX), M4250-12M2XF (MSM4214X), M4250-16XF (XSM4216F), M4250-8G2XF-PoE+ (GSM4210PX), M4250-9G1F-PoE+ (GSM4210PD); File: files/GDC/M4250/M4250L-v13.0.4.23-mibs.zip; Publisher Last-Modified: Fri, 27 Dec 2024 19:01:15 GMT; 825,798 bytes

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in xsm72xxs-v9.0.1.46-mibs.zip.

    Same file in XS508TM_XS516TM-v7.8.11.13-Mibs.zip.

    Same file in mibs-m4500-48xf8c-7.0.5.6.tar.bz2.

    Same file in mibs-m4500-48xf8c-7.0.4.30.tar.bz2.

    Downloaded: 2026-10-24T08:44:37.730798+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: GS724TPv2 MIB V1.1.1.29.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
    
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download RFC2737 - Entity MIB (V2).mib

    Related source files and packages:


    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-24T08:44:40.514763+00:00.

  • NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: MS510TX_TXPP_MIBS_V6.7.0.43.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download rfc2737.mib

    Related source files and packages:

    Show all 8 related files and packages

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in MIB-6.5.1.22.zip.

    Same file in XS728T_XS748T_mib_files.zip.

    Same file in XS728T_XS748T_MIB_V6.5.1.59.zip.

    Same file in XS728T_XS748T_MIB_V6.5.1.42.zip.

    Downloaded: 2026-10-24T08:44:59.353526+00:00.

  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: 2024012909344598z6fl.zip

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a read-
                write community string. However, the agent must take care
                not to return a community string which allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent, or no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated. Agents which implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object, or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB-2737.mib

    Related source files and packages:

    • S3100-16TF Switch SNMP MIB FilesS3100-16TF Switch SNMP MIB Files; Models: S3100-16TF; Catalog updated: 2026-10-08 14:09:01; File: mall/resource/s3100-16tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Thu, 08 Oct 2026 06:09:01 GMT; 2.4 MiB
    • NC8200 and NC8400 Series Switches SNMP MIB FilesNC8200 and NC8400 Series Switches SNMP MIB Files; Models: NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH; Catalog updated: 2024-05-28 19:26:13; File: mall/file/user_manual/nc8200-and-nc8400-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:34:12 GMT; 1.5 MiB
    • S5810 Series Switches SNMP MIB FilesS5810 Series Switches SNMP MIB Files; Models: S5810-28FS, S5810-48FS, S5810-48TS-P; Catalog updated: 2024-05-28 19:26:26; File: mall/file/datasheet/s5810-series-switches-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 04:20:38 GMT; 2.3 MiB
    Show all 9 related files and packages
    • S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0)S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0); Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/2024012909344598z6fl.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:34:50 GMT; 1.5 MiB
    • S3910 Series Swithes SNMP MIB FilesS3910 Series Swithes SNMP MIB Files; Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3910-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:37:14 GMT; 2.4 MiB
    • S5860 Series Swithes SNMP MIB FilesS5860 Series Swithes SNMP MIB Files; Models: S5860-20SQ, S5860-24XB-U, S5860-48SC; Catalog updated: 2026-02-22 10:42:59; File: mall/file/user_manual/s5860-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:40:34 GMT; 2.4 MiB
    • S3410 Series Swithes SNMP MIB FilesS3410 Series Swithes SNMP MIB Files; Models: S3410-24TS-P; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3410-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:36:20 GMT; 2.4 MiB
    • S5810 Series Switches SNMP MIB Files (V1.0)S5810 Series Switches SNMP MIB Files (V1.0); Models: S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/20240129093459svlvsn.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:35:04 GMT; 1.5 MiB
    • N5860 and N8560 Series Switches SNMP MIB FilesN5860 and N8560 Series Switches SNMP MIB Files; Models: N5860-48SC, N8560-32C, N8560-48BC, N8560-64C; Catalog updated: 2024-09-12 14:10:35; File: mall/file/user_manual/n5860-and-n8560-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:33:20 GMT; 1.5 MiB

    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Same file in s3100-16tf-switch-snmp-mib-files.zip.

    Same file in s5860-series-swithes-snmp-mib-files.zip.

    Same file in s3910-series-swithes-snmp-mib-files.zip.

    Same file in s3410-series-swithes-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:05.262054+00:00.

entLogicalCommunity

Status in source: current.

Names: entLogicalCommunity

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "entLogicalCommunity",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also choose to return a community string based on the privileges of the request used to read this object. Note that an agent may choose to return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'main' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'main' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty-string.\"",
    "::=",
    "{",
    "entLogicalEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also choose to return a community string based on the privileges of the request used to read this object. Note that an agent may choose to return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'main' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'main' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty-string."
    ],
    null,
    null,
    null,
    null
  ]
}
  • RFC Editor · RFC 2037 · RFC errata · Publisher's source file: Entity MIB using SMIv2

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download Entity MIB using SMIv2
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-19T00:18:21.757684+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TDomain', 'TAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}
    · Download ENTITY.MIB.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:07.114586+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download rfc2037.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:08.911938+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}
    · Download rfc2037.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.240337+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download rfc2037-Entity.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.557877+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE'], 'RFC1213-MIB': ['mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'SNMPv2-PARTY-MIB': ['TAddress']}
    · Download entity.mi2.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:09.964267+00:00.

  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (1..255))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
                "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'DisplayString', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}
    · Download rfc2037.mib-mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:10.116981+00:00.

entLogicalCommunity

Status in source: mandatory.

Names: entLogicalCommunity

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "entLogicalCommunity",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also choose to return a community string based on the privileges of the request used to read this object. Note that an agent may choose to return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'main' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'main' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty-string.\"",
    "::=",
    "{",
    "entLogicalEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "An SNMPv1 or SNMPv2C community-string which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also choose to return a community string based on the privileges of the request used to read this object. Note that an agent may choose to return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string which allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'main' naming scope. This is possible when the logical entities represented by the same value of entLogicalCommunity have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'main' naming scope. For agents not accessible via SNMPv1 or SNMPv2C, the value of this object is the empty-string."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Preserved mibdepot archive

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX  OCTET STRING
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
               "An SNMPv1 or SNMPv2C community-string which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also choose to return a community string
                based on the privileges of the request used to read this
                object.  Note that an agent may choose to return a community
                string with read-only privileges, even if this object is
                accessed with a read-write community string. However, the
                agent must take care not to return a community string which
                allows more privileges than the community string used to
                access this object.
    
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'main'
                naming scope.  This is possible when the logical entities
                represented by the same value of entLogicalCommunity have no
                object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'main'
                naming scope.
    
    
                For agents not accessible via SNMPv1 or SNMPv2C, the value
                of this object is the empty-string."
        ::= { entLogicalEntry  4 }
    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['TimeTicks'], 'RFC1213-MIB': ['DisplayString', 'mib-2']}
    · Download rfc2037v1.mib.txt
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Archived: 2026-10-19T00:22:11.179460+00:00.

entLogicalCommunity

Status in source: deprecated.

Names: entLogicalCommunity

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "entLogicalCommunity",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object or may continue to return a community string (e.g., tri-lingual agent support).\"",
    "::=",
    "{",
    "entLogicalEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object or may continue to return a community string (e.g., tri-lingual agent support)."
    ],
    null,
    null,
    null,
    null
  ]
}
  • RFC Editor · RFC 6933 · RFC errata · Publisher's source file: Entity MIB (Version 4)

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2c community string, which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a
    
    
    
    
    
    
    
    
    
                read-write community string.  However, the agent must take
                care not to return a community string that allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities,
                represented by the same value of entLogicalCommunity, have
                no object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2c, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent or if no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated.  Agents that implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'UUID-TC-MIB': ['UUIDorZero'], 'IANA-ENTITY-MIB': ['IANAPhysicalClass'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download Entity MIB (Version 4)
    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-19T00:23:29.218781+00:00.

  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2c community string, which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a
    
                read-write community string.  However, the agent must take
                care not to return a community string that allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities,
                represented by the same value of entLogicalCommunity, have
                no object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2c, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent or if no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated.  Agents that implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'UUID-TC-MIB': ['UUIDorZero'], 'IANA-ENTITY-MIB': ['IANAPhysicalClass'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB

    Related source files and packages:


    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-24T02:14:26.997149+00:00.

  • Common and standard MIB copies (LibreNMS/Observium Community) · Publisher's source file: ENTITY-MIB

    Vendor MIB copy from the LibreNMS archive.

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2c community string, which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a
    
                read-write community string.  However, the agent must take
                care not to return a community string that allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities,
                represented by the same value of entLogicalCommunity, have
                no object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2c, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent or if no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated.  Agents that implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'UUID-TC-MIB': ['UUIDorZero'], 'IANA-ENTITY-MIB': ['IANAPhysicalClass'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB

    Related source files and packages:


    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-24T02:51:18.886297+00:00.

  • Netdisco MIB archive copies · Publisher's source file: ENTITY-MIB.txt

    Vendor MIB copy from the Netdisco archive.

    Module: ENTITY-MIB

    Published definition
    entLogicalCommunity OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE (0..255))
        MAX-ACCESS  read-only
        STATUS      deprecated
        DESCRIPTION
                "An SNMPv1 or SNMPv2c community string, which can be used to
                access detailed management information for this logical
                entity.  The agent should allow read access with this
                community string (to an appropriate subset of all managed
                objects) and may also return a community string based on the
                privileges of the request used to read this object.  Note
                that an agent may return a community string with read-only
                privileges, even if this object is accessed with a
    
                read-write community string.  However, the agent must take
                care not to return a community string that allows more
                privileges than the community string used to access this
                object.
    
                A compliant SNMP agent may wish to conserve naming scopes by
                representing multiple logical entities in a single 'default'
                naming scope.  This is possible when the logical entities,
                represented by the same value of entLogicalCommunity, have
                no object instances in common.  For example, 'bridge1' and
                'repeater1' may be part of the main naming scope, but at
                least one additional community string is needed to represent
                'bridge2' and 'repeater2'.
    
                Logical entities 'bridge1' and 'repeater1' would be
                represented by sysOREntries associated with the 'default'
                naming scope.
    
                For agents not accessible via SNMPv1 or SNMPv2c, the value
                of this object is the empty string.  This object may also
                contain an empty string if a community string has not yet
                been assigned by the agent or if no community string with
                suitable access rights can be returned for a particular SNMP
                request.
    
                Note that this object is deprecated.  Agents that implement
                SNMPv3 access should use the entLogicalContextEngineID and
                entLogicalContextName objects to identify the context
                associated with each logical entity.  SNMPv3 agents may
                return a zero-length string for this object or may continue
                to return a community string (e.g., tri-lingual agent
                support)."
        ::= { entLogicalEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TDomain', 'TAddress', 'TEXTUAL-CONVENTION', 'AutonomousType', 'RowPointer', 'TimeStamp', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'mib-2', 'NOTIFICATION-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'UUID-TC-MIB': ['UUIDorZero'], 'IANA-ENTITY-MIB': ['IANAPhysicalClass'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download ENTITY-MIB.txt

    Related source files and packages:


    Source location: ENTITY-MIB::entLogicalCommunity.
    Source version and references

    Downloaded: 2026-10-24T15:28:11.616979+00:00.

entLogicalCommunity

Status in source: unspecified.

Names: entLogicalCommunity

Technical details
{
  "syntax": "OCTET STRING{(0,255)}",
  "max_access": "read-only",
  "object_class": "table column"
}

entLogicalCommunity

Status in source: unspecified.

Names: entLogicalCommunity

Technical details
{
  "syntax": "OctetString min: 0 max: 255",
  "max_access": "read-only",
  "object_class": "table column",
  "implementation_notes": "Get return NULL string"
}

entLogicalCommunity

Status in source: unspecified.

Names: entLogicalCommunity

Technical details
{}

Information from Circitor

entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take



            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

Information from Cisco SMIv1

entLogicalCommunity OBJECT-TYPE
    SYNTAX OCTET STRING(SIZE(0..255))
    ACCESS read-only
    STATUS deprecated
    DESCRIPTION
        "An SNMPv1 or SNMPv2C community-string, which can be used to
        access detailed management information for this logical
        entity.  The agent should allow read access with this
        community string (to an appropriate subset of all managed
        objects) and may also return a community string based on the
        privileges of the request used to read this object.  Note
        that an agent may return a community string with read-only
        privileges, even if this object is accessed with a
        read-write community string.  However, the agent must take
        
        
        care not to return a community string that allows more
        privileges than the community string used to access this
        object.
        
        A compliant SNMP agent may wish to conserve naming scopes by
        representing multiple logical entities in a single 'default'
        naming scope.  This is possible when the logical entities,
        represented by the same value of entLogicalCommunity, have
        no object instances in common.  For example, 'bridge1' and
        'repeater1' may be part of the main naming scope, but at
        least one additional community string is needed to represent
        'bridge2' and 'repeater2'.
        
        Logical entities 'bridge1' and 'repeater1' would be
        represented by sysOREntries associated with the 'default'
        naming scope.
        
        For agents not accessible via SNMPv1 or SNMPv2C, the value
        of this object is the empty string.  This object may also
        contain an empty string if a community string has not yet
        been assigned by the agent, or if no community string with
        suitable access rights can be returned for a particular SNMP
        request.
        
        Note that this object is deprecated.  Agents which implement
        SNMPv3 access should use the entLogicalContextEngineID and
        entLogicalContextName objects to identify the context
        associated with each logical entity.  SNMPv3 agents may
        return a zero-length string for this object, or may continue
        to return a community string (e.g., tri-lingual agent
        support)."
    ::= { entLogicalEntry 4 }

Information from MIBdepot

entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take



            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

Information from Cisco

entLogicalCommunity OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))
    MAX-ACCESS  read-only
    STATUS      deprecated
    DESCRIPTION
            "An SNMPv1 or SNMPv2C community-string, which can be used to
            access detailed management information for this logical
            entity.  The agent should allow read access with this
            community string (to an appropriate subset of all managed
            objects) and may also return a community string based on the
            privileges of the request used to read this object.  Note
            that an agent may return a community string with read-only
            privileges, even if this object is accessed with a
            read-write community string.  However, the agent must take


            care not to return a community string that allows more
            privileges than the community string used to access this
            object.

            A compliant SNMP agent may wish to conserve naming scopes by
            representing multiple logical entities in a single 'default'
            naming scope.  This is possible when the logical entities,
            represented by the same value of entLogicalCommunity, have
            no object instances in common.  For example, 'bridge1' and
            'repeater1' may be part of the main naming scope, but at
            least one additional community string is needed to represent
            'bridge2' and 'repeater2'.

            Logical entities 'bridge1' and 'repeater1' would be
            represented by sysOREntries associated with the 'default'
            naming scope.

            For agents not accessible via SNMPv1 or SNMPv2C, the value
            of this object is the empty string.  This object may also
            contain an empty string if a community string has not yet
            been assigned by the agent, or if no community string with
            suitable access rights can be returned for a particular SNMP
            request.

            Note that this object is deprecated.  Agents which implement
            SNMPv3 access should use the entLogicalContextEngineID and
            entLogicalContextName objects to identify the context
            associated with each logical entity.  SNMPv3 agents may
            return a zero-length string for this object, or may continue
            to return a community string (e.g., tri-lingual agent
            support)."
    ::= { entLogicalEntry 4 }

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.47.1.2.1.1.1 entLogicalIndex00 entLogicalIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of t…
1.3.6.1.2.1.47.1.2.1.1.2 entLogicalDescr00 entLogicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of th…
1.3.6.1.2.1.47.1.2.1.1.3 entLogicalType00 entLogicalType OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the type of …
1.3.6.1.2.1.47.1.2.1.1.5 entLogicalTAddress00 entLogicalTAddress OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The transport service address b…
1.3.6.1.2.1.47.1.2.1.1.6 entLogicalTDomain00 entLogicalTDomain OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the kind of transport s…
1.3.6.1.2.1.47.1.2.1.1.7 entLogicalContextEngineID00 entLogicalContextEngineID OBJECT-TYPE
SYNTAX SnmpEngineIdOrNone
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The authoritat…
1.3.6.1.2.1.47.1.2.1.1.8 entLogicalContextName00 entLogicalContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The contextName that …