6.1 Configurations

New Setup Configuration

Install and configure the ENUM application as mentioned in the following steps:

1. Configure the vENUM setup with ONE PUSH using the vENUM heat template. To refer a sample HEAT template, download ENUM Heat Template.zip file from OHC.

   Note:

   Below is a sample heat template.

   Table 6-1 vENUM MP VM profile

   Name	vCPUs	RAM (GB)	Disk Size (GB)
   vENUM MP	8	8	150

2. Create Server group with Function id STPENUM and add ENUM MPs (according to Requirement) under this Server Group for ENUM feature.

   ENUM tables needs to be configured further, the MO operations supported for this feature are:

   • ENUM ACLs
   • ENUM Options
   • DNS Connection
   • DNS Zone Config
   • DNS Record
   • DNS Server Options
3. Configure the ENUM application using MMI API or ENUM GUI.

Upgrading Existing setup

To upgrade an existing vSTP setup (without ENUM MPs), perform the following steps:

1. Create new ENUM MP(s) instance.
2. Create Server group with Function ID STPENUM at C level on Active NOAM.
3. Add the newly created MPs under the Server Group created in the above step.

Restricted IPs

The set of IPs that are restricted to be used or configured are listed in the below table.

Table 6-2 Restricted IPs

IP	Description
0.0.0.0/8	Broadcast messages to this network, RFC 1700
127.0.0.0/8	Used for loopback addresses to the local host
169.254.0.0/16	Link local, reserved by operating systems for APIPA
192.0.2.0/24	"TEST-NET" for documentation and example source code
192.88.99.0/24	Used by 6to4 anycast relays as specified by RFC 3068
198.18.0.0/15	Testing of inter-network communications, RFC 2544
198.51.100.0/24	"TEST-NET-2" for documentation and example source code
203.0.113.0/24	"TEST-NET-3" for documentation and example source code
224.0.0.0/4	Reserved for multicast assignments as specified in RFC 3171
240.0.0.0/4	255.255.255.255 is limited broadcast, others are reserved by the IANA