Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
See matching posts in thread - ================================================...
See matching posts in thread - External (Type 5) Route Summari...
Junos Continuity software is currently supported on the MX240, MX480, MX960, and MX2000 Series 3D Universal Edge Routers. Watch this video to learn more about how Junos Continuity allows you deploy new hardware components in the network without downtime
To review performance, scalability, and power efficiency validation for the MX Series 3D routers with the Junos Trio chipset, see: EANTC testing validation This article provides answers to the most common questions about the Junos Trio chipset on MX Series routers used with Junos OS Release 10.1 and later
VRF Query Table/View VRF: 1 get: routing-instances/instance args key: name view: VRFView VRFView: fields: instance name: name To retrieve entire sections of the configuration and group per instance, the PyEZ techwiki specifies that configuration can be retrieved using Table/View. To Retrieve Using Table/View: Yaml file content (change according to your need): VRF: get: routing-instances/instance args key: name view: VRFView VRFView: fields: instance name: name instance type: instance-type rd type: route-distinguisher/rd-type vrf import: vrf-import vrf export: vrf-export Code: tbl = VRF(dev) #The change is below set the value=True. When Values set to true allows the retrieval of all data not just named-keys tbl.get(values=True) #make sure to pass values=True for item in tbl: print 'instance name:', item.instance name print 'instance type:', item.instance type print 'rd type:', item.rd type print 'vrf import:', item.vrf import print 'vrf export:', item.vrf export The previous code was meant for the xml below (output of "show routing-instances | display xml"). Change the YAML file ccording to your need: <routing-instances> <instance> <name>blue-vr</name> <instance-type>vrf</instance-type> <interface> <name>fe-0/0/2.0</name> </interface> <route-distinguisher> <rd-type>10.58.255.1:37</rd-type> </route-distinguisher> <vrf-import>test-policy</vrf-import> <vrf-export>test-policy</vrf-export> </instance> <instance> <name>red-vr</name> <instance-type>vrf</instance-type> <interface> <name>fe-0/0/3.0</name> </interface> <route-distinguisher> <rd-type>10.58.255.1:38</rd-type> </route-distinguisher> <vrf-import>test-policy</vrf-import> <vrf-export>test-policy</vrf-export> </instance> </routing-instances> #yaml #junospyez #ScriptingHow-To #How-To
1 Comment - sotiris.ioannou@interoute.com says: The answer was provided by Nitin Kumar on the PyEZ Google Group: Please try out this way: Yaml file content (change according to your need): VRF: get: routing-instances/instance args key: name view: VRFView VRFView: fields: instance name: name instance type: instance-type rd type: route-distinguisher/rd-type vrf import: vrf-import vrf export: vrf-export Code: tbl = VRF(dev) #The change is below set the value=True. When Values set to true allows the retrieval of all data not just named-keys tbl.get(values=True) #make sure to pass values=True for item in tbl: print 'instance name:', item.instance name print 'instance type:', item.instance type print 'rd type:', item.rd type print 'vrf import:', item.vrf import print 'vrf export:', item.vrf export Above code was meant for below xml(output of "show routing-instances | display xml"), hence according to your need do change the YAML file: <routing-instances> <instance> <name>blue-vr</name> <instance-type>vrf</instance-type> <interface> <name>fe-0/0/2.0</name> </interface> <route-distinguisher> <rd-type>10.58.255.1:37</rd-type> </route-distinguisher> <vrf-import>test-policy</vrf-import> <vrf-export>test-policy</vrf-export> </instance> <instance> <name>red-vr</name> <instance-type>vrf</instance-type> <interface> <name>fe-0/0/3.0</name> </interface> <route-distinguisher> <rd-type>10.58.255.1:38</rd-type> </route-distinguisher> <vrf-import>test-policy</vrf-import> <vrf-export>test-policy</vrf-export> </instance> </routing-instances> Thanks Sotiris Posted 06:03, 23 Aug 2014
For example, cons ider the show route command. If we wanted to create a table of route entries, the associated YAML would look like the following: 1 -- 2 RouteTable: 3 rpc: get-route-information 4 args key: destination 5 item: route-table/rt 6 key: rt-destination 7 view: RouteTableView I will leave it as an exercise for the reader to examine the specific Junos OS XML command and response output
3 Comments - In the case of "show route" the default argument is the [destination] field
Making Junos Automation Scripts Robust Making your Junos automation scripts robust ensures that you do not need to manually restart your script any time your router reboots or performs an RE switchover. Learn techniques for making your scripts run reliably by reading: Best Practices Series: Make Your Junos Automation Scripts More Robust Making Scripts Robust: Checking Status Making Scripts Robust: Handling Routing Engine Switchovers Making Scripts Robust: Recovering from Power Loss or Routing Engine Restart Making Scripts Robust: Managing Retries #junosautomation #Slax #ExpertAdvice
The Currently In Use value does not account for all of the memory that the routing protocol process uses. This value does not include the memory used for the TEXT and the TACK segments, and a small percentage of memory used by the routing protocol process’s internal memory manager. Further, the RES value includes shared library pages used by the routing protocol process. Any amount of memory freed by the routing protocol process might still be considered part of the RES value
If GRES is enabled, you must install Junos Continuity software package on both primary and the backup Routing Engines to ensure that the line cards remain operational after a Routing Engine switchover
For more information, see Junos OS Routing Protocols Library for Routing Devices #JUNOS #FAQ #JunosOSroutingprotocols