SCE RDR

Hi All,

The RDR lenghts would vary but you can take a look at this link to confirm the size of each field.
http://www.cisco.com/en/US/products/ps6135/products_technical_reference_chapter09186a00808484a7.html
You will see lengths as :
INT32 : 32 bit integer
INT16 : 16 bit integer
STRING : Variable string length ( I believe it is 256 characters)
Basically they are the same types as you would find in a database.
Hope this helps.
Shelley.

Similar Messages

  • Cisco SCE - RDR length

    We need to estimate the length (bytes) of RDRs generated by SCE.
    In particular we are interested in the following RDR types:
    - HTTP Transaction Usage RDR
    - Transaction Usage RDR
    - Subscriber Usage RDR
    Any suggestion is appreciated.
    Thanks,
    Marco and Fabrizio

    The RDR lenghts would vary but you can take a look at this link to confirm the size of each field.
    http://www.cisco.com/en/US/products/ps6135/products_technical_reference_chapter09186a00808484a7.html
    You will see lengths as :
    INT32 : 32 bit integer
    INT16 : 16 bit integer
    STRING : Variable string length ( I believe it is 256 characters)
    Basically they are the same types as you would find in a database.
    Hope this helps.
    Shelley.

  • SCA BB Console report - Subscriber Average Consumption

    Hi All
    I'm just studying how to implement the multiple thresholds of subscriber quota on my network. I'm generating the report on subscriber average consumption as below to determine what is the right value of quota to be set for each of my subscriber. From the report, it shows the total number of subscriber. Here is my question:
    1. What is mean total subscriber from the report?
    2. Is it the average active subscriber for the particular aggregation period?
    3. Is it active subscriber with traffic session?
    The report generated is as below, for information, our total subscriber is around 1.6 million.
    Very much appreciate for the help. Thanks

    Hi
    This is output from one of the SCE:
    RDR-formatter statistics:
    =========================
    Category 1:
      sent:               154735424
      in-queue:           0
      thrown:             509
      format-mismatch:    0
      unsupported-tags:   0
      rate:               110 RDRs per second
      max-rate:           646 RDRs per second
    What it is mean by thrown?
    For measuring the Active Subscriber, I monitor the Active Subscriber with Session in SCE by using MRTG and (polling the active subscriber with session SNMP OID)
    The active subscriber is as attachment:
    Thanks for your reply.

  • Service Control Application Suite (SCAS BB) SCE 1000 RDR Problems

    Hello,
        I have recently taken over the deployment of the SCAS BB, which includes the SCE 1000, Subscriber Manager, and Collection Manager. If you are reading this thread, then hopefully you already know all about the components of the solution.
    I have a successful connection from the SCE 1000 to the CM, though I am not receiving any RDRs from the SCE, thus I can not run any reports against the CM with the SCAS BB.
    Can anyone provide a place to look as to why the SCE is not sending the RDRs? I have a good connection between the two based on the output of the show RDR-formatter command ....
    SE01#>sh RDR-formatter              
    Status:  enabled
    Connection is: up
    Forwarding mode: redundancy
    Connection Table:
    | Collector       | Port  |Status| Priority per Category:                                |
    | IP-Address  /   |       |      |-------------------------------------------------------|
    | Host-Name       |       |      | Category1   | Category2   | Category3   | Category4   |
    |-----------------|-------|------|-------------|-------------|-------------|-------------|
    | 10.104.0.116    | 33000 | up   | 100 primary | 100 primary | 100 primary | 100 primary |
    RDR:    queued:         0 ,sent:         0, thrown:         0
    UM:     queued:         0 ,sent:         0, thrown:         0
    Logger: queued:         0 ,sent:         0, thrown:         0
    Errors: thrown:         0
    Last time these counters were cleared: 00:10:07  JST  TUE  December  15  2009
    And when issuing a ~pcube/seconf.py --op=list from the Collection Manager, I see the connection up, but no RDRs coming in ...
    bash-2.03$ ./seconf.py --op=list
    IP              Rate            Peak
    10.104.0.115            0.0             0.0
    Can anyone tell me what I may be missing on the SCE 1000? Do I need a mapping of RDR tags to Categories? I have RDR categories defined, but no mappings ...
    SE01#>show running-config | i RDR
    RDR-formatter destination 10.104.0.116 port 33000 category number 1 priority 100
    RDR-formatter destination 10.104.0.116 port 33000 category number 2 priority 100
    RDR-formatter destination 10.104.0.116 port 33000 category number 3 priority 100
    RDR-formatter destination 10.104.0.116 port 33000 category number 4 priority 100
    Any help is MUCH appreciated!!!!
    Joe

    I have a same problem with 4.1 software.
    RAGAdapter, database,cm are alive

  • Errors in Cisco Collection Manager for SCE

    I installed Collection manager and I got errors in logs:
    [root@sce-cm ~]# tail -f /opt/cm/cm/logs/adapter-JDBCAdapter.log
    2012-05-27 22:41:32,073 [wrkr/JDBCAdapter] ERROR com.cisco.scmscm.db.DbInserter.RPT_LUR - insert err (more details in next line), tag=4042321925, fieldNo-1=13 curSqlIndex=16, i=15
    java.lang.ArrayIndexOutOfBoundsException
    2012-05-27 22:41:32,073 [wrkr/JDBCAdapter] ERROR com.cisco.scmscm.adapters.jdbc.JDBCAdapter - processRDR - got Throwable
    java.lang.ArrayIndexOutOfBoundsException
    2012-05-27 22:41:32,073 [wrkr/JDBCAdapter] ERROR com.cisco.scmscm.db.DbInserter.RPT_LUR - insert err - Exception while inserting the rdr values [0, 3, 71, 300, 300, 1338139200, 0, 1, 4, 8, 0, 0, 1], for the rdr tag = 4042321925
    java.lang.ArrayIndexOutOfBoundsException
    2012-05-27 22:41:32,073 [wrkr/JDBCAdapter] ERROR com.cisco.scmscm.db.DbInserter.RPT_LUR - insert err (more details in next line), tag=4042321925, fieldNo-1=13 curSqlIndex=16, i=15
    java.lang.ArrayIndexOutOfBoundsException
    2012-05-27 22:41:32,073 [wrkr/JDBCAdapter] ERROR com.cisco.scmscm.adapters.jdbc.JDBCAdapter - processRDR - got Throwable
    java.lang.ArrayIndexOutOfBoundsException
    RPT_LUR table is empty.
    How can I resolve this issue?
    Version is 3.7.5

    Hello Marat,
    It seems that you might be hitting this one CSCtz20343.
    Please check it.
    Thanks,
    Minja

  • SCE loses Quota Below Threshold events in cutoff redundancy mode

    Hi all,
    We are implementing a inline cascade topology with 2 SCE 2020 devices and the action on the SCE failure is cutoff and we are experiencing delay in "Quota Below Threshold" events.The events consequently generated upon quota depletion (i.e. "Quota Below Threshold" and "Quota Depleted") do appear, but meanwhile the subscriber experiences temporarily loss of service. The most important implication is that the subscriber loses all open downloading sessions. We haven't experienced such an issue while we were working in the "bypass" redundancy mode.
    Here follows an excerpt of our logs which indicate the problem while a subscriber has been downloading a file. The logs are generated by the API quota listeners at the lowest level. The quotas that get replenished each time are 50Mb. The quota threshold was set to 20Mb (from the default 10Mb) in an effort to mask off the problem, but unfortunately it persisted. The downloading rate wasn't high enough to justify a rapid replenishment of quotas.
    2011-05-06 17:40:26,499 DEBUG [handlers.SceQuotaListener] Handling Quota event for subscriber xxx with quota 16426 and type QUOTA_EVENT_TYPE_STATUS
    2011-05-06 17:40:41,491 DEBUG [handlers.SceQuotaListener] Handling Quota event for subscriber xxx with quota 10161 and type QUOTA_EVENT_TYPE_BELOW_THRESHOLD
    2011-05-06 17:41:41,759 DEBUG [handlers.SceQuotaListener] Handling Quota event for subscriber xxx with quota 7668 and type QUOTA_EVENT_TYPE_BELOW_THRESHOLD
    [... QBT event  ???]
    2011-05-06 17:42:41,819 DEBUG [handlers.SceQuotaListener] Handling Quota event for subscriber xxx with quota -910 and type QUOTA_EVENT_TYPE_BELOW_THRESHOLD
    2011-05-06 17:42:41,823 DEBUG [handlers.SceQuotaListener] Handling Quota event for subscriber xxx with quota -910 and type QUOTA_EVENT_TYPE_DEPLETED ...
    We are of the impression that the quota below threshold or depletion conditions are detected after a small delay of 2-3 seconds. Is it possible that this detection gets delayed somehow under certain conditions?
    Thank you in advance

    Rapid use of quota does explain this behavior but seems like you are already aware of this situation.
    Just to be sure, The Threshold should be set by evaluating the volume that the fastest subscriber in the system can consume in 30 seconds period. In your policy this would be both upstream + downstream the fastest subscriber can get (since quota is calculated in both directions). So the volume which the subscriber can consume with such a rate for 30 second period should be a guideline for setting the threshold value (threshold should be set significantly higher than this value).
    The QM uses a Sliding Window Model for measuring subscriber consumption -
    http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel36x/qm_sol/01_overview.html#wp1053153
    The Remaining Quota interval is configured in the SCA-BB GUI (at the RDRs section). What have you configured it as?
    Can you increase the quota replenishment limit to 100megs from 50 megs and leave the below threshold limit to 20 megs.
    Also not sure if you already have this but this link and the paragraph below may help:
    http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel355/qm_sol/02_scenarios.html#wp1053156
    Maximizing Quota Accuracy
    One of the most important aspects of the quota manager is accuracy of the quota levels for any subscriber. When you provision quota using an external server, a trade-off exists between quota accuracy and the number of network messages.
    To maximize accuracy, configure the rate of the periodic remaining quota indication to a high value, and configure the size of the quota dosage to a small value. A configuration causes performance degradation due to the high number of messages being generated in the network.
    Quota inaccuracies may occur during the changeover from one aggregation period to the next, or due to SCE fail-over. The level of inaccuracy depends on the configuration of the following parameters:
    •Rate of the periodic remaining quota indications
    •Quota dosage value
    During an aggregation period changeover, the following occurs until the first quota indication is received in the new aggregation period:
    •Any quota consumed by the subscriber is subtracted from the previous aggregation period.
    •The quota dosage value limits the size of any quota error.
    •The interval between the remaining quota indications limits the length of time during which consumed quota is subtracted from the previous aggregation period.
    In cases of SCE fail-over, the following occurs between the last quota indication in the failed SCE and the first quota indication in the new, active SCE:
    •Any quota consumed by the subscriber is not removed from the subscriber buckets.
    •The quota dosage value limits the size of any quota error.
    •The length of time during which quota is consumed is limited by the interval between the remaining quota indications.
    In all cases of inaccuracy, the quota remaining is calculated in favor of the subscriber. The only exception is if the aggregation period changeover occurs when the subscriber quota is already breached.
    Shelley.

  • Sce cm reporting issue

    hello experts,
    can anybody tell me, how can I solve this issue on CM? Our CM is receiving RDRs, but SCE reporting shows only data till 2 weeks ago. server has lot ot free space, SCE devices are connected to CM (ad they are sending rdrs).
    $ ./cm version 
    CM CD Version 3.5.5 Build 182
    $ ./cm dbversion
    Sybase  ase1502
    $ ./dbfree.sh
    Name                    % Data Free % Log Free
    Database                        0       99
    $ crontab -l
    15 3 * * * /opt/scmscm/db_maint/periodic_del.sh --name='daily real-time' --active=true --daystokeep=90 'RPT_LUR,RPT_MALUR,RPT_MEDIA,RPT_PUR,RPT_SUR,RPT_TOPS_PERIOD0,RPT_TOPS_PERIOD1,RPT_VLUR,RPT_GUR,RPT_TOPS_PERIOD0_CUMULATIVE,RPT_TOPS_PERIOD1_CUMULATIVE' 2>&1 | logger -p daemon.notice
    45 3 * * * /opt/scmscm/db_maint/periodic_del.sh --name='daily rpt_tr' --active=true --daystokeep=30 'RPT_TR' 2>&1 | logger -p daemon.notice
    -bash-3.00$ ~scmscm/db_maint/create_periodic_del_procs.sh
    Old periodic procedure for table RPT_GUR has been dropped.
    Periodic procedure for table RPT_GUR has been created.
    The following problem occured during DB operation:
    Can't allocate space for object 'sysprocedures' in database 'apricot' because 'system' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.
    martin

    My problem repeat every day after 23:15 o'clock. SCA BB don't show graphics (Global Bandwidth per Service) and other
    (user scmscm)
    Test: 01db_up.sh. Status: PASS. Message: db is up
    Test: 02cm_up.sh. Status: PASS. Message: CM is running
    test 03free_db.sh output was invalid, cannot parse status/message
    Test: 03free_db.sh. STATUS: Unknown. Message: Unknown state returned
    test 04free_log.sh output was invalid, cannot parse status/message
    Test: 04free_log.sh. STATUS: Unknown. Message: Unknown state returned
    Test: 05cm_persistent_buffers.sh. Status: FAIL. Message: The following directory/ies have more than 500 files in them - JDBCAdapter
    (from root)
    Test: 01db_up.sh. Status: FAIL. Message: DB is not running
    Test: 02cm_up.sh. Status: PASS. Message: CM is running
    test 03free_db.sh output was invalid, cannot parse status/message
    Test: 03free_db.sh. STATUS: Unknown. Message: Unknown state returned
    test 04free_log.sh output was invalid, cannot parse status/message
    Test: 04free_log.sh. STATUS: Unknown. Message: Unknown state returned
    Test: 05cm_persistent_buffers.sh. Status: FAIL. Message: The following directory/ies have more than 500 files in them - JDBCAdapter
    I do this -
    (user scmscm)
    /home/scmscm/cm/bin/cm restart --- solve my problem but restart cm every day bad idea
    after cm restart
    Test: 01db_up.sh. Status: PASS. Message: db is up
    Test: 02cm_up.sh. Status: PASS. Message: CM is running
    test 03free_db.sh output was invalid, cannot parse status/message
    Test: 03free_db.sh. STATUS: Unknown. Message: Unknown state returned
    test 04free_log.sh output was invalid, cannot parse status/message
    Test: 04free_log.sh. STATUS: Unknown. Message: Unknown state returned
    Test: 05cm_persistent_buffers.sh. Status: PASS. Message: All Adapter persistent buffers are in Normal state
       I have low experience with CM
    vi /home/scmscm/cm/logs/cm.log
    .................many message like that...
    2012-09-13 09:53:41,491 [Thread-9] WARN com.cisco.scmscm.buffer.PersistentBuffer - Persistent Buffer: deleting before read: /home/scmscm/cm/adapters/JDBCAdapter/74.rdr
    2012-09-13 09:53:42,544 [Thread-9] WARN com.cisco.scmscm.buffer.PersistentBuffer - Persistent Buffer: deleting before read: /home/scmscm/cm/adapters/JDBCAdapter/75.rdr

  • SCE Collection Manager prunetable.sh

    I am trying to use the command prunetable.sh but it doesn't work.
    The command is the following:
    -bash-3.2$ ./prunetable.sh 85 INI_VALUES
    Are you sure you want to prune table INI_VALUES ? (yes/no): yes
    Periodic delete not created. Use user guide to create periodic delete procedures.
    -bash-3.2$
    I also checked the periodic delete configuration:
    -bash-3.2$ ./dbperiodic.py --dump
    [4 hourly 30 days]
    active = true
    daystokeep = 30
    tablenames = RPT_LUR,RPT_TOPS_PERIOD1
    minute = 0
    hour = 0,4,8,12,16,20
    day = *
    month = *
    Warning: table name 'RPT_UVLINK' not found in DB, proceeding anyway
    Warning: table name 'RPT_DVLINK' not found in DB, proceeding anyway
    [4 hourly 7 days]
    active = true
    daystokeep = 7
    tablenames = RPT_SUR,RPT_TOPS_PERIOD0,RPT_UVLINK,RPT_DVLINK
    minute = 0
    hour = 2,6,10,14,18,22
    day = *
    month = *
    [4 hourly 14 days]
    active = true
    daystokeep = 14
    tablenames = RPT_PUR,RPT_VLUR
    minute = 0
    hour = 1,5,9,13,17,21
    day = *
    month = *
    [4 hourly 2 days]
    active = true
    daystokeep = 2
    tablenames = RPT_TR,RPT_MALUR
    minute = 0
    hour = 3,7,11,15,19,23
    day = *
    month = *
    -bash-3.2$
    What could be the problem ?
    Thanks,
    Marco

    Thank you for your reply.
    I just used prunetable.sh with a table that stores RDRs and it works.
    I wanted to delete old entries in the INI_VALUES table because some SCEs were removed from the network but they are still present in the SCABB reporter. If I had deleted the INI_VALUES table I would have to reload the service configuration on all the SCEs to regenerate this table. Is it correct ?
    Do you have any suggestion to avoid deleting the INI_VALUES table ?
    Thanks,
    Marco

  • What else SCE couldn't do without Collection manager and Subscriber Manager for SCE?

    Can we still monitor the traffic and control the subscriber even we do not have any Collection manager and Subscriber Manager? with SCE alone couldn't analysis or control the traffic?

    Hi,
    Without CM you can not generate reports based on RDR collection process. For example if you dont have Collection Manager you can not generate reports that are predefined on the SCA Reporter or insight. Only you can do is you can poll SNMP counters/values by a s/w and you can graph them, but it is not suitable and not covers the all data that SCE collects and reports. And for the SM side if you want to communicate with a policy/external server you really need an SM, also you can use its internal Quota manager to count quota.

  • (p3sm –-show) on supsciper manager (SCE)

    Hi All,
    When I issue the command (> p3sm –-show) on the supsciper manager machine I can notice the following line.
    Do anybody know what is the meaning of it.
    LEG block mode is on:              false.
    And how to enable (Auto-resync at SCE reconnect)
    Sample output:
    > p3sm –-show
    Subscriber Management Module Information:
    =========================================
    Persistency in SCE (static):       false
    Auto-resync at SCE reconnect:      false
    Save subscriber state on logout:   false
    Pull mode is on:                   false
    LEG block mode is on:              false
    Logon logging is on:               false
    Statistics:
    Number of logins:                  1872423
    Number of logouts:                 1824239
    Number of auto-logouts:            0
    Number of pull requests:           0
    LEG-SM link failure:
    Clear all subscribers mappings:    false
    Timeout:                           60
    Up time:                           4 hours 16 minutes 44 seconds
    Inactive Subscribers Removal:
    Is Enabled:          false
    Inactivity timeout:  1 hours
    Max removal rate:    10 subscribers per second
    Task interval:       10 minutes
    Last run time:       Was never run
    Automatic Logout (lease-time support):
    Is Enabled:          false
    Max logout rate:     50 IP addresses per second
    Task interval:       disabled
    Grace period:        10 seconds
    Last run time:       Was never run
    Command terminated successfully
    Thanks,
    Mohamed

    Hi Punit,
    This is an unsupported config. You canot have a CM and SM on the same box. You will have similar symptoms if you do have them on the same box. Sometimes the RDR's will work but something else will break. The reason is Databases. CM has it's own Database and SM runs it's own (Timesten). This has caused confusion and data corupption between the SM and CM.
    Given that the latest versions of CM and SM are now tested on VMware, I suggest you run these 2 servers as a VM on the same server.
    Shelley.

  • Two SCE boxes has died after upgrade to FW 3.6 (but not immediatelly)

    I have experienced SCE error with following switching to System Recovery Mode on two SCE 2000 boxes. I upgraded them two days ago but today they switched to Recovery Mode after unexpected platform reload. Difference between these two boxes reload/crash is only 20 seconds.
    Log shows:
    SCE2000#>show log | include 10-04-29
    2010-04-29 19:27:01 | WARN  | CPU #000 | Not enough disk space.
    2010-04-29 19:27:01 | WARN  | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
    2010-04-29 19:27:01 | WARN  | CPU #000 | The SE status changed to Warning
    2010-04-29 19:27:01 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2010-04-29 19:29:56 | INFO  | CPU #000 | A SSH session from 10.48.64.244 was established.
    2010-04-29 19:29:56 | INFO  | CPU #000 | File system operation : del  /tffs0/iwf.txt
    2010-04-29 19:29:57 | INFO  | CPU #000 | Disk space is OK
    2010-04-29 19:29:57 | INFO  | CPU #000 | The SE status changed to Operational
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx9
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx8
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx7
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx6
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx5
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx4
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx3
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx2
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx1
    2010-04-29 19:30:16 | INFO  | CPU #000 | File system operation : copy /tffs0/system/config.txt /tffs0/system/prevconf/config.tx1
    2010-04-29 19:30:16 | INFO  | CPU #000 | Configuration file '/tffs0/system/config.txt' was saved - files size = 4228.
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx9
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx8
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx7
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx6
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx5
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx4
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx3
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx2
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : del  /tffs0/system/prevconf/config.tx1
    2010-04-29 19:30:18 | INFO  | CPU #000 | File system operation : copy /tffs0/system/config.txt /tffs0/system/prevconf/config.tx1
    2010-04-29 19:30:18 | INFO  | CPU #000 | Configuration file '/tffs0/system/p3hidden/config/confX1.txt' was saved - files size = 443.
    2010-04-29 19:30:24 | ERROR | CPU #000 | SE Watchdog Module: An Error occurred. Please report to Cisco's customer support
    2010-04-29 19:30:24 | ERROR | CPU #000 | SE Watchdog Module: An Error occurred. Please report to Cisco's customer support
    2010-04-29 19:30:24 | WARN  | CPU #000 | SE Watchdog Module: A problem occurred. Please report to Cisco's customer support
    2010-04-29 19:30:24 | INFO  | CPU #000 | Party data base was closed.
    ******************** User Log File - started at 2010-04-29 17:33:35  - Version 3.6.0 Build 716 ********************
    2010-04-29 17:33:35 | INFO  | CPU #000 | SCE Application main process starting init phase.
    2010-04-29 17:33:35 | INFO  | CPU #000 | Set connection-mode: connection mode is: inline, box priority is: primary, fail-over mode is: bypass, physically-connected link group is: 0.
    2010-04-29 17:33:35 | INFO  | CPU #000 | Flow data-base (FC) initialized
    2010-04-29 17:33:35 | INFO  | CPU #000 | RuC specific initialization completed
    2010-04-29 17:33:35 | INFO  | CPU #000 | General RuC initialization completed
    2010-04-29 17:33:35 | INFO  | CPU #000 | System clock set to 17:33:35  UTC  THU  April  29  2010.
    2010-04-29 17:33:35 | INFO  | CPU #000 | Logger task Initialized successfully
    2010-04-29 17:33:36 | INFO  | CPU #001 | SCE Application main process starting init phase.
    2010-04-29 17:33:36 | INFO  | CPU #001 | Flow data-base (FC) initialized
    2010-04-29 17:33:36 | INFO  | CPU #001 | RuC specific initialization completed
    2010-04-29 17:33:36 | INFO  | CPU #001 | General RuC initialization completed
    2010-04-29 17:33:36 | INFO  | CPU #002 | SCE Application main process starting init phase.
    2010-04-29 17:33:36 | INFO  | CPU #002 | Flow data-base (FC) initialized
    2010-04-29 17:33:36 | INFO  | CPU #002 | RuC specific initialization completed
    2010-04-29 17:33:36 | INFO  | CPU #002 | General RuC initialization completed
    2010-04-29 17:33:36 | INFO  | CPU #003 | SCE Application main process starting init phase.
    2010-04-29 17:33:36 | INFO  | CPU #003 | Flow data-base (FC) initialized
    2010-04-29 17:33:36 | INFO  | CPU #003 | RuC specific initialization completed
    2010-04-29 17:33:36 | INFO  | CPU #003 | General RuC initialization completed
    2010-04-29 17:33:41 | INFO  | CPU #000 | System clock set to 17:33:41  UTC  THU  April  29  2010.
    2010-04-29 17:33:41 | INFO  | CPU #000 | Subscriber data-base manager initialized successfully.
    2010-04-29 18:33:44 | INFO  | CPU #000 | Time zone set to CET 60 minutes.
    2010-04-29 18:34:02 | INFO  | CPU #000 | state changed from INIT to RECOVERY.
    2010-04-29 18:34:22 | INFO  | CPU #000 | SM: DHCP LEASE QUERY LEG 3.6.0 Build 429 started
    2010-04-29 18:34:31 | INFO  | CPU #000 | EM Agent: EM Agent started. Version: SCE Agent 3.6.0 Build 429
    2010-04-29 18:34:31 | INFO  | CPU #000 | Management agent is up.
    2010-04-29 18:34:31 | INFO  | CPU #000 | EM Agent: SM operational state switched from Initialization to Active.
    2010-04-29 18:34:31 | INFO  | CPU #000 | Beginning execution of configuration files.
    2010-04-29 18:34:32 | INFO  | CPU #000 | System hostname changed to 'sce-2'.
    2010-04-29 18:34:32 | INFO  | CPU #000 | A new password was set for level 0.
    2010-04-29 18:34:32 | INFO  | CPU #000 | A new password was set for level 10.
    2010-04-29 18:34:32 | INFO  | CPU #000 | A new password was set for level 15.
    2010-04-29 19:34:33 | INFO  | CPU #000 | Time zone set to CET 60 minutes.
    2010-04-29 19:34:33 | INFO  | CPU #000 | SM: RDR Server has been started.
    2010-04-29 19:34:33 | INFO  | CPU #000 | EM Agent: PRPC server started on port 14374.
    2010-04-29 19:34:33 | INFO  | CPU #000 | Set connection-mode: connection mode is: inline-cascade, box priority is: secondary, fail-over mode is: bypass, physically-connected link group is: 1.
    2010-04-29 19:34:33 | INFO  | CPU #000 | state changed from INIT to BOOT.
    2010-04-29 19:34:33 | INFO  | CPU #000 | Formatter connection opened: address 127.0.0.1, port 33001.
    2010-04-29 19:34:33 | INFO  | CPU #000 | SM: Connection from 127.0.0.1:1025 opened.
    2010-04-29 19:34:34 | INFO  | CPU #000 | Formatter active connection opened : address 127.0.0.1, port 33001, category 3.
    2010-04-29 19:34:36 | INFO  | CPU #000 | Starting Line Card on slot 0 state change to shutdown
    2010-04-29 19:34:36 | INFO  | CPU #000 | Linecard on slot 0 is disabled
    2010-04-29 19:34:39 | INFO  | CPU #000 | Formatter connection opened: address 10.48.64.78, port 33000.
    2010-04-29 19:34:39 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 0.
    2010-04-29 19:34:39 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 1.
    2010-04-29 19:34:39 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 2.
    2010-04-29 19:34:39 | INFO  | CPU #000 | Starting Line Card on slot 0 state change to no shutdown
    2010-04-29 19:34:39 | INFO  | CPU #000 | Linecard on slot 0 is enabled
    2010-04-29 19:34:40 | ERROR | CPU #000 | Application configuration file executed with 390 errors.
    2010-04-29 19:34:41 | INFO  | CPU #000 | SSH server started.
    2010-04-29 19:34:41 | WARN  | CPU #000 | Link on management port #1 is down.
    2010-04-29 19:34:41 | INFO  | CPU #000 | The SE status changed to Operational
    2010-04-29 19:34:45 | INFO  | CPU #000 | EM Agent: PRPC connection to /10.48.64.113 established, client name is mcn.QuotaManager-10.48.64.74_10.48.64.113_SCE.J.API.PRPC, session name is rpc-0.
    2010-04-29 19:34:45 | INFO  | CPU #000 | EM Agent: QuotaManager-10.48.64.74_10.48.64.113_SCE.J.API.PRPC - connect operation was called, registered listeners: quota
    2010-04-29 19:34:51 | INFO  | CPU #000 | EM Agent: PRPC connection to /10.48.64.113 established, client name is usr.SM, session name is rpc-1.
    2010-04-29 19:34:51 | INFO  | CPU #000 | EM Agent: PRPC connection to /10.48.64.113 established, client name is mcn.SM, session name is rpc-2.
    2010-04-29 19:34:52 | INFO  | CPU #000 | Redundancy: SM connection status changed from NA to UP.
    2010-04-29 19:34:52 | INFO  | CPU #000 | Subscriber Manager connection is up.
    2010-04-29 19:34:52 | INFO  | CPU #000 | EM Agent: SM connection established.
    2010-04-29 19:34:52 | INFO  | CPU #000 | EM Agent: VPN synchronization started.
    2010-04-29 19:34:52 | INFO  | CPU #000 | EM Agent: VPN synchronization finished successfully.
    2010-04-29 19:35:32 | INFO  | CPU #000 | state changed from BOOT to RECOVERY.
    2010-04-29 19:35:33 | INFO  | CPU #000 | state changed from RECOVERY to STANDALONE.
    2010-04-29 19:35:33 | INFO  | CPU #000 | EM Agent: VPN synchronization started.
    2010-04-29 19:35:33 | INFO  | CPU #000 | EM Agent: VPN synchronization finished successfully.
    2010-04-29 19:35:33 | INFO  | CPU #000 | EM Agent: Subscriber synchronization started.
    2010-04-29 19:35:33 | INFO  | CPU #000 | EM Agent: Subscriber synchronization finished successfully.
    2010-04-29 19:36:58 | WARN  | CPU #000 | Not enough disk space.
    2010-04-29 19:36:58 | WARN  | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
    2010-04-29 19:36:58 | WARN  | CPU #000 | The SE status changed to Warning
    2010-04-29 19:36:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
    2010-04-29 19:45:07 | INFO  | CPU #000 | Formatter connection closed: address 10.48.64.78, port 33000.
    2010-04-29 19:45:07 | INFO  | CPU #000 | No Formatter connections is open on category 0.
    2010-04-29 19:45:07 | INFO  | CPU #000 | No Formatter connections is open on category 1.
    2010-04-29 19:45:07 | INFO  | CPU #000 | No Formatter connections is open on category 2.
    2010-04-29 19:45:07 | INFO  | CPU #000 | Formatter connection opened: address 10.48.64.78, port 33000.
    2010-04-29 19:45:08 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 0.
    2010-04-29 19:45:08 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 1.
    2010-04-29 19:45:08 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 2.
    2010-04-29 19:55:07 | INFO  | CPU #000 | Formatter connection closed: address 10.48.64.78, port 33000.
    2010-04-29 19:55:07 | INFO  | CPU #000 | No Formatter connections is open on category 0.
    2010-04-29 19:55:07 | INFO  | CPU #000 | No Formatter connections is open on category 1.
    2010-04-29 19:55:07 | INFO  | CPU #000 | No Formatter connections is open on category 2.
    2010-04-29 19:55:07 | INFO  | CPU #000 | Formatter connection opened: address 10.48.64.78, port 33000.
    2010-04-29 19:55:09 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 0.
    2010-04-29 19:55:09 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 1.
    2010-04-29 19:55:09 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 2.
    2010-04-29 20:04:38 | INFO  | CPU #000 | A SSH session from 10.96.108.90 was established.
    2010-04-29 20:05:37 | INFO  | CPU #000 | Formatter connection closed: address 10.48.64.78, port 33000.
    2010-04-29 20:05:37 | INFO  | CPU #000 | No Formatter connections is open on category 0.
    2010-04-29 20:05:37 | INFO  | CPU #000 | No Formatter connections is open on category 1.
    2010-04-29 20:05:37 | INFO  | CPU #000 | No Formatter connections is open on category 2.
    2010-04-29 20:05:37 | INFO  | CPU #000 | Formatter connection opened: address 10.48.64.78, port 33000.
    2010-04-29 20:05:38 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 0.
    2010-04-29 20:05:38 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 1.
    2010-04-29 20:05:38 | INFO  | CPU #000 | Formatter active connection opened : address 10.48.64.78, port 33000, category 2.
    2010-04-29 20:08:53 | ERROR | CPU #000 | SE Watchdog Module: An Error occurred. Please report to Cisco's customer support
    2010-04-29 20:08:53 | ERROR | CPU #000 | SE Watchdog Module: An Error occurred. Please report to Cisco's customer support
    2010-04-29 20:08:53 | WARN  | CPU #000 | SE Watchdog Module: A problem occurred. Please report to Cisco's customer support
    2010-04-29 20:08:53 | INFO  | CPU #000 | Party data base was closed.

    Try the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • SCE does not capture traffic snmp get-request

    Hi,
    We have SCE 2000 3.5.5.
    I have a problem to capture some snmp traffic.
    From a server To a router, our SCE captures traffic snmp "GET-NEXT-REQUEST". I can see these traffic in RDR (Transaction RDR and Subscriber RDR).
    but, From the same server To the same router, "GET-REQUEST" doesn't.
    I have checked these packets using sniffer software, and the difference of these is only "GET-NEXT-REQUEST" or "GET-REQUEST".
    What could cause this situation??
    Help me!

    Hi, Tom.
    I have controlled that the port is 161 and these packets go through the same SCE.
    I changed the service configuration as you said, but SCE didn't caputured the packets "snmp-get". I write the way that I have done.
         1.     Open "New Service Configuration"
         2.     Add 161 to "UDP ports for which flow should be opened on first packet"
         3.     "RDR Settings" - "Transaction Usage RDRs" - check "select ALL"
         4.     Apply a SCE device
         5.     command "Snmpget" from a pc
         6.     Control RDRs with tag "4042323000"  --> No record from the pc
         7.     mib-browser from the same pc
         8.     Control RDRs with tag "4042323000"  --> find the record from the pc
    I hope i can resolve it soon.

  • RDR server start on SM

    Hi,
    i have CM and SM running on same server. CM is working fine, but SM is not able to receive RDR from SCE ( as i am using sniffer radius LEG). When i see ./p3rdr --show, it shows me that RDR server is not active. I checked the p3sm.cfg file and all is fine, in RDR-server section on this file, i have enabled it as start=yes.
    can someone help me in this case.
    regards

    Hi Punit,
    This is an unsupported config. You canot have a CM and SM on the same box. You will have similar symptoms if you do have them on the same box. Sometimes the RDR's will work but something else will break. The reason is Databases. CM has it's own Database and SM runs it's own (Timesten). This has caused confusion and data corupption between the SM and CM.
    Given that the latest versions of CM and SM are now tested on VMware, I suggest you run these 2 servers as a VM on the same server.
    Shelley.

  • SCE 8000 with High CPU running SCOS 3.6.5

    Hi Guys,
    We have 1 SCE 8000 out of 20 that suddenly started showing high CPU
    SCE_VINA02#>show processes cpu sorted
    CPU utilization for five seconds:  99%/  0%; one minute:  99%; five minutes:  99%
    PID   Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
    6572  1743157450   2912773          0 41.79% 48.95% 42.00%   0 (scos-main)    
    6592   377205520   2822045          0 25.47% 22.96% 26.37%   0 (scos-main)    
    3773 -1131308800   2912909          0 22.09% 22.05% 22.19%   0 RucMain        
    20676   249912990   1895163          0 17.51% 15.86% 18.65%   0 (scos-main)    
    4058  1241380640   2839209          0  8.76%  9.06%  9.00%   0 PartyDBManager 
    4038    58347790   1778224          0  3.18%  3.40%  3.63%   0 controlRpcExtServer
    4042   199502330   2718111          0  1.99%  2.03%  2.06%   0 tFormatter     
    6594    80405570   2558527          0  1.99%  2.59%  2.80%   0 (scos-main)    
    20677    48485580   1405062          0  1.99%  2.28%  2.48%   0 (scos-main)    
    4595   309332240   2912876          0  1.39%  2.13%  2.12%   0 HwChk          
    4040   112684050   2736243          0  1.00%  1.12%  1.14%   0 qReaderExt     
    3639   264215460   2848244          0  1.00%  0.94%  0.91%   0 (scos-main)    
    4041    69509430   2868791          0  0.80%  0.74%  0.75%   0 qReaderInt     
    6573   235121090   2801654          0  0.80% 16.28%  5.13%   0 (scos-main)    
    6574    24244400    624919          0  0.60%  0.96%  3.70%   0 (scos-main)    
    3771    53398760   2912883          0  0.40%  0.38%  0.39%   0 CpuUtilMonitor 
    4037    32594910   2537807          0  0.40%  0.36%  0.38%   0 tLogger        
    3712    16686250   1627766          0  0.20%  0.11%  0.11%   0 fanControlTask 
    3778    46339600   2912908          0  0.20%  0.27%  0.28%   0 MsgQuMess-rcv  
    4028     8361600    734410          0  0.20%  0.07%  0.06%   0 tCCWatchdog    
    4059     5358870    353706          0  0.20%  0.04%  0.02%   0 SNMP agentx Task
    2971     2518240    166310          0  0.20%  0.05%  0.01%   0 (nfsd)         
    The CPU is STUCK at 99%, even when the traffic is minimal, we are seeing that the scos main process is hogging the CPU
    When i do the show interface line 0 counter cpu-utilization it shows me a different value than the first command, which is more reasonable according tho the quantity of traffic that is flowwing through the box at this moment.
    SCE_VINA02#>show interface LineCard 0 counters cpu-utilization
    Traffic Processor CPU Utilization:
    ==================================
    TP 1 CPU Utilization: 17%
    TP 2 CPU Utilization: 16%
    TP 3 CPU Utilization: 23%
    TP 4 CPU Utilization: 17%
    TP 5 CPU Utilization: 17%
    TP 6 CPU Utilization: 15%
    TP 7 CPU Utilization: 18%
    TP 8 CPU Utilization: 16%
    TP 9 CPU Utilization: 16%
    TP 10 CPU Utilization: 15%
    TP 11 CPU Utilization: 18%
    TP 12 CPU Utilization: 18%
    SCE_VINA02#>   
    When i log under linux in the box, it shows me another value different than what the other first two commands showed me
    [root@SCE_VINA02 ~]#>top
    top - 14:26:47 up 169 days,  7:46,  1 user,  load average: 3.86, 3.68, 3.31
    Tasks:  64 total,   1 running,  63 sleeping,   0 stopped,   0 zombie
    Cpu(s): 59.5%us,  2.2%sy,  0.0%ni, 36.4%id,  1.3%wa,  0.2%hi,  0.5%si,  0.0%st
    Mem:   2028668k total,  1914156k used,   114512k free,    47392k buffers
    Swap:        0k total,        0k used,        0k free,   320416k cached
      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                               
    3639 root      20   0 1353m 1.3g  44m S  134 65.9 355517:28 scos-main                                                             
       23 root      15  -5     0    0    0 S    0  0.0  24:59.23 scos-dump                                                             
    2973 root      20   0     0    0    0 S    0  0.0  39:56.53 nfsd                                                                  
    3455 root      20   0 16188 2620 1756 S    0  0.1 122:21.52 scos-sys-cmd-se                                                       
    26549 root      20   0  2476 1116  896 R    0  0.1   0:00.05 top                                                                   
        1 root      20   0  1776  616  540 S    0  0.0   3:17.32 init                                                                  
        2 root      15  -5     0    0    0 S    0  0.0   0:00.00 kthreadd                                                              
        3 root      RT  -5     0    0    0 S    0  0.0   0:58.98 migration/0                                                           
        4 root      15  -5     0    0    0 S    0  0.0   0:42.82 ksoftirqd/0                                                           
        5 root      RT  -5     0    0    0 S    0  0.0   2:25.35 watchdog/0                                                            
        6 root      RT  -5     0    0    0 S    0  0.0   0:59.95 migration/1                                                           
        7 root      15  -5     0    0    0 S    0  0.0   0:02.60 ksoftirqd/1                                                           
        8 root      RT  -5     0    0    0 S    0  0.0   0:18.66 watchdog/1                                                            
        9 root      15  -5     0    0    0 S    0  0.0 161:33.60 events/0                                                              
       10 root      15  -5     0    0    0 S    0  0.0  46:47.38 events/1                                                              
       11 root      15  -5     0    0    0 S    0  0.0   0:00.00 khelper                                                               
       12 root      15  -5     0    0    0 S    0  0.0   9:55.55 kblockd/0                                                             
       13 root      15  -5     0    0    0 S    0  0.0   3:26.99 kblockd/1                                                             
       16 root      15  -5     0    0    0 S    0  0.0   0:03.08 kswapd0                                                               
       17 root      15  -5     0    0    0 S    0  0.0   0:00.00 aio/0                                                                 
       18 root      15  -5     0    0    0 S    0  0.0   0:00.00 aio/1                                                                 
       19 root      15  -5     0    0    0 S    0  0.0   0:00.00 nfsiod                                                                
       20 root      15  -5     0    0    0 S    0  0.0   0:00.00 mtdblockd                                                             
       21 root      15  -5     0    0    0 S    0  0.0  50:36.28 skynet                                                                
       22 root     -86  -5     0    0    0 S    0  0.0 280:11.75 hw-mon-regs                                                           
       24 root     -91  -5     0    0    0 S    0  0.0  22:36.48 wdog-kernel                                                           
       25 root      15  -5     0    0    0 S    0  0.0   0:00.00 rpciod/0                                                              
       26 root      15  -5     0    0    0 S    0  0.0   0:00.00 rpciod/1                                                              
       80 root      15  -5     0    0    0 S    0  0.0   0:00.17 kjournald                                                             
       84 root      15  -5     0    0    0 D    0  0.0  17:05.31 kjournald                                                             
       92 root      15  -5     0    0    0 S    0  0.0   1:36.60 kjournald                                                             
      246 root      15  -5     0    0    0 S    0  0.0  36:09.67 bond0                                                                 
      952 root      20   0     0    0    0 S    0  0.0   0:00.01 pdflush                                                               
    1032 root      20   0     0    0    0 S    0  0.0   3:12.76 pdflush                                                               
    1430 bin       20   0  2024  500  388 S    0  0.0   0:00.01 portmap                                                               
    1459 root      20   0  1884  644  536 S    0  0.0   0:22.97 syslogd                                                               
    1467 root      20   0  1772  408  336 S    0  0.0   0:00.04 klogd                                                                 
    1469 root      20   0  1764  512  448 S    0  0.0   0:00.00 getty                                                                 
    1710 root      20   0  3308 1048  488 S    0  0.1  73:02.73 scos                                                                  
    1711 root      20   0  2476  568  484 S    0  0.0   0:00.19 tee                                                                   
    1733 root      20   0  3308  980  420 S    0  0.0   0:00.00 scos                                                                  
    1735 root      20   0  2948 1280 1080 S    0  0.1   0:00.00 sh                                                                    
    [root@SCE_VINA02 ~]#>
    We have a TAC opened but is being more than a 2 weeks and the engineer hasnt being able to find the source of the issue, she even has a ticket open with the BU
    Please if anybody out there might be facing a similar issue

    here is the RDR statistics and debug summary log.
    SUBSCE8K01#>show RDR-formatter statistics
    RDR-formatter statistics:
    =========================
    Category 1:
      sent:               1733914918
      in-queue:           0
      thrown:             0
      format-mismatch:    0
      unsupported-tags:   0
      rate:               404 RDRs per second
      max-rate:           1984 RDRs per second
    Category 2:
      sent:               919837769
      in-queue:           0
      thrown:             0
      format-mismatch:    0
      unsupported-tags:   0
      rate:               0 RDRs per second
      max-rate:           3657 RDRs per second
    Category 3:
      sent:               0
      in-queue:           0
      thrown:             0
      format-mismatch:    0
      unsupported-tags:   0
      rate:               0 RDRs per second
      max-rate:           0 RDRs per second
    Category 4:
      sent:               156867972
      in-queue:           0
      thrown:             0
      format-mismatch:    0
      unsupported-tags:   0
      rate:               105 RDRs per second
      max-rate:           163 RDRs per second
    Destination:     10.123.2.25 Port: 33000 Status: up   Active: yes
      Sent: 1733915274
      Rate:   396  Max:  1984
      Last connection establishment: 3 weeks, 6 days, 20 hours, 45 minutes, 27 seconds
    Destination:     10.123.2.26 Port: 33000 Status: up   Active: no
      Sent:          0
      Rate:     0  Max:     0
      Last connection establishment:  0 hours, 6 minutes, 14 seconds
    Destination:       127.0.0.1 Port: 33001 Status: up   Active: no
    SUBSCE8K01#>
    SUBSCE8K01#>
    SUBSCE8K01#>sh proc cpu sorted
    CPU utilization for five seconds:  96%/  0%; one minute:  97%; five minutes:  99%
    PID   Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
    4929   293498890    475542          0 99.00% 21.55% 16.40%   0 (scos-main)
    4555   573866000    478707          0 25.65% 25.89% 25.96%   0 RucMain
    4918   625477080    478701          0 25.45% 29.72% 33.67%   0 (scos-main)
    1810       88530       192          0  7.96% 14.82%  9.38%   0 (scos-main)
    4927   172451130    474889          0  7.56% 14.99%  9.97%   0 (scos-main)
    1809       97510       192          0  7.16% 17.72% 12.00%   0 (scos-main)
    5359   122862320    476098          0  6.96% 13.29%  6.39%   0 (scos-main)
    4817    83463610    476198          0  6.36%  6.31%  6.29%   0 controlRpcExtServer
    5358   137770620    476591          0  5.97%  5.68%  6.14%   0 (scos-main)
    5135   107450270    475407          0  4.38%  4.86%  6.47%   0 (scos-main)
    4840   584104440    476935          0  4.37% 11.73%  5.28%   0 PartyDBManager
    4821   152431380    478706          0  3.58%  3.40%  3.37%   0 tFormatter
    4919   249427970    331960          0  2.98%  0.92%  0.92%   0 (scos-main)
    4819    33178220    462486          0  1.59%  1.55%  1.39%   0 qReaderExt
    5516    51751940    478645          0  1.39%  2.17%  2.15%   0 HwChk
    4820    22420960    461376          0  0.99%  0.96%  0.96%   0 qReaderInt
    3345    42535190    476936          0  0.99%  0.87%  0.84%   0 (scos-main)
    4816    16505300    474586          0  0.80%  0.78%  0.72%   0 tLogger
    4560     9043340    478707          0  0.40%  0.34%  0.34%   0 MsgQuMess-rcv
    4521     7505470    476057          0  0.40%  0.36%  0.36%   0 nsm-to-sm-med-dispatcher
    4520     8472310    475729          0  0.40%  0.38%  0.37%   0 sm-to-nms-high-collector
    4551    10427120    478707          0  0.40%  0.45%  0.44%   0 CpuUtilMonitor
    SUBSCE8K01#>
    Summary of debug file.
    ************** CURRENT APPLICATION INFORMATION ***************
    Application file: /apps/data/scos/release_.sli
    Application name: Engage SML Version 3.6.5 build 41 (Protocol Pack 26 build 15)
    Using Lib - PL_V3.6.5_B1
    Using Lib - Classifier_V3.6.5_B1
    Application help: Entry point of Engage
    Original source file: /auto/srbu-proj1-bgl/apps/users/aninatar/autoBuild/App/SML/Engage/V3.6.5/src/com/pcube/AppTemplate/Main/template_app_main.san
    Compilation date: Thu, October 20, 2011 at 23:30:08
    Compiler version: SANc v3.20 Build 14 built on: Tue 08/04/2009 06:58:22.;SME plugin v1.1
    Capacity option used: 'EngageDefaultSCE8000'.
    ************** DBG LOG FILE MESSAGES HISTOGRAM ***************
    MOD ID : MSG ID | SEVERITY  | AMOUNT  |   DROPS    | STRING
    ----------------+-----------+---------+------------|-------
    Total number of different <> messages is 0
    Total number of different <> messages is 0
    [0x0502:0x000a] | | 0120529 | 0000001056 | Party DB: PartyDB::waitForState(pcid=%d) called, maxPCIDs=%d.
    [0x0102:0x0013] | | 0024763 | 0000000000 | Application Subscriber Context: Breach counter is negative for subscriber service counter=%d
    [0x0ce1:0x0010] | | 0000027 | 0000000000 | SnmpMibs: %s %s %d %d.
    [0x0505:0x0194] | | 0000005 | 0000000000 | Party DB Manager: (anonymous) createUnmappedParty - rcid = %lu, pid=%lu, ipAddress = 0x%x - came from ruc=%u, selected ruc=%u wrong ruc selected.
    [0x0300:0x004d] | | 0000013 | 0000000000 | Formatter: RdrVXConnection: Closed existing socket to port %d. (%s)
    [0x0910:0x002c] | | 0000002 | 0000000000 | RuC Interrupt Handler: %s.
    [0x0920:0x000a] | | 0000002 | 0000000000 | Logger: %s
    Total number of different messages is 7
    [0x0a10:0x0004] |     | 0000027 | 0000000000 | System Message: System Info message:
    %s
    [0x0aa2:0x001e] |     | 0000013 | 0000000000 | SNMP Agent: %s
    [0x0300:0x0059] |     | 0000013 | 0000000000 | Formatter: Formatter connection closed: address %s, port %d.
    [0x0aa2:0x001c] |     | 0000008 | 0000000000 | SNMP Agent: %s
    [0x0300:0x0056] |     | 0000008 | 0000000000 | Formatter: No Formatter connections is open on category %d.
    [0x0aa2:0x001d] |     | 0000013 | 0000000000 | SNMP Agent: %s
    [0x0300:0x005a] |     | 0000013 | 0000000000 | Formatter: Formatter connection opened: address %s, port %d.
    [0x0aa2:0x001b] |     | 0000008 | 0000000000 | SNMP Agent: %s
    [0x0300:0x0057] |     | 0000008 | 0000000000 | Formatter: Formatter active connection opened : address %s, port %d, category %d.
    [0x0505:0x029e] |     | 0000001 | 0000000000 | Party DB Manager: notifyPullRequestByPid() - %lu calls for notifySpawn() - failed in the last hour.
    [0x0920:0x0008] |     | 0000004 | 0000000000 | Logger: %s
    [0x0743:0x0000] |     | 0000001 | 0000000000 | TELNET_SSH_SERVER: A %s session from %s was established.
    [0x0730:0x0010] |     | 0000016 | 0000000000 | CLI: Executing CLI command: '%s'.
    [0x0309:0x002c] |     | 0000001 | 0000000000 | CmdlFFS: File system operation : del  %s
    Total number of different     messages is 14

  • Problem installing SCE 2010 on a virtual machine

    I'm having issues while installing SCE on a clean Hyper-V virtual machine running Windows 2008 R2.
    I've tried several options:
    - all-in-one from scratch, no SQL or serverroles/features installed -> error 1603
    - seperate SQL and SCE Management Server -> Management server installation fails, error 1603
    Different variations including and excluding reporting and VM Management with the same results.
    I then went and tried to install tbe Management server on a physical box -> success!
    However, I can't use this box for SCE and need to virtualize the whole thing.
    I'll dig through the SCE setup log files to see where it goes wrong.
    In the mean time, any ideas/suggestions anyone?
    /edit
    Below  a snippet of the setup log. This is the part just before I get 'Return value 3':
    MSI (s) (68:88) [15:42:11:574]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDD55.tmp, Entrypoint: AddPrivilegesToActionsAccount
    AddPrivilegesToActionsAccount: Custom action data property value. *****\administrator
    AddPrivilegeToAccount: Giving privilege to account. *****\administrator
    AddPrivilegeToAccount: Account does not have privilege. SeServiceLogonRight
    MSI (s) (68:14) [15:42:11:637]: Executing op: ActionStart(Name=_SetHealthServiceACL.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
    AddPrivilegeToAccount: Successfully granted privilege right to account. SeServiceLogonRight
    MSI (s) (68:14) [15:42:11:639]: Executing op: CustomActionSchedule(Action=_SetHealthServiceACL.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3073,Source=BinaryData,Target=SetHealthServiceACL,)
    MSI (s) (68:F8) [15:42:11:642]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDD95.tmp, Entrypoint: SetHealthServiceACL
    MSI (s) (68:14) [15:42:11:734]: Executing op: ActionStart(Name=_ChangeMOMHealthServiceRecoverySettings.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
    MSI (s) (68:14) [15:42:11:736]: Executing op: CustomActionSchedule(Action=_ChangeMOMHealthServiceRecoverySettings.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3073,Source=BinaryData,Target=ChangeMOMHealthServiceRecoverySettings,)
    MSI (s) (68:04) [15:42:11:739]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDDF3.tmp, Entrypoint: ChangeMOMHealthServiceRecoverySettings
    MSI (s) (68:14) [15:42:11:755]: Executing op: ActionStart(Name=_RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
    MSI (s) (68:14) [15:42:11:756]: Executing op: CustomActionSchedule(Action=_RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=1025,Source=BinaryData,Target=RegisterMU,CustomActionData=C:\Program Files\System Center Essentials\MUAuth.cab 3)
    MSI (s) (68:A0) [15:42:11:757]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDE04.tmp, Entrypoint: RegisterMU
    RegisterMU: Custom action data property value. C:\Program Files\System Center Essentials\MUAuth.cab 3
    RegisterMU: AddService failed. Error Code: 0x80070005.
    CustomAction _RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (68:14) [15:42:12:017]: User policy value 'DisableRollback' is 0
    MSI (s) (68:14) [15:42:12:017]: Machine policy value 'DisableRollback' is 0
    Action ended 15:42:12: InstallFinalize. Return value 3.

    Hi Guys,
    I am having the exact same issue. I have verified all prerequisites and can find absolutely nothing I am doing wrong with regards to what is prescribed in the guides. I am also trying to install SCE 2010 on a Hyper-V guest on Windows Server 2008 64Bit. I
    tried several times and troubleshooted my way through all the blogs. This is what I have done:
    Re-imaged the server (twice),
    Verified NetBios and FQDN is similar,
    Opened all required ports first and also disabled firewall eventualy,
    Using Domain Admin account,
    Removed ISS and reinstalled(SCE still complaing IIS needs configuration),
    Removed ISS again and let SCE setup fix prerequistes (SCE still complaining IIS needs configuration),
    Also below please find my exact log... The sucess of my SCE 2010 installation is VERY KEY for us, but I believe for the product team as well. We are busy building an Enteorise Management Architecture in a hosted/multi-tennant environment and at this moment
    our POC is a showstopper :(.
    operty(S): RuntimeUseWorkstationGC = 1
    Property(S): ShouldManageMemory = true
    Property(S): MOM_DB_IS_LOCAL = 1
    Property(S): AGENTSERVERCOMPATIBLE = 1
    Property(S): IsValidMgmtGroup = 1
    Property(S): WINDOWS_LANGUAGE_ID = ENS
    Property(S): DNS_COMPUTERNAME = PSGKSTSCE.psgkst.co.za
    Property(S): AD_COMPUTERNAME = PSGKSTSCE.psgkst.co.za
    Property(S): NETBIOS_DOMAINNAME = PSGKST
    Property(S): ENABLE_ERROR_REPORTING = 0
    Property(S): USE_SETTINGS_FROM_AD = 0
    Property(S): SDK_ACCOUNT_FOR_DB = SYSTEM
    Property(S): SDK_DOMAIN_FOR_DB = NT AUTHORITY
    Property(S): ACTIONSDOMAIN_FOR_DB = PSGKST
    Property(S): ACTIONSUSER_FOR_DB = Service-SCE
    Property(S): ROOT_MANAGEMENT_SERVER_DNS = PSGKSTSCE.psgkst.co.za
    Property(S): ROOT_MANAGEMENT_SERVER_AD = PSGKSTSCE.psgkst.co.za
    Property(S): CONFIG_ACCOUNT_FOR_DB = SYSTEM
    Property(S): CONFIG_DOMAIN_FOR_DB = NT AUTHORITY
    Property(S): SOURCEDIR = D:\Setup\AMD64\Server\
    Property(S): SourcedirProduct = {EA43D2A4-0926-445A-A220-6FF0CA34AA09}
    Property(S): MANAGEMENT_GROUP_ID = ac80d722-cdb5-acaa-a3e3-c5b2e1ca4717
    Property(S): ROOT_MANAGEMENT_SERVER_PORT_ID = C51B7833-DA54-1653-D8FD-1A738EF8DED5
    Property(S): ProductToBeRegistered = 1
    MSI (s) (24:C8) [10:55:13:979]: Note: 1: 1708
    MSI (s) (24:C8) [10:55:13:980]: Product: System Center Essentials 2010 -- Installation operation failed.
    MSI (s) (24:C8) [10:55:13:981]: Windows Installer installed the product. Product Name: System Center Essentials 2010. Product Version: 7.0.2432.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (s) (24:C8) [10:55:13:987]: Deferring clean up of packages/files, if any exist
    MSI (s) (24:C8) [10:55:13:987]: MainEngineThread is returning 1603
    MSI (s) (24:2C) [10:55:13:988]: No System Restore sequence number for this installation.
    === Logging stopped: 2010/05/12  10:55:13 ===
    MSI (s) (24:2C) [10:55:13:989]: User policy value 'DisableRollback' is 0
    MSI (s) (24:2C) [10:55:13:989]: Machine policy value 'DisableRollback' is 0
    MSI (s) (24:2C) [10:55:13:989]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (24:2C) [10:55:13:989]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (24:2C) [10:55:13:989]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (24:2C) [10:55:13:990]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (24:2C) [10:55:13:990]: Restoring environment variables
    MSI (s) (24:2C) [10:55:13:991]: Destroying RemoteAPI object.
    MSI (s) (24:10) [10:55:13:991]: Custom Action Manager thread ending.
    MSI (c) (98:48) [10:55:13:993]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (98:48) [10:55:13:994]: MainEngineThread is returning 1603
    === Verbose logging stopped: 2010/05/12  10:55:13 ===

Maybe you are looking for

  • Error while creating instance of Document

    Hi I am creating a java file , in which i m creating an instance of type Document. But it is givign the error "The type Document cannot be instantiated". anybody can please help? Regadrs, Anupreet

  • How do i use my new ringtone as a text tone?

    I had downloaded two ringtones directly to my phone via Itunes. It was fine and I was using one for Texts that came in and another for when my sister calls me, then I synced my phone and they disappeared. I call Apple and they resent them to me and t

  • To combine a multiple jsp pages in a one single page

    hi all, my problem statement is, i have 5 tabbed panes i,e each in a jsp page i need to put all those information into one single jsp page...while submiting the data. so how can i do about this using jsp. regards geetha

  • Automatically start db/listener on solaris startup

    I'm sure this is a simple one but I've very little experience of on Solaris. I've installed 10g on my Solaris box. When I reboot I've to manually start the db and the listener. How can I get the OS to automatically start both on start up? Thanks Paul

  • Question In regards to Frames

    Good Morning Everyone: I have a question in regards to Java Frames. I have just created a button in my princial frame and pressing this button creates another Frame. I have two questions relating to these resulting frame: 1)Every time I close the new