DRAG DROP -
Drag and drop the snippets onto the blanks within the code to construct a script that adds a prefix list to a route map and sets the local preference. Not all options are used.
Select and Place:
DRAG DROP -
Drag and drop the snippets onto the blanks within the code to construct a script that adds a prefix list to a route map and sets the local preference. Not all options are used.
Select and Place:
The answer is wrong. "running": null Name:100 Permit Match
I would put the following: 1. “running”: null <<<<target running config 2. “name”:”100″, <<<<< prefix list name "100" 3. “seq_no”: <<<<<<< there is no permit command within a route map. this is the only logical selection here. 4. “match”: again within a route map we can either set, or match.
There is permit/deny ‘seq no’ https://www.cisco.com/c/en/us/td/docs/security/asa/asa92/configuration/general/asa-general-cli/route-maps.pdf
link did not work. Please re-paste.
Suggested answer is wrong. If I understand correctly, correct should be: * "running": null * "name":"100" * "permit" * "match" The order in the route-map is a bit odd, the "match" part comes first and after that comes the "set" part... But, in the running-config (that is the target) in IOS this would be: * ip prefix-list 100 seq 10 permit 0.0.0.0/0 <- name of prefix-list is "100" * route-map Routes permit 10 <- "permit" 10 * match ip address prefix-list 100 <- "match" the prefix-list "100" * set local-preference 200
1 - running 2 - name 3 - seq (this is a route-map) 4 - match the acl/prefix for the route-map.
Answer: 1. “running”: null 2. “name”:”100″, 3. “seq_no”: 4. “match”:
- "running": null - "name":"100" - "permit" - "match" TIP: runapem
"running": null Name:100 Permit Match NETCONF <edit-config> Request: CLI Format <?xml version="1.0" encoding="UTF-8"?> <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <running/> </target> <config>
given answer is incorrect "running": null "name":"100", "permit": "match": https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-KB/16-02/5200-1671_K_MRG/content/ch11s06.html#:~:text=If%20the%20route%2Dmap%20has%20more%20than%20one%20sequence%2C%20the%20sequence%20number%20is%20required%3A%20route%2Dmap%20name%20permit%20%7C%20deny%20seq%20seq%2Dnum%20. ...........
i think it's like this running name Seq match
after researches, it must be "running": null "name":"100", "permit": "match":
Is it a Resconf sample?