@Antwyon-Givens,

What do real-world switch/router administrators do when they look at an already-installed/configured switch at the new job?

Find what the expectations are for your job role first. Not necessarily just the job description but what is actually expected in terms of who you're supporting and is there a service level you're trying to maintain.

You need to understand the topology, protocols and devices on your network. Without this understanding, the configurations on each router and switch make no sense. You do not know what is allowed on your network and what is not. Context is everything. For example, without these basic networking facts, ACLS, route-maps will mean very little to you.

Also, If you do not know the equipment models and limitation of the devices you're supporting, For example, you may not know there's a difference between a 3750 and a 3570-x and that the replacement of one with the other may not do what you need.

When working with routers and switches, you also need to know what method you will be using to access those devices to verify, troubleshoot and if necessary to change the configuration. For example though, I may be old school and say "console cable all the way." Your company may say, nope...Cisco DNA Center. You've got to know your tools too.

All these things are important if you're not the designer or implementation guy for the network you serve.

@Victor-Rosa-Serrano,

Glad you figured it out.

@Stenly-Mokoginta,

it would be linked to the overview video of ENCOR...there's a link for downloads there.

@Gilson-Banin,

username: ubuntu
password: cisco

@Antwyon-Givens,

There's a couple of different answers and they depend on context!

So, for example in a small company, there may not be any real differences of responsibilities between the CCNA and CCNP. Heck for that fact between Support Desk and Network Infrastructure...You're the "IT Guy". So you may do it all regardless of your certification specialization.

In a large company with well defined Service Management, you may be very limited in your responsibilities. This doesn't mean less responsible but just more specialized and you'll have to perform maybe on an SLA basis...not only structured but interrupt support as well. Let me give you a couple of examples:

As a CCNA, you may be managing lets say the branch office and field installation and maintenance and working with a department to support switch and routing do troubleshooting as well. This may be where you're responsible for cabling, basic configuration and R&R (Remove & Replace) on equipment and escalating. At the CCNP, you may be responsible for troubleshooting what the CCNA is not ready to do but also configuration and optimal routing and network performance. Once again you're goals will be set maybe based on where you work and what needs to be done.

*If we assumed you're a CCNP R+S, you could be hired for your a particular situation like migrating a network routing from EIGRP to OSPF or a rollover to IPv6 in a scheduled time. This would be more contract work and you'll have an SLA. It could be that you'll be providing support services maintaining infrastructure etc.

Many times the difference between the CCNA and CCNP level of knowledge has to do with the WHAT, HOW and WHY. The CCNA knows what to do and HOW to get it done. The CCNP know WHAT, HOW and WHY. The why becomes important is as devices multiple and systems become complex.

HP and Cisco put code in the transceiver on the SFP cables that shows it is their expensive cables. They will work but throw errors. When you call support, they will tell you to buy their cables to solve the problem.

@Gilson-Banin,

I didn't see this post.

B is not true because the Root ID address (MAC address) is different from the Bridge ID address (MAC Address)

E. is not true because the Bridge ID address is not the same as the one listed.

@Gilson-Banin,

Take a moment and look at each of the blueprint topics again. See if you can remember which topics were your difficult topics. And though I cannot answer direct questions about the exam itself. I may be able to help with particular topics.

@Jose-Lopez-Henao,

Is the refplat.iso still attached?

@Daniel-Cook,

The ports do need to be in the same vlans to generate that Virtualized Gateway IP address. If they're in different IP subnets, then it's not possible to do create that virtualized gateway.

Usually, that's why you tend to do FHR (First Hop Redundancy). is because you're trying to provide that redundancy for your gateway. You can do inter-vlan routing between your vlans internally.

Thanks Ronnie. Make sense.

I just saw now more in detail your class on IPSec in the ENCOR CCNP course. Very nice.

Gilson

@Saif-Yaseen,

A PC sends to a destination on another network. It looks it up in its own routing table. When there is no matching layer 3 address in that routing table, it will match it the "default gateway" which is typically the ip address of the router leading out of your LAN.

Does the router have the MAC address of that destination machine...if it's not a router..highly unlikely. So the router instead sends the PC its MAC address instead of the destination MAC address--a proxy mac address. This way your PC1 can forward the frame to the router. The router then can look up the IP address in the routing table to forward your frame to the next router.

Thanks Ronnie

Hi Daniel!

There are two OSPF network types that use the DR/BDR concept. They are the BROADCAST and NBMA (nonbroadcast/multi-access) network types.

Note that if you are using the NMBA network type - you must manually specify neighbors with the OSPF neighbor command.

So the network types that do not use the DR/BDR are:
Point-to-point
Point-to-multipoint
Point-to-multipoint nonbroadcast
Loopback

Yes - is can certainly function as you describe and is therefore much like many third party tools that are available.

Keep in mind that EEM can most likely go above and beyond what these third party tools can do since it is so integrated into the Cisco OS.

Here is a page that will make this tool more clear for you, and allow you to walk through practice examples. All you are going to need is a Cisco router (physical, virtual, or emulated). Have fun!

https://learningnetwork.cisco.com/s/article/understanding-cisco-eem-by-examples-part-1

Ronnie,
Thanks for the AWS info.

Cecil

@Antwyon-Givens,
if CDP is enabled, on the router you can run a show cdp neighbors

@Saif-Yaseen,

You would connect the AP to the same vlan on the switch that the WLC is also connected to. Unless you're trying to directly connect a single AP to the WLC. If that is what you're trying to do, then I cannot do the aggregation.

Here's a link: https://www.cisco.com/c/en/us/support/docs/wireless/8500-series-wireless-controllers/113695-8500-dg-00.html

The very last paragraph

Link Aggregation (LAG)
LAG across the 2x10G interfaces is supported in software versions 7.4 and later. The LAG configuration allows for an active-active link operation with fast failover link redundancy.

Note: The additional active 10G link does not change the total controller network throughput.

@Tito-Luna,

Yes, the protocols used would still work on CAPWAP.

@Victor-Rosa-Serrano,

You will find dhcp-relays in the real world to allow you to send the DHCP Broadcast beyond the Broadcast Domain.
I'm sure that within our Cisco courses you'll see how to configure a DHCP relay agent.

I've never tried to do this the way you're describing.

You'll need a need either a router between the vlans or setup SVIs, then configure the dhcp relay agent correctly.