Specifications

ExtremeXOS 12.3.4 Release Notes
79
PD3-208178928 Adding a static route with an MPLS LSP may cause one of the following problems:
• If a static route is added with an MPLS LSP whose transport setting is “IP traffic
deny,” the route is displayed with an invalid nexthop in the show iproute mpls
command output.
• When a static route is added with an MPLS LSP that is not present in show
iproute mpls command output. For example, if there are 17 RSVP-TE LSPs to the
same destination, only 16 LSPs are eligible for carrying traffic because of a maximum
ECMP path limit of 16. Adding static routes with 17 LSPs results in the same
observation.
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-202184409 Adding/deleting a LAG sharing port changes the VLAN status, which is causing an OSPF/
MPLS reconvergence.
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-118914021 When an OSPF neighbor is configured between two LSRs and MPLS, and an LDP
session is configured between them, the ABR router advertises a default route to the
internal router. The default route is not mapped to a label in the internal router because
the ABR does not advertise the label
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-204793983 The egress rate-limit shown in the command output of the show port utilization
command is not correct.
Table 38: Platform-Specific and Feature PDs (Continued)
PD Number Description