Specifications

Forwarding and Sampling
•
When a firewall filter has one or more terms which have MX Series-only match condition
or actions, such filters will not be listed during SNMP query. This behavior is seen
typically after Routing Engine reboot/upgrade/master-ship switch. Restarting mib2d
process will cause to learn these MX Series-only filters: cli > restart mib-process After
mib2d restart, SNMP mib walk of firewall OIDs will: - list all the OIDs corresponding
this MX Series-only filter - count correctly as configured in the filter Now, despite the
SNMP mib walk for firewall OIDs lists all OIDs and appropriate values, messages logs
will report the following logs for every interface that has this MX Series-only filter
applied. > Jul 8 15:52:09 galway-re0 mib2d[4616]:
%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading
counter names ae33.1009-i: 288 (No such file or directory) > Jul 8 15:52:09 galway-re0
mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed
in reading counter names ae31.1004-i: 257 (No such file or directory) > Jul 8 15:52:09
galway-re0 mib2d[4616]: %DAEMON-3-MIB2D_RTSLIB_READ_FAILURE:
get_counter_list: failed in reading counter names ae33.1010-i: 289 (No such file or
directory) > Jul 8 15:52:09 galway-re0 mib2d[4616]:
%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE: get_counter_list: failed in reading
counter names ae31.1004-i: 257 (No such file or directory) The above two issues are
addressed in this PR fix. PR988566
General Routing
•
On TXP/TXP-3D platform, a bad I2C device on SFC Switch Interface Board (SIB) might
cause Switch Processor Mezzanine Board (SPMB) to crash and all SIBs to be unable
to online. PR846679
•
Changing the redundancy mode of rlsq interface from "hot-standby" to "warm-standby"
on the fly might lead to kernel crash and the router will go in db> prompt. PR880451
•
A few particular sequence of member failures in an AMS with HA-enabled and with
NAPT-44 configured can cause sessions to reset after a GRES (or SPD restart).
PR910802
•
In scale DHCP subscribers scenario (e.g. 54K dual-stack DHCPv4/DHCPv6), graceful
Routing Engine switchover (GRES) is configured. If Routing Engine switchover occurs,
after that execute the command "root@user> show dynamic-configuration" many
times, large scale DHCP or DHCPv6 subscribers might be terminated. PR968021
•
In the dual Routing Engines scenario with 8K PPP dual stack subscribers. In rare
condition, after Routing Engine switchover, some subscribers are stuck in terminating
state forever. PR974300
•
1) Due to a previous fix chassisd on the protocol master Routing Engine and the protocol
backup Routing Engine connect to the main snmpd on the protocol master using the
following methods. a) Chassisd on the protocol master Routing Engine connects using
a local socket since snmpd is running locally. b) Chassisd on the protocol backup
Routing Engine connects using a TNP socket since snmpd is not local. 2) However this
fix changed the way the other daemons connect to snmpd. All important daemons
run on the protocol master and should connect to snmpd using a local socket. However
the fix changed it so that all daemons that ran on the protocol master (other than
103Copyright © 2015, Juniper Networks, Inc.
Resolved Issues