Cisco Service Control Management Suite Subscriber Manager User Guide, Release 4.2.x

SM Not Running

SM in Failure Mode

Cisco Service Control Subscriber Manager Uninstallation Fails

General

1. EM Agent Started. Version: {Version number}

2. EM Agent shutdown

3. Running {operational name} operation due to management link failure

4. Failure in setting up SM database : {exception message and class name}

5. Creating support file { the name of the support file }

6. Restarting EM Agent in {number of seconds} seconds.

7. Detected LEG {leg name} connection failure.

8. The database is full

HTML Adaptor

1. HTML adaptor server started on port {port}

2. Unable to start HTML adaptor server on port {port}

3. HTML adaptor server stopped

4. HTML adaptor server port changed from{old port} to {new port }

FTP Server

1. FTP server started on port {port number}. Passive ports are: {first passive port - last passive port}.

2. Unable to start FTP server on port {error message exception}

3. FTP server stopped.

4. FTP server port changed from{old port} to {new port}

5. FTP server passive ports changed from{old first port - old last port} to {new first port- new last port}

Domain Messages

1. Domain {domain name} added

2. Errors occurred while adding network elements {elements logical names} to domain {domain name}

3. Domain {domain name} removed.

4. All of the domains were removed.

5. All of the elements were removed from domain {domain name}

6. Elements {logical names of elements (one or more)} were removed from domain {domain name}

7. Domain {domain name} was moved to {target domain}

8. Domain {old name} was renamed to {new name}.

9. Domains were reset back to defaults.

10. All SM domains reset to defaults

11. Domain {domain name} was cleared from subscribers.

SCE Messages

1. Network element {logical name-super user-description} at host {host} added.

2. Connection to {logical name} is ready.

3. Connection to {logical name} is lost, trying to establish connection...

4. Connection to {logical name} lost.

5. Network element {logical name} reset back to defaults.

6. All network elements were reset back to defaults.

7. All network elements were removed.

8. Network element {logical name} was removed.

9. All network elements were removed

10. Network element {logical name} was removed.

11. SCE {logical name} has been put in quarantine for the next {quarantine time} seconds - {quarantine reason}

12. Quarantine of SCE {logical name} ended

13. Quarantine of SCE {logical name} was stopped by the user

14. Post-quarantine timeout has expired for SCE { logical name}

Subscriber Manager-SCE Synchronization Messages

1. Started SM synchronization of {SE logical name} in {domain name} domain

2. Started SM pull-mode synchronization of {SE logical name} in {domain name} domain

