System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

icap exception after npar ignite recovery

 
SOLVED
Go to solution
Highlighted
Frequent Advisor

icap exception after npar ignite recovery

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
5 REPLIES 5
Highlighted
Acclaimed Contributor

Re: icap exception after npar ignite recovery

>we've found an ICAP/ICOD exception

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

Re: icap exception after npar ignite recovery

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.
Highlighted
Honored Contributor

Re: icap exception after npar ignite recovery

It's showing your temporary capacity expired.

Temporary capacity available: (negative) 262 days, 1 hours, 0 minutes
Projected temporary capacity expiration: Expired
Regards
Shibin
Highlighted
Frequent Advisor

Re: icap exception after npar ignite recovery

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.
Highlighted
Frequent Advisor
Solution

Re: icap exception after npar ignite recovery

Closing. will aproach vendor.