Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Changes to and Errata in Documentation for Junos OS Release 12.3 for EX Series Switches

Changes to Junos OS for EX Series Switches Documentation

The following changes have been made to the documentation for Junos OS Release 12.3 for EX Series switches since it was published:

  • The EZ Touchless Provisioning feature has been renamed Zero Touch Provisioning (ZTP). The feature was introduced on EX Series switches in Junos OS Release 12.2. For more information, see Understanding Zero Touch Provisioning.
  • The EX2200 Virtual Chassis and the EX2200-C Virtual Chassis no longer require a software license. The document describing the software licenses for EX Series switches has been updated with this information. See Understanding Software Licenses for EX Series Switches.
  • The request system software validate command is not supported on EX Series switches. The documentation for the request system software validate command has been updated with this information. See request system software validate. [This issue is being tracked by PR/821244.]
  • The request system software add command validate option is not supported on EX Series switches. The documentation for the request system software add command has been updated with this information. See request system software add. [This issue is being tracked by PR/821244.]

Errata

This section lists outstanding issues with the published documentation for Junos OS Release 12.3 for EX Series switches.

  • The EX4500 switch models that support Converged Enhanced Ethernet (CEE) now also support IEEE Data Center Bridging Capability Exchange protocol (IEEE DCBX). These switches previously supported only DCBX version 1.01. The documentation does not reflect this support update. See New Features in Junos OS Release 12.3 for EX Series Switches for more information about the feature.
  • You can configure VN_Port to VN_Port FIP snooping if the hosts are directly connected to the same EX4500 switch. See Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to the Same FCoE Transit Switch) for details about this configuration. The documentation does not yet reflect this support update for EX4500 switches.
  • The documentation for firewall filters on the switches states: By default, a configuration that does not contain either ether-type or ip-version in a term applies to IPv4 traffic. This is incorrect; the configuration must include the match condition ether_type = ipv4 for an Ethernet-switching filter to be applied to only IPv4 traffic.
  • The documentation for the EX9200 switches does not mention that the EX9200 switches do not process media access control (MAC) PAUSE frames.
  • The documentation for the EX9200 switches does not mention that the EX9200 switches calculate the IRB interface family inet MTU by taking the minimum MTU of its Layer 2 members.
  • The documentation for the 12.3 release does not mention the dedicated Virtual Chassis port (VCP) link aggregation feature on EX4550 switches. Starting in Junos OS Release 12.3R2, the dedicated VCPs on EX4550 switches automatically form a link aggregation group (LAG) bundle when two or more dedicated VCPs are used to interconnect the same Virtual Chassis member switches . An EX4550 switch can include up to four dedicated VCPs, and all four dedicated VCPs can act as member links in a LAG when they are used to interconnect to the same Virtual Chassis member switch. Dedicated VCPs and optical ports configured as VCPs cannot be member links in the same LAG and are placed into different LAGs when both are configured to connect to the same EX4550 member switch.
  • The OSPF Configuration Guide incorrectly includes the transmit-interval statement at the [edit protocols ospf area area interface interface-name] hierarchy level. The transmit-interval statement at this hierarchy level is deprecated in the Junos OS CLI.
  • The NETCONF XML Management Protocol Guide incorrectly states that when performing a confirmed commit operation using the <commit> element, the <confirm-timeout> value specifies the number of minutes for the rollback deadline. The value of the <confirm-timeout> element actually specifies the number of seconds for the rollback deadline.

    [NETCONF XML Management Protocol Guide]

  • PR963565 was erroneously added to the Junos OS 12.3 release notes. We removed it from the Outstanding Issues section of the release notes at Release 12.3R12.

Related Documentation

Modified: 2016-06-09