Specifications

MSVCS_LOG_SESSION_CLOSE system log messages are modified to toggle the order
of the destination IPv4 address and destination port address displayed in the log
messages be consistent and uniform with the formats of the session open and close
logs of MS-DPCs.
The following is the modified format of the MSVCS_LOG_SESSION_OPEN and
MSVCS_LOG_SESSION_CLOSE system log messages:
month date hh:mm:ss syslog-server-ip-address yyyy-mm-dd hh:mm:ss
{NAT-type}<MSVCS_LOG_SESSION_CLOSE or MSVCS_LOG_SESSION_OPEN>:App:
application, source-interface-name fpc/pic/port\address in hexadecimal format
source-address:source-port source-nat-information ->
destination-address:destination-port destination-nat-information (protocol-name)
The following is an example of the session closure message generated for MS-MPCs
and MS-MICs.
Nov 26 13:00:07 10.137.159.1 2014-11-26 07:22:44:
{Dynamic-NAT-64-SS-NHS-1}MSVCS_LOG_SESSION_CLOSE: application:none, ae4.454
2402:8100:1:160:1:2:d384:463c:36822 [49.14.64.37:12261] -> [141.101.120.14]
64:ff9b::8d65:780e:80 (TCP)
Software Installation and Upgrade
•
Upgrading Junos OS in one step (MX Series)—Starting in Junos OS Release 13.3, you
can specify multiple configuration files in one step when you upgrade Junos OS on your
device. When you enter the request system software add or the request system software
validate command, you can use the upgrade-with-config option. You can also use the
upgrade-with-config-format option when the configuration file is in the text format.
Subscriber Management and Services
•
Subscriber login when lawful intercept fails—Starting in Junos OS Release 13.3, when
lawful intercept activation fails during a subscriber login, the subscriber login is not
denied. An SNMP message is still generated that indicates the lawful intercept activation
failed. In Junos OS releases prior to 13.2R2, the subscriber login was denied if lawful
intercept activation failed.
•
Change to test aaa ppp user and test aaa dhcp user commands—Starting in Junos OS
Release 13.3, the test aaa ppp user and test aaa dhcp user commands no longer display
service activation status because service activation is not required in these commands.
In earlier releases, the commands displayed service activation status to indicate whether
service activation failed or succeeded. Service-related RADIUS attribute values are
still displayed.
•
Configuring domain maps to use the default routing instance (MX Series)—Starting
in Junos OS Release 13.3, on MX Series routers you can explicitly configure a domain
map to use the default (master) routing instance for the AAA or subscriber contexts.
This enhancement enables you to configure a domain map to use the default routing
instance in cases where a nondefault routing instance is currently referenced, or in
other scenarios in which you need to explicitly reference the default routing instance.
63Copyright © 2015, Juniper Networks, Inc.
Changes in Behavior and Syntax