Need Flexibility to define Scheduled Outage for device components like Interface, Fan, Card etc.

[Joe]

Description

When work is done on the network it would be nice to be able to schedule an outage for an interface vs. the entire node.  Putting an entire Node into "Out of Service" results in a loss of too much information.  I

Benefit

Allows for maintenance to occur while still monitoring the rest of a device.  Important in an enterprise environment.  

Design Details

Model it after "Schedule Outage" for nodes.  

[AkashDeep]

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage, and we expect the community to help prioritize the idea with comments and community support (votes/kudos).

[Joe]

@AkashDeep 
Any update?  Seems these ideas get submitted and then get no action.  Is there a timeline on when it will be actioned one way or another?  

[qz07sg]

Should I open a new IE?  Related to this idea: I'd like to be able to put a fan, power supply, really an managed component of a device into maintenance / scheduled outage.  Like original poster mentioned -- putting the entire node in scheduled outage results in the loss of events.  Like the node maybe in a degraded state but still operational and I'd like to still get management events re: node down, interface down, power supply, fan, card, etc alarms.

[Joe]

@AkashDeep I'd expand my request to include @qz07sg qa07sg's comments above.  The ability to schedule outages for portions of a device is a feature that's really needed. 

[qz07sg]

A follow-up on this -- someone just asked me about searching for the ID that created the scheduled outage.  It would be *AWESOME* when looking at a node's SCHEDULED OUTAGE tab that the ID of the user that scheduled the outage was visible as a column in the display