VJX1000-12.1

VJX1000 Junos®OS 12.1 Release Notes

Release 12.1R114May 2012Revision 2

These release notes accompany VJX1000 and Release 12.1R1 of the Junos OS. They

describe feature support and known problems with the software. VJX Series is a new

family of Junos OS-based virtual routers that run within the Junosphere environment.

For more information about Junosphere, see

http://www.juniper.net/techpubs/en_US/release-independent/junosphere/information-products/pathway-pages/junosphere/product/index.html.

For the latest, most complete information about outstanding and resolved issues with

the JunosOSsoftware, see the JuniperNetworksonlinesoftwaredefect searchapplication

at http://www.juniper.net/prsearch.

You can also find these release notes on the Juniper Networks Junos OS Documentation

Web page, which is located at http://www.juniper.net/techpubs/software/junos/.

Contents VJX1000 Series Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Supported Features for VJX1000 Virtual Devices . . . . . . . . . . . . . . . . . . . . . . . 3

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chassis Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Ethernet Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Packet-Based Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

IPv6 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Layer 2 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Stateless Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Upgrading and Rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1Copyright © 2012, Juniper Networks, Inc.

http://www.juniper.net/techpubs/en_US/release-independent/junosphere/information-products/pathway-pages/junosphere/product/index.html

http://www.juniper.net/prsearch

http://www.juniper.net/techpubs/software/junos/

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Copyright © 2012, Juniper Networks, Inc.2

VJX1000 12.1 Release Notes

VJX1000 Series Release Notes

The VJX Series delivers the software functionality of Juniper routers including

command-line interfaces (CLIs), control plane behavior, protocol operation, andmost

forwarding functions.

• Supported Features for VJX1000 Virtual Devices on page 3

Supported Features for VJX1000 Virtual Devices

This section provides feature support information for VJX1000 Virtual Routers.

• Alarms

• Chassis Management

• Class of Service

• Ethernet Link Aggregation

• File Management

• Packet-Based Processing

• Interfaces

• IPv6 Support

• Layer 2 Mode

• Management

• MPLS

• Multicast

• Routing

• Stateless Firewall Filters

• System Log Files

• Upgrading and Rebooting

• User Interfaces

Alarms

Junos OS supports two types of alarms:

• Chassis alarms indicatea failureon thedeviceor oneof its components. Chassis alarms

are preset and cannot bemodified.

• Systemalarms indicateamissing rescueconfigurationor software license,where valid.

System alarms are preset and cannot bemodified, although you can configure them

to appear automatically in the J-Web or CLI display.

Table 1 on page 4 lists the alarm features that are supported on VJX1000 virtual devices.


VJX1000 Series Release Notes

Table 1: Alarm Support

Supported on VJX1000?Feature

NoChassis alarms

NoInterface alarms

YesSystem alarms

Chassis Management

The chassis properties include the status of virtual hardware components on the device.

Table 2 on page 4 lists the chassis management support on VJX1000 virtual devices.

Table 2: Chassis Management Support


YesChassis management

Class of Service

When a network experiences congestion and delay, some packets must be dropped.

Junos OS class of service (CoS) allows you to divide traffic into classes and offer various

levels of throughput and packet loss when congestion occurs. This allows packet loss

to happen according to the rules you configure.

Table 3 on page 4 lists the CoS features that are supported on VJX1000 virtual devices.

Table 3: CoS Support


YesClassifiers

YesCode-point aliases

NoEgress interface shaping

YesForwarding classes

YesIngress interface policer

YesSchedulers

NoSimple filters

YesTransmission queues

NoTunnels



Table 3: CoS Support (continued)


NoVirtual channels

Ethernet Link Aggregation

Link aggregation groups (LAGs) based on IEEE 802.3admake it possible to aggregate

physical interface links on a device. LAGs provide increased interface bandwidth and link

availability by linking physical ports and load-balancing traffic crossing the combined

interface.

