Cloud Native应用交付
  • 首页
  • 关于本站
  • 个人介绍
  • Downloads
  • Repo
    • Github
    • Container
  • F5
    • F5 Python SDK
    • F5-container
    • F5-LBaaS
  • 社交
    • 联系我
    • 微信/微博
    • 公众号
    • 打赏赞助
行至水穷处 坐看云起时
☁️We are in new App Mesh era: imesh.club ☁️
  1. 首页
  2. F5技术
  3. 正文

同步系统和硬件时间

2008年07月15日 3836点热度 0人点赞 0条评论

OL3381: Setting the time and date on BIG-IP


Updated: 3/20/08 10:52 AM
Solution

 

 

The BIG-IP system uses the following two clocks to track time:
  • Hardware clock

    The hardware clock tracks time even when the system is unplugged. It is used to initialize the operating system clock when the system is booted.

  • Operating system clock

    The operating system clock is a software clock that is used when the system is running. This clock stores time according to the local time zone that you configure when you initially set up the system.

Note: Versions of BIG-IP prior to 9.0 allowed you to configure the hardware clock using the BIOS Configuration utility. This option is no longer possible, and is not necessary on systems running version 9.0 or later.

To set the operating system time on a BIG-IP system, perform the following procedure:

  1. Log in to the command line.

  2. Change the operating system time using the following command syntax:

    date <month><day><hour><minute><year>.<second>
     

    The specific format is as follows:

    date MMDDHHMMYYYY.SS

    For example, to set the time to 1:00pm on January 1, 2007, you would type the following command:

    date 010113002007.00

  3. Save the time to the hardware clock (BIOS), by typing the following command:

    hwclock --systohc

  4. In order to ensure the BIG-IP system daemons operate and log properly once the operating system clock has been changed, you will need to reboot the BIG-IP system. To reboot the BIG-IP, type the following command:

    reboot

本作品采用 知识共享署名 4.0 国际许可协议 进行许可
标签: 暂无
最后更新:2008年07月15日

纳米

http://linjing.io

打赏 点赞
< 上一篇
下一篇 >

文章评论

取消回复

纳米

http://linjing.io

☁️迈向Cloud Native ADC ☁️

认证获得:
Kubernetes: CKA #664
Microsoft: MCSE MCDBA
Cisco: CCNP
Juniper: JNCIS
F5:
F5 Certified Solution Expert, Security
F5 Certified Technology Specialist, LTM/GTM/APM/ASM
F5 Certified BIG-IP Administrator
  • 点击查看本博技术要素列表
  • 分类目录
    • Avi Networks (3)
    • Cisco ACI (1)
    • CISCO资源 (21)
    • F5 with ELK (8)
    • F5-Tech tips (38)
    • F5技术 (203)
    • Juniper (4)
    • Linux (7)
    • Nginx (18)
    • SDN (4)
    • ServiceMesh (19)
    • WEB编程 (8)
    • WINDOWS相关 (7)
    • 业界文章 (18)
    • 交换机技术 (20)
    • 化云为雨/Openstack (35)
    • 协议原理 (52)
    • 容器/k8s (64)
    • 我的工作 (19)
    • 我的生活 (70)
    • 网站技术 (19)
    • 路由器技术 (80)
    • 项目案例 (28)
    文章归档
    标签聚合
    F5 k8s openstack nginx istio DNS envoy gtm docker network flannel api irule bigip neutron cc kubernetes ELK vxlan BGP dhcp VPN IPSec lbaas ingress ingress controller nginx plus sidecar IPSec VPN NAT sql
    最新 热点 随机
    最新 热点 随机
    Say hello for 2021 二进制flannel部署,非cni网络模式下与k8s CIS结合方案 又是一年国庆 Service Account Token Volume Projection Istio ingressgateway 静态TLS证书加载与SDS发现方式配置区别 Istio里Gateway的port定义与实际ingressgateway的listener端口关系及规则 Helm 3 部署NGINX Ingress Controller 应用交付老兵眼中的Envoy, 云原生时代下的思考 Istio sidecar iptables以及流量控制分析 Istio 熔断策略及envoy配置
    Say hello for 2021
    Security (IPSec) Encryption-CHS版 [学习笔记]OSPF中的接口状态机与邻居状态机 DNS TMOS_Order_of_Operations_v2 NGINX Plus 增强模块-命令-参数 Ubuntu14.04用devstack安装openstack 通过ihealth API 自动化提取诊断分析结果 以太网类型帧与802.3/802.2定义的帧区别 Mirror Your Browser Request 二进制flannel部署,非cni网络模式下与k8s CIS结合方案
    链接表
    • Jimmy Song‘s Blog
    • SDNap
    • SDNlab
    • SDN论坛
    • Service Mesh社区
    • 三斗室
    • 个人profile

    COPYRIGHT © 2020 Cloud Native应用交付. ALL RIGHTS RESERVED.

    THEME KRATOS MADE BY VTROIS

    京ICP备14048088号-1

    京公网安备 11010502041506号

    [ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin