Authentication
■ On J Series devices, your attempt to log in to the router from a management
device through FTP or Telnet might fail if you type your username and password
in quick succession before the prompt is displayed, in some operating systems.
As a workaround, type your username and password after getting the prompts.
[PR/255024]
■
On J Series devices, after the user is authenticated, if the webauth-policy is deleted
or changed and an entry exists in the firewall authentication table, then an
authentication entry created as a result of webauth will be deleted only if a traffic
flow session exists for that entry. Otherwise, the webauth entry will not get
deleted and will only age out. This behavior will not cause a security breach.
[PR/309534]
AX411 Access Point
■ On SRX210 PoE devices, the access point reboots when 100 clients are associated
simultaneously and each one is transmitting 512 bytes packets at 100 pps.
[PR/469418]
■ On SRX650 devices, when an access point is part of default cluster and you
change the default cluster after the access point is connected to it, the changes
might not be reflected. As a workaround, restart the wireless LAN service.
[PR/497752]
Chassis Cluster
■
On J Series devices in a chassis cluster, the show interface terse command on
the secondary Routing Engine does not display the same details as that of the
primary Routing Engine. [PR/237982]
■
On J4350 Services Routers, because the clear security alg sip call command
triggers a SIP RTO to synchronize sessions in a chassis cluster, use of the
command on one node with the node-id, local, or primary option might result in
a SIP call being removed from both nodes. [PR/263976]
■ On J Series devices, when a new redundancy group is added to a chassis cluster,
the node with lower priority might be elected as primary when the preempt
option is not enabled for the nodes in the redundancy group. [PR/265340]
■ On J Series devices, when you commit a configuration for a node belonging to
a chassis cluster, all the redundancy groups might fail over to node 0. If graceful
protocol restart is not configured, the failover can destabilize routing protocol
adjacencies and disrupt traffic forwarding. To allow the commit operation to
take place without causing a failover, we recommend that you use the set chassis
cluster heartbeat-threshold 5 command on the cluster. [PR/265801]
■ On J Series devices in a chassis cluster, a high load of SIP ALG traffic might result
in some call leaks in active resource manager groups and gates on the backup
router. [PR/268613]
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ■ 143
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
To Next Page
Loading...
Need help?
General
