You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, topology updates of switch/link/interface is only considering is_active(). But, on kytos-ng status_reason can also have logical states which represents a non operational state. For instance, maintenance, liveness all of these logical interruptions (liveness doesn't use actual interruptions yet, but equivalent approach), they can represent that a given entity isn't operationally available.
If you guys also expect for this to reflect accordingly you might want to also check if status_reason isn't empty, and to be safe only consider something active if status is also UP.
Here's an example with maintenance (notice active True, but status_reason not empty and status not UP):
Currently, topology updates of switch/link/interface is only considering
is_active()
. But, on kytos-ngstatus_reason
can also have logical states which represents a non operational state. For instance,maintenance
,liveness
all of these logical interruptions (liveness doesn't use actual interruptions yet, but equivalent approach), they can represent that a given entity isn't operationally available.If you guys also expect for this to reflect accordingly you might want to also check if
status_reason
isn't empty, and to be safe only consider somethingactive
ifstatus
is alsoUP
.Here's an example with maintenance (notice active
True
, but status_reason not empty and status not UP):The text was updated successfully, but these errors were encountered: