OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

NTP Overview Configuring Network Time Protocol (NTP) Stratum Stratum is the term used to define the relative proximity of a node in a network to a time source (such as a radio clock). Stratum 1 is the server connected to the time source itself. (In most cases the time source and the stratum 1 server are in the same physical location.) An NTP client or server connected to a stratum 1 source would be stratum 2. A client or server connected to a stratum 2 machine would be stratum 3, and so on, as demonstrated in the diagram below: UTC Time Source Stratum 1 Stratum 2 Stratum 3 The farther away from stratum 1 a device is, the more likely there will be discrepancies or errors in the time adjustments done by NTP. A list of stratum 1 and 2 sources available to the public can be found on the Internet. Note. It is not required that NTP be connected to an officially recognized time source (for example, a radio clock). NTP can use any time source to synchronize time in the network. Using NTP in a Network NTP operates on the premise that there is one true standard time (defined by UTC), and that if several servers claiming synchronization to the standard time are in disagreement, then one or more of them must be out of synchronization or not functioning correctly. The stratum gradiation is used to qualify the accuracy of a time source along with other factors, such as advertised precision and the length of the network path between connections. NTP operates with a basic distrust of time information sent from other network entities, and is most effective when multiple NTP time sources are integrated together for checks and crosschecks. To achieve this end, there are several modes of operation that an NTP entity can use when synchronizing time in a network. These modes help predict how the entity behaves when requesting or sending time information, listed below: • A switch can be a client of an NTP server (usually of a lower stratum), receiving time information from the server but not passing it on to other switches. • A switch can be a client of an NTP server, and in turn be a server to another switch or switches. • A switch (regardless of its status as either a client or server) must be peered with another switch. Peering allows NTP entities in the network of the same stratum to regard each other as reliable sources of time and exchange time information. • The OmniSwitch by default will act as an NTP server and be able to respond to NTP client requests, and establish a client/server peering relationship. The OmniSwitch NTP server functionality allows the Omniswitch to establish an active peering relationship with another server, enable broadcast server functionality, disable a given IP for NTP and employ MD5 authentication for clients and active peers. page 11-6 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Configuring Network Time Protocol (NTP) NTP Overview Examples of these are shown in the simple network diagram below: UTC Time Source Stratum 1 NTP Servers 1a 1b NTP Server/Clients Stratum 2 2a 2b Stratum 3 NTP Clients 3a 3b Servers 1a and 1b receive time information from, or synchronize with, a UTC time source such as a radio clock. (In most cases, these servers would not be connected to the same UTC source, though it is shown this way for simplicity.) Servers 1a and 1b become stratum 1 NTP servers and are peered with each other, allowing them to check UTC time information against each other. These machines support machines 2a and 2b as clients, and these clients are synchronized to the higher stratum servers 1a and 1b. Clients 2a and 2b are also peered with each other for time checks, and become stratum 2 NTP servers for more clients (3a and 3b, which are also peered). In this hierarchy, the stratum 1 servers synchronize to the most accurate time source available, then check the time information with peers at the same stratum. The stratum 2 machines synchronize to the stratum 1 servers, but do not send time information to the stratum 1 machines. Machines 2a and 2b in turn provide time information to the stratum 3 machines. It is important to consider the issue of robustness when selecting sources for time synchronization. It is suggested that at least three sources should be available, and at least one should be “close” to you in terms of network topology. It is also suggested that each NTP client is peered with at least three other same stratum clients, so that time information crosschecking is performed. When planning your network, it is helpful to use the following general rules: • It is usually not a good idea to synchronize a local time server with a peer (in other words, a server at the same stratum), unless the latter is receiving time updates from a source that has a lower stratum than from where the former is receiving time updates. This minimizes common points of failure. OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 11-7
Page 1 and 2:
Part No. 060391-10, Rev. A May 2014
Page 3 and 4:
Contents About This Guide .........
Page 5 and 6:
Contents Using the Switch as an FTP
Page 7 and 8:
Contents Account and Password Polic
Page 9 and 10:
Contents Authentication Trap ......
Page 11 and 12:
Contents Firmware Upgrade Files ...
Page 13 and 14:
About This Guide This OmniSwitch AO
Page 15 and 16:
About This Guide Documentation Road
Page 17 and 18:
About This Guide Related Documentat
Page 19 and 20:
1 Logging Into the Switch Logging i
Page 21 and 22:
Logging Into the Switch Quick Steps
Page 23 and 24:
Logging Into the Switch Overview of
Page 25 and 26:
Logging Into the Switch Accessing t
Page 27 and 28:
Logging Into the Switch Setting the
Page 29 and 30:
Logging Into the Switch Using Secur
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Logging Into the Switch Modifying t
Page 37 and 38:
Logging Into the Switch Enabling th
Page 39 and 40:
Logging Into the Switch Enabling th
Page 41 and 42:
2 Managing System Files This chapte
Page 43 and 44:
Managing System Files Switch Admini
Page 45 and 46:
Managing System Files File and Dire
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Managing System Files Loading Softw
Page 55 and 56:
Managing System Files Loading Softw
Page 57 and 58:
Managing System Files Setting the S
Page 59 and 60:
Managing System Files Setting the S
Page 61 and 62:
3 Managing CMM Directory Content Th
Page 63 and 64:
Managing CMM Directory Content CMM
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Managing CMM Directory Content Mana
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Managing CMM Directory Content Usin
Page 77 and 78:
4 Using the CLI Alcatel-Lucent’s
Page 79 and 80:
Using the CLI Command Entry Rules a
Page 81 and 82:
Using the CLI Command Help -> sh vl
Page 83 and 84:
Using the CLI Logging CLI Commands
Page 85 and 86:
Using the CLI Customizing the Scree
Page 87 and 88:
5 Working With Configuration Files
Page 89 and 90:
Working With Configuration Files Tu
Page 91 and 92:
Working With Configuration Files Qu
Page 93 and 94:
Working With Configuration Files Co
Page 95 and 96:
Working With Configuration Files Cr
Page 97 and 98:
Working With Configuration Files Cr
Page 99 and 100:
6 Managing Switch User Accounts Swi
Page 101 and 102:
Managing Switch User Accounts User
Page 103 and 104:
Managing Switch User Accounts Overv
Page 105 and 106:
Managing Switch User Accounts Overv
Page 107 and 108:
Managing Switch User Accounts Creat
Page 109 and 110:
Managing Switch User Accounts Confi
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Managing Switch User Accounts Setti
Page 117 and 118:
Managing Switch User Accounts Multi
Page 119 and 120:
7 Managing Switch Security Switch s
Page 121 and 122:
Managing Switch Security Switch Sec
Page 123 and 124:
Managing Switch Security Authentica
Page 125 and 126:
Managing Switch Security Quick Step
Page 127 and 128:
Managing Switch Security Setting Up
Page 129 and 130:
Managing Switch Security Configurin
Page 131 and 132:
8 Using WebView The switch can be m
Page 133 and 134:
Using WebView WebView CLI Commands
Page 135 and 136: Using WebView WebView Overview Conf
Page 137 and 138: 9 Using SNMP The Simple Network Man
Page 139 and 140: Using SNMP Quick Steps for Setting
Page 141 and 142: Using SNMP Quick Steps for Setting
Page 143 and 144: Using SNMP SNMP Overview Using SNMP
Page 145 and 146: Using SNMP Using SNMP For Switch Se
Page 147 and 148: Using SNMP Using SNMP For Switch Se
Page 149 and 150: Using SNMP Working with SNMP Traps
Page 151 and 152: Using SNMP Verifying the SNMP Confi
Page 153 and 154: 10 Web Services, CLI Scripting, and
Page 155 and 156: Web Services, CLI Scripting, and Op
Page 181 and 182: 11 Configuring Network Time Protoco
Page 183 and 184: Configuring Network Time Protocol (
Page 185: Configuring Network Time Protocol (
Page 195 and 196: 12 Managing Automatic Remote Config
Page 197 and 198: Managing Automatic Remote Configura
Page 219 and 220: 13 Configuring Virtual Chassis A Vi
Page 221 and 222: Configuring Virtual Chassis Virtual
Page 223 and 224: Configuring Virtual Chassis Quick S
Page 227 and 228: Configuring Virtual Chassis Managin
Page 229 and 230: Configuring Virtual Chassis Managin
Page 235 and 236: Configuring Virtual Chassis Interac
Page 237 and 238:
Configuring Virtual Chassis Configu
Page 239 and 240:
Configuring Virtual Chassis Configu
Page 241 and 242:
Configuring Virtual Chassis Display
Page 243 and 244:
A Software License and Copyright St
Page 245 and 246:
Alcatel-Lucent License Agreement Al
Page 247 and 248:
B SNMP Trap Information This append
Page 249 and 250:
SNMP Traps Table No. Trap Name Obje
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Index Symbols !! command 4-6 A aaa
Page 295 and 296:
Index Network Time Protocol see NTP
show all

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Create successful ePaper yourself

Delete template?

Save as template?