Specifications
Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.2 Release Notes
69
PD3-192821161 For Summit X650, X450 a-series and e-series switches, and the BlackDiamond 8800
series of switches, the maximum number of supported IP interfaces is 512 (IPv4 and
IPv6 combined). If there are more IP interfaces configured, the following log message is
displayed:
<Info:HAL.VLAN.Info> Maximum # of IP interfaces (512) already
configured. Could not add IP address 0x0A010101 mask 0xFFFFFF00
PD3-202580681 Enabling IP route compression may cause temporary slow path forwarding for some of the
L3 traffic.
PD4-718946965 Directed broadcast traffic is not being forwarded.
Mirroring
PD3-79867211 If you create a load sharing group (trunk), then enable mirroring to a port, the software
allows you to add the mirroring port to the load sharing group.
MPLS
PD4-464587012 All unicast traffic routed by MPLS is stopped when penultimate hop popping (PHP) is
enabled on all MPLS VLANs. VPLS traffic is not impacted.
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-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.
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description