Cisco Headend System Release 2.7 Installation Guide

Page of 158
 
 
 
Post-Upgrade Procedures for the loadPIMS and BOSS Web Services 
 
4035749 Rev B 
143 
 
147.191.126.37
 
147.191.126.38
 
147.191.126.39
 
24.40.12.107
 
24.40.12.108
 
24.40.12.52
 
24.40.13.104
 
24.40.13.105
 
With these new directives, we are allowing requests from 65,788 hosts. The 
24.40.0.0/16
 directive allows 65,534 hosts (24.40.0.1 - 24.40.255.254) and the 
147.191.126.0/24
 directive allows 254 additional hosts (147.191.126.1 - 
147.191.126.254). 
 
Configure Apache to Listen for Web Service Requests 
Determine the Hostname(s) of Network Interfaces to Receive Web Service Requests from PIMS 
Servers 
Chose one server IP address in each unique network identified in the allow 
directives previously recorded. Complete the following procedure for each server IP 
address in order to determine the DNCS network interface on which Web service 
requests will be received. 
1  Type the following command and press Enter.  
Note:  We will use IP address 24.40.13.104 in this example. 
traceroute 24.40.13.104
    
Result:  Output similar to the following should appear. 
traceroute: Warning: Multiple interfaces found; using 192.168.2.1 @ ce1
 
traceroute to 24.40.13.104 (24.40.13.104), 30 hops max, 40 byte packets
 
 1  cisco (192.168.2.254)  0.522 ms  0.286 ms  0.252 ms
 
Example:  In this sample output, ce1 represents the network interface; its IP 
address is 192.168.2.1
Important:  It is possible that servers in different networks will make requests to 
different DNCS interfaces. Contact your Network Administrator if you are not 
sure of the interface on which traffic from the PIMS servers will be received. 
2  Examine the /etc/hostname.[interface] file that corresponds to the network 
interface identified in step 1. 
cat /etc/hostname.ce1
 
Example:  
dncseth netmask 255.255.255.0 broadcast +
 
Note: The first column of the output represents the hostname of the network 
interface. In this example, the hostname is dncseth