I have had this bookmarked for awhile. It helped out today so I figured I would share it. Applies to other phone systems doing HTTP configs.
I am starting an ongoing series involving a semi-static set of devices. These will involve different tutorials on things such as OSPF, cambium configuration, vlans, and other topics. Below is the general topology I will use for this lab network. As things progress I will be able to swap different manufacturers and device models into this scenario without changing the overall topology. We may add a device or two here and there, but overall this basic setup will remain the same. This will allow you to see how different things are configured in the same environment without changing the overall scheme too much.
We will start with very basic steps. How to login to the router, how to set an IP address, then we will move to setting up a wireless bridge between the two routers. Once we have that done we will move onto setting up OSPF to enable dynamic routing. After that the topics are open. I have things like BGP planned, and some other things. If there is anything you would like to see please let me know.
In an article earlier today, I wrote about certifications and the ISP. The biggest area I see folks go wrong when it comes to networking is having a good understanding of design. One of the analogies I like to use is building a house. You have several key roles when you build a house. These can be directly applied to the networking world.
The first is the Architect. Everything starts with this person or team’s vision. The Architect lays out the design and how the network will function. This person needs a wide variety of skills. They know the product lines they are supporting, they know how these products fit into the overall vision of the network, and they know the limitations of what they are working with, to name just a few of their many skills. These are your CCIE and higher level CCNP folks in certification terms. They have enough breadth of knowledge to see the entire picture. Not just what the device in front of them can do. A network architect would know that a certain wireless CPE does not fully support a VPLS tunnel, and would either recommend not using that equipment or come up with a workaround to implement it into the network, if in fact, they were using VPLS. Many large companies have Architects who implement and validate network designs. These are then pushed to the next group of folks to implement.
The “tradesmen” or “tradeswomen” are the ones who actually implement the designs around the Architects blueprints for the network. Just like a house who has carpenters, brick layers, and roofers, so do you have folks who know wireless, routing, security, and other disciplines. These are the folks who can make the machines do what they want them to do. They work off the blueprints to actually make the network talk and function according to the Architects design. these are your CCNA and CCNP level folks. These folks know the equipment configuration in and out. They are the most responsible for making things work, and knowing how to make it work. The more experienced of these folks typically collaborate with the Architects to provide expert opinions on the latest features of the equipment they are implementing or any limitations of the equipment.
Many folks working in the ISP world wear multiple hats at the same time. There is nothing whatsoever wrong with this. You just have to know the limitations of yourself and the things you have to work with. I see multiple illustrations of this on a daily basis. Clients take a router and make it do BGP, OSPF, PPPoE termination, firewall rules, and other things. Sometimes this is a budgetary thing, maybe just a lack of understanding, or it can even be a sales hype thing. however, not having an understanding of the design and architecture of a network can be costly.
Anyone can build a house. Go to the lumberyard and get some materials, some tools, and watch a few YouTube videos. Bam you are set. That will probably work until the first time it rains, or it gets cold. Then you are wondering where your design went wrong. Using plastic on your roof sounded like a good idea until the wind ripped it. Same can be said in networks. Start and always have design considerations in mind. Not just design, but how individual components are best used in that design. Then rely on the tradesmen to implement them. You might be one and the same, but don’t wing it as you go.