Specifications

ae0 of switch C 4. enable iccp link of router A. (Please wait until iccp status up.) 5.
enable ae0 of switch C 6. enable ae0 of router A. PR982713
•
When upgrading to 13.3R2, customer may see the following messages: Chassis control
process: rtslib: ERROR kernel does not support all messages: expected 104 got 103,a
reboot or software upgrade may be required Chassis control process: Chassis control
process: rtslib: WARNING version mismatch for msg macsec (103): expected 99 got
191,a reboot or software upgrade may be required Chassis control process: Chassis
control process: rtslib: ERROR kernel does not support all messages: expected 104 got
103,a reboot or software upgrade may be required Chassis control process: Chassis
control process: rtslib: WARNING version mismatch for msg macsec (103): expected
99 got 191,a reboot or software upgrade may be required These messages are generated
during validating the new chassis management daemon against the old kernel, and
are harmless. PR983735
•
1GbE SFP(EX-SFP-1FE-LX) output optical power is restored after reseating by manual
removal/insert of SFP although the IF is disabled. PR984192
•
SNMP OID VRRP-MIB::vrrpAssoIpAddrRowStatus returns only one Ip address when
the interface ifl has configured with two virtual-addressees under two vrrp-groups.
PR987992
•
Following messages could be seen on the router for the FPC slot which are even empty.
These messages are cosmetic and could be ignored. chassisd[1637]: %DAEMON-6:
FPC 0 does not support Pic power off config cmd ignoring the config change
chassisd[1637]: %DAEMON-6: FPC 2 does not support Pic power off config cmd
ignoring the config change. PR988987
•
CFMD may crash after configuration change of an interface in a logical system which
is under OAM config for a l2vpn instance. PR991122
Layer 2 Features
•
When DHCP local server and DHCP relay are both configured on same router, the DHCP
relay binding might get lost if a graceful Routing Engine switchover (GRES) is performed.
PR940111
•
In L3 Wholesale environment, the DHCP clients might fail to renew their address in
DHCP relay scenario. PR956675
•
Configuring Ethernet Ring Protection Switching (ERPS), after changing interface's
MTU on Ring Protection Link (RPL) owner, all the interfaces on RPL owner change into
forwarding state, hence cause a layer 2 loop. PR964727
•
On MX Series platform with Ethernet Ring Protection Switching (ERPS) configuration,
after disabled Ring Protection Link (RPL) interface and then move RPL from west
interface to east interface, as a result, the ERPS east and west interface might go into
discard state at same time. PR970121
•
In DHCPv6 subscriber environment, changing the c-tags (inner vlan) without clear the
DHCPv6 clients first is not recommended, it might cause the subscriber to use the old
inner vlan even after DHCPv6 RENEW process. PR970451
117Copyright © 2015, Juniper Networks, Inc.
Resolved Issues