So, then which MAC address does 255.255.255.255 belong to? And which port is it on?
Thats right, none of them AND all of them. So it gets sent out all ports. Its the broadcast address.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
Stacking Network Switches
- Thread starter Pulserider
- Start date
So, then which MAC address does 255.255.255.255 belong to? And which port is it on?
Thats right, none of them AND all of them. So it gets sent out all ports. Its the broadcast address.
Yes, obviously any network broadcast will go through the switch,
For some reason i was thinking of things from the switch point of view and the traffic it will broadcast.
The amount of broadcasts should be very little though, depending on the arp cache on the IP cameras (im not sure how IP camera's work with this actually or how long they keep an arl entry etc)
Im still not sure why he is mentioning Vlans though for this scenario?
Last edited:
Grep
Senior Member
Just chuck the netgear and get a Juniper and your problems will disappear
Have a single malt ( you need to be brave if you buy Cisco )
Gigabit Cisco Catalyst switches are NOT cheap -- even re-furb
and
Then you may need GBICS or SFP's
There are a few on Bid or Buy -- local is lekker
Gigabit Cisco Catalyst switches are NOT cheap -- even re-furb
and
Then you may need GBICS or SFP's
eCliPSe
Well-Known Member
Well if you are looking for stackable POE switches its not going to be cheap xD If you want cheaper switches that can do the job HP (AKA old 3com) has some good switches for a good price. Also Alcatel isnt to bad ether.There are a few on Bid or Buy -- local is lekker
Gigabit Cisco Catalyst switches are NOT cheap -- even re-furb
and
Then you may need GBICS or SFP's
One does not have to stack or use gbics/sfps, there's always trunking.
eCliPSe
Well-Known Member
Jip. You can create ether channels (trunk ports in some terminology) for cheaper solutions.
Ether channels and trunking are not necessarily the same thing (in cisco terms anyway).
Ether channels combine multiple ports into 1 logical link (this is cool for redundancy without having to worry about STP).
Trunking carries vlan information (multiple vlans),
Usually you would find Ether channel links as trunks, but they dont have to be,
eCliPSe
Well-Known Member
Please read my comment again. The part about " (Trunk ports in some terminology) " . As I have Multiple Cisco Certifications myself and i know the terminology very well thank you. No need to try and educate me
When you are talking about HP/3Com the terminology its called trunks. Aka LACP and not Dot1Q encapsulation.
If you really want to be an@l you can call it "Link Aggregation" as that is what it really is.
Kind Regards
Daniel
Last edited:
Please read my comment again. The part about " (Trunk ports in some terminology) " . As I have Multiple Cisco Certifications myself and i know the terminology very well thank you. No need to try and educate me
When you are talking about HP/3Com the terminology its called trunks. Aka LACP and not Dot1Q encapsulation.
If you really want to be an@l you can call it "Link Aggregation" as that is what it really is.
Kind Regards
Daniel
relax, I didnt say you were wrong, i was just posting that they are not always the same thing and explaining the difference in Cisco terms (hence the in cisco terms).
Arent you missing the ten million cisco certs in your signature?
eCliPSe
Well-Known Member
Im chilled Eh working on my CCIE security then I will do that xD
it also helps my plausible deny-ability for when i am wrong
Eh working on my CCIE security then I will do that xD
it also helps my plausible deny-ability for when i am wrong
lol, when you doing your lab?
I've got my security lab in may when the mobiles come out. My hopes for a first time pass are quite low
Roman4604
Executive Member
This is the main reason you'd want to stack vs. trunk in L2 environments. To eliminate reliance on the scourge that is STP.
With stacking, a single L2/L3 control plane engine is in directing frames/packets on all switches. With trunking you're dealing with multiple independent engines, which adds unnecessary complexity.
eCliPSe
Well-Known Member
GOOD LUCK!!! Yeah I dont think there are many people that passes the lab even less that does it in the first try. I will be doing the lab next year. I am doing my CISSP and then my written CCIE Security this year.
Eish, sorry for causing this terminology bun fight
I think you all know what I meant "Link Aggregation" or whatever specific vendor terminology you wanna use.Never had issues with trunking but then again this was in large campus networks following a access-dual distribution-dual core design
Roman4604
Executive Member
In my experience this is the exact type of environments where STP's idiosyncrasies and complexities raise their heads.
Large access switching domains with dual uplinks all round create 10s if not 100s of Ethernet loops. If your STP is not precisely tuned and managed, some very strange issues can happen. Even with meticulous care, all it takes is the insertion of one switch, slightly misconfigured or with flaky firmware, to disrupt Ethernet forwarding in the domain e.g. two switches get into a pissing contest about who's the root bridge.
These days there are enough options to design Ethernet access networks without having to rely on STP for Ethernet diversity re-routing. Most common method is to use multi-chassis Etherchannel type functionality like stacked switches, VSS or vPC. Obviously one can also go for a pure L3 access layer, but this limits flexibility.
Something like this,
12 more 10/100 access switches connected to distribution stack (plus AP's and wireless controller plus a few routers but was to lazy to add them all now) will be upgraded to 10/100/1000 access switches soon, but need to upgrade links between core and distribution to 10Gb X 4 before that happens
12 more 10/100 access switches connected to distribution stack (plus AP's and wireless controller plus a few routers but was to lazy to add them all now) will be upgraded to 10/100/1000 access switches soon, but need to upgrade links between core and distribution to 10Gb X 4 before that happens
Access and control was tight, limited to a few individuals, someone willy nilly plugging a switch in would result in severe disciplinary action. We never had issues, probably because we were aware of the pitfalls and were very thorough with our planning and configs. Even if something were to happen it would only have occurred outside of operational/business hours during a scheduled maintenance period after you jumped though countless change control authorization procedures.
But yes it can get very nasty if you stuff up.