Looking at an issue we have faced with our facility--we have two new offices coming up with AT&T ASE circuits (cloud). Headend is located at our main data center and connected to VSP 9000. The remote sites have ERS 4850 with OSPF routing licenses.
Details;
WAN P2P
VLAN 100
/25 subnet
VSP 9000 has 1 interface (10.0.0.1) -- this is where ASE headend is connected
Port is TAG ALL on VLAN 100
Remote Site 1 is 10.0.0.2 VLAN 100
Uplink is PVID 1, VLAN Member 100, UntagPVIDonly
Loopback 192.168.0.1
Remote Site 2 is 10.0.0.3 VLAN 100
Uplink is PVID 1, VLAN Member 100, UntagPVIDonly
Loopback 192.168.0.2
Each remote site has VLAN 5 and VLAN 10 locally; one is data, other is voice.
Each remote site has default route 0.0.0.0 pointing to 10.0.0.1 (VSP 9K interface)
OSPF is used: I see routing entries for subnets at both locations locally and on VSP 9K.
Here lies the problem;
Remote Site 1: I can ping the WAN IP, Loopback IP, and SSH to either one all day long with no problems.
Remote Site 2: I can ping the WAN IP, but when I ping the Loopback it's super inconsistent (it's either responding once every 20 packets, responding solid for 5 minutes, then gone for 10.) I can SSH to loopback when it's responding--otherwise I have to use WAN IP.
I've been told numerous times this design will work -- just interested in others thoughts/experiences. My next step is to put some guys at either end and do some packet captures. My fear is some packets are just getting lost in AT&T's cloud.
This is our first time doing this using Avaya hardware--we're experienced with OSPF P2P with Cisco ASR and Cisco Routers at remote sites.