3. Finished SM synchronization of {SE logical} in {domain name} domain ({logins} subscribers

4. Finished SM pull-mode synchronization of {SE logical} in {domain name} domain.

5. Aborted SM synchronization of {SE logical name} in {domain name} domain

6. {subscriber/VPN name} - operation failure {description} on {SE logical name} domain{domain}

7. Started SM VPN synchronization of {logical name} in {domain name} domain.

8. Finished SM VPN synchronization of {logical name} in {domain name} domain ({successful logins} VPNs, {failed logins} failures).

9. Aborted SM VPN synchronization of {logical name} in {domain name} domain.

Auto-Logout Messages

1. Starting task of logging out expired subscribers

2. Finished task of logging out expired subscribers. Task ran for {number of seconds task ran} seconds. Logged out {number of subscriber logged out} IP mappings

3. Finished task of logging out expired subscribers. Task ran for {number of seconds task ran} seconds. Sent {number of subscriber sent to external pull } IP mappings to external MBean

Inactive Subscribers Removal Messages

1. Removed subscriber {subscriber ID} due to inactivity

PRPC Messages

1. PRPC connection to {Peer inet address} established, client name is {client name}, session name is {session encoding}

2. PRPC connection to {peer inet address} closed ok: {message}

3. PRPC connection to {peer inet address} closed BAD: {message}

4. PRPC server started on port {port}

5. PRPC server port changed from {old port} to {new port}

6. PRPC server stopped.

Subscriber Messages

1. Removing all subscribers from SM

2. VLAN {removed VLAN} was removed from {logged out subscriber} due to conflict with VLAN {removed} of {logged in subscriber} on domain {domain}.

3. IP mapping {removed IP range} was removed from {logged out subscriber} due to conflict with {gained IP range} of {logged in subscriber} on domain {domain}.

4. {subscriber name} - Operation failure {description} on {SE logical name} (domain: {domain}).

5. Clearing subscribers mapping in domain {domain name}, due to LEG {leg name} connection failure.

6. Failed {import\export operation name}: {error string}

7. Could not find configuration file { import\export file name}

8. Reloading configuration

9. Getting all subscriber names to file {file name}

10. Importing subscribers from file {file name}

11. Exporting subscribers to file {file name}

12. Adding subscriber {Subscriber name}

13. Removing subscriber {Subscriber name}

14. Showing subscriber by name {Subscriber name}

15. Showing subscriber by ip-range {Subscriber name}

16. Showing subscriber by VLAN {Subscriber name}

17. Setting domain of subscribers {Subscriber name} to {domain name}

18. Setting mapping of {subscriber name} to {mapping}

19. Getting mapping of {subscriber name}

20. Clearing mapping of {subscriber name}

21. Setting property {property name + value} of {subscriber name} to {property name + value}

22. Getting property {property name} of {subscriber name}

23. Setting properties of {Subscriber name}

24. Getting properties of {Subscriber name}

25. Clearing all subscribers.

26. Getting the number of subscribers.

27. Login: {login info}

28. Introduce: {subscriber info}

29. Unintroduce: {subscriber name} from domain {domain name}

30. Logout: {Subscriber info}

31. Logout by IP: {Subscriber IP}

32. Logout by VLAN: {Subscriber VLAN}

33. Remove: {Subscriber name}

34. Put: {Subscriber info}

35. Rename: {Subscriber name} to {Subscriber name}

36. Add IP: added IP {IP address} to {Subscriber name}

37. Add VLAN: added VLAN {VLAN ID} to {Subscriber name}

38. Extended the lease of IP {IP address} to {date}}

39. Pull response for {Subscriber name}: pulled IP: {IP mapping}, returned IP {IP mapping}

Cable-Related Messages

1. Importing cable modems from file {filename}

2. Exporting cable modems to file {filename}

3. Cleared all cable modems

4. Reload configuration called.

High-Availability Messages

1. The agent’s Operational state has changed to failure.

2. The Agent’s Operational state has changed to fatal. {Operation performed : restart or shutdown}

3. Agent {agent name}: {operation fail message}. details: {error details}

4. Agent {agent name} timeout expired during operation {operation}.Agent {agent name} failed while performing {operation}. details: {error details}

5. SM operational state switched from {mode} to {mode}

Configuration File Messages

1. Loaded p3sm.cfg configuration file

2. Warning : {Warning name}

3. Unknown property {property name} found in section [{section name}] in configuration file {configuration filename}.

4. Unknown section [{section name}] found in configuration file {configuration filename}.

5. Error value {property value} for property {property name} in section [{section name}]. Optional values: [{allowed values}]

6. Property key {property name} does not match expected type in section [{section name}].

7. Missing mandatory property {property name} in section [{section name}].

8. Error value {property value} for property {property name} in [{section name}] section. Valid format: [0..255].[0..255].[0..255].[0..255]

9. Error empty value for { property name} property in [{section name}] section - must have at least one character

10. Configuration file loading failed due to { num of errors} errors {num of warnings } warnings

11. Configuration file loaded successfully - {warning message}

Quota Manager Messages

1. Got quota notification {quota notification name} for subscriber {subscriber ID}

2. Subscriber {Subscriber ID} has more quota in SCE than expected (bucket ID= {bucket ID}, last quota= {last quota}, current quota= {current quota}). Possible causes: Another server provisions quota to this subscriber, QM restart

3. Quota profile ID { quota profile ID } does not exist in configuration - Ignoring quota notification {quota notification name } for subscriber {subscriber ID}

4. Subscriber {subscriber ID} was moved from SCE {old SCE IP} to SCE {new SCE IP}

5. Got quota notification {quota notification name} at {provision time} for subscriber {subscriber ID} that is too adjacent to last provision time ({last provision time })

