[j-nsp] jnxOperatingCPU problem

[Maria Cecilia Cena]

Hi,

Need to monitor RE1 and RE2 CPU usage via snmp using jnxOperatingCPU...but I don´t know why from both REs I received the same value (from router cli, I can see that values are not identical between the two      REs). Here you can see:

XXXXX> show snmp mib walk jnxOperatingCPU.9
jnxOperatingCPU.9.1.0.0 = 96
jnxOperatingCPU.9.1.1.0 = 0
jnxOperatingCPU.9.2.0.0 = 96
jnxOperatingCPU.9.2.1.0 = 0

{master}
XXXXX > show chassis routing-engine
Routing Engine status:
  Slot 0:
    Current state                  Master
    Election priority              Backup
    Temperature                 39 degrees C / 102 degrees F
    CPU temperature             39 degrees C / 102 degrees F
    DRAM                       640 MB
    Memory utilization          87 percent
    CPU utilization:
      User                      80 percent
      Background                 0 percent
      Kernel                    16 percent
      Interrupt                  4 percent
      Idle                       0 percent
    Model                          RE-2.0
    Serial ID                      08000008bc167501
    Start time                     2009-09-02 16:04:57 UTC
    Uptime                        558 days, 23 hours, 30 minutes, 25 seconds
    Load averages:                 1 minute   5 minute  15 minute
                                       1.06       0.84       0.50
Routing Engine status:
  Slot 1:
    Current state                  Backup
    Election priority              Master
    Temperature                 29 degrees C / 84 degrees F
    CPU temperature             29 degrees C / 84 degrees F
    DRAM                       768 MB
    Memory utilization          30 percent
    CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     0 percent
      Interrupt                  0 percent
      Idle                      99 percent
    Model                          RE-2.0
    Serial ID                      8b000007346e7801
    Start time                     2010-10-04 09:50:37 UTC
    Uptime                        162 days, 5 hours, 44 minutes, 35 seconds

Do you have any idea about this? Could it be related with graceful-switchover configured for routing-engine redundancy?

Thanks for your help!

Regards, Cecilia