Learn About Cisco IP Telephony for Release 4.x1 | 2 |
A. BAT must be installed on a publisher in the CallManager environment.
B. BAT requires Internet Explorer 4.01 Service Pack 2 or later.
C. BAT must be installed on a subscriber in the CallManager environment.
D. Because of its streamlined design, BAT can be used at any time.
E. BAT requires Internet Explorer 5.0 or later.
F. Because of its huge overhead, BAT should be used off hours.
A, B, F
To have read/write access to the CallManager database, you must install BAT on the publisher, which is the only server with the read/write copy of the CallManager database. The subscribers receive a read-only copy of the CallManager database. Therefore, you cannot install BAT on any subscriber.
To access the Web-based BAT, you must use either Internet Explorer 4.01 Service Pack 2 or later or Netscape 4.5 or later. You may be able to access BAT using third-party browsers, but you will not be able to receive Cisco support for any issues if you do not use the Cisco-specified browsers.
BAT is used to automate changes to multiple phones in a batch process. Because it involves many changes to many devices, it is recommended that you run BAT off hours to ensure CallManager resources are not exhausted.
Bulk Administrative Tool User Guide, Release 4.1(1) – Installation
Objective: Monitor and manage an IP telephony network using Internal Server Tools.
Sub-objective: Describe the tools inherent in the operating system and database, and also provided by Cisco, to monitor CallManager operation.
Single answer, multiple-choice
You are experiencing issues with your CallManager server. You want to use Event Viewer on the server to troubleshoot. What should you review to see CallManager specific events?
A. System log
B. Security log
C. DNS server log
D. Application log
You should review the application log. CallManager will write events to the application log. You can check the application log to quickly see if there were any events leading up to the problem you are troubleshooting. It is common to see multiple information and warning events prior to the error event. The event that occurred prior to the error event often provides more troubleshooting data than the actual error event.
The system log contains operating system and local service events such as services failing to start or drivers failing to load. The security log contains security events such as successful and failed log-on attempts and file access. The DNS server log contains events related to the DNS server service running on the server.
System Event Viewer Tips