Juniper BXOS 4.1 R2, Release Note

Page: 18 / 24

BXOS 4.1 R2 Software Release Notes
18 „
Resolved Issues
„ If you delete all ISO addresses configured on the gateway when IS-IS is
enabled, the gateway causes inconsistent protocol behavior. As a workaround,
retain at least one ISO address configured on the gateway. [PR/418230: This
issue has been resolved.]
„ The gateway reboots if you continuously perform operations such as creating
or deleting the interfaces, and enabling or disabling protocols in random. As a
workaround, perform the operations in a proper sequence. [PR/419466: This
issue has been resolved.]
„ If you configure two alarm values for RMON in a single commit, the CLI stops
responding. As a workaround, configure the RMON alarm values separately.
[PR/419480: This issue has been resolved.]
„ If you change the loopback IP when protocols are enabled, the gateway
reboots. As a workaround, disable all protocols before changing the loopback
IP. [PR/419577: This issue has been resolved.]
„ The BXOS software does not support a separate CLI command to delete RMON
alarms and events. There is no workaround. [PR/419800: This issue has been
resolved.]
„ If you reconfigure the framer mode of a TDM interface from T1 mode to E1
mode in another parallel SSH session while PPP configuration is in progress,
the DPM module stops responding. As a workaround, change the framer mode
of the TDM interface from the same CLI session. [PR/420654: This issue has
been resolved.]
„ When a bypass tunnel is being used as a backup tunnel to carry the traffic,
deleting the bypass tunnel priority brings down the tunnel. As a workaround,
delete and configure the bypass tunnel when primary tunnel is carrying traffic.
[PR/420967: This issue has been resolved.]
„ When two E1 interfaces are associated with an MLPPP bundle, if a secondary
link comes to operational state before the primary link, the primary link is not
operationally up. There is no workaround. [PR/421496: This issue has been
resolved.]
„ When you select a MAC address as the engine ID, save the configuration, and
then reboot the gateway, the system configuration does not persist. As a
workaround, configure the engine ID using the BXOS CLI. [PR/423295: This
issue has been resolved.]
„ When you delete an SNMPv3 view with more than 30 characters, the view is
not deleted, and the CLI terminates. As a workaround, configure the SNMPv3
view name with less than 30 characters. [PR/424489: This issue has been
resolved.]
„ When you configure SNMPv3 with username, security name, and group name
greater than 30 characters, the configuration does not exist after reboot. As a
workaround, configure SNMPv3 with username, security name, and group
name less than or equal to 30 characters. [PR/424529: This issue has been
resolved.]