Changes in Default Behavior and Syntax in Junos OS Release 10.3 for J-SRX Series Services Gateways
On J-SRX Series devices, when you configure identical IPs on a single interface, you no
longer get a warning message; instead, a syslog message appears.
Interfaces and Routing
On J-SRX Series devices, to minimize the size of system logs, the default logging level
in the factory configuration has been changed from
On J-SRX100, J-SRX210, and J-SRX240 devices, the autoinstallation functionality on
an interface enables a DHCP client on the interface and remains in the DHCP client
mode. In previous releases, after a certain period, the interface changed from being a
DHCP client to a DHCP server.
On T1/E1 Mini-Physical Interface Module installed on J-SRX210 and J-SRX240 devices,
the Loopback LED is turned ON based on the Loopback configuration as well as when
the FDL loopback commands are executed from the remote-end. The Loopback LED
remains OFF when no FDL Loopback commands are executed from the remote-end,
even though
remote-loopback-respond
On J-SRX100, J-SRX210 and J-SRX240 devices, support for USB auto-installation is
added. This feature simplifies the upgrading of Junos OS images in cases where there
is no console access to a J-SRX Series device located at a remote site. Allows you to
upgrade the Junos OS image with minimum configuration effort by simply inserting a
USB flash drive into the USB port of the J-SRX Series device and performing a few
simple steps. This feature can also be used for reformatting boot device and recovering
J-SRX Series services gateway after a boot media corruption.
J-Web
URL separation for J-Web and dynamic VPN—This feature prevents the dynamic VPN
users from accessing J-Web accidentally or intentionally. Unique URLs for J-Web and
dynamic VPN add support to the webserver for parsing all the HTTP requests it receives.
The webserver also provides access permission based on the interfaces enabled for
J-Web and dynamic VPN.
CLI changes: A new configuration attribute
[edit system services web-management]
when both J-Web and dynamic VPN are enabled on the same interface. The following
example describes the configuration of the new attribute:
web-management {
traceoptions {
level all;
flag dynamic-vpn;
flag all;
}
management-url my-jweb;
http;
https {
system-generated-certificate;
}
limits {
debug-level 9;
}
to
any any
any critical
is configured on the HOST.
is introduced at the
management-url
hierarchy level to control J-Web access
.
13