Linkaggregationextends to chassis cluster configurations, allowinga redundantEthernet

interface toaddmultiple child interfaces frombothnodesand therebycreatea redundant

Ethernet interface link aggregation group. For a list of chassis cluster features that are

supported on SRX Series and J Series devices, see Chassis Cluster.

TheLinkAggregationControlProtocol (LACP), asubcomponentof IEEE802.3ad,provides

additional functionality for LAGs. LACP is supported in standalone deployments, where

aggregatedEthernet interfacesare supported, and in chassis cluster deployments,where

aggregated Ethernet interfaces and redundant Ethernet interfaces are supported

simultaneously.

Table 4 on page 5 lists the Ethernet link aggregation features that are supported on

VJX1000 virtual devices.

Table 4: Ethernet Link Aggregation Support

Supported of VJX1000?Feature

Routingmode

NoLACP in chassis cluster mode

YesLACP in standalonemode

NoLACP in transparent mode

YesLink aggregation in standalonemode

NoLayer 3 LAG on routed ports

NoStatic LAG in chassis cluster mode

NoStatic LAG in standalonemode

NoStatic LAG in transparent mode



File Management

You can use the J-Web interface to perform routine file management operations such

as archiving log files and deleting unused log files, cleaning up temporary files and crash

files, and downloading log files from the routing platform to your computer. You can also

encrypt the configuration files with the CLI configuration editor to prevent unauthorized

users from viewing sensitive configuration information.

Table 5 on page 6 lists the file management features that are supported on VJX1000

virtual devices.

Table 5: File Management Support


YesClean up unnecessary files

YesDelete backup software image

YesDelete individual files

YesDownload system files

YesEncrypt/decrypt configuration files

YesManage account files

Packet-Based Processing

A packet undergoes flow-based processing after any packet-based filters and policers

havebeenapplied to it. A flow is a streamof relatedpackets thatmeet the samematching

criteria and share the same characteristics. Junos OS treats packets belonging to the

same flow in the samemanner.

Apacketundergoespacket-basedprocessingwhen it is dequeued from its input (ingress)

interface and before it is enqueued on its output (egress) interface. Packet-based

processingapplies stateless firewall filters andclass-of-service (CoS) features todiscrete

packets. You can apply a firewall filter to an ingress or egress interface, or to both.

Table 6 on page 6 lists flow-based and packet-based features that are supported on

VJX1000 virtual devices.

Table 6: Packet-Based Processing Support


YesAlarms and auditing

NoEnd-to-end packet debugging

NoFlow-based processing



Table 6: Packet-Based Processing Support (continued)


NoNetwork processor bundling

YesPacket-based processing

YesSelective stateless packet-based services

Interfaces

Youmustconfigureeachnetwork interfacebefore it canoperateon thedevice.Configuring

an interface can define both the physical properties of the link and the logical properties

of a logical interface on the link.

Table 7 on page 7 lists the physical and virtual interfaces features that are supported

on VJX1000 Virtual devices.

Table 7: Physical and Virtual Interface Support


No1-Port Gigabit Ethernet SFP Mini-PIM interface

No10-Gigabit Ethernet interface

No10-Gigabit Ethernet Interface SFP+ slots

No10-Gigabit Ethernet interface XFP slots

No3Gwirelessmodem ExpressCard slot interface

No3Gwireless modemUSB-based interface

No3Gwireless modem interface using the CX-111external wireless bridge

NoADSL interface

NoChannelized E1/T1 interface

NoChannelized ISDN PRI interface

NoDOCSIS Mini-PIM interface

NoDS3/E3 interface

NoEthernet interface

NoFast Ethernet interface



Table 7: Physical and Virtual Interface Support (continued)


NoFractional T1/E1 interface

NoFrame Relay interface

NoGigabit Ethernet, Copper (10-Mbps, 100-Mbps,or 1000-Mbps port)

YesGigabit Ethernet interface

NoISDN BRI interface

