cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
7348
Views
5
Helpful
27
Replies

Ask the Expert:Cisco Service Control Solution

ciscomoderator
Community Manager
Community Manager

Read the bioWith Karthik Natarajan

Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions of expert Karthik Natarajan about how to troubleshoot various components of Cisco Server Control Solution products including Cisco SCE 2000 Series Service Control Engine, Cisco SCE 8000 Series Service Control Engine, Cisco Service Control Subscriber Manager (SCMS SM), Cisco Service Control Collection Manager (SCMS CM), Cisco Service Control Application for Broadband (SCA BB). Karthik Natarajan is a manager in the Edge Routing Business Unit. He works on worldwide escalations about Cisco Service Control Engine Solutions. Natarajan has been associated with Cisco for more than 11 years working in several engineering positions in NMS and LAN Switching Technologies. He holds a bachelor's degree in computer sciences and engineering from Bharath Institute of Technology at Chennai, India. He also holds CCNP certification.

Remember to use the rating system to let Karthik know if you have received an adequate response. 

Karthik might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Service Providers sub-community   discussion forum shortly after the event. This event lasts through February 10, 2012. Visit this forum often to view responses to your questions and the questions of other community members.

27 Replies 27

Hi Karthik,

What is the correct method of communication with TAC, how can we connect with TAC without opening a TAC case.

Thanks.

Hi Gurcan,

Opening service request is the way to reach TAC. Once the service request is raised, TAC engineer would perfom the investigation of the support file, and recommend on the diagnostics part, if required.

Cisco Technical Support site:

http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

-

Karthik N.

Hi Karthik,

I´m currently doing a lab tests of SCOS 3.7.2 and I´m seeing a issue when a want to see the reportes in SCABB.

The SCE8000 has a correct time configured and also the Collection Manager, but when we create a new report the Reporter shows a correct protocol classification but whith one hour of delay.

Best regards,

Jaime Soto.

Hi Jamie,

You had mentioned that the reports are one hour out of sync, so it looks like its related to daylight savings. In CM, you would have configured the SCE Offset. Check if the value is correct. The SCA Reporter does not use the correct time intervals unless the offset stored in the Collection Manager is consistent with the timezone of the SCE.

~scmscm/cm/bin/updatetimezone.sh --rdr

Refer to http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel37x/cmug/Managing_the_Collection_Manager.html#wp1074349

As you had checked the time in SCE and CM are in sync. Could you also check the following,

1) Check if the machine running SCA Reporter is as well in sync with the other two components.

2) In SCE, the commands to configure time and timezone are different, so double check once.

clock set (in priv exec mode): http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel37x/sce8000_cli_ref/CLI_Ref_1.html#wp1085017

clock timezone (in global config mode): http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel37x/sce8000_cli_ref/CLI_Ref_1.html#wp1086316

-

Karthik N.

Thanks Karthik,

The issue was the timezone in Collection Manager, now it is working well.

Regards,

Jaime.

Hi Karthik,

In our lab where we are testing SCOS 3.7.2 we are seeing a new issue. When SCE is reloaded it no longer sends RDRs to CM, even though from SCE the CM is UP.

For example before of reload:

SCE8000#>sh RDR-formatter

Status:  enabled

Connection is: up

Forwarding mode: simple-load-balancing

Connection Table:

------------------------------------------------------------------------------------------

| Collector       | Port  |Status| Priority per Category:                                |

| IP-Address  /   |       |      |-------------------------------------------------------|

| Host-Name       |       |      | Category1   | Category2   | Category3   | Category4   |

|-----------------|-------|------|-------------|-------------|-------------|-------------|

| 192.168.105.20  | 33000 | up   | 90  current | 90  current | 90  current | 90  current |

------------------------------------------------------------------------------------------

RDR:    queued:     0 ,sent:   104, thrown:     0, format-mismatch:     0

UM:     queued:     0 ,sent:     0, thrown:     0

Logger: queued:     0 ,sent:     0, thrown:     0

Errors: thrown:     0

