Junos Os Xml Api And Scripting - Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6 Release Note

Copyright © 2011, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
Once the control queue feature is disabled, then the Layer 2 and Layer 3 control packets
are subject to queue selection based on the BA classification. However, the following
control protocol packets are not classified using BA classification, as they might not
have a VLAN, MPLS, or IP header:
Untagged ARP packets
Untagged Layer 2 control packets such as LACP or Ethernet OAM
Untagged IS-IS packets
When the control queue feature is disabled, untagged ARP/IS-IS and other untagged
Layer 2 control packets will go to the restricted queue corresponding to the forwarding
class associated with queue 0.
[Network Interfaces]
Microcode remap (M320 and M120 routers)—M320 routers with E3 type-1 FPCs and
M120 routers with a single type-1 FPC mapped to an FEB, support a new microcode
map to resolve microcode overflow resulting in bad PIC combinations.
On M320 routers, the new microcode map is enabled by default and is the only option
available.
On M120 routers, you can enable the new microcode map by using the
ucode-imem-remap statement at the
M120 routers, the default microcode map remains configured if the
statement is not configured.
[edit chassis]
feb
slot number
ucode-imem-remap
{
}
NOTE: On M120 routers, the FEB is automatically restarted once the
ucode-imem-remap
[System Basics]

Junos OS XML API and Scripting

New Junos OS XML API operational request tag elements—Table 1 on page 16 shows
the Junos OS Extensible Markup Language (XML) operational request tag elements that
are new in Junos OS Release 10.4 along with the corresponding CLI command and
response tag element for each one.
[edit chassis feb slot number]
statement is configured and committed.
hierarchy level. On
ucode-imem-remap
15