NoSerial interface

NoSymmetric high-speed digital subscriber line(G.SHDSL) interface

NoT3 interface

NoUSBmodem physical interface

NoVDSL interface

Table 8 on page 8 lists the services features that are supported on VJX1000 devices.

Table 8: Services Support

Supported on VJX1000 Series?Feature

YesAggregated Ethernet interface

NoGRE interface

NoIEEE 802.1X dynamic VLAN assignment

NoIEEE 802.1X MAC bypass

NoIEEE 802.1X port-based authentication controlwith multi-supplicant support

NoInterleaving using MLFR

NoInternally configured interface used by thesystem as a control path between theWXCIntegrated Services Module and the RoutingEngine

NoInternally generated GRE interface (gr-0/0/0)



Table 8: Services Support (continued)


NoInternally generated IP-over-IP interface(ip-0/0/0)

NoInternally generated link services interface

NoInternally generated Protocol IndependentMulticast de-encapsulation interface

NoInternally generated Protocol IndependentMulticast encapsulation interface

NoIP-over-IP encapsulation interface

NoLink fragmentation and interleaving interface

NoLink services interface

YesLoopback interface

YesManagement interface

NoPassive monitoring interface

NoPPP interface

NoPPPoE-based radio-to-router protocol

NoPPPoE interface

NoPromiscuous mode on interfaces

NoProtocol Independent Multicastde-encapsulation interface

NoProtocol Independent Multicast encapsulationinterface

NoRedundant Ethernet interface

NoSecure tunnel interface



IPv6 Support

IPv6 is the successor to IPv4. IPv6 builds upon the functionality of IPv4, providing

improvements to addressing, configuration andmaintenance, and security. These

improvements include:

• Expandedaddressingcapabilities—IPv6providesa largeraddressspace. IPv6addresses

consist of 128 bits, whereas IPv4 addresses consist of 32 bits.

• Header formatsimplification—The IPv6packetheader format isdesigned tobeefficient.

IPv6 standardizes the size of the packet header to 40 bytes, divided into 8 fields.

• Improved support for extensions and options—Extension headers carry Internet-layer

information and have a standard size and structure.

• Improved privacy and security—IPv6 supports extensions for authentication and data

integrity, which enhance privacy and security.

Table 9 on page 10 lists the VJX1000 device features that support IPv6.

Table 9: IPv6 Support


NoIPv6 ALG Support for FTP

Routing, NAT, NAT-PT support

NoIPv6 ALG Support for ICMP

Routing, NAT, NAT-PT support

NoIPv6 NAT

NAT-PT, NAT support

NoIPv6 NAT64

YesIPv6–related protocols

BFD,BGP,ECMPv6, ICMPv6,ND,OSPFv3,RIPng

NoIPv6 ALG support for TFTP

YesSystem services

DHCPv6, DNS, FTP, HTTP, ping, SNMP, SSH,syslog, Telnet, traceroute

IPv6 address configuration

NoAddress books

YesInterfaces

YesSecurity policy rule matching

IPv6 address reporting



Table 9: IPv6 Support (continued)


YesCLI show commands

YesLogging

YesSNMPMIB

IPv6 IDP

NoApplication Identification

NoIDP detector (attack detection and flow)

NoIDP in an active/active chassis cluster

NoIDP logging

NoIDP signature database

Logical systems

NoAdmin operations (Telnet, SSH, HTTPS, and soon.)

NoChassis clusters

NoFirewall authentication

NoFlows

NoInterfaces

NoIPv6 dual-stack lite (DS-Lite)

NoNAT (except interface NAT)

NoRouting (BGP only)

NoScreen options

NoZones and security policies

Layer 2 Mode

Ethernet framescanbe forwarded fromoneLANsegmentorVLANtoanotherbybridging

or switching functions on Juniper Networks devices. Bridging and switching functions are

performed in Layer 2 of the Open Systems Interconnection (OSI) referencemodel—the

