R5.0 : Svc chain: All the re-originated routes not getting deleted when right intf of one of the svc instances in a service chain goes down
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| Trunk |
Invalid
|
Medium
|
Ananth Suryanarayana | |||
Bug Description
Fate sharing
Scenario :
SI-1 and SI-2 belongs to the same svc group.
left vm ---In net SI-1 --- In-net SI-2 ----Right Vm
Problem:
Right Intf of SI-1 is down. Routes not deleted from SI-2's right RI table.
Right intf of SI-1 is down as shown below :
SI-1 :
ctest-si-
Right: ctest-right_
(1 more)
Service Instance Details
Instance Name ctest-si-97126894
Display Name ctest-si-97126894
UUID 9faa91fb-
Template ctest-service_
# Instance(s) 1
Networks Management: ctest-mgmt_
Right: ctest-right_
Left: ctest-left_
Port Tuples ctest-port_
Service Health Checks (Interface Type: right) ctest-TestMulti
Availability Zone -
Instance Status No Server found.
Interface Status
Interface Status Health Status IP Address
74a65139-
29eb9de2-
20085e02-
SI-2 :
ctest-si-
Right: ctest-right_
(1 more)
Service Instance Details
Instance Name ctest-si-30067953
Display Name ctest-si-30067953
UUID 3dce6a8a-
Template ctest-st-58835363 (in-network, version 2)
# Instance(s) 1
Networks Management: ctest-mgmt_
Right: ctest-right_
Left: ctest-left_
Port Tuples ctest-port_
Availability Zone -
Instance Status No Server found.
Interface Status
Interface Status Health Status IP Address
ae105eff-
d04d8e67-
40c1aa59-
Right VM:
ctest-
86.144.82.3
contrail_
left VM:
ctest-TestMulti
77.89.64.3
contrail_
Schema:
RoutingInstance
routing_instances
name service_chain connections
default-
26fe3a82-
connections
default-
default-
connections
default-
default-
26fe3a82-
connections
default-
RoutingInstance
routing_instances
name service_chain connections
default-
26fe3a82-
connections
default-
default-
connections
default-
default-
26fe3a82-
connections
default-
Contrail
Collapse
Expand
Wrap
NoWrap
ShowRouteResp
tables
routing_instance routing_table_name deleted deleted_at prefixes paths primary_paths secondary_paths infeasible_paths stale_paths llgr_stale_paths routes listeners
default-
default-
false
-
3
3
0
3
0
0
0
routes
prefix last_modified paths
0.255.255.218/32
2018-Mar-01 19:20:59.395325
paths
protocol last_modified local_preference med local_as peer_as peer_router_id source as_path next_hop label origin replicated primary_table secondary_tables communities origin_vn flags tunnel_encap sequence_no origin_vn_path pmsi_tunnel load_balance cluster_list originator_id edge_discovery edge_forwarding
XMPP
2018-Mar-01 19:20:59.395325
200
100
0
0
-
nodeh3
-
10.204.217.107
72
incomplete
true
default-
secondary_tables
communities
target:
source-as:64512:0
rt-import:
encapsulation:gre
encapsulation:udp
secgroup:
originvn:64512:23
default-
flags
None
tunnel_encap
gre
udp
-
origin_vn_path
pmsi_tunnel
type -
ar_type -
identifier -
label
0
flags
flags
load_balance
decision_type -
fields
fields
cluster_list
-
edge_discovery
edge_forwarding
86.144.82.3/32
2018-Mar-01 19:20:59.395315
paths
protocol last_modified local_preference med local_as peer_as peer_router_id source as_path next_hop label origin replicated primary_table secondary_tables communities origin_vn flags tunnel_encap sequence_no origin_vn_path pmsi_tunnel load_balance cluster_list originator_id edge_discovery edge_forwarding
XMPP
2018-Mar-01 19:20:59.395315
200
100
0
0
-
nodei7
-
10.204.217.119
30
incomplete
true
default-
secondary_tables
communities
target:
source-as:64512:0
rt-import:
encapsulation:gre
encapsulation:udp
mobility:
secgroup:
originvn:64512:23
default-
flags
None
tunnel_encap
gre
udp
1
origin_vn_path
pmsi_tunnel
type -
ar_type -
identifier -
label
0
flags
flags
load_balance
decision_type -
fields
fields
cluster_list
-
edge_discovery
edge_forwarding
86.144.82.5/32
2018-Mar-01 19:20:59.395471
paths
protocol last_modified local_preference med local_as peer_as peer_router_id source as_path next_hop label origin replicated primary_table secondary_tables communities origin_vn flags tunnel_encap sequence_no origin_vn_path pmsi_tunnel load_balance cluster_list originator_id edge_discovery edge_forwarding
XMPP
2018-Mar-01 19:20:59.395470
200
100
0
0
-
nodeh3
-
10.204.217.107
72
incomplete
true
default-
secondary_tables
communities
target:
source-as:64512:0
rt-import:
encapsulation:gre
encapsulation:udp
mobility:
secgroup:
originvn:64512:23
default-
flags
None
tunnel_encap
gre
udp
1
origin_vn_path
pmsi_tunnel
type -
ar_type -
identifier -
label
0
flags
flags
load_balance
decision_type -
fields
fields
cluster_list
-
edge_discovery
edge_forwarding
listeners
id name state_count
0
RibOut Type: XMPP
3
1
RoutePathReplicator
0
next_batch
more
false
| Changed in juniperopenstack: | |
| importance: | Undecided → Medium |
| Changed in juniperopenstack: | |
| milestone: | none → r5.0.0 |
| Ananth Suryanarayana (anantha-l) wrote | #1 |
By design, this is intended. Only ServiceChain routes re-originated by control-node are marked and treated as a group and deleted and re-added as applicable. Any XMPP protocol learned route directl from the agent (the route in the right most RI) shall remain as is, until the egress agent withdraws the route.
During test automation, we should check for the presence/absence of connected re-originated routes only. Any route with source protocol XMPP/BGP should be ignored.