OVERKILL
$100 Site Donor 2021
So, one of the buildings we own (the company I work for) is leasing out the third floor to four doctors offices.
We wired the building in a way that each floor has its own rack for networking gear with runs between the floors to be utilized if needed. The first two floors are rented to a large company we deal with, they have internal IT, so outside of providing and configuring the Cisco gear for them (a whack of Gig-E 2960's) I don't have to deal with much there.
The third floor is another story
The original plan was a /29 from an ISP we deal with, and then separate VLAN's for the physicians. That didn't end up working out, as some of them wanted to have their own providers.
Ultimately, we ended up with three separate ISP's at this point, with a 4th potentially down the road, as we only have the three tenants right now.
Routing gear is pretty basic (these aren't big offices), using a Cisco 1921.
Switching gear is also pretty basic, using a Catalyst 3560-X.
4x VLAN's were configured on the (gi0/0) LAN interface:
VLAN1 - Management
VLAN2 - Doctor1
VLAN3 - Doctor2
VLAN4 - Doctor3
3x VLAN's were configured on the (gi0/1) WAN interface:
VLAN100 - Doctor1
VLAN101 - Doctor2
VLAN102 - Doctor3
Route maps were used of course for the NAT config.
On the switch:
Port 1 - Trunked to LAN interface on router
Port 2 - VLAN1 (management)
Ports 3 through 12 - VLAN2
Ports 13 through 24 - VLAN3
Ports 25 through 36 - VLAN4
Port 45 - VLAN102 - ISP3
Port 46 - VLAN101 - ISP2
Port 47 - VLAN100 - ISP1
Port 48 - Trunked to WAN interface on router
Now, I could have just put all the VLAN's on int gi0/0 on the router and used the single trunk port and done router on a stick, but I have a personal preference of using separate dedicated physical interfaces for LAN and WAN when possible, and in this case, it was possible. Also, using the two interfaces allows for more bandwidth. Though that isn't really much of an issue here. I'm mentioning this in case somebody asks "why didn't you just run all the VLAN's off the single trunk port?".
What is nice here is that if the building configuration changes, I can move physical ports to different VLAN's to reflect those changes quickly and easily. This will likely prove to be very useful (and a time saver!) going forward. Most of the time, with buildings like these, the tenant provides their own gear, have their own wiring done, have their own closets, and things get butchered. It makes configuration and occupancy changes a longer, drawn out, and more expensive process.
Not an overly complex or expensive network by any means, but I don't post much about my work on here, and this small job certainly has a bit "more to it" than the average consumer stuff usually discussed, so I thought you guys might enjoy it
We wired the building in a way that each floor has its own rack for networking gear with runs between the floors to be utilized if needed. The first two floors are rented to a large company we deal with, they have internal IT, so outside of providing and configuring the Cisco gear for them (a whack of Gig-E 2960's) I don't have to deal with much there.
The third floor is another story
The original plan was a /29 from an ISP we deal with, and then separate VLAN's for the physicians. That didn't end up working out, as some of them wanted to have their own providers.
Ultimately, we ended up with three separate ISP's at this point, with a 4th potentially down the road, as we only have the three tenants right now.
Routing gear is pretty basic (these aren't big offices), using a Cisco 1921.
Switching gear is also pretty basic, using a Catalyst 3560-X.
4x VLAN's were configured on the (gi0/0) LAN interface:
VLAN1 - Management
VLAN2 - Doctor1
VLAN3 - Doctor2
VLAN4 - Doctor3
3x VLAN's were configured on the (gi0/1) WAN interface:
VLAN100 - Doctor1
VLAN101 - Doctor2
VLAN102 - Doctor3
Route maps were used of course for the NAT config.
On the switch:
Port 1 - Trunked to LAN interface on router
Port 2 - VLAN1 (management)
Ports 3 through 12 - VLAN2
Ports 13 through 24 - VLAN3
Ports 25 through 36 - VLAN4
Port 45 - VLAN102 - ISP3
Port 46 - VLAN101 - ISP2
Port 47 - VLAN100 - ISP1
Port 48 - Trunked to WAN interface on router
Now, I could have just put all the VLAN's on int gi0/0 on the router and used the single trunk port and done router on a stick, but I have a personal preference of using separate dedicated physical interfaces for LAN and WAN when possible, and in this case, it was possible. Also, using the two interfaces allows for more bandwidth. Though that isn't really much of an issue here. I'm mentioning this in case somebody asks "why didn't you just run all the VLAN's off the single trunk port?".
What is nice here is that if the building configuration changes, I can move physical ports to different VLAN's to reflect those changes quickly and easily. This will likely prove to be very useful (and a time saver!) going forward. Most of the time, with buildings like these, the tenant provides their own gear, have their own wiring done, have their own closets, and things get butchered. It makes configuration and occupancy changes a longer, drawn out, and more expensive process.
Not an overly complex or expensive network by any means, but I don't post much about my work on here, and this small job certainly has a bit "more to it" than the average consumer stuff usually discussed, so I thought you guys might enjoy it
