This chapter describes the tasks that you perform after installing Broadband Access Center (BAC):
•Enabling a Network Registrar Spoofing DNS Server
•Configuring the Syslog Utility to Receive Alerts from BAC
Enabling a Network Registrar Spoofing DNS Server
A spoofing DNS server redirects all DNS requests to the same IP address. You can enable spoofing to enforce a self-provisioning flow for a new subscriber.
For example, assume that a DNS host is dns.acme.com, and has an IP address of 10.10.10.5. Assume also that the Web server with the self-provisioning flow is 10.10.10.6.
On the DNS server, set the following parameters in Cisco Network Registrar:
nrcmd> zone . create primary dns.acme.com postmaster.dns.acme.com
nrcmd> zone . addrr * a 10.10.10.6
When DNS reloads, the changes take effect.
On the DHCP server, set the following parameters in Network Registrar:
nrcmd> policy unprovisioned setoption domain-name-servers 10.10.10.5
nrcmd> policy unprovisioned setoption domain-name acme.com
Configuring the Syslog Utility to Receive Alerts from BAC
You can configure the syslog file on any BAC component server to receive alerts and debugging information from the system.
Note Configuring the syslog file is an optional task.
BAC generates alerts through the Solaris syslog service. Syslog is a client-server protocol that manages the logging of information on UNIX. BAC syslog alerts are not a logging service; they notify that a problem exists, but do not necessarily define the specific cause of the problem. This information might reside in the appropriate BAC log files (rdu.log and dpe.log). If you choose to configure the syslog file, these alerts are directed to a separate log file.
For more information on error messages and alerts, refer to the Cisco Broadband Access Center Administrator Guide 2.7.1.
To configure the syslog utility on the Network Registrar extension points and the RDU server:
Step 1 Log in, as root, on the Network Registrar server.
Step 2 At the command line, create the log file.
Step 3 Open the /etc/syslog.conf file with a text editor, such as vi.
Step 4 Add this line to the /etc/syslog.conf file:
Note You must insert one or more tabs between the local6:info and /var/log/bpr.log information.
Step 5 Save and close the /etc/syslog.conf file.
Step 6 To force the syslog utility to accept the new configuration, enter:
root 217 1 0 Nov 26 ? 0:00 /usr/sbin/syslogd
Note The process ID (PID) in this example is 217, but may change when you run ps -ef | grep syslogd. Use the correct output from that command as the input to kill -HUP.
Syslog is now ready to receive alerts from BAC.