Both required a good initial configuration, but when "issues" occurs like link flaps or ISP outage (when MPLS fails), Dynamic may affect Router performance (CPU, Memory, etc).

Using Dynamic Routing; if you have no backup link or you dont have a proper failover configuration with correct threshold, the network updates will cause router performance degradation. It constantly will try to reach destination via default gateway.

Using Static Routing; If you have not a recovery plan or a back door to enter the remote router, you will have zero access to that device until link or issue is restored. Packets will be forwarded to a dead route.

For both, Initial design and configuration is the Key, when issues happens troubleshooting is a nightmare when things are not well done.

@mary said in Switch Interface Properties - CompTIA Network+ N10-007 Prof Messer:

Are port mirrors common for companies that monitor what employees are doing on the network or is something else used?

No, that would be insanely impractical. A port mirror doesn't give you a copy of what someone is actually doing, it gives you a copy of the network traffic. Which is a butt load of disconnected data. It's not like you would know what the end user was doing, only what was being transferred on the wire.

If you think about what you'd see on the wire... a single file transfer or LAN based action might generate a huge amount of traffic. Or going to a website might create a bunch of unintentional traffic from ads that aren't something that the end user cared about. Or a website or app open in the background might generate gops of traffic for something that isn't being used.

It would be able to tell you if the person is on YouTube or Spotify, but would not tell you what they are doing that for or if they are actively "using" that thing. Basically you'd be flooded with information that would take ages to sort through, and the resulting information would tell you essentially nothing about what the end user was doing.

@melvinsilva said in Spanning Tree Protocol - CompTIA Network+ N10-007 Prof Messer:

I had experience when "users" manipulate patch panel or switch and plug both end of the cable (patch cord) to the same switch, creating a physical loop, but STP blocks this and prevent network issues.

Yeah, having switches that have STP turned on by default can be such a life saver in those situations. One place I worked liked to put in unmanaged switches all over the place. Caused me multiple long nights just tracking down which switch was the issue and then finding the loop cable. I knew exactly what was going on, finding it without good documentation and people saying "Oh, there's another network thingy over here." was just so much.... fun.

Is there a limit to how many trunks you can use?

@scottalanmiller said in Protocol Data Units - CompTIA Network+ N10-007 Prof Messer:

@WrCombs said in Protocol Data Units - CompTIA Network+ N10-007 Prof Messer:

Why would you not want to fragment a frame?

Performance. Fragmentation takes time and effort. If you can avoid it, there is less work to be done and, all other things being equal, that means cheaper equipment going faster.

Ah, That makes sense.

It's more purpose based. Unicast is for normal communications. Broadcast is normally reserved for special cases like DHCP where there is no way to do unicast.

Can anyone give me an example of a broadcast domain? This seems a bit basic. It made me think of things like push notifications, so I'm not sure if I'm getting the concept.

Worth noting that STP (Spanning Tree) is common in good switches, but it's also common to have switches that don't have it.

Watched this one during lunch today, I thought This was a good way to explain Network behavor.

I'd like to think of "L3 switch" as being short for switch with layer 3 functions.
Often they are used for routing traffic between VLANs. A router can do that as well but a L3 switch can usually do faster and on more ports at the same time.

Typical is to have a bunch of L2 switches where the end points connect and then the L2 switches are uplinked to one L3 switch that takes care connecting the L2 switches together and do inter-VLAN routing.

There are also L3 Lite switches (aka L2+) which are L2 switches with a limited L3 functionality like for instance static routing.

L3 switches are usually the ones with the most features in all categories so sometimes you need to buy a L3 switch because you are after some other feature, like redundant power or what not.

In small networks L3 switches are usually not needed.

As an example Dell's PowerSwitches for instance are managed switches for building out the network to end points (campus).

They are like this:

N1100 series - L2 switch N1500 series - L3 Lite switch N2000, N3000 series - L3 switch

They have the same OS and work the same but each step up in the series gives you more features and more speed and higher cost.

this is amazingly didactical... really enjoy this.

This video was a great introduction to networks. I like the description of the moving truck, it gives an image to start.

I think that he skips mentioning that PPP, the Point to Point Protocol is not a VPN protocol. Even in the 1990s it was not considered that as it is not virtually private, as a VPN is. It's useful to have mentioned here and the Network+ might require it and it is certainly good to know and understand, but he lists it along with VPN protocols and I didn't hear him ever point out that it isn't a VPN Protocol even though it was the first one mentioned in the VPN Protocol list.