Probably means the port is operating at full capacity/bandwidth. Again, I would check the documentation on that model of switch/device to confirm what that means specifically

Without actually seeing the devices and setup you've got there, I would say check the wireless APs themselves, as they should have their own ground under the UL rating without something having to be improvised. You may also set up surge protectors on the switches the APs are connected to to prevent surges from lightning or other from damaging the devices.

​@@AceNetworker Thank you dear technician for your quick response, Actually,Our APs do not have have grounding cable in AC. I am wondering if using inactive pins as an earthing system! I can connect these 4 inactive pins to switches box... ! Thank you Technician.

You can use either of those types of connections, but here's what you will encounter: You are creating a loop with 2 cables between the same 2 switches. So you'll want to change the Spanning Tree configuration settings on at least 1 of those cable connections to have a higher Spanning Tree "Cost" - This will force the 2 switches to utilize only 1 cable until that connection is not available, then it will start using the 2nd cable only if the first cable (the one with the lower "cost") is not working or connecting. Another option is to NOT use the uplink port and use only 2 normal network interface ports, but configure both of those physical interfaces into a Link Aggregation to function as a single LOGICAL interface. Do that on both switches to have them match each other.

@@AceNetworker Thank you so much Ace for your fast response! I really appreciate your help! Do you have a video that explain Spanning Tree configuration settings or can you suggest me one? You are the best!

I don't have a video explaining the actual settings yet (working on it). But I can list an example here: Setting the cost to 2000 on interface 1/1/1 (or the interface on the cable connection you wanted to be stand-by): switch(config)# interface 1/1/1 switch(config-if)# spanning-tree cost 2000 Setting the cost to the default on interface 1/1/2 (or the interface(s) on the cable you want the switches to utilize primarily): switch(config)# interface 1/1/2 switch(config-if)# no spanning-tree cost You may have different interface numbers and you may have different command parameters, but these are some of the basic commands for Cisco switches.

@@AceNetworker Thanks a lot Ace! .. this is very helpful! ... i assume these commands will work only on managed switches right?

@@mihaitodea8510 Correct. These types of commands will work only on managed switches. Now, if you DON'T add a higher cost to one of those connections, Spanning Tree (assuming these are managed switches, or at least 1 of them is a managed switch) will automatically detect a loop created there and should technically block one of those connections until the 1 working connection doesn't work/connect - at which time it will "unblock" the blocked cable connection/interface and allow it to function. Again, preferable that BOTH switches are managed switches, but if they're not, at least 1 of them needs to be using Spanning Tree for this to work.

You're welcome. Thanks for watching! 😊

You are welcome! Thanks for watching

You are welcome!

Thanks for watching! I'm just (personally) elated this still has validity in today's newer technology, and that Ethernet still uses these basics at its core that I can leave this video up and it still has significant relevance in networking. But again Thank you for watching! And if you'd like anything specific in the realm of networking, let me know on here 😎

You're welcome! Thank you for watching!

Awesome! Glad to hear it! Thanks for watching!

1 - All switches start out defaulted to VLAN 1, so they are all in the same subnet until you configure different VLANs on the interfaces 2 - Depending on the brand of switch, you can usually set up a management IP address in each VLAN. If only one management IP is allowed, then it's usually only allowed in VLAN 1 or you have to create the Management IP address within the subnet of the VLAN you wish to access management of the switch within. For Example: If you wanted to manage/access the switch in VLAN 3, you would create a Management IP address on that switch that is in the same subnet as what the devices on VLAN 3 are using. 3 - Multiple VLANs are usually recommended, especially if you have more than one subnet going across a switch. The Uplink port can also be configured into a different VLAN (other than the default of VLAN 1) and/or be trunked with multiple VLANs Hope that mostly answers your questions. But let me know if I need to clarify anything there. Thanks for watching!

Thanks a lot', your are a geniuos!

You're welcome! Thanks for watching!

Thanks for the sub! And thank you for watching! That is EXACTLY why I create these videos, to simplify it as much as possible for anyone that may be just getting into the field/industry

Thank you! I appreciate that. Thanks for watching!

Working on it. Thanks for watching! I didn't have good sound equipment or software in the beginning, so working with better stuff now 😎

That's good news,@@AceNetworker! I've subscribed!

You're welcome! Thanks for watching!

Great suggestion!

Thank you, and thanks for watching!

Any time! Hope you were able to successfully get them connected. Let me know if you have any issues and I may be able to help further.

You are so welcome! Thanks for watching!

Yep. Exactly the way it was meant to be

Glad it helped!

Computer networks can be set up and configured where they can primarily be managed remotely. However, there is still a lot for techs and admins to do on-site to make sure networks are functioning correctly. If a piece of network hardware stops functioning or a cable goes bad and stops passing traffic, all of the on-site work needs to be done physically by someone present. If you're looking for something remotely from home, my personal suggestion would be to look into something with A.I. (setting up AI profiles, using AI to create sales pieces, social media, etc.) as that's where all of the remote jobs are moving. But just my 2 cents worth. There are still a lot of remote work careers/jobs out there - just probably not in networking. Although, there may be some companies that would pay to "monitor" a network.

Thanks for watching! No IP's will be used on Layer 2 Switches or their connections to each other. Now that is not a "blanket" answer - as you can assign a Management IP Address to a switch for use with pinging it on/over the network and accessing its management configuration. But for the actual connections between switches, they will not need (or use) IP addresses...No. Hope that helps 🙂

Thanks a lot and greetings from Monterrey México ​@@AceNetworker

​@@AceNetworker Got it, that should be if you just use the native vlan 1, but what happen if you need to create and use multiple vlans? how do you should setup the uplinks port in order be able to communicate betwwen the vlans?

You're very welcome! Thanks for watching!

You're welcome!

Great to hear! Thanks for watching!

Great to hear! Thank you for watching! That's exactly my goal with this channel - to explain the "weird" and complicated in networking in a way that makes it SIMPLE and EASY to understand.

Thank you, I appreciate that

That can be the broadcast address for the 192.168.1.0 network. It can potentially be the back door for login to a number of routers.

You're welcome!

Glad it was helpful! Thanks for watching!

Using multiple uplink ports on the same switch can get somewhat complex. Theoretically, you could, but there are a lot of factors to consider: Are both uplink ports on the same LAN/VLAN in the switch configuration? Are they both connected to the same router (for the ISP)? If both are connected to the same router, do they both use the same default gateway IP address? I guess to simplify the answer (or possible solution), consider the uplink ports just like any other ports on the switch for initial considerations (what they're connected to, how the other device(s) handle traffic coming from or going to those uplink ports, etc.). Then also consider that uplink ports are primarily designed to be connected to other switches for Layer 2 traffic, unless this is a Layer 3 capable switch.

@@AceNetworker I believe my BV switch is basically a dumb switch, for lack of better words. It doesn't come with an interface for creating vlans, etc. I believe I've found an inexpensive option that does what I need it to do. The TP-Link ER605 V2 has the multi vlan interface.