Specifications

Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.1 Release Notes
69
PD4-476351932 Performing a restart process mpls or restart process ospf on a spoke
node in an HVPLS setup causes the Label Distribution Protocol (LDP) peer to go down
with the core node.
Workaround: Disable and enable MPLS.
PD4-475414370 The following warning message is seen numerous times after changing VLAN Virtual
Private LAN Services (VPLS) mappings:
<Warn:MPLS.LDP.InternalProb>
PD4-475414505 In more complex topologies, detour Label Switched Path (LSP) connections are not set
up.
PD4-475414558 Changing a Label Switch Router (LSR) ID causes all Label Distribution Protocol (LDP)
peers to go into a NonExistent state.
PD4-452308541 The secondary pseudo wire on an ESRP master switch does not take the secondary core
node pseudo wire after the primary core is rebooted.
PD3-157687121 ExtremeXOS software uses Control Channel Type 2 to indicate router alert label mode. In
MPLS Router Alert Label mode, VCCV packets are encapsulated in a label stack. However,
the existing VCCV packets are sent like a stack without any PW label.
PD3-184989177 When an LDP advertise static setting is set to all, all static routes are treated as
egress routes and egress LSPs are created. That is, a label is generated and advertised for
the static route. If the router at the end of the static route advertises a label matching
that static route, the LSP that was previously an egress LSP becomes a transit LSP. An
ingress LSP should also be created whenever a label is received, however, the ingress LSP
is never created.
Workaround: Do not use the LDP advertise static all configuration in situations
where an ingress LSP for a static route is required.
PD3-139423053 Running the show mpls rsvp-te lsp summary command on a system configured
with 2,000 ingress LSPs takes an excessive amount of time to process.
PD3-121985381 You cannot configure an IP MTU that is greater than the configured jumbo frame size.
However, when the jumbo frame size is configured using a smaller value than the IP
MTU, the configuration is accepted and the traffic is forwarded using the larger packet
sizes.
PD3-92653036 The show mpls label, show mpls rsvp-te label, and show mpls rsvp-te
lsp command output currently does not display egress LSPs using advertised implicit
NULL labels.
PD3-111544904 When a router receives an explicit NULL label, it is incorrectly treated as an implicit
NULL label, so rather than sending label 0, no label is sent.
PD3-93218551 If either an egress or a transit LSP traverses the system, and an MPLS labelled packet
containing a router alert label is received, that packet is not forwarded.
PD3-93069318 Only VLANs configured as protocol any should be added to MPLS.
PD3-104731701 When a traceroute is performed by setting the MPLS TTL to the IP TTL, ExtremeXOS does
not correctly send back an ICMP response. The result is “*” characters in the traceroute
for the routers that timed out. If a route is available, ExtremeXOS should attempt to send
back an ICMP response.
PD3-93630853 LDP should not advertise a label mapping for a direct VLAN that does not have IP
forwarding enabled.
PD3-203917264 When an explicit route object (ERO) is changed for an LSP session that is up, the LSP
that is already up is not torn down. LSP stays up based on the older values. The retry
count continues to increment as LSP tries to come up with new values by querying routes
every 30 seconds. This is done while the earlier LSP session is still active using the
previously configured values. See the retry count in the command output for the show
mpls rsvp-te lsp <lsp_name> detail command.
Multicast
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description