Actually we have an infrastructure like the one that is represented in the image below.
The Local Router has two TGU's with DLCI 20. The Remote Sites can be connect to one TGU or to another one.
On both Sites we have the End To End KeepAlive to make an ISDN to be ready when the FR link goes down.
We need to migrate the actual infrastructure to a E3 - 34mbps link over ATM and the Architecture will become the follow:
In This way the TGUs will "collapse" in the new 34mbps ATM link.
The ISP in this architecture needs to "switch" ATM/FR Packets between the Local Router Vs Remote Routers.
Now the question...the doubt...
If We enable the OAM on the sub-interfaces that we'll create on the Local Router (one for each remote router), the "compatibility" between the EEK and OAM is effective?
There is no support for end-to-end keepalive in ATM/FR inteworking.
Note, ATM and FR are both are obsolete techonolgies today. You should look for a pure IP solution, e.g MPLS for best results.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: