L3 VPRN services

• Non-default customer assignment are not supported for Wavence domain.

• Consider two VPRN (PE) sites A and B, if the spoke-SDP binding from A to B goes down (admin/operational) then spoke-SDP binding from B to A will remain admin and operational up (but will contain alarms related to spoke SDP binding from A to B on the "Affected Alarms" tab of spoke-SDP binding from B to A). 

• VPRN SAP related statistics show field names that are common across multiple domains (for example, SR, SAR, and so on).

• IP stats are applicable only to the network interface and the same is displayed for Wavence nodes.

• VPRN interface creation via the routing sub-tree view in the NFM-P is not supported.

• The creation of L3 SAP requires IP address assignment.

• The System IP address of NEs managed in the NFM-P should be unique (/32 subnet mask).

L3 VLAN ID

• The range of the L3VLAN IDs configured on the NE should 0 and 2 to 4080.

• VLAN IDs present in the NE VLAN Table cannot be selected as IP Data Plane L3VLAN ID and IP Data Plane L3VLAN ID cannot be used to the NE VLAN Table.

• When the L3VLAN ID is set to 0, it is not allowed to create network IP interfaces and administratively enable the system IP interfaces and modify any L3 VPN related parameters.

• The IP Data Plane L3VLAN ID can be changed only when all the created network IP interfaces and the System IP interface are administratively disabled. Setting VLAN ID to 0 after having created network IP interfaces will not allow to administratively enabling these interfaces.

IP network creation/configuration

• Ports involved in the network interface cannot be reused for another network interface creation.

• The network interface cannot be administratively enabled if the port and address are not assigned to the interface.

• The system interface cannot be modified or deleted when the interface administrative state is enabled.

Static LSP

• Static hops (Swap, Pop) configured under a static LSP will be listed only in the case of creation. If a discovered node has a static LSP along with static hops (Swap, Pop) already configured, then static hops are not listed as these are NFM-P only attributes and there are no common parameters to associate them. Because of this limitation, a “MissingHopConfiguration” warning alarm is raised on the Static LSP.

• Destination IP address will not be assigned to static LSPs in the NFM-P if they are created from WebCT. It is required to assign complete static LSP parameters (Source IP, Destination IP, Next Hop and labels) if the user is configuring static LSPs from WebCT.

• When LSP is created with static hop entries (SWAP/POP), end to end LSP path will be created in the NFM-P. The hop (SWAP/POP) objects are associated to LSP through static hop entries. If the user tries to delete the LSP, it will delete the associated static hop entries (SWAP/POP).

• For discovered static LSP, static hop entries (SWAP/POP) are not listed as these objects are not related. If the user tries to delete LSP, the hops are not deleted as they are independent objects. The user has to delete static labels (SWAP/POP) from slabel maps tab of MPLS interface.

• User encounters deployment error if static LSP's are deleted with "Turn Up" Administrative state, it’s always required to shut down the static LSP before attempting to delete it.

SR-TE LSP

• When creating an MPLS Path, use the System Interface IP address instead of the Network Element IP address for network elements on the path.

• When creating an SR-TE LSP, the Source and Destination IP should use the respective node System Interface IP.

SDP tunnels

• SDP tunnels cannot reuse LSP that are already configured under other SDP tunnels.

• SDP Tunnel page show some irrelevant tabs or attributes for Wavence, which are relevant across SR/SAR nodes.

• SDP Tunnel creation form requires source and destination node IPs.

Network QoS

The node will accept the configuration only if the LSP EXP in profile and LSP EXP out profile bits are same.

Transport setup

Transport setup is not supported for disjoint topology. If any discrepancies are detected, transport setup will display an error and it is the responsibility of the user to delete such configurations.