Cisco Systems DOC-7812945= 사용자 설명서
11-16
Cisco WAN Manager User’s Guide
Version 10.5, Part Number 78-12945-01 Rev. D0, August 2003
Chapter 11 CWM to CWM Communications
Limitations for CWM to CWM Communications
It might take several minutes for all of the processes and messages to end, depending upon the number
of nodes in the network.
of nodes in the network.
Step 3
Press Return to redisplay the CWM main menu.
Step 4
From the main menu, enter x to exit the CWM application.
Step 5
Enter create_db, or coldstart -F or Sv+CreateDb -F.
Dozens of messages will be displayed, starting with the message dropping db. Additional messages will
indicate that tables are being created and procedures stored. The shell prompt will return in less than a
minute.
indicate that tables are being created and procedures stored. The shell prompt will return in less than a
minute.
Step 6
At the CWM workstation, enter CWM to redisplay the main menu.
Step 7
From the main menu, enter 1 to select the Start Core option.
Step 8
When the CWM main menu is displayed, enter 3 to launch the CWM Desktop.
Limitations for CWM to CWM Communications
•
The Secondary CWMs have to wait for the Primary CWM to finish syncing up with the network.
Trap 28075 (svDatabaseInSync) is sent when the Primary CWM has finished syncing up with the
network.
Trap 28075 (svDatabaseInSync) is sent when the Primary CWM has finished syncing up with the
network.
•
All the CWM workstations managing the same network must have seed nodes or gateway nodes that
have IP addresses within the same domain.
have IP addresses within the same domain.
Note
The network.conf file does not have to be the same on all CWM stations in the domain as long
as the gateway nodes specified in this file are part of the same network. Even though CWMs that
manage the same network can talk to each other, managing the same network does not require
having identical network.conf files on all Secondary and Primary CWMs.
as the gateway nodes specified in this file are part of the same network. Even though CWMs that
manage the same network can talk to each other, managing the same network does not require
having identical network.conf files on all Secondary and Primary CWMs.
•
The Configurator can only be run on the Primary CWM.
•
If all the Secondary CWM Gateways lose IP connection with the Primary CWM Gateway (no
heartbeat received in the past 2 consecutive Heartbeat Intervals), then all the Secondary CWM
Gateways will function in degraded mode and wait for the connection problem to be resolved.
heartbeat received in the past 2 consecutive Heartbeat Intervals), then all the Secondary CWM
Gateways will function in degraded mode and wait for the connection problem to be resolved.
Note
Do not cold start -F without first verifying that a Secondary CWM has switched over to become
the new Primary CWM of the domain, otherwise the node_id and other user data will become
inconsistent.
the new Primary CWM of the domain, otherwise the node_id and other user data will become
inconsistent.
Enabling CWM to CWM Communications
In Release 10.5, CWM provides a script to sync up a CWM database with another remote CWM
workstation without running the two CWMs in primary-secondary mode.
workstation without running the two CWMs in primary-secondary mode.
The script synchronizes the following user-related tables in the stratacom database: