Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 158

JUNOS 10.1 Software Release Notes
Network Address Translation (NAT)
Power over Ethernet (PoE)
158
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
On SRX5800 devices, rebooting is required for any NP bundle configuration
change to take effect. Currently there is no notification displayed after the bundle
configuration change to notify that a reboot is required for the change to take
effect. [PR/441546]
On SRX Series and J Series devices with
you should not clear sessions manually when too many sessions are in status
"used". [PR/445730]
On SRX5600 and SRX5800 devices, data path debug trace messages are getting
dropped at above 1000 packets per second (pps). [PR/446098]
On J2350, J4350, and J6350 devices, extended bit error rate test (BERT) takes
an additional 3 hours to complete even though a BERT-period of 24 hours is set.
[PR/447636]
On SRX240 High Memory devices in a chassis cluster, the secondary node can
go to DB> mode when there are many policies configured and TCP, UDP, and
ICMP traffic matches the policies. [PR/493095]
On J4350 devices, when you place internal calls, interface-based persistent NAT
displays only one active hairpinning session instead of two, even after the call
is established. [PR/504932]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, NAT behavior in event
logs is incorrect for JUNOS Release 10.1. Because of a bug, the log output shows
both source and destination IP from the client/server instead of only the IP
address with NAT. The output incorrectly shows 4.0.0.0->5.0.0.1.
The correct output should be as follows:
For destination NAT, the IP address in the log should be 0.0.0.0->5.0.0.1.
For source NAT, the ip address displayed in log should be 4.0.0.0->0.0.0.0.
[PR/505454]
On SRX240 and SRX210 devices, the output of the PoE operational commands
takes roughly 20 seconds to reflect a new configuration or a change in status of
the ports. [PR/419920]
On SRX210 and SRX240 devices, the
not deactivate the PoE ports. Instead, the PoE feature can be turned off by using
the disable configuration option. Otherwise, the device must be rebooted for the
deactivate setting to take effect. [PR/426772]
On SRX210 and SRX240 devices, reset of the PoE controller fails when the restart
chassis-control command is issued and also after system reboot. PoE functionality
is not negatively impacted by this failure. [PR/441798]
On SRX210 PoE devices managing AX411 Access Points, the devices might not
be able to synchronize time with the configured NTP Server. [PR/460111]
and
session-init session-close
deactivate poe interface all
enabled,
command does