icap exception after npar ignite recovery

[Paul Wasik]

Hi, we've found an ICAP/ICOD exception after an NPAR's OS was recovered with ignite (back to Oct 6). note that there are two other NPARs (each with single OS, no vpars) in the dome.

would the ignite recovery not have recovered the ICOD entitlements? or codewords? could there be another step to complete the recovery (and fix the icods exception) ?

it doesn't make sense that the icods were not in exception prior to the recovery. does this situation make sensse, and how?

please advise, and any and all input is apreciated.

-Paul

[Dennis Handly]

>we've found an ICAP/ICOD exception

What command were you using and what was the error message?

[Paul Wasik]

attached is the root email and the icap status output. no emails were recieved rpior to the recovery but I don't have previous icap status output.

[Shibin_2]

It's showing your temporary capacity expired.

Temporary capacity available: (negative) 262 days, 1 hours, 0 minutes
Projected temporary capacity expiration: Expired

[Paul Wasik]

I see that.

the question is how the ignite restore impacted the ICOD ... is there another step to fix it (like after igniting, use icap command to on other npar to get this partiton back in synch)?

see questions above.

[Paul Wasik · Accepted solution]

Closing. will aproach vendor.