- Preface
- Cisco Prime IP Express Components
- Cisco Prime IP Express User Interfaces
- Server Status Dashboard
- Deploying Cisco Prime IP Express
- Configuring Administrators
- Managing the Central Configuration
- Maintaining Servers and Databases
- Backup and Recovery
- Managing Address Space
- Managing Hosts
- Managing Owners and Regions
- Managing Reports
- Introduction to the Domain Name System
- Managing Zones
- Configuring DNS Views
- Managing Resource Records
- Managing Authoritative DNS Server Properties
- Managing Caching DNS Server Properties
- Configuring High-Availability DNS Servers
- Introduction to Dynamic Host Configuration
- Configuring Scopes and Networks
- Configuring Policies and Options
- Managing Leases
- Advanced DHCP Server Properties
- Configuring Client-Classes and Clients
- Using Expressions
- Managing DHCPv6 Addresses
- Managing DHCP Failover
- Configuring DNS Update
- Using Extension Points
- Introduction to Cisco Prime IP Express Virtual Appliance
- Managing the Cisco Prime IP Express Virtual Appliance
- Resource Records
- DHCP Options
- DHCP Extension Dictionary
- Glossary
Cisco Prime IP Express 8.2 User Guide
- Updated:
- February 11, 2018
Chapter: Maintaining Servers and Databases
Maintaining Servers and Databases
This chapter explains how to administer and control your local and regional server operations.
Managing Servers
If you are assigned the server-management subrole of the ccm-admin role, you can manage the Cisco Prime IP Express servers as follows:
- Start —Load the database and start the server.
- Stop —Stop the server.
- Reload —Stop and restart the server. (Note that you do not need to reload the server for all RR updates, even protected RR updates. For details, see Chapter 29, “Configuring DNS Update”.)
- Check statistics —See the “Displaying Statistics” section.
- View logs —See the “Searching the Logs” section.
- Manage interfaces —See the specific protocol pages for how to manage server interfaces.
Starting and stopping a server is self-explanatory. When you reload the server, Cisco Prime IP Express performs three steps—stops the server, loads configuration data, and restarts the server. Only after you reload the server does it use your changes to the configuration.
Note The CDNS, DNS, DHCP, and SNMP servers are enabled by default to start on reboot. You can change this using [server] type enable or disable start-on-reboot in the CLI.
Local Basic or Advanced and Regional Web UI
You can manage the protocol servers in the following ways depending on if you are a:
- Local or regional cluster administrator —Choose Manage Servers from the Operate menu to open the Manage Servers page.
The local and regional cluster web UI access to server administration is identical, even though the available functions are different. As a regional administrator, you can check the state and health of the regional CCM server, server agent. However, you cannot stop, start, reload, or view statistics, logs, or interfaces for them.
At the local cluster, to manage the DHCP, DNS, CDNS, or SNMP servers, select the server in the Manage Servers pane and do any of the following:
– Click the Statistics tab to view statistics for the server. (See the “Displaying Statistics” section.)
– Click the Log tab in the View Log column to view the log messages for the server. (See the “Logging Server Events” section.)
– Click the Start Server button to start the server.
– Click the Stop Server button stop the server.
– Click the Restart Server button to reload the server.
- Local cluster DNS administrator —Choose DNS Server from the Deploy menu to open the Manage DNS Authoritative Server page.
Along with the Statistics, Startup Logs, Logs, HA DNS Server Status, Start Server, Stop Server, and Restart Server functions, you can also perform other functions when you click the Commands button to open the DNS Commands dialog box.
The server command functions are:
– Forcing all zone transfers (see the “Enabling Zone Transfers” section)—Click the Run icon. This is the equivalent of dns forceXfer secondary in the CLI.
– Scavenging all zones (see the “Scavenging Dynamic Records” section)—Click the Run icon. This is the equivalent of dns scavenge in the CLI.
- Local cluster Caching DNS server— Choose CDNS Server from the Deploy menu to open the Manage DNS Caching Server page.
Along with the Statistics, Startup Logs, Logs, Start Server, Stop Server, and Restart Server functions, you can also perform other functions when you click Commands button to open the CDNS Commands dialog box.
In Advanced and Expert modes, you can flush Caching CDNS cache and flush the resource records. Click the Commands button to execute the commands.
- Local cluster DHCP administrator —Click DHCP Server from the Deploy menu to open the Manage DHCP Server page.
Along with the Statistics, Startup Logs, Logs, Start Server, Stop Server, and Restart Server functions, you can also perform other functions when you click the Commands button to open the DHCP Server Commands dialog box.
This page provides the Get Leases with Limitation ID feature, to find clients that are associated through a common limitation identifier (see the “Administering Option 82 Limitation” section). Enter at least the IP address of the currently active lease in the IP Address field, then click the Run icon. You can also enter the limitation ID itself in the form nn : nn : nn or as a string ( " nnnn " ), in which case the IP address becomes the network in which to search. This function is the equivalent of dhcp limitationList ipaddress limitation-id show in the CLI.
CLI Commands
In the CLI, the regional cluster allows CCM server management only:
- To start the server, use server type start (or simply type start ; for example, dhcp start ).
- To stop the server, use server type stop (or simply type stop ; for example, dhcp stop ). If stopping the server, it is advisable to save it first using the save command.
- To reload the server, use server type reload (or simply type reload ; for example, dhcp reload ). Cisco Prime IP Express stops the server you chose, loads the configuration data, and then restarts the server.
- To set or show attributes for the server, use [ server ] type set attribute = value or [ server ] type show . For example:
Scheduling Recurring Tasks
In Basic and Advanced user mode in the local cluster web UI, you can schedule a number of recurring tasks. These tasks are:
– If in staged dhcp edit mode, reload the main DHCP server.
– Synchronize the failover configuration to the backup DHCP server.
– If in staged dhcp edit mode, reload the backup DHCP server.
– If in staged dhcp edit mode, reload the main DNS server.
– Synchronize the HA DNS configuration to the backup DNS server.
– If in staged dhcp edit mode, reload the backup DNS server.
– If in staged dhcp edit mode, reload the main DNS server.
– If in staged dhcp edit mode, reload the backup HA DNS server.
– Synchronize the zone distribution maps.
– If in staged dhcp edit mode, reload the secondary DNS server or servers.
Local Basic or Advanced Web UI
To set up one or more of these recurring server tasks:
Step 1 From the Operate menu, choose Schedule Tasks to open the List/Add Scheduled Tasks page.
Step 2 Click the Add Scheduled Tasks icon in the Scheduled Tasks pane on the left to open the Add Scheduled Task page.
Step 3 Enter values in the appropriate fields:
a. Name of the scheduled task. This can be any identifying text string.
b. Pull down from the available list of task types, which are:
- dhcp-reload —Reloads the DHCP server
- dns-reload —Reloads the DNS server
- cdns-reload —Reloads the Caching DNS server
- sync-dhcp-pair —Synchronizes the DHCP failover server pair
- sync-dns-pair —Synchronizes the HA DNS failover server pair
- sync-zd-map —Synchronizes zone distribution maps
- sync-dns-update-map —Synchronizes DNS update maps
c. Indicate the time interval for the scheduled task, such as 60m or 4w2d.
Step 4 Click Add Scheduled Task .
Step 5 If you click the name of the task on the List/Add Scheduled Tasks page, on the Edit Scheduled Task page you can view (in the Task Status section) the last status or the list of last errors (if any) that occurred during the task execution. Click Run Now to run the task immediately.
Note The DNS server startup and background loading slows down when HA is enabled before the HA DNS server communicates to its partner. You need to allow the HA DNS server to communicate with its partner before reloading or restarting the DNS server.
Logging Server Events
When you start Cisco Prime IP Express, it automatically starts logging Cisco Prime IP Express system activity. Cisco Prime IP Express maintains all the logs by default on:
- Windows — install-path \logs
- Linux — install-path /logs (to view these logs, use the tail -f command)
Tip To avoid filling up the Windows Event Viewer and preventing Cisco Prime IP Express from running, in the Event Log Settings, check the Overwrite Events as Needed box. If the events do fill up, save them to a file, then clear them from the Event Log.
Local Basic or Advanced and Regional Web UI
Server logging is available in the web UI when you open the Manage Servers page for a server (see the “Managing Servers” section), then click the Log icon in the View Log column for the server. This opens the Log for Server page. The log is in chronological order with the page with the latest entries shown first. If you need to see earlier entries, click the left arrow at the top or bottom of the page.
Searching the Logs
The web UI provides a convenient way to search for entries in the activity and startup log files. You can locate specific message text, log message IDs, and message timestamps using a regular expression string entry. When you click the Log icon in the View Log or View Startup Log column on the Manage Servers page (or one of the specific server pages), this opens a Log for Server page. In the text field next to the Search icon at the top or bottom of the page, enter the search string in the regular expression syntax. (For example, entering name? searches for occurrences of the string name in the log file.) Click the Search icon to view the results of log search.
Click the name of the log message, which opens the Log for Server page with the full message text. To view the full message text, click the name of the log message. Change between Table and Text view by clicking the Log icon. Click Close on the Log Search Result page to close the browser window.
Logging Format and Settings
The server log entries include the following categories:
- Activity —Logs the activity of your servers.
- Info —Logs standard operations of the servers, such as starting up and shutting down.
- Warning —Logs warnings, such as invalid packets, user miscommunication, or an error in a script while processing a request.
- Error —Logs events that prevent the server from operating properly, such as out of memory, unable to acquire resources, or errors in configuration.
Note Warnings and errors go to the Event Viewer on Windows (see the Tip on page 7-4). For a description of the log messages for each server module, see the install-path/docs/msgid/MessageIdIndex.html file.
Local Basic or Advanced and Regional Web UI
You can affect which events to log. For example, to set the logging for the local cluster DNS and DHCP server:
- DNS —From the Deploy > DNS menu, choose DNS Server to open the Manage DNS Server page. Click the name of the server to open the Edit DNS Server page. Expand the Log Settings section to view the log settings. Make changes to the attributes as desired, click Save , then reload the server. (See Table 17-2 for the log settings to maximize DNS server performance.)
- DHCP —From the Deploy > DHCP menu, choose DHCP Server to open the Manage DHCP Server page. Click the name of the server to open the Edit DHCP Server page. Expand the Log Settings section to view the log settings. Make changes to the attributes as desired, click Save , then reload the server. (See Table 24-3 for the log settings to maximize DHCP server performance.)
Log Files
Table 7-1 describes the Cisco Prime IP Express log files in the install-path /logs directory.
catalina.
date
.log.txt |
CCM database for Tomcat server and web UI (Because new files are created daily, periodically archive old log files.) |
Each component can generate a number of log files, each with a preconfigured maximum size of 1 MB. The first log file name has the _log suffix. When this file reaches its maximum size, it gets the .01 version extension appended to its name and a new log file is created without the version extension. Each version extension is incremented by one for each new file created. When the files reach their configured maximum number, the oldest file is deleted and the next oldest assumes its name. The usual maximum number is four for the DNS, and DHCP servers.
Cisco Prime IP Express also has server_startup_log files. This applies to the CCM, DHCP, and DNS servers. These files log the start up and shut down phases of the server (the information is similar to the normal log file information). Server startup log files are useful in diagnosing problems that have been reported when the server was last started.
The number of these start-up logs is fixed at four for a server, and the size is fixed at one MB per server.
Note Some user commands can create User authentication entries in the Server Agent log because of separate connections to the cluster. Do not interpret these as a system security violation by another user.
CLI Commands
You can check the configured maximums for the DNS, and DHCP servers using [ server ] type serverLogs show in the CLI, which shows the maximum number ( nlogs ) and size ( logsize ) of these protocol server log files. You can adjust these parameters using [ server ] type serverLogs set nlogs= value and [ server ] type serverLogs set logsize= value . You cannot adjust these maximums for any of the other log files.
Note A change to the server logs will not take effect until you restart Cisco Prime IP Express.
View Change Log
In the web UI, you can view the change logs and tasks associated with configurations you make.
Local Basic and Advanced Web UI
From the Operate menu, choose Change Log . To view the change log, you must be assigned the database subrole of the ccm-admin or regional-admin role:
- The View Change Log page shows all the change logs, sorted by DBSN name. To get to the bottom of the list, click the right arrow at the bottom left of the page. Click the DBSN number of the change log entry to open a View Change Set page for it.
On the View Change Log page, you can filter the list, manually trim it, and save it to a file. You can filter the list by:
- Start and end dates
- Administrator who initiated the changes
- Configuration object class
- Specific object
- Object identifier (ID), in the format OID-00:00:00:00:00:00:00:00
- Server
- Database
Click Filter List or Clear Filter (to clear the filter that persists through the session). You can initiate a trim of the change log by setting how many days old you want the record to get before trimming it, by setting a number of days value in the “older than” field and clicking the Delete icon.
To save the change log entries to a comma-separated values (CSV) file, click the Save icon.
If a task is associated with a change log, it appears on the View Change Set page. You can click the task name to open the View CCM Task page for it.
Dynamic Update on Server Log Settings
The DHCP and the DNS servers register the changes on the server logs only during the server configuration, which happens during a reload. Reloading the servers is time consuming. Cisco Prime IP Express allows the DHCP and DNS servers to register the changes to log settings, without a reload.
Local Basic or Advanced Web UI
To dynamically update DHCP server log settings, do the following:
Step 1 From the Deploy > DHCP menu, choose DHCP Server. The Manage DHCP Server page appears.
Step 2 Click the name of the DHCP server in the left pane to open the Edit DHCP Server page.
Step 3 Modify the log settings as desired.
Step 4 Click Save at the bottom of the page. The new log settings are applied to the DHCP server. The Manage DHCP Server page is displayed with an updated page refresh time.
To dynamically update DNS server log settings, do the following:
Step 1 From the Deploy > DNS menu, choose DNS Server. This opens the Manage DNS Server page.
Step 2 Click the name of the DNS server in the left pane to open the Edit DNS Server page.
Step 3 Modify the log settings as desired.
Step 4 Click Save at the bottom of the page. The new log settings are applied to the DNS server. The Manage DNS Server page is displayed with an updated page refresh time.
Note If the dhcp-edit-mode or dns-edit-mode is set to synchronous, and if the server running, the change in server log settings is communicated to the server.
To dynamically update the DHCP or DNS server log settings using the CLI, you must have the appropriate edit-mode set to synchronous. After changing the server log settings, use the save command to save the settings.
Monitoring and Reporting Server Status
Monitoring the status of a server involves checking its:
Related Topics
Server States
Displaying Health
Displaying Statistics
Displaying IP Address Usage
Displaying Related Servers
Displaying Leases
Server States
All Cisco Prime IP Express protocol servers (DNS, DHCP, and SNMP) pass through a state machine consisting of the following states:
- Loaded —First step after the server agent starts the server (transitional).
- Initialized —Server was stopped or fails to configure.
- Unconfigured —Server is not operational because of a configuration failure (transitional).
- Stopped —Server was administratively stopped and is not running (transitional).
- Running —Server is running successfully.
The two essential states are initialized and running, because the server transitions through the states so quickly that the other states are essentially invisible. Normally, when the server agent starts the server, it tells the server to be up. The server process starts, sets its state to loaded, then moves up to running. If you stop the server, it walks down the states to initialized, and if you restart, it moves up to running again. If it fails to configure for some reason, it drops back to initialized, as if you had stopped it.
There is also an exiting state that the server is in very briefly when the process is exiting. The user interface can also consider the server to be disabled, but this rarely occurs and only when there is no server process at all (the server agent was told not to start one).
Displaying Health
You can display aspects of the health of a server, or how well it is running. The following items can decrement the server health, so you should monitor their status periodically. For the:
- Server agent (local and regional clusters)
- CCM server (local and regional clusters)
- DNS server (local cluster):
– Inability to contact its root servers
Server Health Status
The server health status varies from the value 0 to 10. The value 0 means the server is not running and 10 means the server is running. Some of the servers report only 0 or 10, and not anything in between. When a server reports a value from 1 to 9, it means that it detected conditions that indicate possible problems. It has nothing to do with the actual performance of the server. So, if the health of the server is a value from 1 to 9, the server log files need to be reviewed to see what errors were logged.
Note Depending on the level of activity and the size and number of log files, the condition that reduced the server health might not be visible in the log files. It is important to review the log files, but the servers do not log all the conditions that reduce the server health.
The following conditions can reduce the DHCP server health:
- Configuration errors (occurs when the server is getting started or restarting)
- When the server detects out-of-memory conditions
- When packet receive failures occur
- When packets are dropped because the server is out of request or response buffers
- When the server is unable to construct a response packet
Tip Health values range from 0 (the server is not running) to 10 (the highest level of health). It is recommended that the health status can be ignored, with the understanding that zero means server is not running and greater than zero means server is running. On Linux, you can run the cnr_status command, in the install-path/usrbin/ directory, to see if your local cluster server is running. For more information on how to check whether the local cluster server is running, see the Cisco Prime IP Express Installation Guide.
Local Basic or Advanced and Regional Web UI
From the Operate menu, select Manage Servers . Check the Manage Servers page for the state and health of each server.
CLI Commands
Use [ server ] type getHealth . The number 10 indicates the highest level of health, 0 that the server is not running.
Local Basic or Advanced and Regional Web UI
Go to the Manage Servers page, click the name of the server in the left pane, then click the Statistics tab, if available. On the Server Statistics page, click the name of the attribute to get popup help.
The DHCP, DNS, and CDNS statistics are each divided into two groups of statistics. The first group is for total statistics and the second group is for sample statistics. The total statistics are accumulated over time. The sample statistics occur during a configurable sample interval. The names of the two categories vary per server and per user interface, and are identified in Table 7-2 .
To set up the sample counters, you must activate either the collect-sample-counters attribute for the server or a log-settings attribute value called activity-summary. You can also set a log-settings value for the sample interval for each server, which is preset to 5 minutes. The collect-sample-counters attribute is preset to true for the DNS server, but is preset to false for the DHCP server. For example, to enable the sample counters and set the interval for DHCP, set the following attributes for the DHCP server:
CLI Commands
In the CLI, if you use [ server ] type getStats , the statistics are encoded in curly braces followed by sets of digits, as described in Table 7-3 for DNS, Table 7-5 for DHCP.
Reset the counters and total statistic by using dhcp resetStats , dns resetStats , or cdns resetStats .
DNS Statistics
The DNS server statistics in the web UI appear on the DNS Server Statistics page, click on the statistic’s name to read its description. You can refresh the DNS Server Statistics.
The DNS server statistics that you can view are:
- Attribute—Displays server statistics such as server identifier, recursive service, process uptime, time since reset, and so on.
- Performance Statistics—Displays the total statistics of the DNS Server performance.
- Query Statistics—Displays the total statistics of the queries.
- Security Statistics—Displays the total statistics of the security.
- Error Statistics—Displays the total statistics of the errors.
- Max Counter Statistics—Displays the total statistics of the maximum number of concurrent threads, RRs, DNS update latency, concurrent packets, and so on.
- HA Statistics—Displays the total statistics of the HA DNS Server.
- IPv6 Statistics—Displays the total statistics of the IPv6 packets received and sent.
- Performance Statistics—Displays the sample statistics about the DNS Server performance.
- Query Statistics—Displays the sample statistics about the queries.
- Security Statistics—Displays the sample statistics about the security.
- Error Statistics—Displays the sample statistics about the errors.
- HA Statistics—Displays the sample statistics about the HA DNS Server.
- IPv6 Statistics—Displays the sample statistics about the IPv6 packets received and sent.
Note To get the most recent data, click the Refresh Server Statistics icon at the top left corner of the page.
The CLI dns getStats command has the following options:
dns getStats [performance | query | errors | security | maxcounters | ha | ipv6 | all] [total | sample]
The dns getStats all command is the most commonly used.
CDNS Statistics
The CDNS server statistics in the web UI appear on the DNS Caching Server Statistics page, click on the name of the statistics to read its description. You can refresh the CDNS Server Statistics.
DHCP Statistics
The DHCP server statistics in the web UI appear on the DHCP Server Statistics page, click on the statistic’s name to read its description.
The DHCP server statistics details are available for:
- Attribute—Displays the server statistics such as server start time, server reload time, server up time, and statistics reset time.
- Total Statistics—Displays the total statistics of the scopes, request buffers, response buffers, packets and so on.
- Lease Counts (IPv4)—Displays the sample statistics of the IPv4 lease counts such as active leases, configured leases, reserved leases, and reserved active leases.
- Packets Received (IPv4)—Displays the sample statistics of the IPv4 packets received.
- Packets Sent (IPv4)—Displays the sample statistics of the IPv4 packets sent.
- Packets Failed (IPv4)—Displays the statistics of the failed IPv4 packets.
The Additional Attributes are:
- Failover Statistics—Displays the statistics of the DHCP failover server.
- IPv6 Statistics—Displays the statistics of the IPv6 prefixes configured, timed-out IPv6 offer packets and so on.
- Lease Counts (IPv6)—Displays the statistics of the IPv6 lease counts of active leases, configured leases, reserved leases, and reserved active leases.
- Packets Received (IPv6)—Displays the statistics of the IPv6 packets received.
- Packets Sent (IPv6)—Displays the statistics of the IPv6 packets sent.
- Packets Failed (IPv6)—Displays the statistics of the failed IPv6 packets.
Additional Attributes also includes Top Utilized Aggregations.
The CLI dhcp getStats command has the following options:
The dhcp getStats all command is the most commonly used.
Note To get the most recent data, click the Refresh Server Statistics icon at the top left of the page.
The CLI dhcp getStats command has the following options:
The dhcp getStats all command is the most commonly used. The dhcp getStats command without this option returns the statistics in a single line of positional values in the following format (Table 7-5 shows how to read these values):nrcmd> dhcp getStats
Displaying IP Address Usage
Displaying IP address usage gives an overview of how clients are currently assigned addresses.
Local Advanced and Regional Web UI
You can look at the local or regional cluster address space, or generate a lease history report at the regional cluster, to determine IP address usage. These functions are available in both web UIs in the Design > DHCPv4 menu, if you have address space privileges at the local or regional cluster.
You can determine the current address space utilization by clicking the View icon in the Current Usage column for the unified address space, address block, and subnet (see the “Viewing Address Utilization for Address Blocks, Subnets, and Scopes” section). You can also get the most current IP address utilization by querying the lease history (see the “Querying Leases” section). In the latter case, the regional CCM server references the appropriate DHCP server directly. To ensure this subnet-to-server mapping, you must update the regional address space view so that it is consistent with the relevant local cluster. Do this by pulling the replica address space, or reclaiming the subnet to push to the DHCP server (see the “Reclaiming Subnets” section). Also ensure that the particular DHCP server is running.
CLI Commands
You can generate an IP address usage report using the report command. The command has the following syntax:
The column-separator specifies the character string that separates the report columns (the preset value is the space character). If you want to include more than one space, precede them with the backslash ( \ ) escape character (enclosed in quotation marks). You can specify DHCPv4 or DHCPv6 addresses ( dhcp-only is the same as dhcpv4 ). Not specifying the VPN returns the addresses in the current VPN only.
Displaying Related Servers
Cisco Prime IP Express displays the relationship among servers in a DNS zone distribution or a DHCP failover configuration. In the web UI, you can view a related servers page when you click the Related Servers icon on various pages. You can use the display of related servers to diagnose and monitor misconfigured or unreachable servers.
Related Topics
Monitoring Remote Servers Using Persistent Events
DNS Zone Distribution Servers
DHCP Failover Servers
Monitoring Remote Servers Using Persistent Events
To service clients that require updates to DNS and LDAP related servers, the DHCP server uses a persistent event algorithm to ensure updates to related servers when a related server is temporarily unavailable. In addition, the algorithm prevents a misconfigured or offline DNS server from using up all the available update resources.
At startup, the DHCP server calculates the number of related servers in the configuration that require persistent events. A preconfigured Maximum Pending Events attribute (an Expert mode attribute that specifies the number of in-memory events that is preset to 40,000) is divided by the number of servers to obtain a limit on the number of events permitted for each remote server. This calculation covers related DNS and LDAP servers (DHCP failover does not use persistent storage for events). The DHCP server uses this calculation to issue log messages and take the action described in Table 7-6. The table shows a hypothetical case of a DHCP server with four related DNS servers each having a limit of 10K events.
SNMP traps and DHCP server log messages also provide notification that a related server is unreachable.
DNS Zone Distribution Servers
A DNS zone distribution simplifies creating multiple zones that share the same secondary server attributes. You can view and set the primary and secondary DNS servers in a zone distribution.
Local Basic or Advanced Web UI
From the Deploy > DNS menu, click Zone Distribution . This opens the List Zone Distributions page. The local cluster allows only one zone distribution, the default. Click this zone distribution name to open the Edit Zone Distribution page, which shows the authoritative and secondary servers in the zone distribution.
Regional Web UI
From the Deploy > DNS menu, choose Zone Distributions . This opens the List/Add Zone Distributions page. The regional cluster allows creating more than one zone distribution. Click the zone distribution name to open the Edit Zone Distribution page, which shows the primary, authoritative, and secondary servers in the zone distribution.
CLI Commands
Create a zone distribution using zone-dist name create primary-cluster , then view it using zone-dist list . For example:
DHCP Failover Servers
Related servers in a DHCP failover pair relationship can show the following information:
- Type —Main or backup DHCP server.
- Server name —DNS name of the server.
- IP address —Server IP address in dotted octet format.
- Requests —Number of outstanding requests, or two dashes if not applicable.
- Communication status —OK or INTERRUPTED.
- Cluster state —Failover state of this DHCP server.
- Partner state —Failover state of its partner server.
For details on DHCP failover implementation, see Chapter28, “Managing DHCP Failover”
Local Basic or Advanced Web UI
From the Deploy > DHCP menu, choose Failover Pairs . The List/Add DHCP Failover Pairs page shows the main and backup servers in the failover relationship.
CLI Commands
Use
dhcp
getRelatedServers
to display the connection status between the main and partner DHCP servers. If there are no related servers, the output is simply
100 Ok
.
Displaying Leases
After you create a scope, you can monitor lease activity and view lease attributes.
Local Basic or Advanced Web UI
From the Design > DHCPv4 menu, choose Scopes ; or from the Design > DHCPv6 menu, choose Prefixes (in Advanced mode). On the List/Add DHCP Scopes or List/Add DHCPv6 Prefixes page, click the View icon in the Leases column to open the List DHCP Leases for Scope or List DHCP Leases for Prefix page.
Regional Web UI
From the Operate > Reports > DHCPv4 menu or Operate > Reports > DHCPv6 menu, choose Lease History . Set the query parameters, then click Query Lease History . (See the “Querying Leases” section.)
Running Data Consistency Rules
Using consistency rules, you can check data inconsistencies such as overlapping address ranges and subnets. You can set data consistency rules at the regional and local clusters.
The table on the List Consistency Rules page explains these rules. Check the check box next to the rule that you want to run.
The List Consistency Rules page includes functions to select all rules and clear selections. You can show the details for each of the rule violations as well as view the output. The rule selections you make are persistent during your user session.
Local Basic or Advanced and Regional Web UI
To run consistency rules, do the following:
Step 1 From the Operate > Reports menu, choose Consistency Reports .
The List Consistency Rules page appears.
Step 2 Check the check boxes for each of the listed consistency rules that you want to apply.
The Consistency Rules Violations page appears.The rules are categorized by violation type.
Step 4 Click Return to return to the List Consistency Rules page.
CLI Tool
Use the cnr_rules consistency rules tool from the command line to check for database inconsistencies. You can also use this tool to capture the results of the rule in a text or XML file.
The cnr_rules tool is located at:
To run the cnr_rules tool, enter:
- –N username —Authenticates using the specified username.
- –P password —Authenticates using the specified password.
- options —Describes the qualifying options for the tool, as described in Table 7-7 . If you do not enter any options, the command usage appears.
Troubleshooting
The following sections describe troubleshooting the configuration and the DNS, and DHCP servers.
Related Topics
Immediate Troubleshooting Actions
Modifying the cnr.conf File
Troubleshooting Server Failures
Linux Troubleshooting Tools
Using the TAC Tool
Immediate Troubleshooting Actions
When facing a problem, it is crucial not to cause further harm while isolating and fixing the initial problem. Here are things to do (or avoid doing) in particular:
Modifying the cnr.conf File
Cisco Prime IP Express uses the cnr.conf file for basic configuration parameters. This file is normally located in the install-path /conf directory. Cisco Prime IP Express creates the file during installation and processes it line by line.
You can edit this file if configuration parameters change. Note that during normal operation, you would not want to change the values. However, certain conditions might require you to modify certain values, such as when you move the data files for disk space reasons.
The format of the cnr.conf file consists of parameter name-value pairs, one per line; for example, for a Windows local cluster installation:
Directory paths must be in the native syntax for the operating system. The format allows the use of colons (:) in directory paths, but not as name-value pair separators; it does not allow line continuation or embedded unicode characters. Other modifications to the file might include the location of the log directory (see the “Log Files” section) or the time cnr_shadow_backup backups should occur (see the “Setting Automatic Backup Time” section).
In rare cases, you might want to modify the file; for example, to exclude certain data from daily backups due to capacity issues. To do this, you need to add the appropriate settings manually.
Caution We recommend that you use the default settings in this file. If you must change these settings, do so only in consultation with the Cisco Technical Assistance Center (TAC) or the Cisco Prime IP Express development team.
The following settings are supported:
- cnr.backup-dest—Specify the destination to place backed up databases. Defaults to cnr.datadir if not specified.
- cnr.backup-dbs—Provide a comma-separated list of the databases you want to backup. For a local cluster the default is ccm,dhcp,dns,mcd. For a regional cluster it is ccm,lease6hist,leasehist,subnetutil,replica.
- cnr.backup-files—Provide a comma-separated list of files and the complete path to the files that you want copied as part of the backup. Files are copied to cnr.backup-dest.
- cnr.dbrecover-backup—Specify whether to run db recover and db verify on a backed up Oracle Berkeley database. The default is true. This setting is used for daily backups only. Manual backups ignore this setting. Disabling the automatic operation means that you must run the operation manually, preferably on a separate machine, or at a time when the Cisco Prime IP Express servers are relatively idle.
- cnr.daily-backup—Specify whether to run the daily back up. The default is true.
Troubleshooting Server Failures
The server agent processes (nwreglocal and nwregregion) normally detect server failures and restart the server. You can usually recover from the failure and the server is not likely to fail again immediately after restarting. On rare occasions, the source of the server failure prevents the server from successfully restarting, and the server fails again as soon as it restarts. In such instances, perform the following steps:
Step 1 If the server takes a significantly long time to restart, stop and restart the server agent. On:
Step 2 Keep a copy of all the log files. Log files are located in the install-path /logs directory on Linux, and the install-path \logs folder on Windows. The log files often contain useful information that can help isolate the cause of a server failure.
Step 3 Use the TAC tool, as described in the “Using the TAC Tool” section, or save the core or user.dmp file, if one exists, depending on the operating system:
Step 4 On Windows, use the native event logging application to save the System and Application event logs to files. You can do this from the Event Viewer. These event logs often contain data that helps debug Cisco Prime IP Express server problems. For a description of the log messages for each server module, see the install-path /docs/msgid/MessageIdIndex.html file.
Linux Troubleshooting Tools
You can also use the following commands on Linux system to troubleshoot Cisco Prime IP Express. To:
Using the TAC Tool
There may be times when any amount of troubleshooting steps will not resolve your problem and you have to resort to contacting the Cisco Technical Assistance Center (TAC) for help. Cisco Prime IP Express provides a tool so that you can easily assemble the server or system error information, and package this data for TAC support engineers. This eliminates having to manually assemble this information with TAC assistance. The resulting package from this tool provides the engineers enough data so that they can more quickly and easily diagnose the problem and provide a solution.
The cnr_tactool utility is available in the bin directory of the Windows, and usrbin directory of the UNIX or Linux, installation directories. Execute the cnr_tactool utility:
The output directory is optional and normally is the temp directory of the installation directories (in the /var path on Linux). If you do not supply the username and password on the command line, you are prompted for them:
The tool generates a packaged tar file whose name includes the date and version. The tar file contains all the diagnostic files.
Feedback