TPLINK-SYSTIME-MIB

All MIBs › TPLINK-SYSTIME-MIB

Organization: TPLINK

Last Updated: 2012-12-13

Category: Switch and Device Management

Description: Manages TP-Link switch system clock, NTP server configuration, and timezone settings.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TPLINK-SYSTIME-MIB?

TPLINK-SYSTIME-MIB is a vendor-private MIB from TP-Link used on its managed switch line (e.g., JetStream/SafeStream series) to configure and inspect the device's system clock. It exposes configuration-style data rather than performance counters: NTP server address, timezone offset, and daylight-saving-time settings. Its main monitoring value is confirming that a device's time base is correctly configured and synchronized, since accurate clocks underpin reliable event-log timestamps, certificate validation, and cross-device event correlation, making it an indirect but important piece of overall device health/configuration monitoring. It has no significant dependency on other MIBs beyond the standard SNMPv2 framework used for object indexing. It is typically deployed in SMB and mid-size network environments where TP-Link managed switches are polled via SNMP alongside other configuration MIBs to keep fleet-wide clocks aligned. Engineers can download the TPLINK-SYSTIME-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TPLINK-SYSTIME-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

TP-Link managed switch

Monitoring Examples

No sample objects were provided for this module, so specific object names cannot be confirmed, but based on the description an admin would expect to poll scalar objects for the configured NTP server IP and timezone/DST settings. Checking these values across a switch fleet would reveal a device pointed at an unreachable or wrong NTP server, or a timezone misconfiguration causing skewed log timestamps relative to other network equipment. This remains a general characterization since no concrete object names were supplied.

What Can Be Monitored

configured NTP server address
system timezone setting
daylight saving time configuration
clock synchronization state

Imported Objects

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From TPLINK-MIB

