Would you like some insight into how other Juniper customers utilize our products? This new Day One book lets you hear directly from our customers.
When our customers write books, they describe practical and proven techniques and tips that are grounded in everyday issues. And this second cookbook from the Juniper Ambassadors program displays 18 use-case solutions complete with configurations, from interop tips in mixed-vendor networks to optimizing network routing, switching, and security performance. You'll want to take this cookbook into the lab and immediately put it to use in your production networks.
OpenFlow v1.3.1 (EX9204, EX9208, EX9214, and MX Series)
OpenFlow offers a lot of wonderful ways to streamline your network.
With OpenFlow v.1.3.1, you will have some great features with which you can streamline and further refine OpenFlow itself. In particular, this new version of OpenFlow can help reduce the number of individual actions you need to apply to a flow by allowing you to categorize actions into groups. Once the groups are created, you can then apply them to one or more flow. You can also use a group to further process packets in a flow and assign more specific forwarding actions to these packets.
Do you dislike wasting time while trying to determine whether alarms are arising at your domain level or at a lower level?
If this is you, it’s time to check out our new ETH-AIS feature for MX Series routers. You can now configure the ETH-AIS feature and sit back and relax while the system takes care of all those pesky alarms.
Mixed Rates on Aggregated Ethernet Bundles (MX Series)
How many times have you wished that you could configure multiple rates on aggregated Ethernet links so that you are using all of the bandwidth available?
Your prayers are answered with the new mixed rates on aggregated Ethernet bundle feature for MX240, MX480, MX960, MX2010, and MX2020 routers. With this feature, you can configure an aggregated bundle with 10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet links according to your requirements.
How many route filters do you have configured on your network? If the answer is a lot, then you are probably concerned about how those filters are affecting network performance. If this is a concern for you, the walkup for route filters feature might help you reduce the number of route filters in your network (and improve your network performance as a result).
By default, Junos OS evaluates multiple route filters in a policy statement by making a route fail if it fails even one filter. Because of this default behavior, some network administrators have created separate policy statements for each route filter.
The walkup feature is for those who wish to change the default behavior of policy statements so that just one match within a policy statement makes it so that route will not be excluded (hidden).
You cannot deploy a robust firewall unless you have determined what you must protect. This new Learn About provides you with all the essential elements that comprise any best-practice network firewall design.
By the end of a few short pages, you’ll know what information to collect, what to do with it, and how to process your network’s demand for both connectivity and security. Whether for the plane, train, or just before that big meeting, learn about what makes great firewall deployments.
Synchronization of Committed Configurations for Satellites in a JNU Group (MX Series)
You no longer need to manually configure a Junos Node Unifier (JNU) controller and all its satellites. A new JNU management daemon—called JNUD—will do the work for you.
This daemon extracts the configuration settings for each satellite in a JNU group from the controller configuration (which contains the configurations for the controller itself and all the satellite configurations) and propagates them to each satellite.
When you commit the configuration on the controller, the JNU management daemon extracts and forwards the satellite configuration to each of the satellites, performs a commit check on all the satellites, and, if all the satellites confirm that the candidate configuration is valid, the new configuration is activated on the controller and all the satellites.
User-Configurable Traffic Class Map (T4000 Routers with Type 5 FPCs)
At times the transmission rate of incoming packets is much higher than the rate that a Flexible PIC Concentrator (FPC) can handle. In these instances, FPCs have a fixed rule that network control packets are the high-priority packets that will go through in such an instance.
Sometimes this is a good rule. However, sometimes you might want to prioritize other packets, such as SSH or FTP, ahead of network control packets.
To overcome this limitation, you can now prioritize and classify traffic entering a PFE by configuring a traffic map that prioritizes packets based on traffic class, such as real-time, network control, or best effort. During any oversubscription, your router would use the traffic map rather than the fixed rule in deciding which packets to prioritize.
VXLAN, which solves the scaling limitations of VLANs while enabling you to segment your network, is now supported on Juniper’s EX9200 platform. This means that now you can theoretically create as many as 16 million VXLANs in an administrative domain on an EX9200.
In addition, you can create smaller Layer 2 domains that are connected over Layer 3 networks. This means that you don’t need to use STP to converge the topology; you can use more robust routing protocols in the Layer 3 network instead.
Have you ever wondered whether you could use a single PIC for two different speeds?
Well, with our new unique PIC P2-10G-40G-QSFPP (for PTX5000 routers), you can do just that. With the correct transceivers, you can operate the PIC in either 10-Gigabit or 40-Gigabit Ethernet speed, giving you total value for the money invested.
A new-generation 100-Gigabit Ethernet OTN PIC (P2-100GE-OTN) for PTX5000 routers has also been introduced. This PIC has 4 ports, each with 100-Gigabit Ethernet of capacity. You can configure them as LAN ports or OTN ports as required.
Both these PICs need to be installed on the FPC2-PTX-P1A FPC (a 1-Tbps FPC).