Sunday, 14 October 2012

Junos : JTAC Recommended Junos Software Versions



SRX Series Services Gateways
Platform
JTAC Recommended Junos Software by Platform
Release Type
Last updated
SRX100
JUNOS 11.4R5.5
Standard
27 September 2012
SRX110
JUNOS 11.4R5.5
Standard
27 September 2012
SRX210 (*1)
JUNOS 11.4R5.5
Standard
27 September 2012
SRX220
JUNOS 11.4R5.5
Standard
27 September 2012
SRX240
JUNOS 11.4R5.5
Standard
27 September 2012
SRX550
JUNOS 12.1R3.5
Standard
27 September 2012
SRX650
JUNOS 11.4R5.5
Standard
27 September 2012
SRX1400 (*2)
JUNOS 10.4R11.4
Standard
27 September 2012
SRX3400
JUNOS 10.4R11.4
Standard
27 September 2012
SRX3600
JUNOS 10.4R11.4
Standard
27 September 2012
SRX5600
JUNOS 10.4R11.4
Standard
27 September 2012
SRX5800
JUNOS 10.4R11.4
Standard
27 September 2012
(*1) SRX210 recommendation includes old SRX210-B/H/H-POE platforms and new SRX210-BE/HE-HE-POE platforms.
(*2) SRX 1400 deployment as a Chassis Cluster requires version Junos 11.1 and above.

Thursday, 11 October 2012

Junos: RPD crash while performing PIM stress testing


Products Affected:
This issue can affect all Junos routers running Junos OS 11.1R1 or later, configured to utilize the PIM protocol.

Platforms Affected :

  • JUNOS 12.x
  • Security
  • JUNOS 11.x
  • SIRT Security Advisory 



  • PSN Issue :
    During extended stress testing of the PIM protocol, a malformed PIM Hello message triggered an RPD crash. While the crash was caused by a malformed PIM message, simply replaying the crafted packet alone does not lead to the crash. This issue affects both IPv4 PIM and IPv6 PIM.

    Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

    No other Juniper Networks products or platforms are affected by this issue.


    Solution:
    All Junos OS software releases built on or after 2012-10-05 have fixed this specific issue. Releases containing the fix specifically include: 11.4R5, 12.1R3-S2, 12.2R1-S1, and all subsequent releases (i.e. all releases built after 12.2R1-S1).

    Customers can confirm the build date of any Junos OS release by issuing the command 'show version detail'.

    This issue is being tracked as PR 792334 and is visible on the Customer Support website.

    KB16765 - "In which releases are vulnerabilities fixed?" describes which release vulnerabilities are fixed as per our End of Engineering and End of Life support policies.

    Workarounds
    Use access lists or firewall filters to limit access to the router via PIM only from trusted hosts.


    Solution Implementation:
    How to obtain fixed software:

    Security vulnerabilities in Junos are fixed in the next available Maintenance Release of each supported Junos version. In some cases, a Maintenance Release is not planned to be available in an appropriate time-frame. For these cases, Service Releases are made available in order to be more timely. Security Advisory and Security Notices will indicate which Maintenance and Service Releases contain fixes for the issues described. Upon request to JTAC, customers will be provided download instructions for a Service Release. Although Juniper does not provide formal Release Note documentation for a Service Release, a list of "PRs fixed" can be provided on request. 


    While fixes were checked into all non-EOE releases, the root cause of this issue only exists in Junos OS 11.1 and later.
     

    Wednesday, 10 October 2012

    Junos : Junos-Space



    Junos Space is an open, secure, and scalable software platform that allows customers, partners, and developers to build and deploy simple, smart applications that manage and analyze network element data and optimize network infrastructure and operations management.
    The Junos Space Platform allows customers to maximize their network value and scale solutions while reducing complexity. Provided with the platform is a set of robust, out-of-the-box applications that are easy to use and provide business solutions for security, mobility, the data center, and more. In addition, Junos Space offers a developer SDK for companies that want to build customized applications specific to their needs. Junos Space is the platform of choice for companies that want to extract maximum value from their network and deliver solutions that fulfill their business needs.
    Junos Space benefits include:
    • Network-wide visibility and control
    • Quick Scaling of Services
    • Insights for Extending the Platform
    • Reduced OPEX
    • Rapid Deployment of Switch, Router, and Security Infrastructure
    • Reduced time for problem identification and resolution
    Junos Space includes applications for network infrastructure automation. Today these include: Ethernet Design, Security Design, Service Now, Service Insight, Network Activate, QoS Design and Transport Activate.
    The Junos Platform is a layered software platform to run the network and enable applications to interact with the network from the client to cloud. Service providers and enterprises can look beyond building networks made up of individual, disparate boxes toward a unified system for designing and deploying new services in software. The Junos Platform includes the Junos Operating System, Junos Space network application platform, and the Junos Pulse integrated network client.

    Friday, 5 October 2012

    Junos: Send Security Log Messages to a Remote Syslog Server



    The following example specifies that security log messages in structured-data format are sent from 10.30.30.1 to a file named trafficlogs at 192.30.80.76 (remote syslog server).
    1. Specify that the IP address of the source system is 10.30.30.1 (for example, the SRX Series device's loopback or other interface IP address).
    user@host# set security log source-address 10.30.30.1
    1. Specify that the messages are streamed to a file named trafficlogs on a remote log server with an IP address of 192.30.80.76.
    user@host# set security log stream trafficlogs host 192.30.80.76
    1. Starting in Junos 10.0, you can specify that security logs are sent from the data plane to the control plane, which is referred to as 'event' mode.  The default is 'stream' mode, which sends the traffic out the interface ports. You can also specify the rate at which logs are forwarded from the data plane to the control plane. 

      Specify that the security logs are sent at a rate of 500 messages per second:

      user@host# set security log event-rate 500
    To specify that security logs are handled through the eventd process, use the following command:

    user@host# set security log mode event

    Tuesday, 2 October 2012

    Junos : Methods for Configuring Junos OS


    Method
    Description

    Command-line interface
    (CLI)
    Create the configuration for the device using the CLI. You can enter commands from a single command line, and scroll through recently executed commands.
    ASCII file
    Load an ASCII file containing a configuration that you created earlier, either on this system or on another system. You can then activate and run the configuration file, or you can edit it using the CLI and then activate it.

    J-Web graphical user interface (GUI)
    Use the J-Web graphical user interface (GUI) to configure the device. J-Web enables you to monitor, configure, troubleshoot, and manage the router on a client by means of a Web browser. The J-Web GUI is preinstalled on J Series Services Routers and is an optional software package that can be installed on M Series and T Series routers. J-Web is not available for the QFX Series.

    Junos XML management protocol (API)

    Use Junos XML protocol Perl client modules to develop custom applications for configuring information on devices that run Junos OS. Client applications use the Junos XML management protocol to request and change configuration information on Juniper Networks J Series, M Series, and T Series routers. The Junos XML management protocol is customized for Junos OS, and operations in the API are equivalent to those in the Junos OS CLI.

    NETCONF application programming interface (API)

    Use NETCONF Perl client modules to develop custom applications for configuring information on devices that run Junos OS. Client applications use the NETCONF XML management protocol to request and change configuration information on Juniper Networks J Series, M Series, and T Series routers. The NETCONF XML management protocol includes features that accommodate the configuration data models of multiple vendors.

    Configuration commit scripts

    Create scripts that run at commit time to enforce custom configuration rules. Commit scripts are written in Extensible Stylesheet Language Transformations (XSLT). Commit scripts are not available for the QFX Series.

    loading...