tplinkMgmt

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
tplinkSysTimeMIB	1.3.6.1.4.1.11863.6.2			Private MIB for system time configuration.
tplinkSysTimeMIBObjects	1.3.6.1.4.1.11863.6.2.1
OCT tpSysTimeCurrentTime	1.3.6.1.4.1.11863.6.2.1.1	OCTET STRING	read-only	The current local date and time for the system.
OCT tpSysTimeSource	1.3.6.1.4.1.11863.6.2.1.2	OCTET STRING	read-only	The time source
OCT tpSysTimeMode	1.3.6.1.4.1.11863.6.2.1.3	OCTET STRING	read-only	the time mode
tpSysTimeManualTimeConfig	1.3.6.1.4.1.11863.6.2.1.4
INT tpSysTimeManualTimeStatus	1.3.6.1.4.1.11863.6.2.1.4.1	INTEGER	read-write	0.disbale 1.enable
OCT tpSysTimeTimeToSet	1.3.6.1.4.1.11863.6.2.1.4.2	OCTET STRING	read-write	A date-time specification. For example, Saturday May 26, 2012 at 1:30:15 would be given as: 2012-05-26 01:30:15
tpSysTimeNTPClientConfig	1.3.6.1.4.1.11863.6.2.1.5
INT tpSysTimeNTPClientStatus	1.3.6.1.4.1.11863.6.2.1.5.1	INTEGER	read-write	0.disbale 1.enable
INT tpSysTimeNTPTimezone	1.3.6.1.4.1.11863.6.2.1.5.2	INTEGER	read-write	time zone select: utc-1200, --International Date Line West utc-1100, --Coordinated Universal Time-11 utc-1000, --Hawaii utc-0900, --Alaska utc-0800, --Pacific Time (US & Canada), Baja California utc-0700, --Mountain Time (US & Canada), Chihuahua, La Paz, Mazatlan, Arizona utc-0600, --Saskatchewan, Central America, Central Time (US & Canada), Guadalajara, Mexico City, Monterrey utc-0500, --Eastern Time (US & Canada), Bogota, Lima, Quito, Indiana (East) utc-0430, --Caracas utc-0400, --Atlantic Time (Canada), Cuiaba, Santiago, Asuncion, Georgetown, La Paz, Manaus, San Juan utc-0330, --Newfoundland utc-0300, --Buenos Aires, Salvador, Brasilia, Greenland, Montevideo, Cayenne, Fortaleza utc-0200, --Mid-Atlantic, Coordinated Universal Time-02 utc-0100, --Azores, Cape Verde Is. utc, --Dublin, Edinburgh, Lisbon, London, Monrovia, Reykjavik, Casablanca, Coordinated Universal Time utc0100, --Belgrade, Bratislava, Budapest, Ljubljana, Prague, Sarajevo, Skopje, Warsaw, Zagreb, Tripoli, Windhoek, Brussels, Copenhagen, Madrid, Paris, West Central Africa, Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna utc0200, --E. Europe, Cairo, Amman, Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius, Athens, Bucharest, Jerusalem, Beirut, Harare, Pretoria, Damascus, Istanbul, utc0300, --Kuwait, Riyadh, Baghdad, Nairobi, Kaliningrad, Minsk utc0330, --Tehran utc0400, --Abu Dhabi, Muscat, Baku, Yerevan, Tbilisi, Port Louis, Moscow, St. Petersburg, Volgograd utc0430, --Kabul utc0500, --Islamabad, Karachi, Tashkent utc0530, --Chennai, Kolkata, Mumbai, New Delhi, Sri Jayawardenepura utc0545, --Kathmandu utc0600, --Dhaka, Astana, Ekaterinburg utc0630, --Yangon (Rangoon) utc0700, --Novosibirsk, Bangkok, Hanoi, Jakarta utc0800, --Beijing, Chongqing, Hong Kong, Urumqi, Krasnoyarsk, Kuala Lumpur, Singapore, Taipei, Ulaanbaatar, Perth utc0900, --Seoul, Irkutsk, Osaka, Sapporo, Tokyo utc0930, --Darwin, Adelaide utc1000, --Canberra, Melbourne, Sydney, Brisbane, Hobart, Guam, Port Moresby, Yakutsk utc1100, --Solomon Is., New Caledonia, Vladivostok utc1200, --Fiji, Magadan, Auckland, Wellington, Petropavlovsk-Kamchatsky, Coordinated Universal Time+12 utc1300, --Nuku'alofa, Samoa
IP tpSysTimeNTPServerAddr	1.3.6.1.4.1.11863.6.2.1.5.3	IpAddress	read-write	The ip address of ntp server to fetch time,for example: 133.100.9.2.
IP tpSysTimeNTPBackupServerAddr	1.3.6.1.4.1.11863.6.2.1.5.4	IpAddress	read-write	The ip address of ntp backup server,for example: 139.78.100.163.
INT tpSysTimeNTPUpdateRate	1.3.6.1.4.1.11863.6.2.1.5.5	INTEGER	read-write	Specify the rate fetching time from ntp server
tpSysTimeDstConfig	1.3.6.1.4.1.11863.6.2.1.6
INT tpSysTimeDstStatus	1.3.6.1.4.1.11863.6.2.1.6.1	INTEGER	read-write	An indication of whether the summertime feature is disabled(0) or is in date(3), predefined(1) or recurring(2) mode on this device. When this object is set to date(3),then the tpSysTimeDstOffset, tpSysTimeDstDateTimeToStart, tpSysTimeDstDateTimeToEnd objects work effectively and the summertime feature works one-off. When this object is set to predefined(1), the the tpSysTimeDstRegionSelected object works effectively and the summertime feature works recurrently. when this object is set to recurring(2), then the tpSysTimeDstOffset, tpSysTimeDstRecurringToStart, tpSysTimeDstRecurringToEnd objects work effectively and the summertime feature work recurrently.
INT tpSysTimeDstOffset	1.3.6.1.4.1.11863.6.2.1.6.2	INTEGER	read-write	The value of this object indicates number of minutes to add or to subtract during summertime.This object is not instantiated when dstStatus object is set to disable.
tpSysTimeDstDateMode	1.3.6.1.4.1.11863.6.2.1.6.3
OCT tpSysTimeDstDateTimeToStart	1.3.6.1.4.1.11863.6.2.1.6.3.1	OCTET STRING	read-write	Indicates summertime starts at this time. For example, Saturday May 26, 2012 at 1:30 would be given as: 2012-05-26 01:30
OCT tpSysTimeDstDateTimeToEnd	1.3.6.1.4.1.11863.6.2.1.6.3.2	OCTET STRING	read-write	Indicates summertime ends at this time. For example, Saturday May 26, 2012 at 1:30 would be given as: 2012-05-26 01:30
tpSysTimeDstPredefinedMode	1.3.6.1.4.1.11863.6.2.1.6.4
INT tpSysTimeDstRegionSelected	1.3.6.1.4.1.11863.6.2.1.6.4.1	INTEGER	read-write	Indicates the region selected when the dstStatus object is set to predefined. 1.none indicates the dstMode object is not set to predefined. 2.USA indicates the summertime is starts from the second Sunday in March at 02:00am and ends to the first Sunday in November at 02:00am 3.Australia indicates the summertime is starts from the first Sunday in October at 02:00am and ends to the first Sunday in April at 03:00am next year 4.Europe indicates the summertime is starts from the last Sunday in March at 01:00am and ends to last Sunday in October at 01:00am. 5.New Zealand indicates the summertime is start from the last Sunday in September at 02:00am and ends to the first Sunday in April at 03:00am next year
tpSysTimeDstRecurringMode	1.3.6.1.4.1.11863.6.2.1.6.5
OCT tpSysTimeDstRecurringToStart	1.3.6.1.4.1.11863.6.2.1.6.5.1	OCTET STRING	read-write	Indicates summertime starts at this time every year. octets contents range 1 week 1..4,ff where last = ff 2 day 0..6 where sunday = 0 saturday = 6 3 month 1..12 where january = 1 december = 12 4 hour 0..23 5 min 0..59 For example, the first Monday in Feb at 14:30pm should be given as 01 01 02 0e 1e For the last Tuesday in dec at 1:20am should be given as ff 02 0c 01 14 This object is not instantiated when dstStatus object is not set to recurring.
OCT tpSysTimeDstRecurringToEnd	1.3.6.1.4.1.11863.6.2.1.6.5.2	OCTET STRING	read-write	Indicates summertime ends at this time every year. octets contents range 1 week 1..4,ff where last = ff 2 day 0..6 where sunday = 0 saturday = 6 3 month 1..12 where january = 1 december = 12 4 hour 0..23 5 min 0..59 For example, the third friday in February at 3:30am should be given as 03 05 02 03 1e For the first Tuesday in May at 1:20am should be given as 01 02 05 01 14 This object is not instantiated when dstStatus object is not set to recurring.
tplinkSysTimeNotifications	1.3.6.1.4.1.11863.6.2.2

RFC description

Manages system time configuration for TP-Link devices, including manual time setup and NTP client settings.

Start monitoring TP-Link managed switch (NTP/timezone sync config status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TPLINK-SYSTIME-MIB

What Is TPLINK-SYSTIME-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description