Data Link Layer. Though the termsbridgingand switchingare often used interchangeably,



switching functionsare typically performed inhardware in application-specific integrated

circuits (ASICs) while bridging functions are usually performed in software.

Table 10 on page 12 lists the Layer 2 features that are supported on VJX1000 devices.

Table 10: Layer 2 Mode Support


No802.1x port-based network authentication

NoFlexible Ethernet services

NoGeneric VLAN registration protocol

NoIGMP snooping

NoIRB

NoIRB interface

NoLLDP and LLDP-MED

NoMAC limit (Port Security)

NoQ-in-Q tunneling

NoSpanning Tree protocols

NoVLAN retagging

YesVLANs

Management

The Network Time Protocol (NTP) provides themechanisms for synchronizing time and

coordinating time distribution in a large, diverse network. NTP uses a returnable-time

design in which a distributed subnet of time servers operating in a self-organizing,

hierarchical primary-secondary configuration synchronizes local clockswithin the subnet

and tonational timestandardsbymeansofwireor radio. The servers also can redistribute

reference time using local routing algorithms and time daemons.

Table 11 on page 12 lists the management features that are supported on VJX1000

devices.

Table 11: Management Feature Support


YesNTP



MPLS

MPLS provides a framework for controlling traffic patterns across a network. The MPLS

framework allows VJX1000 devices to pass traffic through transit networks on paths

that are independentof the individual routingprotocols enabled throughout thenetwork.

The MPLS framework supports traffic engineering and the creation of virtual private

networks (VPNs). Traffic is engineered (controlled) primarily by the use of signaling

protocols to establish label-switched paths (LSPs). VPN support includes Layer 2 and

Layer 3 VPNs and Layer 2 circuits.

Table 12 on page 13 lists the MPLS features that are supported on VJX1000 devices.

Table 12: MPLS Feature Support


YesCCC

YesCLNS

YesInterprovider and carrier-of-carriers VPNs

YesLayer 2 VPNs for Ethernet connections

YesLayer 3 MPLS VPNs

YesLDP

YesMPLS VPNs with VRF tables on provider edgerouters

YesMulticast VPNs

YesOSPF and IS-IS traffic engineering extensions

YesP2MP LSPs

YesRSVP

YesSecondary and standby LSPs

YesStandards-based fast reroute

YesVPLS

Multicast

Multicast traffic lies between the extremes of unicast (one source, one destination) and

broadcast (one source, all destinations). Multicast is a “one source, many destinations”



method of traffic distribution, meaning that only the destinations needing to receive the

information from a particular source receive the traffic stream.

IP network destinations (clients) do not often communicate directly with sources

(servers), so the routers between source and destination must be able to determine the

topology of the network from the unicast ormulticast perspective to avoid routing traffic

haphazardly. Themulticast router must find multicast sources on the network, send out

copies of packets on several interfaces, prevent routing loops, connect interested

destinationswith theproper source, andkeepthe flowofunwantedpackets toaminimum.

Standard multicast routing protocols provide most of these capabilities.

Table 13 on page 14 lists the multicast features that are supported on VJX1000 Series

devices.

Table 13: Multicast Support


YesFiltering PIM register messages

YesIGMP

YesPIM RPF Routing Table

YesPrimary routingmode(densemodeforLANandsparse mode for WAN)

YesProtocol Independent Multicast Static RP

YesSession Announcement Protocol (SAP)

YesSDP

Routing

Routing is the transmission of data packets from a source to a destination address. For

packets to be correctly forwarded to the appropriate host address, the host must have

a unique numeric identifier or IP address. The unique IP address of the destination host

forms entries in the routing table. These entries are primarily responsible for determining

the path that a packet traverses when transmitted from source to destination.

Table 14 on page 14 lists the routing features that are supported on VJX1000 devices.

Table 14: Routing Support


YesBGP

YesBGP extensions for IPv6



