4A0-220 Leak Questions

The Feasibility File is a file that contains a set of target values for various optical impairment parameters, such as OSNR, CD, PMD, and PDL, that are used to determine whether a given LSP can be routed through the GMRE network. The Feasibility File is generated by the Network Planning Application (NPA) based on the network design and the service requirements. The Feasibility File is then loaded into the GMRE nodes and used by the GMPLS routing engine to perform feasibility checks for LSP requests. The Feasibility File ensures that the LSPs are routed in accordance with the network plan and the optical performance criteria12. References:

• 1: Nokia GMPLS-controlled Optical Networks Course | Nokia
• 2: GMPLS - Nokia

The provisioning steps that are common in both CP to plain MP networks are node creation, CPB provisioning process, node synchronization, and CPB power balance. These steps are required to create and commission the nodes, provision the cross-connect boards (CPBs), associate the links between the nodes, synchronize the network elements (NEs) with the NFM-T, and balance the power levels of the CPBs. References : Nokia GMPLS-controlled Optical Networks Course | Nokia, Nokia Advanced Optical Network Management with NFM-T Course | Nokia

The Upstream Label Object in RSVP-TE is an optional object that allows a node to suggest a label to its upstream neighbor for the purpose of provisioning bidirectional LSPs. The upstream label object is carried in the Resv message and contains the label value that the node wants to use for receiving traffic from its upstream neighbor. The upstream neighbor can accept or reject the suggested label based on its local policy and resource availability. The upstream label object simplifies the label allocation process for bidirectional LSPs and avoids the need for additional signaling messages. References : RSVP-TE - Hewlett Packard Enterprise, RSVP - Nokia

RSVP-TE Notify message is a message type defined in the RSVP-TE protocol, which is an extension of the RSVP protocol for MPLS traffic engineering. RSVP-TE Notify message is used to inform non-adjacent nodes of LSP events, such as setup, modification, or teardown. This allows the nodes to update their local state information and perform actions based on the notification. For example, a Notify message can be used to trigger a fast reroute mechanism in case of a link or node failure12. References:

• 1: RFC 3473 - Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
• 2: RFC 3471 - Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description