Welcome to my Cisco page. This is a list of Cisco routers and switches I have worked with over the years. At the bottom of the page you
will find sample configs and guides to various Cisco issues I have resolved.
My first experience working with Cisco equipment was the 700 Series ISDN routers. To be honest, I really disliked it. These things
were extremely difficult to work with. I have since been told that they were actually repackaged with the Cisco label. You had to use this very poorly designed
gui from within Windows, and the configuration was less than intuitive. I managed to get everything working except the
second ISDN channel, which was pretty goofy. I even had the phone company that sold us the routers come out, and their
guys had trouble getting these routers to work. The phone company eventually allowed us to return them, and we built out two linux hosts with 3com ISDN dual-channel modems. Sometimes, the easiest thing is to just build the router you need, I guess ;-)
Before working at IBS, I had worked a little with 2500 Series routers in Florida. Mainly with Supernet and OPC. I never got very
good with them, but started to learn a little bit about working with Ciscos IOS. Since being with IBS, I have worked with
several 2500 series routers, running IOS 10.2 - 11.1. I have also used them as victims for testing exploits that come out
from time to time.
During my years at Solve (IBS), I continued to learn and use Cisco quite frequently. A big part of that
learning was on a couple of 7200vxr routers. These things rock! But for 20k, you would think Cisco would throw
in a faster processor and support for more RAM. At IBS, we had these configured in a redundant setup.
Besides the two connections, we also had these setup to manage a ring of 3500XL Series switches. This made the management of the network very easy to work with.
Cisco really impressed me with these switches. These switches operate at Layer 2 of
the OSI model. Click here
for a diagram. These switches also allow
the network administrator to split the switch up and assign each port to a different block of network addresses (vlan's).
The best thing with these switches is the ISL protocol; Cisco's version of trunking. But if you have some know how with Unix or Linux (and Windows),
you can use 802.1q trunking and use one interface of a computer for multiple connections. This is nothing short of awesome.
For instance, say you manage three network blocks, 24.164.29.x, 24.164.30.x, 24.164.31 (Don't use these, they belong to RoadRunner); You
could actually have one computer with three different ip addresses from three different networks assigned to one interface on that computer.
This is typically not possible with unmanaged switches, and would force you to have three network cards, three ports on a hub or switch and
all the cables in between (Big pain in the butt). So yeah, I really dig these things :).
When I first started at IBS, they where doing quite a bit of networking and several customers where being provided internet
access via 56k and ISDN links. There where also several customers connected via T1 connections. During this time,
I got some exposure to the Cisco 1600 Series of routers. Most of these where providing the connection while a Unix box provided
all the network services. I have also used these in lab environments for testing of protocols such as OSPF and RIP .