Cisco Cisco Aironet 1310 Access Point Bridge 릴리즈 노트

다운로드
페이지 19
 
8
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(21a)JY
OL-20668-02
  Important Notes
Important Notes
This section describes important information about access points and bridges.
Synchronize IOS Supplicant Clocks and Save Time Setting to NVRAM
An IOS device whose supplicant is configured to perform certificate-based authentication of its network 
connection may be unable to connect to the network unless you take the following steps.
To make sure that the device supplicant, after a reload but before it has connected to the network, knows 
approximately what time it is so it can validate the server's certificate, you must configure the supplicant 
to learn the time from an NTP server, and to write the time to its NVRAM.  This is a requirement for any 
system that runs Cisco IOS release 12.4(21a)JY.
Complete these steps:
Step 1
Configure the supplicant to synchronize its time to a known good NTP server, to which the supplicant 
has network access, and to store its time in its NVRAM.
Example configuration on a system with SNTP, and without a hardware calendar:
Supp(config)#sntp server 10.0.47.1
Supp(config)#clock save interval 8
Supp(config)#end
Supp#write memory
Example on a system with NTP, and with a hardware calendar:
Supp(config)#ntp server 10.0.47.1 iburst
Supp(config)#ntp update-calendar
Supp(config)#end
Supp#write memory
Step 2
Make sure that the supplicant has network connectivity to the NTP server, and has synchronized its time.  
Example:
Supp#show sntp
SNTP server     Stratum   Version    Last Receive
10.0.47.1          3         1        00:00:09     Synced
Example:
Supp#show ntp status
Clock is synchronized, stratum 4, reference is 10.95.42.129
[ ... ]
Step 3
Make sure that the correct time is saved to the supplicant’s hardware calendar (if it has one), or to 
NVRAM (if it does not).
On a system with no hardware calendar:
Reload the Supplicant, to make sure that the time is saved to NVRAM. After it reloads, verify that 
the  time is approximately correct, even when the NTP server is unavailable:
Supp#show clock detail
*08:24:30.103 -0700 Thu Apr 15 2010
No time source
On a system with hardware calendar:
Write the current, correct time to the hardware calendar: