jonny18

there should be a script on the desktop "sectionxx.sh" to change the names to the wrong version if you run it on the terminal it should change the names to the wrong versions

there use to be a scenario where the devices managed by dnac did not have the correct management name/ipss, the api link is used to change this to the correct management names/ips. Last time a did the exam this was not requested, however not sure if there is some exam version that this is required, so best is to know how to do it I do recall that there was a new question to configure tacacs via dnac on ise and to enable on line vty only of some routers, but i dont remember the exact wording or how that could be solved

Same, initially the purpose of the virtual-link here eluded me, but i guess in this case is there to transform the inter-area routes into intra-area routes so the ospf cost can work in both cases.

That script will not run properly a space is missing in the print statements: Should be if 'ipv4' in vrf_address_fam: print(cli.execute('show ip route vrf '+vrf_name)) if 'ipv6' in vrf_address_fam: print(cli.execute('show ipv6 route vrf '+vrf_name)) If 3.2 did not change the wording should be fine to do it like this

Was noticing this also, increasing the ospf cost on the sw102/sw202 link this works on traffic between DC->HQ it ill use sw101/sw201 link , however the HQ->DC wil still use the direct link. if the ospf routes on sw102 are checked they still point to eth 0/2 and this is because , the HQ is now in area 1 so any route coming from the sw101/sw101 link towards sw102 is going from area 0 to area 1 (via the port channel between Sw101 and Sw102) so the routes will be O*IA which are less preferable that the O routes coming from the direct link regardless the cost that is set As previously posted an alternative is to setup a virtual-link between sw101 and sw102, this will make the traffic go allways via sw101/201 link as requested, and doesnt go against any statement on the question.

Yes, was not thinking about this properly also. So all ospf speaking devices on HQ (sw101,102,r11,r12) should switch to area 1 with the exception of the uplinks to DC on sw101/102 eth0/2 interfaces which will be on area 0, then in the ospf process of sw101/102 area range 10.1.0.0 255.255.0.0 will summarize the HQ routes towards DC, tested this and seems connectivty is not lost from any of the branch sites towards 10.1.x.x

other thing there might be more that 1 version of the same exam being given to candidates, this was certainty true a coupe of years ago no reason why they would not do it now.

Yeah agree it sounds funny, since as per the question sw201/202 should be in area 0 since they are in the DC, they technically are since only the up-link interfaces are in area 1 however there are not many more options for ABRs that i can think of (perhaps sw101/102 can be abr's alternatively) , its possible this has some influence further down the exam, so labbing up both options i guess is the best

no not this time, i was using outdated dumps. on DNA they ask to configure tacacs on some routers but the config is done over DNA, this is basically integrating dna with ise and enabling tacacs there is a cisco doc has a step by step on how to do this **MPLS** the wording is the same as in old dumps on 1.10 point 2 and 3 - dont think is label range related because there was no range mentioned in the question, makes no sense to configure a random label range Belive the answer is as already seen in a few dumps: mpls label mode all-vrfs protocol bgp-vpnv4 per-vrf mpls label mode all-vrfs protocol bgp-vpnv6 per-vrf no mpls ip propagate-ttl forwarded

Have attended the lab recently and as per the task is the wording is simple like setup hq in ospf area 1 and dc in area 0 make sure only the summary route 10.x.x.x/16 is seen on DC. i don't remember seeing any restrictions for this. So for hq to be in area 1 all l3 ospf devices need to be in area 1 (sw01,sw02,R12,R11) , the dc devices dont change because they already are in area 0, however the sw201,202 link interfaces can change to area 1, if all devices on hq are changed to area 1 dc will receive all the routes as inter-area routes, and sw01 and sw02 become abr'sa and route sumarization can be done there with area 1 range x.x.x.x A virtual-link doesn't feel correct because it is used when there are disjointed areas and in this is not the case. hq and dc area linked directly.

No putty, everything is web based , so the whole scenario is embedded in a webpage access via firefox, telnet sessions, lab guide , network scenarios and questions. the only thing outside in the desktop of the pc is a notpad and a calculator The webpage as soon as the lab starts has a counter with the lab time that when it reaches 0 the lab closes automatically, also if you finish the design stage early you can start the configuration stage, but you dont get any extra time for the configuration stage for it, you just get to start the config stage early but that means you also finish early

Just to share my experience , did an attemtp in Brussels last week: The Pass Enterprise Lab dumps posted in the forum i would say its now arround 70-60%. What i found new: Keep in mind this is what i remember, some of this might already be known *L2* - Spanning Tree is now MST with password showing as 32b hex (password hidden command) - VPT V3 for MST *OSPF* - HQ is now in area 1 - DC is in area 0 - DC should only see 1 10.x.x.x/16 route coming from HQ - OSPF Connection between sw101/sw201 should be used as primary and fallback to sw102/sw202 if it fails (don't remember the exact wording) **SP-BGP** - Asking for Peer-groups between R3/R4/R5 with R3 as RR, and asking to minimize the number of of connections **DNA** - Asking to configure tacacs on ise via dna on the vty lines only of some routes **MPLS** - Limit the number of mps lables - Hide the MPLS lables

@CCIEstudent also preparing for the lab, please add me

@briansmith41 if the group is still open would like to join the group