National Research and Education Network
Education Cloud Data Center
Multi-Channel HD Telemedicine Solution
Over The Top/Multi-Tenant Data Center (OTT/MTDC)
Internet Exchange Point (IXP)
Internet Access Provider (IAP)
Design & Simulation
Planning & Analytics
Oil & Gas IoT
HPC & Operations Management
Digital Urban Rail
Retail Cloud Platform
Enterprise Data Center
Enterprise Cloud Communications
Network Management System
Buy from Huawei
Buy from resellers
Search for a nearby reseller and get direct contact information.
Become a Partner
Resources and Support
Huawei Authorized Learning Partner
Huawei Authorized Information and Network Academy
We use eSight eSight V300R003C20SPC101 HA edition, based on SuSe Linux 11 SP3.
We noticed that alarm report time at device (AC6605) is right and real, but eSight showed the same alarm and logs with 1 hour delay.
We checked SuSe system time and timezone (Moscow). It was correct.
YaST2 Control Center, choose System and click Data and Time.
Checked device current time (display clock) it was also correct and the same as at Linux.
Used several CLI commands at Linux terminal.
Moscow has changed time from UTC+4 to UTC+3 at 26.10.2014.
Two parts from SUSE, time doesn’t match. Linux with time UTC+4; JRE with time UTC +3 ( eSight get time form JRE interface).
Current time zone configure is UTC+4:
Install SUSE time zone patch at : https://download.suse.com/Download?buildid=ICGHskqP4jQ~ ( 2 files)
1, Change both eSight server’s time into UTC+4. That means 1 hour faster than your local time.
2, Using rpm -Uvh --nodeps *.rpm command to install both attached patches at 2 servers.
3, Using date –R to see if it’s changed successfully
After applying patch time at eSight logs and device logs became the same.