VRU_PIM is not getting activated

[subhransu Acharya]

Hello Team,
I am implementing UCCE in a lab environment.

My VRU_PIM is not getting activated, it is going as Activating->Shutdown-> Idle. In router, I have pg configured as 1-9.

I validated the PIM and OPC logs and in the OPC logs I can see:

05:00:00:085 pg1a-opc Trace: Capture was enabled at 4:35:27
05:00:00:085 pg1a-opc Trace: Output Capture was disabled at 4:35:27
05:00:00:241 pg1a-opc Trace: ProcessPeriphTableUpdateComplete: - !INFORM! - PID:5000 Logger reported DateTime = 07/07/2022 11:45:00 (0x54e75da0)
05:00:00:288 pg1a-opc Trace: ProcessCtrlrTableUpdateComplete: - !INFORM! - LCID:5000 Logger reported DateTime = 07/07/2022 11:30:00 (0x54e75bc0)
05:00:27:038 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:00:27:038 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:00:32:538 pg1a-opc Trace: GlobalInformtion::SetCentralControllerTime - CC Time set to 2022-07-07 12:00:32.535, OPC Time set to 2022-07-07 12:00:32.538, offset set to -3 milliseconds
05:01:27:033 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:01:27:033 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:02:27:043 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:02:27:043 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:03:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:03:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:04:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:04:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:05:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:05:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.
05:05:32:541 pg1a-opc Trace: GlobalInformtion::SetCentralControllerTime - CC Time set to 2022-07-07 12:05:32.527, OPC Time set to 2022-07-07 12:05:32.541, offset set to -14 milliseconds
05:06:27:041 pg1a-opc Trace: PeripheralPerform::ComputeServiceLevel - Invalid serviceLevelType 0 specified for Peripheral 5000.

[TalkingScientist]

Looks like PG2A is having the issue but you set us logs for PG1A.

We'll also need to see some configs. Are if you are OK with SQL run this on the AWDB:

select lc.LogicalControllerID, lc.EnterpriseName as LogicalController, lc.LogicalControllerType, lc.ClientType, p.PeripheralID, p.EnterpriseName as Peripheral, p.ClientType from Logical_Interface_Controller lc
LEFT JOIN Peripheral p ON p.LogicalControllerID = lc.LogicalControllerID

Then go to the PG and open regedit.

Go to 

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<yourinstancename>\PG2A\PG\CurrentVersion\PIMS\pim1\GenericData

And get a screenshot for the Generic Data values on any pims you see under the pims key.

Likely you have and ID mismatch. 

[subhransu Acharya]

sorry for the delay.

The issue is resolved now actually.

[bill.king1]

What was the fix/issue in case it can help someone else in the future?