global.globalTimeManagement.timebase.dayPlanStatus.0
.1.3.6.1.4.1.1206.4.2.6.3.3.6.0
Always 0
global.globalTimeManagement.timebase.timeBaseScheduleTableStatus.0
.1.3.6.1.4.1.1206.4.2.6.3.3.7.0
Always 0
devices.global.globalTimeManagement.globalLocalTimeDifferential.0
.1.3.6.1.4.1.1206.4.2.6.3.4.0
Deprecated*** !
global.globalTimeManagement.controllerStandardTimeZone.0
.1.3.6.1.4.1.1206.4.2.6.3.5.0
Calculated
global.globalTimeManagement.controllerLocalTime.0
.1.3.6.1.4.1.1206.4.2.6.3.6.0
Calculated
global.globalReport.*
.1.3.6.1.4.1.1206.4.2.6.4.*
Not Supported
global.security.communityNameAdmin.0
.1.3.6.1.4.1.1206.4.2.6.5.1.0
**
global.security.communityNamesMax.0
.1.3.6.1.4.1.1206.4.2.6.5.2.0
Configurable/10
…communityNameTable.communityNameTableEntry.communityNameIndex.x
.1.3.6.1.4.1.1206.4.2.6.5.3.1.1.x
Tab Index
…communityNameTable.communityNameTableEntry.communityNameUser.x
.1.3.6.1.4.1.1206.4.2.6.5.3.1.2.x
**
…communityNameTable.communityNameTableEntry.communityNameAccessMask.x
.1.3.6.1.4.1.1206.4.2.6.5.3.1.3
**
** Note regarding the “global.security” subtree:
•
The Microsoft SNMP framework used only supports a simple security model, i.e. a “community name” either has “write/read”
access to ALL OIDs, or read-
only access to all OIDs (or no access at all). This includes the “global.security” subtree.
•
Configuration changes (add/change/delete community names) in the “security” subtree automatically lead to a reboot of the
LCom, because these settings only take effect after an operating system reboot.
*** Note regarding “deprecated” OIDs: these OIDs are only supported if the corresponding parameter (“support deprecated OID”) is set
for the NTCIP SNMP Agent.