6. Subscriber {subscriber ID} changed quota profile from {old quota profile ID} to {new quota profile ID} - Quota is replenished (with or without reset history)

7. Subscriber {subscriber ID} changed quota profile from {old quota profile ID} to {new quota profile ID}. Number of configured buckets is not equal between profiles. Therefore - replenish quota

8. Subscriber {subscriber ID} changed quota profile from {old quota profile ID} to {new quota profile ID}. Slice periods are not equal between profiles. Therefore - replenish quota

9. Quota profile {quota profile ID} configuration was changed - Quota is replenished for subscriber {subscriber ID}

10. New aggregation period started for subscriber {subscriber ID} - Quota is replenished

11. Calling quota update for subscriber {subscriber ID}: {quota operation}

12. Quota Update operation for subscriber {subscriber ID} failed, error message = {error message}

13. Get Quota Status operation for subscriber {subscriber ID} succeeded

14. Get Quota Status operation for subscriber {subscriber ID} failed, error message = {error message}

15. Subscriber {subscriber ID} has negative quota in SCE (bucket ID={ bucket ID}, last quota={last quota}, current quota={current quota}).

16. Quota bucket { subscriber ID} has depleted for subscriber {bucket ID} till {end of aggregation period}

17. Quota bucket { bucket ID } has depleted for subscriber {subscriber ID}

18. Cannot update quota bucket {bucket ID} for subscriber {subscriber ID} due to large update value {update value} - setting the dosage value instead

19. Identified breach of bucket {bucket ID} for subscriber {subscriber ID} - moving the subscriber to {penalty profile} profile for {penalty period} minutes period.

20. Subscriber {subscriber ID} usage was lower than {post penalty threshold} - going to move the subscriber to quota profile {profile ID}

21. Identify breach within bucket {bucket ID} for subscriber {subscriber ID} while moving to penalty profile {penalty profile}. Remaining quota is {remaining quota}.

22. Ignoring the bucket id {bucketId} values reported : {sceRemainingQuotaReported} as part of Quota Status rdr since last quota provisioning is close.

This message is triggered instead of the message “Got quota notification {quota notification name} at {provision time} for subscriber {subscriber ID} that is too adjacent to last provision time ({last provision time })” if the handle_multi_bucket_in_grace_period tunable is enabled

23. Subscriber: {subscriberID} reported unexpected quota: {sceRemainingQuotaReported} without quota update in SCE for bucket id:{bucketId}

This message is triggered if a quota RDR reports a positive value as the remaining quota even before the quota update reaches the Cisco SCE.

24. Notification recieved from a Cisco SCE that belongs to a different domain, quota will be replenished.

25. Ignoring the additional quota update with threshold rdr: {updateValue}

This messages is triggered typically on receiving a threshold RDR from the Cisco SCE for the last dosage. If the remaining quota in Cisco Service Control Quota Manager is less than the dosage, additional quota update is ignored and the above message is triggered.

RDR Formatter Messages

1. Quota RDR server started on port {server Port}

This message is displayed when the quota RDR server becomes active.

2. Quota RDR Client {SCE IP} connection is created.

This message is displayed when a Cisco SCE connects to the quota RDR server.

3. Client {SCE IP} has closed the socket connection

This message is displayed when a Cisco SCE closes the socket connection.

4. Not processing quota indication because redundancy mode is not Active or no PRPC connection to SCE
SCE :: {SCE IP} quota RDR processing is stopped.

This message is displayed when an RDRis received from the standby machine or the PRPC connection between Cisco Service Control Subscriber Manager and Cisco SCE is lost.

5. Can not create new client connection, exceeded maximum limit: {maxConections}

This message is displayed when the total number of Cisco SCE RDR clients connected to the quota RDR server exceeds the maximum number of connections.

6. Cannot accept SCE RDR Connection {sceIP} as there is no QM PRPC connection.

This message is displayed when the PRPC connection between Cisco Service Control Subscriber Manager and Cisco SCE is not established and the RDR connection from Cisco SCE is ignored.

7. Quota rdr queue is over threshold so dropping non priority rdr's, total dropped rdr's: {rdrStats.countDropped()}

This messages is displayed when the quota RDR queue crosses the threshold and hence the status and threshold RDRs are dropped.

