CPS Troubleshooting Guide, Release 20.2.0 (4)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

CPS Troubleshooting Guide, Release 20.2.0 (4)

Chapter Title

Check Subscriber Access

Results

Updated:
August 27, 2020

Chapter: Check Subscriber Access

Check Subscriber Access

Checking Access

When you are confident that the installation and configuration tasks are complete and processing properly, try running a small amount of test traffic, following it through the system. Here are three ways to ascertain correct process of access from a subscriber perspective.

Testing Subscriber Access with 00.testAccessRequest.sh

00.testAccessRequest.sh is a test script used to test subscriber access to the ISG and CPS system.

You can find 00.testAccessRequest.sh in /opt/broadhop/installer/isg/troubleshooting directory on the CPS server.

To configure the subscriber used, edit the /opt/broadhop/installer/isg/troubleshooting/config.ini file.

Procedure

Step 1

In the config.ini file, change the User-Name and Password fields.

Note

 

You may need to change some of the other parameters in order to match your configuration. The other main attributes to change will be the NAS-IP-Address and Framed-IP-Address.

Step 2

Run the script from a command line. No arguments are necessary:

00.testAccessRequest.sh

Upon success, this output is displayed as follows:
Figure 1. 00.testAccessRequest.sh Output


Testing Subscriber Access with soapUI

This procedure tests end subscriber access to your system.

Procedure

Step 1

Download soapUI from here: http://www.soapui.org/

You only need the freeware version (not the soapUI Pro).

Step 2

Launch soapUI.

Step 3

Right click on Projects and select New soapUIProject from the drop-down list.

Step 4

Name your project and enter into Initial WSDL/WADL the appropriate WSDL URL (you may have to replace the IP in display with your own IP) and select OK.

Figure 2. New soapUIProject


Step 5

In the tree, select Demo > SubscriberBinding > GetSubscriber > Request 1 as shown in the following figure:

Figure 3. Request 1 Node


Step 6

Select edit current.. to edit the end point. Enter the appropriate IP.

Figure 4. Request 1 XML File


Step 7

In the XML file:

  • Replace ? in <typ:networkId>?</typ:networkId> with the appropriate credential or network ID.

  • Replace ? in <typ:returnSessions>?</typ:returnSessions> with True.

  • Replace ? in <typ:returnBalance>?</typ:returnBalance> with True.

Figure 5. Request 1 XML File


Step 8

Click the green arrow (underneath Request 1).

Figure 6. Request 1 XML File


Step 9

Check the resulting XML output. Pay special attention to the relevant subscriber information.

Figure 7. XML Output


Was this Document Helpful?

FeedbackFeedback

Contact Cisco