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
The issue occurred during Y-Flow with protected path creation(a flaky issue as it was caught for a specific switch triplet), but it seems like there is an available path for both main and protected path
STR:
Create Y-Flow with protected path (swT: shared ep(sw3) --> ep1(sw7)-ep2(sw2))
{
"y_flow_id" : "28Nov-y-flow",
"shared_endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:03",
"port_number" : 10
},
"maximum_bandwidth" : 1000,
"path_computation_strategy" : "COST",
"encapsulation_type" : "transit_vlan",
"max_latency" : null,
"max_latency_tier2" : null,
"ignore_bandwidth" : false,
"periodic_pings" : false,
"pinned" : false,
"priority" : null,
"strict_bandwidth" : false,
"description" : "See, how she leans her cheek upon her hand! O that I were a glove upon that hand, that I might touch that cheek!.",
"allocate_protected_path" : true,
"diverse_flow_id" : null,
"sub_flows" : [ {
"flow_id" : "S1.y-flow",
"endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:07",
"port_number" : 10,
"vlan_id" : 1696,
"inner_vlan_id" : 1786
},
"shared_endpoint" : {
"vlan_id" : 501,
"inner_vlan_id" : 3951
},
"description" : null
}, {
"flow_id" : "S2.y-flow",
"endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:02",
"port_number" : 11,
"vlan_id" : 2001,
"inner_vlan_id" : 2125
},
"shared_endpoint" : {
"vlan_id" : 3578,
"inner_vlan_id" : 770
},
"description" : null
} ]
}
Actual result:
{
“correlation_id” : “3edfd053-3615-4f1a-858a-13721da1142a : fn-tests-46ba0db7-f2c3-48e3-a4bb-4c944659be3c”,
“timestamp” : 1732721372672,
“error-type” : “Object was not found”,
“error-message” : “Could not create y-flow”,
“error-description” : “ResourcesAllocationAction failed: Not enough bandwidth or no path found. Couldn’t find non overlapping protected path”
}
BUT Y-Flow with protected path on switch triplet swT: shared ep(sw3) --> ep1(sw2)-ep2(sw7) has been created successfully.
{
"y_flow_id" : "28Nov-y-flow",
"shared_endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:03",
"port_number" : 10
},
"maximum_bandwidth" : 1000,
"path_computation_strategy" : "COST",
"encapsulation_type" : "transit_vlan",
"max_latency" : null,
"max_latency_tier2" : null,
"ignore_bandwidth" : false,
"periodic_pings" : false,
"pinned" : false,
"priority" : null,
"strict_bandwidth" : false,
"description" : "See, how she leans her cheek upon her hand! O that I were a glove upon that hand, that I might touch that cheek!.",
"allocate_protected_path" : true,
"diverse_flow_id" : null,
"sub_flows" : [ {
"flow_id" : "S1.y-flow",
"endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:02",
"port_number" : 10,
"vlan_id" : 1696,
"inner_vlan_id" : 1786
},
"shared_endpoint" : {
"vlan_id" : 501,
"inner_vlan_id" : 3951
},
"description" : null
}, {
"flow_id" : "S2.y-flow",
"endpoint" : {
"switch_id" : "00:00:00:00:00:00:00:07",
"port_number" : 11,
"vlan_id" : 2001,
"inner_vlan_id" : 2125
},
"shared_endpoint" : {
"vlan_id" : 3578,
"inner_vlan_id" : 770
},
"description" : null
} ]
}
The issue occurred during Y-Flow with protected path creation(a flaky issue as it was caught for a specific switch triplet), but it seems like there is an available path for both main and protected path
STR:
Actual result:
BUT Y-Flow with protected path on switch triplet swT: shared ep(sw3) --> ep1(sw2)-ep2(sw7) has been created successfully.
YFlowWithProtectedPathDetailsSwT3---2-7.json
YFlowWithProtectedPathSwT3---2-7.json
The text was updated successfully, but these errors were encountered: