If you take the honor of choosing a hardware solution for your company's network infrastructure …. LAN or WAN …. the evaluation process may be overwhelming. Without plan there is no loss … and huge migraine.
Keep in mind that it is important to take into account the culture of the business and the qualities it assesses.
For example, if you value self-reliance in IT – or think it's the core of the company – you are more likely to look for the best solution. If IT is less central to the business, the solution can be a well-resourced solution that is easily accessible to experienced people.
Briefly, we can simply create a list of quality properties that we want in a fishing gear manufacturer. To explain which elements should be highlighted in the analysis, is the real challenge and analysis that really makes the decision.
To make matters simpler … focus on the simple attributes mentioned in the rating.
The first answer is the integrity of the company. Most importantly, the company is committed to ensuring that its products are advertised and documented and does not exclude quality assurance.
Another important factor, but is related to customer service and technical support. What's the time for the replacement parts to be defective. If you talk to technical support, you know or have a certificate about the product they support and product platforms.
Provides the above rating of the provider and the rest follows.
Next …. confirms the design requirements of how much network traffic, what traffic (data, VoIP, etc.), the number of remote networks to WAN, future growth, redundancy. Cisco has an online tool that suggests the right tool for responding to these types of questions.
Cost if you can not find an object with Cisco. It is worth evaluating the freezer and foundry according to your needs, and for SMB solutions you may consider open source options such as the Vyatta router / firewall.
Over the years, I've seen people handle this issue in a variety of ways. What I've seen more than not is the desire to make more documentation / analysis of products / due-diligence without focusing on the bets.
Do not complicate the question too much – focus on your individual needs and not exclude your future. What you need is just the ice breaker you need in the future.
The other big question that I'm thinking about is also ignoring the remaining costs associated with purchased equipment. Many companies maintain maintenance every year. Remember that there are costs associated with shutdowns and in some environments this cost is priceless; in some cases it has no effect. Identify these things in the assessment as well as the costs that support the solution.
A quick checklist:
* First, evaluate well-known and proven brands, if possible because the company's continued support and warranty repair and replacement would be available.
* Second – Select the appropriate product level for your work. Do not use additional features if your customer never, never (take care of things to change) use these things. Do not buy a limousine if you only need a bicycle.
* Third – Comparison of Time between Performance, Price and Errors (MTBF). Look for the "end of life" announcements. If you are looking for a bargain or a long lifetime, then that's a good idea.
* Fourth – Google in the product (s) concerned to find reviews and other feedback.
* Fifth – Hands-on assessment with the call for support for final products.
Somewhere there is a need for error or redundancy. If this unit shows a single fault location without backup … then the warranty of the cross ship or local availability may be critical.
Generally ….. it begins with knowledge of your needs. Routers are able to connect networks with different media, even with different networking techniques. For example Fiber-to-UTP and Ethernet-to-ADSL. Obviously, you must have a tool that meets your needs. Will your needs change in the future, and if so, can the device adapt to these changes?
Additional considerations for security … the tool is at the edge of the network, endangering the attack; or is somewhere in the middle of the LAN, merely connecting classes to its core. In the first case, you need something with the firewall function set, and in the second case, a layer switch 3.
Do not forget … the amount of traffic the router has to work on.
If you know what you need and sends your white list to the devices you need, you need to have multiple choices.
Generally speaking, money is a big issue. Because IT is generally considered to be something that costs money. So for the first thoughts the price of the equipment is important.
You must also consider this network environment management. If your initial costs are low, but you spend a lot of time doing it and running, it's difficult to adapt to changes or you've lost network failures for corporate sufferers … your leadership will not be happy. So you have to look at the MTBF numbers, the time between the failure, and how fast you can get a replacement. Some exotic brands can replace the problem.
Truly important routers need to consider a hot standby configuration that spends more, but it happens automatically if an error occurs without anyone knowing that your primary router is dead. Except for you, of course, because you are watching both devices.
Another important element in handling the equipment is how it fits into its IT department. If the network engineering department is a well-trained group of Juniper professionals, buying Cisco adds additional costs to training.
The most interesting message:
First of all, considering all the business considerations taking into account the costs, it makes no sense to look at the top of the market if the business is not going to stretch a point. It is also worth duplicating the cheaper options if your business is ready to pay for the right solution and not the cheapest.
The following consideration depends on the nature of the business, the need for security and reliability. But on a general level, most businesses need something reliable. This means that if you are away or your remote offices require little support, you want something that is big enough to make mistakes. Security often depends on the nature of business protection. Financial and medical information, for example, is seen as a greater risk than most general data. There is always a need for security … but in the same way as always there must be a balance between cost, usability and security. It can never be the only point. It also depends on the size of the IT support organization. Hundreds of people have access to this equipment … or will it be limited to a few selected ones? Do you want to centralize and audit your organization for your organization?
Eligibility is also part of this equation; you might have some great remote management skills or just something that anyone can sustain. If you buy less equipment, it's harder to find the capacity of remote service personnel. However, if you plan your system well … with spare parts and redundant routes … a centralized body can handle this for you. You see that all this depends on the approach we have to the problem.
Next, how high will it be, is there any forecast for growth in the future? There are new applications or new business acquisitions that seriously affect the solution. Will you say that the backbone of a DS3 orchestra comes to the backbone of an OC3 band in a few years?
After examining all the considerations, it must be consistent. Classify different sites and set standards for configuring operating systems, hardware platforms, IP addresses, and web sites. This is great for TCO and makes the network easier and cheaper. Even if you use low standby equipment that replaces a standard item, the kit is much easier if you try to figure out a new configuration when a network is out of sync. This facilitates documentation, which is the essence of world-class architecture. Supporting non-documentation websites is always a nightmare.
Network designers obviously have many brand considerations, but most often recommend CISCO solutions. I recommend CISCO for security, supervision, scalability and eligibility. However, this is pretty expensive to suit your needs.
You have to handle the balance between price and the rest. It may be that a different carrier will arrive with the route, switch, wireless, VOIP, etc. For. The most important thing is trying to handle it. The product price is not the total cost of considering maintenance, support, and reliability in the equation. Sometimes, the most expensive option has much better support costs than the low cost options available.
You choose any solution at the end … hopefully you will need a well thought-out plan in the process that includes the above questions and suggestions.