I guess a good way to start would be to make an inventory of the equipment that is being used in your WAN and then get basic knowledge about the functionality of the equipment. Make a backup of the individual device configurations, in order to create a benchmark for a working environment. Usually in a WAN environment you are dealing with providers; I always found it extremely important to have good and accurate contact information of the providers, because 9 out of 10 times, if something goes wrong in the WAN, it is a fault caused by the provider.
I would also get familiar with the WAN technologies used in your WAN, here is a good link from Cisco:
I would also start to make a drawing of the WAN, it is usually just easier to visualize when something goes wrong with a good drawing.
In general I would say there is nothing to be really scared of in a WAN, you will gain a lot of knowledge just by doing the administration and by looking at the configurations. WAN outages are, in my experience, less frequent, but if something happens, you will be a popular guy, because everybody will look for you.
I'm with GP here. Document everything that you can. Backup configurations. I strongly agree that you should make sure all your contact information with providers is updated. Make contact with them and introduce yourself.
Learn and document the topology. Gosh, I guess I'm just repeating the other post.
Congrats on the position. I am hoping to get into some position like this as I am not getting anywhere at my current job.
Scully here. Yes, new user name - long story - go with it. So, I already have the contact info, and copies of the current configs. I need to get a performance baseline and from the sound of it, Visio is going to become my new best friend, but other than that, it almost sounds like I just get to hang out and wait for stuff to break? There's not really a "check this everyday, check this every week" kind of a thing?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...