DM: Nodes from different clusters not allowed to peer

[Shashikiran H]

2.20-61~icehouse
Topo:
nodec15 -- yuvaraj(mx)

A config already exists which was pushed by a node, which is in a different cluster using DM:
regress@yuvaraj# show | display set
set version 15.1B1-PS.4
set groups __contrail__ routing-options route-distinguisher-id 10.204.217.190
set groups __contrail__ routing-options autonomous-system 64512
set groups __contrail__ protocols bgp group __contrail__ type internal
set groups __contrail__ protocols bgp group __contrail__ multihop
set groups __contrail__ protocols bgp group __contrail__ local-address 10.204.217.190
set groups __contrail__ protocols bgp group __contrail__ hold-time 90
set groups __contrail__ protocols bgp group __contrail__ keep all
set groups __contrail__ protocols bgp group __contrail__ family inet-vpn unicast
set groups __contrail__ protocols bgp group __contrail__ family inet6-vpn unicast
set groups __contrail__ protocols bgp group __contrail__ family evpn signaling
set groups __contrail__ protocols bgp group __contrail__ family route-target
set groups __contrail__ protocols bgp group __contrail__ neighbor 10.204.216.5
set groups __contrail__ protocols bgp group __contrail__ neighbor 10.204.216.245
set groups __contrail__ protocols bgp group __contrail_external__ type external

If I try to add yuvaraj as a peer from nodec15, with some config already present on mx, config is not pushed:
On c15
2015-06-24 13:17:52.225 BgpPeerMessageTrace: BGP Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj SEND Open AS 64512, Hold Time 90, Identifier 10.204.216.72, Code MpExtension Family inet-vpn, Code MpExtension Family e-vpn, Code MpExtension Family route-target, Code MpExtension Family erm-vpn, Code MpExtension Family inet6-vpn, Code GracefulRestart controller/src/bgp/bgp_peer.cc 902
2015-06-24 13:17:52.226 BgpPeerMessageTrace: BGP Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj RECV Unsupported Capability: MpExtension (1) controller/src/bgp/bgp_proto.cc 112
2015-06-24 13:17:52.226 BgpPeerNotificationTrace: Bgp Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj RECV Notification with Code 6 and SubCode 5 ( Cease:Connection is rejected by the peer ) controller/src/bgp/state_machine.cc 307
2015-06-24 13:17:52.226 BgpPeerNotificationTrace: Bgp Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj SEND Notification with Code 2 and SubCode 7 ( OPEN Message Error:Unsupported Capability ) controller/src/bgp/bgp_session.cc 108
2015-06-24 13:17:52.226 BgpPeerEventTrace: BGP Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj Initiating close process controller/src/bgp/bgp_peer_close.cc 229
2015-06-24 13:17:52.226 BgpPeerEventTrace: BGP Peer default-domain:default-project:ip-fabric:__default__:nodec15:default-domain:default-project:ip-fabric:__default__:yuvaraj Close process is complete controller/src/bgp/bgp_peer_close.cc 139

After I delete groups and apply-groups, it allows me to configure bgp peering with c15(10.204.216.72):
regress@yuvaraj# show | display set
set version 15.1B1-PS.4
set groups __contrail__ routing-options router-id 10.204.217.190
set groups __contrail__ routing-options route-distinguisher-id 10.204.217.190
set groups __contrail__ routing-options autonomous-system 64512
set groups __contrail__ protocols bgp group __contrail__ type internal
set groups __contrail__ protocols bgp group __contrail__ multihop
set groups __contrail__ protocols bgp group __contrail__ local-address 10.204.217.190
set groups __contrail__ protocols bgp group __contrail__ hold-time 90
set groups __contrail__ protocols bgp group __contrail__ keep all
set groups __contrail__ protocols bgp group __contrail__ family inet-vpn unicast
set groups __contrail__ protocols bgp group __contrail__ family inet6-vpn unicast
set groups __contrail__ protocols bgp group __contrail__ family evpn signaling
set groups __contrail__ protocols bgp group __contrail__ family route-target
set groups __contrail__ protocols bgp group __contrail__ neighbor 10.204.216.72

[Suresh Balineni (sbalineni)]

This does not look like a Bug.
If you move mx from one cluster to another cluster, and inorder to push config, you must have to configure physical router/bgp router parameters on the new Config node. If physical router config is not present on the new config node, DM would not either push or delete exsting config.

[Suresh Balineni (sbalineni)]

Can you please send physical router / bgp router config present on the new cluster for the MX?

[Nischal Sheth (nsheth)]

Lowered priority since it's not clear if this a bug.
Please respond to Suresh's comments.

[Shashikiran H (skiranh)]

I am not sure which config you are looking for.
Cluster 1: nodec15
I add a physical node in webui for nodec15 using Configure->Physical Devices->Physical Routers for mx(yuvaraj). And then create a new BGP router in Configure->Infrastructure->BGP Routers in nodec15 and map that to the physical router I created in the first step.
The DM config gets pushed on yuvaraj correctly.

Cluster 2: nodec26
With the above step in place and DM config of nodec15 already on mx, I add a physical node in webui for nodec26 using Configure->Physical Devices->Physical Routers for the exact same mx(yuvaraj). And then create a new BGP router in Configure->Infrastructure->BGP Routers in nodec26 and map that to the physical router I created in the first step.
Now DM config does not get pushed. This is the bug.
If you are looking for the configuration that gets pushed on the mx, its present in the description. Can you clarify the config part?

[Suresh Balineni (sbalineni)]

This is not a bug. The way to make 2 clusters peer with mx is to create a BGP router for cluster 1 on cluster2 and then peer this with the mx box.