This post will show you how to configure a trunk port with a native vlan. In this specific example I am configuring a range of ports, but the commands for an individual interface will be the same once you have entered the config for a particular port.
First enter configuration mode
Now we configure the range of ports. Here we are configuring the range of ports to be a trunk, using dot1q encapsulation. We are allowing vlans 96-99, and vlan 101. We are also setting vlan101 to be the native vlan (no vlan tagging required).
Now we enable spanning-tree portfast and bpduguard
%Warning: portfast should only be enabled on ports connected to a single
host. Connecting hubs, concentrators, switches, bridges, etc… to this
interface when portfast is enabled, can cause temporary bridging loops.
Use with CAUTION
%Portfast will be configured in 13 interfaces due to the range command
but will only have effect when the interfaces are in a non-trunking mode.
In my homelab setup I am dumping syslog on all my devices to my Linux desktop. Have not figure out what I am going to do with it yet, but I see myself either setting up Splunk or Greylog in the near future. Note, a while back I wrote a post on how to configure rsyslog on RHEL 6 – s0 if you are interested you can find that post here.
So lets get down to brass tacks and configure some freaking syslog.
In this instance we are configuring syslog redirection on a Cisco 3548xl switch. Note we are in configure terminal mode.
First we must tell our device to insert timestamps on
s-3550-1(config)#service timestamps log datetime
Now we tell the device where to send the syslog messages
Now we tell the device which log levels to send to the syslog server. In this instance I am sending warning level messages and above. This is pretty verbose, but its a home lab so I am not worried about a slew of log messages pounding my syslog server.
s-3550-1(config)#logging trap warning
For reference I am including the logging levels below.
Now lets review what we have done with the show logging command
So I was planning on blogging about this process simply because I keep forgetting it. Being that I am in the middle of building out my lab, and have a ton of old cisco hardware with ancient images, I have found myself going through the process of updating firmware quite a bit as I tinker with different IOS images.
The first thing that you are going to need is a tftp server, which I am running on my Fedora 18 desktop. Its a very easy setup, and has been simply documented on the link below. Note the article below is specfically about how to setup a tftp server on RHEL, however the process is pretty much the same.
The Cisco Catalyst 3506G is a layer 3 switch which went end-of-life in 2009. For the home lab its a pretty nice switch to have due to its layer 3 support and gigabit speed. Mine is the model seen to the left, 24 gigabit ports and 4x1gb SFP uplinks.
The Cisco Catalyst 3560 is available with one of two software images:
IP Base software includes advanced quality of service (QoS),
rate limiting, access control lists (ACLs), Open Shortest Path First
(OSPF) for routed access, and IPv6 functionality.
IP Services software provides a broader set of
enterprise-class features, including advanced hardware-based IP Unicast
and IP Multicast routing, as well as policy-based routing (PBR).
Anyway, gathered here are a few manadatory resources for the Cisco Catalyst 3560G.