Nokia 7210 SAS-M User Manual

System Management
268
7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
3HE 16132 AAAB TQZZA Edition: 01
• The active and standby CPM should boot from same boot drives (cf1:\, cf2:\, or
uf:\). For example, if the active CPM is booted from cf1:\, the standby CPM must
use cf1:\ to bootup. Although it is possible to make the CPMs operational by
booting them using any drive on active and standby, Nokia recommends that the
same drives should be used to boot the system.
• The user should ensure that a valid bootstrap image (boot.tim) and BOF
(bof.cfg) exist in the cf1:\, cf2:\, or uf1:\ drive of both active and stand-by CPM
cards. The user must verify that bof.cfg resides on the same drive as the
boot.tim.
• The TiMOS application images (cpm.tim and iom.tim) and the configuration file
can reside in any location (local or remote), but the locations in the BOF should
be configured identically on both active and standby CPM for primary,
secondary, and tertiary locations.
• Boot-env synchronization must be performed before config synchronization.
To do so, run the admin redundancy synchronize boot-env command,
followed by the admin redundancy synchronize config command.
• Synchronization can only occur locally between compact flash drives cf1:Active
to cf1:Standby, cf2:Active to cf2:Standby, and uf1:Active to uf1:Standby.
Synchronization across different drives is not supported.
• If the active and standby CPM are not synchronized for some reason, users can
manually synchronize the standby CPM by running the admin redundancy
synchronize boot-env CLI command, and rebooting the standby CPM by
running the admin reboot standby command.
6.5 Network Synchronization
This section describes the network synchronization capabilities available
on7210 SAS platforms. These capabilities involve multiple approaches to network
timing, including Synchronous Ethernet, PTP/1588v2, adaptive timing, and others.
These features address barriers to entry as follows:
• provide synchronization quality required by mobile networks, such as radio
operations and circuit emulation services (CES) transport
• augment and potentially replace the existing (SONET/SDH) timing infrastructure
and deliver high quality network timing for time-sensitive wireline applications
Note: See the information in this section and refer to the 7210 SAS OS Software Release
Notes 11.0Rx for information about network synchronization options supported on each
7210 SAS platform.

Nokia 7210 SAS-M Specifications

General

Brand	Nokia
Model	7210 SAS-M
Category	Cell Phone
Language	English