cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1265
Views
10
Helpful
2
Replies
michgri
Beginner

Can't create fault severity assignment policy in 3.2(1m)

So I was digging around in ACI 3.2(1m) and I noticed that I cannot create a fault severity assignment policy like I could in 2.x. I've created monitoring policies at the tenant and fabric levels and there is literally no option to add a monitoring object.

 

It is however possible to add monitoring objects for the event severity assignment policies, though. I don't think it's an account issue; I'm using the built-in admin account (this is a lab environment).

 

Has this changed, do I need to configure another policy elsewhere in order to activate this or am I missing something obvious? 

 

See the attached screenshots

1 ACCEPTED SOLUTION

Accepted Solutions
michgri
Beginner

A quick update so this doesn't become yet another unanswered ACI question: apparently you need to right-click on the fault and select "Ignore Fault" or "Change Severity." It'll then appear underneath the monitoring policy in use for that tenant or EPG.

To put it into a custom monitoring policy, you need to create a custom monitoring policy either in your tenant or the common tenant (which is where the default tenant monitoring policy is). Apply it to your tenant or the the EPG. Generate a fault; F0467 is easy to generate by trying to statically apply an EPG on an unconfigured interface. Right-click on the fault and select "Ignore Fault" or "Change Severity."

I can't tell you if this actually works to squelch the faults, though, since it looks like there is a bug preventing it from working properly. If you select "Ignore Fault," the fault will disappear from its current location--but new faults will not be squelched. The bug ID is CSCvk00011 and it appears to apply only to 3.2(1m). I'll add that it's annoying to have to generate the fault in order to configure it; there are situations where you would want to do that in advance (i.e., before you do maintanence).

Finally, I couldn't do anything with faults at the fabric level. Right-clicking on a fault like F0532 gives you only the standard ACI object options (save, post, etc.). I'm not sure if this is a design decision, if there is some other procedure required or even some other location where I need to do this.

View solution in original post

2 REPLIES 2
michgri
Beginner

A quick update so this doesn't become yet another unanswered ACI question: apparently you need to right-click on the fault and select "Ignore Fault" or "Change Severity." It'll then appear underneath the monitoring policy in use for that tenant or EPG.

To put it into a custom monitoring policy, you need to create a custom monitoring policy either in your tenant or the common tenant (which is where the default tenant monitoring policy is). Apply it to your tenant or the the EPG. Generate a fault; F0467 is easy to generate by trying to statically apply an EPG on an unconfigured interface. Right-click on the fault and select "Ignore Fault" or "Change Severity."

I can't tell you if this actually works to squelch the faults, though, since it looks like there is a bug preventing it from working properly. If you select "Ignore Fault," the fault will disappear from its current location--but new faults will not be squelched. The bug ID is CSCvk00011 and it appears to apply only to 3.2(1m). I'll add that it's annoying to have to generate the fault in order to configure it; there are situations where you would want to do that in advance (i.e., before you do maintanence).

Finally, I couldn't do anything with faults at the fabric level. Right-clicking on a fault like F0532 gives you only the standard ACI object options (save, post, etc.). I'm not sure if this is a design decision, if there is some other procedure required or even some other location where I need to do this.

Update: it works for fabric faults of various types as well. You just have to (sigh) make sure you're looking at an individual fault instance and not the summary shown under System->Faults.