Key Smadi Sonwi Technology News

Posts Tagged ‘switch’

Whether you’re just starting to think about passing the CCNA or CCNP exams, or you’ve been on the certification track for a while, you’ve got to have a plan for success. If you wanted to drive your car from Florida to California, you’d create a plan to get there. You’d get a map and decide how far you wanted to drive per day, and maybe even make some hotel reservations in advance. You certainly wouldn’t get in your car, just drive it randomly down the nearest highway, and hope you ended up in California, would you?

Certainly not. Earning your CCNA certification is the same way. It’s not enough to just study a few minutes “when you feel like it”, or tell yourself that you’ll start studying for the exams “when I get such-and-such done”. The perfect time to start on the road to Cisco certification is not tomorrow, and it’s not next week. It’s today.

You’re much better off with one hour of solid study than three hours of interrupted, unfocused study. Here are a few ways to go about getting the kind of quality study time that will get you to the CCNA or CCNP (or any Cisco certification, for that matter!).

Schedule your study time, and regard this study time as you would an appointment with a client. If you were to meet a customer at 10:00 to discuss a network install, would you just decide not to show up and watch television instead? Not if you wanted the job. The same goes for your study time. That’s an appointment with the most important customer of all – YOU. Read the rest of this entry »

As a CCNA or CCNP, one thing you’ve got to get used to is that change is constant. Cisco regularly issues new IOS versions, not to mention the many different kinds of hardware they produce! While it’s always nice to have “the latest and the greatest” when it comes to routers, switches, firewalls, etc., we have to be prepared for the fact that not all our clients are going to have that latest and greatest!

For instance, there are still quite a few Catalyst 5000 switches out there humming away, and if you’re used to working on IOS-driven switches like the 2950, the same command can have dramatically different results.

Let’s say you’re going to examine the spanning tree protocol (STP) setup of a new client. You’re used to working with newer 2950 switches, and you’ve always run show span on those switches to display spanning-tree information. Then, you run show span on a Catalyst 5000 – and something like this shows:

switch (enable) show span

Destination : Port 6/1

Admin Source : Port 6/2

Oper Source : Port 6/2

Direction : transmit/receive

Incoming Packets: disabled

Learning : enabled

Multicast : enabled

Filter : -

Status : active

Total local span sessions: 1

What’s going on here?

The command show span on a 5000 will not show spanning tree stats – instead, what you’re going to see are statistics relating to Switched Port ANalyzer (SPAN). Surprise!

Consider an example where you’re used to running show span on 5000 switches to see SPAN information. When you run that on a 2950, you know now what you’re going to get – spanning tree information! On a 2950, you’ll need to run show monitor session, followed by the SPAN session number.

SW1#show monitor session 1
Read the rest of this entry »

More CCNA and CCNP candidates than ever before are putting together their own home labs, and there’s no better way to learn about Cisco technologies than working with the real thing. Getting the routers and switches is just part of putting together a great CCNA / CCNP home lab, though. You’ve got to get the right cables to connect the devices, and this is an important part of your education as well. After all, without the right cables, client networks are going to have a hard time working!

For your Cisco home lab, one important cable is the DTE/DCE cable. These cables have two major uses in a home lab. To practice directly connecting Cisco routers via Serial interfaces (an important CCNA skill), you’ll need to connect them with a DTE/DCE cable. Second, if you plan on having a Cisco router act as a frame relay switch in your lab, you’ll need multiple DTE/DCE cables to do so. (Visit my website’s Home Lab Help section for a sample Frame Relay switch configuration.) Read the rest of this entry »

CCNA and CCNP candidates are well-versed in Spanning-Tree Protocol, and one of the great things about STP is that it works well with little or no additional configuration. There is one situation where STP works against us just a bit while it prevents switching loops, and that is the situation where two switches have multiple physical connections.

You would think that if you have two separate physical connections between two switches, twice as much data could be sent from one switch to the other than if there was only one connection. STP doesn’t allow this by default, however in an effort to prevent switching loops from forming, one of the paths will be blocked.

SW1 and SW2 are connected via two separate physical connections, on ports fast0/11 and fast 0/12. As we can see here on SW1, only port 0/11 is actually forwarding traffic. STP has put the other port into blocking mode (BLK).

SW1#show spanning vlan 10

(some output removed for clarity)

Interface Role Sts Cost Prio.Nbr Type

Fa0/11 Root FWD 19 128.11 P2p

Fa0/12 Altn BLK 19 128.12 P2p

While STP is helping us by preventing switching loops, STP is also hurting us by preventing us from using a perfectly valid path between SW1 and SW2. We could literally double the bandwidth available between the two switches if we could use that path that is currently being blocked.

The secret to using the currently blocked path is configuring an Etherchannel. An Etherchannel is simply a logical bundling of 2 – 8 physical connections between two Cisco switches.

Configuring an Etherchannel is actually quite simple. Use the command “channel-group 1 mode on” on every port you want to be placed into the Etherchannel. Of course, this must be done on both switches if you configure an Etherchannel on one switch and don’t do so on the correct ports on the other switch, the line protocol will go down and stay there.

The beauty of an Etherchannel is that STP sees the Etherchannel as one connection. If any of the physical connections inside the Etherchannel go down, STP does not see this, and STP will not recalculate. While traffic flow between the two switches will obviously be slowed, the delay in transmission caused by an STP recalculation is avoided. An Etherchannel also allows us to use multiple physical connections at one time.

Here’s how to put these ports into an Etherchannel:

SW1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

SW1(config)#interface fast 0/11

SW1(config-if)#channel-group 1 mode on

Creating a port-channel interface Port-channel 1

SW1(config-if)#interface fast 0/12

SW1(config-if)#channel-group 1 mode on

Read the rest of this entry »