app_cnr

Table Of Contents

CNS Network Registrar Configuration

Setting Up CNS Network Registrar

Cisco Broadband Access Center ipservice.cfg Variables

Network Registrar resourceMgr.cfg Variables

Configuring Cisco Network Registrar

CNS Network Registrar Configuration

---

TBD: REVIEWERS: Are the directories, pathnames, and procedures changed for the 2.5 release? If so, please mark up these pages with revisions.

This appendix provides information about what you need to do in to use the Cisco Networking Services Network Registrar (CNS Network Registrar) product in conjunction with Cisco Broadband Access Center (BAC). CNS Network Registrar includes two servers that provide distinct services. The first is to set up scopes with designated IP addresses and subnet mask in the Dynamic Host Configuration Protocol (DHCP) servers. The second is to add and delete the mapping of IP addresses and fully qualified domain names (FQDNs) to the Domain Name Service (DNS) server.

---

Note Use of the CNS Network Registrar features with Cisco BAC is optional. Therefore, if you are not in need of the CNS Network Registrar functionality, the information in this appendix can be used for informational purposes.

---

Setting Up CNS Network Registrar

---

Note The Network Registrar software is not included with the Cisco Broadband Access Center software. You must purchase the Network Registrar software and license separately. The Network Registrar software must be installed on a separate machine from where the Cisco Broadband Access Center Server and the Oracle Database are installed.

---

The Network Registrar software should be up and running before you start the Cisco Broadband Access Center software, and you should know your DNS server and your scope of IP addresses because you must verify this information during the Cisco Broadband Access Center software installation process. You do this by confirming your desire to edit, using a vi editor, the $CCNSC_HOME/resourceMgr/common/ipservice.cfg and $CCNSC_HOME/resourceMgr/common/resourceMgr.cfg files. If you do not have this information before you start the installation process, click Cancel when the Updating window appears. See the Cisco Network Registrar documentation for detailed information.

Although you are not required to update the above files before Cisco Broadband Access Center installation, it is recommended that you do, because if updates to the above files are necessary, they must be updated before you start the Cisco Broadband Access Center servers.

See "Cisco Broadband Access Center ipservice.cfg Variables" section for an example of the ipservice.cfg file variables that are associated with Network Registrar and Cisco BAC. See "Network Registrar resourceMgr.cfg Variables" section for an example of the resourceMgr.cfg file variables that are associated with Network Registrar and Cisco BAC.

Cisco Broadband Access Center ipservice.cfg Variables

Following is a sample $CCNSC_HOME/resourceMgr/common/ ipservice.cfg file showing the variables that are associated with Network Registrar and Cisco BAC.

DB_HOST=cem-e250-7

DB_PORT=1521

DB_SID=CCNSC

DB_USER_ID=ccnsc

DB_PASSWD=ccnsc

Network Registrar resourceMgr.cfg Variables

Following is a sample $CCNSC_HOME/resourceMgr/common/ resourceMgr.cfg file that shows the Network Registrar scope range of signal and bearer channel variables that are associated with Network Registrar and Cisco BAC.

#Lay out of this config file:

#     Region

#          Group

DNS_HOST=cem-u5-2.devtest.cisco.com

[begin devtest-scope]

     USE_DHCP=yes

     CNR_HOST=cem-u5-2.devtest.cisco.com

     CNR_USER=admin

     CNR_PASSWD=<changeme>

     CNR_CLIENT_PATH=/opt/CSCOcnscs/bin

          [begin signal_B]

               FROM_ADDR=172.1.4.0

               TO_ADDR=172.1.4.1

               SUBNET_MASK=255.255.255.0

          [end signal_B]

          [begin signal_A]

               FROM_ADDR=172.1.3.0

               TO_ADDR=172.1.3.1

               SUBNET_MASK=255.255.255.0

          [end signal_A]

[end devtest-scope]

Configuring Cisco Network Registrar

The Cisco Broadband Access Center software handles assignment and reservation of IP addresses for the signaling and bearer channels. It also updates the IP to hostname mapping in DNS for the signaling channel and checks the forward and reverse zone. To allow these operations to function properly, Cisco Network Registrar must be configured as described below.

Procedure

---

Step 1 From the command line, configure DHCP so that the signaling and bearer channels reside in different subnetworks.

The following is an example:

Scope signal_A 172.1.3.0 255.255.255.0

Scope signal_A addRange 172.1.3.1 255.255.255.0

Scope signal_B 172.1.4.0 255.255.255.0

Scope signal_B addRange 172.1.4.1 255.255.255.0

Once you complete the entire configuration, reload DHCP.

Step 2 Configure DNS so the Cisco Broadband Access Center software can update the IP to hostname mapping in DNS for the signaling channel.

a. Configure a zone (domain name) for the subnetwork, for example, cisco.com.

You can divide the domain into subzones if needed, for example, sanjose.cisco.com, sanfrancisco.cisco.com, ny.cisco.com, and so forth. You must provide this domain name or subdomain name when you create a subnetwork or DSL complex through the Cisco Broadband Access Center GUI.

b. Define an authority server and name server for each zone (domain).

Typically, these servers are the same as your DNS host.

c. For each zone and reverse zone, select DNS > DHCP > Enable dynamic DNS updates at the Network Registrar GUI and provide the IP address of the host where the Cisco BAC Provisioning Service component is located.

This allows the Provision Service server to update DNS.

Step 3 Once the DHCP is configured, provide the $CCNSC_HOME/resourceMgr/common/ipservice.cfg file with the same information you have configured.

---