Start a conversation

Error: IP Null When CPE Connects with Front End Server

Article Original Creation Date: 2015-03-12

Overview

Each time the Customer Premise Equipment (CPE) contacts the Front-end Server, Java errors mentioned, are raised:

2015-03-06 09:35:57,078 [62.167.34.8] INFO ACS - IP: null, CPE: c0b05c26c4e733c28ed2ea23bdace144, Received: Inform , Event: 0 BOOTSTRAP
2015-03-06 09:35:57,357 [62.167.34.8] ERROR ACS - Unexpected error occurred java.lang.IllegalArgumentException: Invalid IP address java.lang.IllegalArgumentException: Invalid IP address

Environment

  • Solaris 10
  • Oracle 10g
  • jboss4.0.4.GA
  • Apache-5.5.25

Root Cause

The root cause of the failure is the Auto-Configuration Server (ACS) does not have the IP-Address of Customer Premise Equipment (CPE), as the DeviceIPAddressSource is not using the Connection Request URL.

Resolution

To solve the issue mentioned previously, On the front_end within the tomcat service folders, a setting in ACS.properties called DeviceAddressSource needs an extra search string.

To update the settings, replace the following string:

DeviceIPAddressSource=EXTERNAL_IP_ADDRESS

in ACS.properties files for both ACS-server and ACS-API, with:

DeviceIPAddressSource=EXTERNAL_IP_ADDRESS,CONNECTION_REQUEST_URL

To update the settings, follow the steps mentioned below:

  1. Modify the ACS.properties file on ACS-server:

    1. Navigate to the folder:

      tomcat_home_dir/webapps-acs/ACS-server/
    2. Copy ACS.properties to ACS.properties.<timestamp>-acs using the below command:

      cp ACS.properties ACS.properties.<timestamp>-acs
    3. Edit ACS.properties file using the vi editor (or any other preferred editor):

      vi ACS.properties
    4. Replace

      DeviceIPAddressSource=EXTERNAL_IP_ADDRESS 

      with

      DeviceIPAddressSource=EXTERNAL_IP_ADDRESS,CONNECTION_REQUEST_URL
    5. Save the file.

    6. Move ACS.properties.<timestamp>-acs using the following command:

      mv ACS.properties.<timestamp>-acs /<home_dir>
  2. Modify the ACS.properties file in ACS-api:

    1. Navigate to the folder:

      tomcat_home_dir/webapps-api/ACS-api/
    2. Copy ACS.properties to ACS.properties.<timestamp>-acs using the below command:

      cp ACS.properties ACS.properties.<timestamp>-acs
    3. Edit ACS.properties file using the vi editor (or any other preferred editor):

      vi ACS.properties
    4. Replace

      DeviceIPAddressSource=EXTERNAL_IP_ADDRESS 

      with

      DeviceIPAddressSource=EXTERNAL_IP_ADDRESS,CONNECTION_REQUEST_URL
    5. Save the file.

    6. Move ACS.properties.<timestamp>-acs using the following command

      mv ACS.properties.<timestamp>-acs /<home_dir>
  3. Rebuild both ACS-server.war and ACS-api.war with the updated ACS.properties files:

    1. Navigate to the folder:

      tomcat_home_dir/webapps-api/ACS-server/
    2. Create the war file with updated properties using the command below:

      jar uf ../ACS-api.war ACS.properties
    3. Navigate to the folder:

      tomcat_home_dir/webapps-api/ACS-api/
    4. Create the war file with updated properties using the command below:

      jar uf ../ACS-api.war ACS.properties
  4. Restart Tomcat Service.

Confirmation

After implementing the steps detailed previously and restarting the Tomcat Service, CPE connects with the front end, without raising any error.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments