11 replies
by jonathanty Accepted solution
by Former member Accepted solution
So you can have the cake and Eat it too.
So go for the 10/100/1000 auto switch boxes. :)
Please post back if you have anymore problems or questions.
by jonathanty Accepted solution
by jellimonsta Accepted solution
It depends on the price break for the 10/100 vs. 1GB. If you were quoting Cisco 1GB Ethernet, the price break is quite significant.
If you are using a Cisco VoIP system, I would personally recommend Cisco switches (so you can verify QoS). In that case I would most likely go with 10/100 Ethernet with 1GB uplinks.
General office traffic does not need 1GB, and the video access and Internet will be limited by the bandwidth from the ISP.
You will want to bear in mind what switch connectivity you need, and whether you are going with a collapsed core environment (which I would recommend in this scenario as it sounds small). If you have multiple switches you will most likely want a 1GB fiber backbone between the switches.
If you want to make sure any servers are not bottlenecked you can go with 1GB SFP or GBIC to the server. For a small environment I would just usually recommend you use smaller Cisco 10/100 switches with 1GB SPF and auto-qos for voice.
Good luck.
by jonathanty Accepted solution
by jdclyde Accepted solution
by jonathanty Accepted solution
by dibthree Accepted solution
It would be a huge mistake to install outdated technology. You cannot have too much bandwidth. You can?t go wrong with Gig especially when you consider everything you are going to have running over that network.
Make sure who ever does the cabling has it ?certified? at Cat6. You can spend all the money in the world on expensive Systemax cable, and if it is not installed right you wasted your money. Getting a cable to ?certify? Cat 6 can be difficult. The cable must be installed properly for it to pass the test. Require your cable vendor to give you the test results from a Fluke DTX-1800 (or another one of the level 3 or 4 cable certifiers).
But there are much more important long term issues to think about. Because you are giving internet access to the public you have legal liabilities. There have been some interesting court cases on this.
For your public users connecting in places like your coffee bar:
All you need is one script kid sitting in the coffee bar to have a law suit. Or worse yet someone could sit in the parking lot and steal identities.
How will you be redirecting their browsers to the EULA? Do you know what your EULA needs to say?
How will you handle port security on your wireless network so that users can?t see one another? If I connect to the wireless network and run an Angry-Scan who and what will I see?
Do you have the two networks physically completely separated or is the Church sharing resources like access points, switches, and the internet with the public? If so how will you keep your public users from accessing the Church network?
With an install like this the hardware won?t be cheap but with the liabilities you really don?t want it to be. You want to be able to stand up in court and say you did everything that was possible to protect your public users and to warn them about the risks of using public internet access.
Of course you will also need to keep up the maintenance with the manufacturer to keep the IOS on your hardware up to date. Just like with any other OS once there is a known hack you have to patch it to close the hole. But if you are using Cisco phone systems you already know that.
No matter how much you save by going with cheap hardware it will never make up the cost of a single law suit.
Good luck. Hope this helps.
by jonathanty Accepted solution
by larryd4 Accepted solution
by jonathanty Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending