Comment 6 for bug 1450683

Recreated on build 30.

Setup has 2 TORs, each with 2 interfaces/BMS, one in vlan10 and the other in vlan20. Initially, all the routes are correctly programmed and connectivity is fine. Upon deleting the physical/logical interfaces belonging to one of the TORs (TOR-2) from the UI, the symptoms described in the bug are seen. The broadcast route on the vRouter points to the TSN, however, the TSN node does not have corresponding entries for the incoming mpls labels. As such, all traffic is dropped with error invalid NH. Same as what is described in the bug above.

Setup details:

Controller: 10.87.129.245, root:n1keenA
TSN: 10.87.129.74 (mgmt), root:n1keenA, 11.1.1.2 (Data)
Compute: 10.87.140.126 (mgmt), root:juniper123, 11.1.7.2 (Data)
TOR-2: 10.87.140.225 (mgmt), root:juniper123, 11.1.9.2 (Data)
TOR-3: 10.87.130.83 (mgmt), root:n1keenA, 11.1.6.2 (Data)