"Generally, we recommend using the provider L2 service as a link between L3 devices at each site. And having local sites in their own broadcast domain."
This is what we have. The VLAN (default 1000) is only assigned to the interface that faces the provider. It then has to route to enter our production vlans. So, broadcast is limited to each site.
"With an eLAN you would have a single ip subnet with a L3 address at each site and full mesh peering for your OSPF or BGP route distribution. (or use static routes)"
This is what we are doing wrong. Instead of assigned an IP address on the interfaces at each site, they used put the VLAN at each of the sites and used intervlan routing. It has been making my head spin.......
"Here there is a need to bridge VLAN and broadcast domains between sites. We generally recommend a transparent service that is used as a trunk port between the two sites. The devices on each side then can control which VLANs are shared between the DC. And generally use MSTP per VLAN."
Yes, this is what they were trying for. Unfortunately, they never implemented VSTP or MSTP on the VLAN between the data centers, or anywhere else for that matter.
Thank you for the info... this verifies what I was thinking and gives me a path for moving forward.