8. Quota rdr queue is full, total dropped rdr's: {rdrStats.countDropped()}

This message is displayed when the quota RDR queue is full and hence the quota RDRs are dropped.

Lease Query LEG Messages

1. Lease-Query LEG: Session {session Id}: sending query of IP {queried IP} to the DHCP server ({DHCP server IP})

2. Lease-Query LEG: Session {session Id}: queried IP ({queried IP}) and CIADDR ({CIADDR field}) do not match, reply is discarded

3. Lease-Query LEG: Session {session Id}: the lease is not active for IP {queried IP}

4. Lease-Query LEG: Session {session Id}: Lease reply received for IP {queried IP}, but there is no session in the repository - maybe the session has expired

5. Lease-Query LEG: Session {session Id}: no modem MAC address (option 82) was provided for IP {queried IP}, reply is discarded

6. Lease-Query LEG: Session {session Id}: successful query, subscriber info: {subscriber Info}

7. Lease-Query LEG: Session {session Id}: subscriber properties customization failed. DHCP info: {DHCP packet info}

8. Lease-Query LEG: Session {session Id}: query of IP {queried IP} to the DHCP server ({DHCP server IP}) has timed-out, releasing session

9. Lease-Query LEG: Server {DHCP server IP} failure detected, but there is no redundant server to switch to

10. Lease-Query LEG: Server {failed DHCP server IP} failure detected, failing-over to {1}

11. Lease-Query LEG: LEG initialization failure: {message}

12. Failed to assign default package to {subscriber ID} (package ID {package ID}).

13. Assigned a default package to {subscriber ID} (package ID {package ID}).

14. No package ID was found for {subscriber ID} under the package-name of {package ID}

15. Failed to assign a package to {subscriber ID} (package ID {package ID}).

16. Assigned a package to {subscriber ID} (package ID {package ID}).

17. Successfully logged CPE: subscriber name {subscriber ID}, mapping {IP}, lease time {lease-time}

18. Successfully logged CM: subscriber name {subscriber ID}

19. Successfully logged out CPE: mapping {logged out IP address}

20. Failed to login CPE: subscriber name {subscriber ID}, mapping {IP} ({exception name })

21. Failed to login CM: subscriber name {subscriber ID} ({exception name})

22. Failed to logout CPE: mapping {logged out IP address} ({exception name })

23. Dropped RDR due to missing option 51. Assigned IP {Assigned IP}

24. Dropped RDR due to missing option 82. Assigned IP {Assigned IP}

25. Dropped RDR due to missing package information for subscriber { subscriber ID} (no default package is configured)

SOAP LEG Messages

1. SOAP-LEG query operation for : {subscriber ID}

2. SOAP-LEG query failed for : {subscriber ID}

3. SOAP-LEG query success for : {subscriber ID}

4. SOAP-LEG convert fail for : {subscriber ID}

5. SOAP-LEG login operation for : {subscriber ID}

6. SOAP-LEG login operation failed for {subscriber ID} : {error description}

VLM Messages

For VLM messages please refer to the Cisco Service Control for Managing Remote Cable MSO Links Solution Guide - Userlog Messages section.

RADIUS Listener LEG Messages

7. Login of subscriber {subscriber name} failed, {error message}

8. Logout of subscriber {subscriber name} failed, {error message}

9. Login of subscriber {subscriber name} failed, cannot translate attribute value {attribute value} to property {property name}. Check mapping table configuration.

10. Missing data to login {subscriber name} - ignoring. NAS {NAS}

11. Accounting-Stop received from NAS {NAS} with no subscriber-Id attribute and no Network-Id

12. Accounting-{Start/Interim} received from NAS {NAS} with no subscriber-Id attribute and no Network-Id

13. Invalid Framed-IP-Address attribute received - {error description}

14. Invalid attribute {attribute} received: {attribute data}

15. Invalid attribute {attribute} received: {attribute data} - {error description}

16. Invalid Framed-IP-Address attribute received: {attribute data}

17. Invalid IP Address, IP address {attribute} is reserved by the application.

18. Invalid VPN attribute {attribute} received: {attribute data}

BGP LEG Messages