Table 14: Routing Support (continued)


NoCompressed Real-Time Transport Protocol(CRTP)

NoECMP flow-based forwarding

YesInternet Group Management Protocol (IGMP)

YesIPv4 options and broadcast Internet diagrams

YesIPv6 routing, forwarding, global addressconfiguration, and Internet Control MessageProtocol (ICMP)

YesIS-IS

NoMultiple virtual routers

YesNeighbor Discovery Protocol and SecureNeighbor Discovery Protocol

YesOSPF v2

YesOSPF v3

YesRIP next generation (RIPng)

YesRIP v1, v2

YesStatic routing

NoVirtual Router Redundancy Protocol (VRRP)

Stateless Firewall Filters

A stateless firewall filter evaluates the contents of packets transiting the device from a

source to a destination, or the contents of packets originating from, or destined for, the

Routing Engine. Stateless firewall filters applied to the Routing Engine interface protect

the processes and resources owned by the Routing Engine. A stateless firewall filter

evaluates every packet, including fragmented packets.

A stateless firewall filter, often called a firewall filter or access control list (ACL), statically

evaluates packet contents. In contrast, a stateful firewall filter uses connection state

information derived frompast communications and other applications tomake dynamic

control decisions.

Table 15 on page 16 lists the stateless firewall filters support on VJX1000 Series devices.



Table 15: Stateless Firewall Filters Support


YesStateless firewall filters (ACLs)

System Log Files

JunosOSsupports configuringandmonitoringof system logmessages (alsocalled syslog

messages). You can configure files to log systemmessages and also assign attributes,

suchas severity levels, tomessages. TheViewEventspage in the J-Web interfaceenables

you to filter and view system logmessages.

Table 16 on page 16 lists the system log files features that are supported on VJX1000

Series devices.

Table 16: System Log Files Support


YesArchiving system logs

YesConfiguring system logmessages

YesDisabling system logs

YesFiltering system logmessages

NoMultiple system logservers (control-plane logs)

YesSending system logmessages to a file

YesSendingsystemlogmessages toauser terminal

YesViewing data plane logs

YesViewing system logmessages

Upgrading and Rebooting

VJX1000 devices starts (boots) up using its primary boot device.. These devices also

support secondary boot devices, allowing you to back up your primary boot device and

configuration.

As new features and software fixes become available, youmust upgrade your software

to use them. Before an upgrade, we recommend that you back up your primary boot

device.

You can configure the primary or secondary boot device with a snapshot of the current

configuration, default factory configuration, or rescueconfiguration. Youcanalso replicate

the configuration for use on another device, or configure a boot device to receive core

dumps for troubleshooting.



Table 17 on page 17 lists the upgrading and rebooting features that are supported on

VJX1000 Series devices.

Table 17: Upgrading and Rebooting Support


NoAuto recovery

NoBoot device configuration

NoBoot device recovery

YesChassis components control

YesChassis restart

NoDownloadmanager

NoDual-root partitioning

NoIn-band cluster upgrade

NoLow-impact cluster upgrades

YesSoftware upgrades and downgrades

User Interfaces

You can use two user interfaces to monitor, configure, troubleshoot, andmanage your

device—the J-Web interface and the command-line interface (CLI) for Junos OS.

Table 18 on page 17 lists the user interface features that are supported onVJX1000Series

devices.

Table 18: User Interfaces Support


YesCLI

NoJ-Web user interface

YesJunos XML protocol

YesNetwork and Security Manager

NoSRC application

RelatedDocumentation

Junos OS Initial Configuration Guide for Security Devices•

• Junos OSMonitoring and Troubleshooting Guide for Security Devices



http://www.juniper.net/techpubs/en_US/junos12.1/information-products/topic-collections/security/software-all/initial-config/junos-security-swconfig-initial.pdf

http://www.juniper.net/techpubs/en_US/junos12.1/information-products/topic-collections/security/software-all/monitoring-and-troubleshooting/junos-security-monitoring-troubleshooting.pdf

