HP Switches 2530 vs 1950 vs 1920
-
@JaredBusch said:
@scottalanmiller said:
This is why I recommend a single big flat network with a single switching infrastructure. Gets rid of the bottlenecks.
I recommend OBFN because I never know who may follow behind me, and VLAN setup is NOT simple for many in the SMB market.
But that reasoning has nothing to do with actual functionality and broadcast domain max sizes.
That too, easier to set up, easier to make highly performant and way easier to hand off.
-
You can still do stacked switches or a single switch at this size without doing away with VLANs. But VLANs mean you need more expensive switches that have to do more processing. Technically, VLANs would necessitate L3 processing which, in turn, puts the switches at more risk of being overloaded as they are doing a lot more. But normally you overbuy L3 switches compared to L2, but latency still increases.
-
Yeah all that makes sense - Damn it will be a hassle to convert... but It's probably time to consider it. Now would be better than when I move to another 50 IP phones in a few months.
-
What I would recommend considering is this:
- Get a new switch designed around migrating to OBFN (stackable.)
- Slowly move IPs over time to the new IP range as you can do so easily.
- Every time you replace a switch, get another stack member and move things over.
- Profit
-
@Dashrender said:
Yeah all that makes sense - Damn it will be a hassle to convert... but It's probably time to consider it. Now would be better than when I move to another 50 IP phones in a few months.
Yes, when putting in a new switch and when doing a big move would be a good time.
-
Don't just do OBFN, I would really go to the stacked switches too. It means you end up with a "single switch" effectively at the end of the day. One thing to manage, one thing to monitor, one thing to troubleshoot and no bottlenecks between ports.
-
We don't have any VLANs here anywhere. But we do buy very high end switches from both Cisco and HP. We monitor the network heavily rather than block everything with the switches.
-
@thecreativeone91 said:
We don't have any VLANs here anywhere. But we do buy very high end switches from both Cisco and HP. We monitor the network heavily rather than block everything with the switches.
Good way to go. Once you get to any size you need good switches with full monitoring capabilities (fully managed.)
-
Unless the switches can stack over ethernet (I know some can) that won't be possible completely. We have 3 switches in one building and 3 in another (I just remembered about the 6th one).
-
@Dashrender said:
Unless the switches can stack over ethernet (I know some can) that won't be possible completely. We have 3 switches in one building and 3 in another (I just remembered about the 6th one).
At least stack those that you can, lower the total number of bottlenecks.
-
@Dashrender said:
Unless the switches can stack over ethernet (I know some can) that won't be possible completely. We have 3 switches in one building and 3 in another (I just remembered about the 6th one).
You don't usually stack like that anyway. You usually stack your core switches and then use Etherchannel over fiber to each access switch, they are spread out so you can't stack them like you normally would effectively but, you can set them up on Cisco Switches to share configs and VLAN databases.
-
Good to know, thanks.
-
@scottalanmiller said:
What I would recommend considering is this:
- Get a new switch designed around migrating to OBFN (stackable.)
- Slowly move IPs over time to the new IP range as you can do so easily.
- Every time you replace a switch, get another stack member and move things over.
- Profit
Would you start with a whole new IP range for the new network?
For example I currently use
172.168.30.x main network
172.168.40.x remote location 1
172.168.50.x remote location 2
172.168.60.x remote location 3
172.168.70.x remote location 4
172.168.80.x VOIP
172.168.90.x Wireless
172.168.100.x VPNFor my migration should I create something like 192.168.192/22?
We are closing 2 of the remote locations, so I'll still need two of those smaller networks for them. -
Well it depends BUT from looking at yours I would use 172.168.30.0/22 and put all new devices above 172.168.31.0 so that there is no overlap.
-
For security reasons, keeping VLANs or physically separate networks for VPN, DMZ and WiFi might make sense.
-
OK, Let's talk about those.
The VPN currently has to allow access to both the servers and the PC's because we have some people who RDS into their PC at work, and others who just connect to the servers. Unless I do more segregation, there isn't much gained by splitting out VPN from the main network.
DMZ - yeah well that's always good to split, assuming you have one. Which currently I don't. Which begs, for a company my size is it worth the efforts of maintaining a DMZ? I currently host email in house and will for at least the next two years.. after that we might be ready to move to O365.
The WiFi is currently limited only to staff, and even the staff are not allowed to join their personal devices to the network.
I've talked to the board about offering free WiFi to patients, which of course the staff would take full advantage of for their personal stuff too, but so far they've said no. IF I did that, it would definitely be on its own VLAN for that SSID and only allowed out to the internet, and u-turns allowed at the firewall if found to be required.Additionally - is it worth the effort to have servers be in there own VLAN separate from workstations?
-
@Dashrender said:
DMZ - yeah well that's always good to split, assuming you have one. Which currently I don't. Which begs, for a company my size is it worth the efforts of maintaining a DMZ? I currently host email in house and will for at least the next two years.. after that we might be ready to move to O365.
DMZ is necessitated by use, not by size. But often you don't need one, but if you do, obviously you gotta do something to secure it well.
For email as the only thing being hosted, normally I would not bother.
-
Especially if only for two years. How long before you would have it implemented? At least six months, I'm sure. Then the time frame gets less and less.
-
@Dashrender said:
The WiFi is currently limited only to staff, and even the staff are not allowed to join their personal devices to the network.
I've talked to the board about offering free WiFi to patients, which of course the staff would take full advantage of for their personal stuff too, but so far they've said no. IF I did that, it would definitely be on its own VLAN for that SSID and only allowed out to the internet, and u-turns allowed at the firewall if found to be required.Keep in mind not all firewalls/routers allow hairpining.
Anyway I would not ask to put in a Guest network if you didn't have one. We have one here that is separate and we'd love to get rid of it but people think they need it. We block streaming, P2P and most media type things on it though.
-
As part of patient satisfaction I think we should have one. If we put it on it's own internet pipe the cost would be less than $100 a month, but we are moving soon to a new 100/20 pipe from a 10/10 pipe... so we'll have plenty of bandwidth, and with the limitations that creative mentions kinda makes it a non issue.