19. Received an Add-Route message from BGP LEG for a known VPN {VPN: PE@RD} with IP range {bgpRange} and MPLS tag {label}

20. Received a Remove-Route message from BGP LEG for an existing route with IP range {bgpRange} and MPLS tag {label} for VPN {VPN: PE@RD}

21. Database format is not compatible with MPLS/VPN mappings, see release notes to fix that

Cannot Run this Script–/etc/motd File Exists

install-sm.sh Script–User is not Root

install-sm.sh Script–User pcube Exists

Introduction

The Subscriber Manager database configuration consists of several configuration files. This section explains the purpose and scope of each of these files. When troubleshooting the Subscriber Manager database, you will be requested to edit these configuration files and reboot the machine or restart the Subscriber Manager. In most cases, the defaults applied by the Subscriber Manager installation procedure are satisfactory.

• System (Kernel) Configuration File
• Subscriber Manager Database Configuration File sys.odbc.ini
• Configuration File ~pcube/.odbc.ini

System (Kernel) Configuration File

The kernel configuration file is a system configuration file, which affects systemwide configuration parameters:

• For RedHat, it is the file /etc/sysctl.conf .

The Subscriber Manager installation procedure configures this file to add extra semaphores and shared memory to the system. After editing this file, you must reboot the machine for the changes to take effect.

Subscriber Manager Database Configuration File sys.odbc.ini

The file sys.odbc.ini is a Subscriber Manager database configuration file that configures system DSNs. Any user on the machine on which the system DSN is defined can use this file. The Subscriber Manager DSNs are system DSNs that are named PCube_SM_Repository and PCube_SM_Local_Repository , and have the following system DSN configuration parameters:

• LogFileSize—The size of the Subscriber Manager database log file, in megabytes.
• PermSize—The size of the permanent memory region for the data store, in megabytes. You may increase PermSize but not decrease it.

The data stored in the permanent memory region includes tables and indexes that make up a Subscriber Manager database data store. The permanent data partition is written to the disk periodically.

• TempSize—The size of the memory allocated to the temporary region, in megabytes.

Temporary data includes locks, cursors, compiled commands, and other structures needed for command execution and query evaluation. The temporary data partition is created when a data store is loaded into memory and is destroyed when the data store is unloaded.

NoteFor additional information, seeTable 4-6 (Memory Configuration Parameters Versus Number of Subscribers—without Quota Manager) or Table 4-9 (Memory Configuration Parameters Versus Number of Subscribers—with Quota Manager).

• SMPOptLevel—Optimizes the database operation on multi-processor machines. If the machine is a multi-processor platform, set parameter SMPOptLevel to 1 (default is 0).

Use the sm-db-conf.sh script to configure the parameters (PermSize,TempSize, LogFileSize and SMPOptLevel) in sys.odbc.ini. The sm-db-conf.sh script is in the Subscriber Manager installation package.

Configuration File ~pcube/.odbc.ini

The file ~pcube/.odbc.ini is a Subscriber Manager database configuration file that configures user DSNs.

Subscriber Manager Database DSN Configuration—Cannot Find Requested DSN

Subscriber Manager Database DSN Configuration—Data Source Name Not Found

Subscriber Manager Database Settings—Cannot Connect to Data Source

Subscriber Manager Database Configuration Error—Not Enough Memory

Subscriber Manager Database Configuration Error—Incorrect Memory Definitions

Subscriber Manager Database Configuration Error—Cannot Create Semaphores

Subscriber Manager Database Configuration Error—Cannot Read Data Store File

Subscriber Manager Database Configuration Error—Data Store Space Exhausted

Subscriber Manager Database Error on Uninstall—Failed to Uninstall SM Database

First Connection—Operation Timed Out

Status Error—Connection Down

Status Error—Subscriber Management Down

Resync Timeout Error

CSV File Validation Error

Clear-all Error in Cluster Mode

Subscriber Database is Not Replicated on Standby Server

CSV File Import Error

Network Management Errors

Domain Errors

PRPC Errors

RADIUS Listener Errors

Common Validation Errors

The following configuration errors are relevant for all sections/parameters of the p3sm.cfg file.

RDR Formatter Errors