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
This attribute of an EVC indicates if a dynamic path can or cannot be used, so maybe it should be called simple "dynamic_path".
Its default value is set to "False", but I think it should be "True" if there is no primary or secondary path defined.
The text was updated successfully, but these errors were encountered:
Yes, I agree with the new name and expected behavior. If the request is for an intra-switch circuit (both UNIs are in the same switch), the path (dynamic or defined by the user) will not matter. If the request is for an inter-switch EVC, then either the path must be defined by the user or a dynamic path should be calculated (e.g., by pathfinder).
Another issue related to this is: when you create an EVC with primary_path field and dynamic_backup_path=True, mef_eline just use any dynamic path instead of setup the primary path as requested by the user.
Another issue related to this is: when you create an EVC with primary_path field and dynamic_backup_path=True, mef_eline just use any dynamic path instead of setup the primary path as requested by the user.
@italovalcy, I was unable to reproduce this behavior. Can you describe your environment and your queries?
This attribute of an EVC indicates if a dynamic path can or cannot be used, so maybe it should be called simple "dynamic_path".
Its default value is set to "False", but I think it should be "True" if there is no primary or secondary path defined.
The text was updated successfully, but these errors were encountered: