Cisco Router – Configure NAT (NAT Overload)
NAT Overload KB ID 0000971 Problem NAT is the process of taking one or more IP addresses and translating it/them into different IP addresses. You may require your router to translate all your internal IP addresses to your public (ISP allocated) IP address. To do that we use a process called NAT Overload. Solution : Nat Overload 1. Connect to the router, and got to enable mode, then global configuration mode. PetesRouter#configure...
Cisco IOS: Ether-Channel Trunks
KB ID 0001533 Problem This is a subject that every time I need to create an Ether-Channel I end up checking beforehand, so it’s about time I wrote it up. We are combining two different things, an Ether-channel, (an aggregation of links) and a Trunk (the ability to carry many VLANS). If you are NOT from a Cisco background then you might want to read though the following post first to avoid confusion about the world...
Setup RANCID and ViewVC (Part Two) Adding Cisco Devices
KB ID 0001332 Problem Before on Part One we setup our RANCID and ViewVC server ready to start backing up our devices, now we will look at adding the devices, and automating the backup process. Solution To add a Cisco device you need to do TWO things*. Firstly you need to add and entry in the ‘router.db’ file that lives in the ‘Group’ folder you created back in part one. Secondly you need to add the access...
Cisco IOS – Enabling LLDP
KB ID 0001289 Problem If you’re running Cisco IOS on all you devices then you can use CDP to see what’s directly connected, (unless you are on a Cisco firewall, but I did say IOS devices). Petes-Switch#show cdp neighbors Capability Codes: R – Router, T – Trans Bridge, B – Source Route Bridge S – Switch, H – Host, I – IGMP, r – Repeater, P – Phone, D – Remote, C...
Cisco IOS – An interface whose trunk encapsulation is “Auto” can not be configured to “trunk” mode.
KB ID0001167 Problem If you try and change a ports status, to make it a trunk port, you may see this error; Petes-Switch(config-if)#switchport mode trunk Command rejected: An interface whose trunk encapsulation is “Auto” can not be configured to “trunk” mode. Trunk Settings I don’t know if this is a throwback to when we had ISL trunking and 802.1q, but you need to specify the encapsulation before you can...