Last time these counters were cleared: 17:23:40  CHI  WED  February  8  2012

SCE8000#>

and after of reload:

SCE8000#>sh RDR-formatter

Status:  enabled

Connection is: up

Forwarding mode: simple-load-balancing

Connection Table:

------------------------------------------------------------------------------------------

| Collector       | Port  |Status| Priority per Category:                                |

| IP-Address  /   |       |      |-------------------------------------------------------|

| Host-Name       |       |      | Category1   | Category2   | Category3   | Category4   |

|-----------------|-------|------|-------------|-------------|-------------|-------------|

| 192.168.105.20  | 33000 | up   | 90  current | 90  current | 90  current | 90  current |

------------------------------------------------------------------------------------------

RDR:    queued:     0 ,sent:     0, thrown:     0, format-mismatch:     0

UM:     queued:     0 ,sent:     0, thrown:     0

Logger: queued:     0 ,sent:     0, thrown:     0

Errors: thrown:     0

Last time these counters were cleared: 17:43:06  CHI  WED  February  8  2012

But, if we apply the service configuration from SCABB to SCE, this one send RDRs again. (This conclusion was after a many time of troubleshooting, reload SCE, delete rdr configuration and load again, stop and start CM service, etc)

SCE8000#>sh RDR-formatter

Status:  enabled

Connection is: up

Forwarding mode: simple-load-balancing

Connection Table:

------------------------------------------------------------------------------------------

| Collector       | Port  |Status| Priority per Category:                                |

| IP-Address  /   |       |      |-------------------------------------------------------|

| Host-Name       |       |      | Category1   | Category2   | Category3   | Category4   |

|-----------------|-------|------|-------------|-------------|-------------|-------------|

| 192.168.105.20  | 33000 | up   | 90  current | 90  current | 90  current | 90  current |

------------------------------------------------------------------------------------------

RDR:    queued:     0 ,sent:    76, thrown:     0, format-mismatch:     0

UM:     queued:     0 ,sent:     0, thrown:     0

Logger: queued:     0 ,sent:     0, thrown:     0

Errors: thrown:     0

Last time these counters were cleared: 17:43:06  CHI  WED  February  8  2012

Obviously this behavior isn´t normal, so I would like to know if you can help me. I checked this several times and always the only way to recover RDRs from SCE was the same.

SCE and CM are with 3.7.2 version.

Regards,

Jaime.

hi,

we hit the same thing like you, and we opened a case.

And this is confirmed as bug, the bug ID is CSCtx48102.

Hi Gurcan,

Thanks for sharing the defect ID.

Hi Jaime,

The issue you are facing is tracked by the defect mentioned. As a workaround we would suggest you to run the following command after any changes to the CLI or applying service configuration. This would retain the configuration even after reload.

SCE8000#>copy running-config-all startup-config-all

We are currently updating the defect with these details, and would be soon available on Cisco Bug Toolkit.

-

Karthik N.

Hi Karthik,

I applied that command always after I did a change and also before reload it but the issue still appears: After reload the SCE don't send RDRs to CM until I apply the service configuration in the SCABB again.

Regards,

Jaime.

Hi Jaime,

We had tested the workaorund before suggesting it. As 3.7.2 is recently released, it could be possible that we are missiing some scenario. This would require further troubleshooting. So, I would suggest you to open a service request, and we can take it forward.

-

Karthik N.

Thanks Karthik, I will open a service request.

Regards,

Jaime.

Pavel Dimow
Level 1
Level 1

Hi Karthik,

is there any other way to manage multiple configuration for multiple SCE beside SCA BB?

Thank you.

Hi Pavel,

Yes, we do have a API flavor for service configuration. You can refer to Programming Guide section under SCA BB.

http://www.cisco.com/en/US/products/ps6135/products_programming_reference_guides_list.html

For applying/retriving the service configuration to the SCE, we do support the servconf CLU.

http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel37x/scabbug/14_SCA_BB_UG.html#wp1044435

-

Karthik N.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: