Date: Thu, 28 Mar 2024 17:44:21 +0000 (UTC) Message-ID: <1108772752.12954.1711647861007@wiki.mef.net> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12953_1441008573.1711647861006" ------=_Part_12953_1441008573.1711647861006 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As noted in section 6.6, a UCS can be designated as Backu=
p. When there is at least one non-Backup UCS available at an SD-WA=
N Edge (availability of a UCS is described by [R22] and the explanatory tex=
t around it), Ingress IP Packets are not forwarded toward the egress UNI ov=
er a UCS that is designated as Backup. However, since Backup=
em> UCSs may have lower bandwidth and/or higher cost, it may be desirable t=
o restrict which Application Flows are permitted to use them. This control =
can be achieved using the BACKUP Policy Criterion. It can have the value
[R32] Application Flows = MUST NOT be forwarded toward the destination egress UNI ov= er a UCS that is designated as Backup if a non-Backup UCS to the destinatio= n egress UNI is available.
[R33] If the Policy Crit= erion BACKUP=3DNo is assigned to an Application Flow, then the App= lication Flow MUST be discarded if only Backup UC= Ss to the destination egress UNI are available.
Note that Application Flows that have BACKUP=3Dyes will likely = be more resilient than those with BACKUP=3Dno.
PUBLISHED= span>
MEF-SDCP Exam Study Reference