Dan, Ingress-node-replication was not pushed by Device Manager on purpose. The corresponding MX image could be any daily build equal to or greater than 14.2-20150627.0.
Vedu From: Dan Houtz <[email protected]<mailto:[email protected]>> Date: Saturday, July 4, 2015 at 1:47 PM To: OpenContrail Users List - 2 <[email protected]<mailto:[email protected]>> Subject: [Users] Problem with Device Manager's VXLAN config in Contrail 2.2 Has anyone else tried configuring EVPN VXLAN on an MX using device manager in Contrail 2.2? In my testing the configuration being pushed my netconf is not valid: root@gw2z0# commit check [edit routing-instances _contrail_l2_4_Test bridge-domains bd-4] 'vxlan' multicast-group or ovsdb-managed or ingress-node-replication should be enabled error: configuration check-out failed: (statements constraint check failed) To fix this you must manually configure ingress-node-replication: root@gw2z0# set groups __contrail__ routing-instances _contrail_l2_4_Test bridge-domains bd-4 vxlan ingress-node-replication root@gw2z0# commit check configuration check succeeds Is this possibly MX junos version specific? I am using a daily build given to me by my SE as I don't believe any released versions support VXLAN: root@gw2z0# run show version Hostname: gw2z0 Model: mx80-48t Junos: 14.2-20150527_rpd_v2_evpn_vnid.0 I doubt it matters but it's also odd that device manager is applying this since I'm using VXLAN: root@gw2z0# show groups __contrail__ protocols mpls interface all; Thanks! Dan
_______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
