Specifications

Type 5. One of the checks PIM makes is to determine if it is the local RP for the S,G.

During a re-configuration period where any commit is done, PIM re-evaluates whether

it is a local RP. It waits until all the configuration is read and all the interfaces have

come up before making this determination. The local rp state is cleared out early in

this RP re-evaluation process, however, which allows for a window of time where the

local RP state was cleared out but it has not yet been re-evaluated. During this window

PIM may believe it is not the local rp and return FALSE to MSDP for the given source.

If MSDP makes the call into PIM during this window after a configuration

change(commit), then it is possible that the Source Active(Type 5) state will be

removed. The fix will be to clear out the local rp state right before it is re-evaluated ie

after it reads configuration for all interfaces; to not allow any time gap where it could

be inconsistent. PR1015155

Resolved Issues: Release 13.3R4

Resolved Issues

Authentication and Access Control

•

The syslog message "UI_OPEN_TIMEOUT: Timeout connecting to peer" might appear

if "show version detail" command is executed. This log is a cosmetic log and can be

ignored. This issue is fixed from Junos OS Release 13.3 onwards. PR895320

Class of Service (CoS)

•

On MX Series routers with both MX linecard (in this case, MPC and MPCE on the box)

and other type linecard (DPCE on the box). When the Default Frame Relay DE Loss

Priority Map is configured and commited, all FPCs are getting restarted with core-files.

PR990911

•

SNMP get-request for OID jnxCosIngressQstatTxedBytes (ingress queue) might return

the value of jnxCosQstatTxedBytes (egress queue). But SNMP walk works fine since

it uses get-next-request. PR1011641

Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series