• Junos OS Interfaces and Routing Configuration Guide

• Junos OS Security Configuration Guide



Junos OS Interfaces and Routing Configuration Guide

http://www.juniper.net/techpubs/en_US/junos12.1/information-products/topic-collections/security/software-all/security/junos-security-swconfig-security.pdf

Junos OS Documentation and Release Notes

For a list of related Junos OS documentation, see

http://www.juniper.net/techpubs/software/junos/ .

If the information in the latest release notes differs from the information in the

documentation, follow the Junos OS Release Notes.

To obtain the most current version of all Juniper Networks®technical documentation,

see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/ .

JuniperNetworkssupportsa technicalbookprogramtopublishbooksby JuniperNetworks

engineers and subject matter experts with book publishers around the world. These

books go beyond the technical documentation to explore the nuances of network

architecture, deployment, and administration using the Junos operating system (Junos

OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,

published in conjunction with O'Reilly Media, explores improving network security,

reliability, and availability using Junos OS configuration techniques. All the books are for

sale at technical bookstores and book outlets around the world. The current list can be

viewed at http://www.juniper.net/books .

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

[email protected], or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include

the following information with your comments:

• Document name

• Document part number

• Page number

• Software release version

Requesting Technical Support

Technical product support is available through the JuniperNetworksTechnicalAssistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

or are covered under warranty, and need postsales technical support, you can access

our tools and resources online or open a case with JTAC.

• JTAC policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/customers/support/downloads/710059.pdf.

• Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/.


Junos OS Documentation and Release Notes

http://www.juniper.net/techpubs/software/junos/

http://www.juniper.net/techpubs/

http://www.juniper.net/books

mailto:[email protected]

https://www.juniper.net/cgi-bin/docbugreport/

http://www.juniper.net/customers/support/downloads/710059.pdf

http://www.juniper.net/support/warranty/

• JTAC Hours of Operation —The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides youwith the

following features:

• Find CSC offerings: http://www.juniper.net/customers/support/

• Search for known bugs: http://www2.juniper.net/kb/

• Find product documentation: http://www.juniper.net/techpubs/

• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

• Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

• Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

• Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

• Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

Toverify serviceentitlementbyproduct serial number, useourSerialNumberEntitlement

(SNE) Tool located at https://tools.juniper.net/SerialNumberEntitlementSearch/.

Opening a Casewith JTAC

You can open a case with JTAC on theWeb or by telephone.

• Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .

• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, visit us at

http://www.juniper.net/support/requesting-support.html.

If you are reporting a hardware or software problem, issue the following command from

the CLI before contacting support:

user@host> request support information | save filename

To provide a core file to Juniper Networks for analysis, compress the file with the gzip

utility, rename the file to include your company name, and copy it to

ftp.juniper.net:pub/incoming. Then send the filename, along with software version

information (the output of the show version command) and the configuration, to

[email protected]. For documentation issues, fill out the bug report form located at

https://www.juniper.net/cgi-bin/docbugreport/.



http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/

http://www.juniper.net/techpubs/

http://kb.juniper.net/

http://www.juniper.net/customers/csc/software/

https://www.juniper.net/alerts/

http://www.juniper.net/company/communities/

http://www.juniper.net/cm/

https://tools.juniper.net/SerialNumberEntitlementSearch/

http://www.juniper.net/cm/

http://www.juniper.net/support/requesting-support.html

http://www.juniper.net/support/requesting-support.html

mailto:[email protected]

https://www.juniper.net/cgi-bin/docbugreport/

Revision History

14 May 2012—Revision 2, Junos OS 12.1R1

15 March 2011—Junos OS 12.1R1

Copyright © 2012, Juniper Networks, Inc. All rights reserved.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,transfer, or otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that areowned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.


Requesting Technical Support

VJX1000-12.1

Documents

Transcript of VJX1000-12.1