viernes, 9 de agosto de 2013

10 competitors Cisco couldn’t kill off

 
10 competitors Cisco couldn’t kill off
Cisco CEO John Chambers loves to talk about the companies that have tried to compete with Cisco and failed. He refers to companies like 3com, Nortel, Synoptics, etc — and he's right. However, here are 10 companies that have managed to thrive in this era of Cisco dominance and have stood the test of time.



F5 Networks
Load balancing was once considered a market that would rapidly be commoditized, but F5 has managed to create sustainable differentiation as the "L4-7" market has evolved into "Application Delivery Controllers" (ADCs). F5 today has the broadest and deepest application relevancy and can significantly reduce the deployment time and improve the performance of applications, such as SharePoint and Exchange. F5's strategy has worked so well that it caused Cisco to dump its own product in favor of partnering with the No. 2 vendor, Citrix.



Riverbed
One can argue the technical merits of Riverbed's Steelhead versus Cisco's WAAS. From people I have interviewed who have tested the two products, Riverbed can accelerate the performance of a broader range of applications than Cisco, but for many of the core enterprise applications, WAAS is close. However, the real reason many customers buy Riverbed is that it's fast to deploy and easy to manage. I also think Riverbed has done a great job of creating sustainable differentiation, after adding application optimization features over the years.



Juniper
One might look at this and scratch his head, particularly enterprise network managers. While I agree that Juniper's enterprise initiatives have floundered over the years, the company is the de facto No. 2 vendor in the service provider routing space. Cisco and Juniper tend to leap-frog one another in technical superiority. But Juniper's latest releases include the T4000, MX and PTX lines, which are great products and should fuel the Cisco-versus-Juniper SP wars into the foreseeable future.



Arista
How's this for respect? Just a couple of years old and joining the ranks of some long-time Cisco competitors. But Arista seems to have the right mindset to create sustainable differentiation against Cisco in the data center. I had a chance to sit down with Doug Gourlay at Interop and he talked a lot about the value of staying focused. Arista will not venture into markets like ADCs or Metro Ethernet, and will remain laser-focused on data center networking. In fact, he said Arista wants to be to the data center what Juniper is to SP routing, and that's the industry’s de facto No. 2.

 
Polycom
There's arguably no company that did more good for Polycom than Cisco. Cisco's acquisition of Tandberg was supposed to kill off the niche video vendor, correct? That didn't happen, and Cisco's incidentally created a rising tide for both companies. Initially, Polycom wasn't able to do much with the opportunity created by Cisco. In 2010, though, Polycom gutted its management team and CEO Andy Miller re-tooled the company to compete. Some smart people and good execution on Polycom's part, combined with some slow product cycles on Cisco’s part, allowed Polycom to grab some market share.




Aruba Networks
Over the past five years, Aruba's share in Wi-Fi has more than doubled and is now in the high teens. While this hasn't all been at Cisco's expense (Aruba has taken share from Motorola as well), Aruba did implement a "Trojan Horse" strategy with its Airwave management tools a number of years ago. Aruba accepted that Cisco customers buy Cisco hardware, and sold Airwave into those environments to manage the solution. Then the company jumped all over the 802.11n upgrade cycle and used the Airwave footprint to grab some share.

 
Brocade
Brocade has been the market and technology leader in Fibre Channel switching for years now. It was first to have 8 Gig FC, 16 and will likely get to 32 Gig first as well. Despite much of the hype around FCoE, Brocade has kept its focus on delivering faster and more feature-rich FC and now owns about two-thirds of the market. The company appears to have a real shot now, as the shift to fabrics and software defined networks (SDNs) require data networks to be more efficient, resilient and reliable — like a storage fabric.



HP
Under John McHugh, HP Networking came out of nowhere and went from relative obscurity to the No. 2 share vendor almost overnight. HP caught Cisco sleeping and managed to grab some share with value buyers at the access edge. Since then, Cisco has countered with purpose-built products that are more in line with HP pricing. HP then countered by acquiring 3Com to refresh its portfolio and challenge Cisco in the data center. Both companies are building integrated data center "stacks," so we should expect to see the once-great partners remain bitter rivals as the battle for the data center rages on.



Microsoft
There's no vendor that I can remember in recent history that has been more problematic for Cisco than Microsoft. Lync, Microsoft's UC solution, introduced new buyers into the mix that have the same level of loyalty to Redmond as network engineers have to Cisco. Cisco has spent countless hours trying to prove that its solution is not only more reliable than Lync, but cheaper and broader. This may be true, but customers buy Lync because of Microsoft familiarity, and that's a tough value proposition to compete with.



Avaya
Before there was a Cisco-versus-Microsoft battle, there was Cisco versus Avaya. Most people don't realize this, but through its acquisition of Nortel, Avaya actually has over 20% share in voice (not VoIP, but all voice) meaning they control 1 out of every 5 business phones. Under Kevin Kennedy the company has streamlined much of its business, making it more agile than it was in the past, and it will continue to be a threat in the UC space.


 

CCNA 640-802 Lab - Connect, configure, and verify operation status of a device interface

Exam: 640-802

Exam Objective: Connect, configure, and verify operation status of a device interface



Contents

  • Introduction
  • Technology Background
  • Lab Scenario
  • Lab Objectives
  • Lab Solution

Introduction

Two types of interfaces are supported on Cisco Routers: Physical and Virtual interfaces. The types of physical interfaces on a device depend on its interface processors or port adapters. The virtual interfaces that Cisco routers support include subinterfaces and IP tunnels.
Some of the interface types supported by Cisco routers are:
  • Asynchronous serial
  • ATM
  • Dialer
  • Ethernet
  • Fast Ethernet
  • FDDI
  • High-Speed Serial Interface (HSSI)
  • ISDN BRI
  • ISDN PRI
  • Loopback
  • Null
  • Synchronous serial
  • Token Ring
  • Tunnel

Technology Background

Interface configuration is one of the most important parts of configuring a router because without correct configuration the router will not communicate with the network and would not be able to perform any of its function. You can configure Network Layer Address, Layer 2 Protocol, bandwidth and other various things on the interface.
Different routers number their interfaces differently. Some older routers such as the 2500 series number their interfaces as <type><number>. For example: ethernet0 or serial1. New modular routers number their interface as <type> <slot>/<port>. For example: Serial 0/0 or Fastethernet 1/0. This is because they have slots where modules containing interfaces can be added.
To know what interfaces exist on a router; you can use the "show interface" or "show ip interface brief" command. This is what you would see:
Router#show ip interface brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            unassigned      YES manual administratively down down    
FastEthernet0/1            unassigned      YES manual administratively down down    
This tells us that this Router has to FastEthernet interfaces in slot0.
To enter the interface configuration mode use the "interface <type> <slot>/<number>" global configuration command. In the Router mentioned above we have to use the "interface Fastethernet0/0" or "interface fa0/0" command.
By default all interfaces are in "administratively down" status. This means that the interface has been shutdown by configuration. You can bring up the interface using the "no shutdown" interface command.
At this stage the interface is ready for Layer 2 and Layer 3 configuration. Some interfaces like the Serial interface support multiple Layer 2 protocols. On Cisco Routers Serial interfaces support HDLC (default), PPP and Frame Replay protocols at Layer 2. Layer 2 protocol can be changed using the "encapsulation <protocol>" command at the interface level.
Most interfaces support multiple Layer 3 protocols such as IPv4, IPv6, IPX, AppleTalk etc depending on the Layer 2 protocol. IP is the most used Layer 3 protocol and that is what Cisco requires you to know for CCNA.
IP address can be configured on an interface using the "ip address <address> <subnet mask>" command. An interface can have two IP addresses belonging to different subnets. The second IP address can be used using the "ip address <address> <subnet mask> secondary" command. Without the secondary keyword, the command will override previously configured address. If you want to the interface to get an IP address using DHCP then the "ip address dhcp" command can be used.
Special care must be taken with Serial Interfaces because by default these interfaces are configured for Data Terminal Equipment (DTE). This means that they receive clocking from a DCE connected via a CSU/DSU. In the lab when you connect two Routers back-to-back using a Serial cable, you will need to configure one of the interfaces to provide clocking as a DCE. This can be done using the "clock rate <speed in bits>" command.
On all interfaces you can add a description so that you remember where the link connects to in future. This can be done using the "description <text>" command.
Another important interface command is the bandwidth command. It has nothing to do with how data is transferred but the configured bandwidth is used by routing protocols such as EIGRP to calculate the best path to a destination. The significance of it can be realized by understanding that by default the bandwidth of a Serial Interface is 1.544MBps. If you have a 128Kbps connection terminating on the Serial link then the Routing protocol is miscalculating the metrics of the path by using 1.544Mpbs instead of 128Kbps. In such situations correcting the bandwidth is essential. Bandwidth is specified in Kilobits.

Lab Scenario

We need help in initial configuration of routers in our network. Your task is to configure the following in the network shown in Figure 1:
  • Configure the Interface with IP information shown. Fa0/0 of RouterA must belong to both the networks
  • RouterA's s0/0 interface should be configured such that any Cisco Router can connect to it back-to-back using a serial interface. No additional configuration apart from IP address should be required on any device connecting to RouterA's s0/0 interface in such manner.
  • EIGRP should always take the bandwidth of RouterA's s0/0 interface as 512KBps

Figure 1


Lab Objectives


  • Configure IP Addresses on the shown interfaces. RouterA's fa0/0 interface will have a secondary address also
  • Clock rate needs to be configured on Serial1/0 interface of RouterA
  • Bandwidth needs to be configured on Serial1/0 interface of RouterA

Lab Solution


IP address configuration on all the Routers will be done using the following commands:
RouterA(config)#interface s1/0
RouterA(config-if)#ip address 192.168.3.1 255.255.255.0
RouterA(config-if)#no shut
RouterA(config)#interface fa0/0
RouterA(config-if)#ip address 192.168.1.1 255.255.255.0
RouterA(config-if)#ip address 192.168.2.1 255.255.255.0 secondary
RouterA(config-if)#no shut
RouterB(config)#interface fa0/0
RouterB(config-if)#ip address 192.168.1.2 255.255.255.0
RouterB(config-if)#no shut
RouterB(config)#interface fa0/0
RouterB(config-if)#ip address 192.168.2.2 255.255.255.0
RouterB(config-if)#no shut
We need to configure the clock rate on RotuerA's s0/0 interface since it would be connecting back-to-back with other Cisco Routers which will be in DTE mode:
RouterA(config)#interface s1/0
RouterA(config-if)#clock rate 512000

Finally we need to configure the bandwidth on RouterA's s0/0 interface so that EIGRP uses 512Kbps to calculate the route metrics:
RouterA(config)#interface s1/0
RouterA(config-if)#bandwidth 512

We can verify the configuration using the "show ip interface brief" command:
RouterA#show ip interface brief
Interface                  IP-Address      OK? Method Status Protocol
FastEthernet0/0    192.168.1.1      YES manual up        up
Serial1/0               192.168.3.1      YES manual up        up
RouterB#show ip interface brief
Interface                  IP-Address      OK? Method Status Protocol
FastEthernet0/0    192.168.1.2      YES manual up        up
RouterC#show ip interface brief
Interface                  IP-Address      OK? Method Status Protocol
FastEthernet0/0    192.168.2.2      YES manual up        up
References:

Cisco IOS Interface Configuration�Guide - Configuring LAN Interfaces
http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/icflanin.html#wp1012559

CCNA 640-802 Lab - Configure, verify, and troubleshoot RSTP operation

Exam: 640-802

Exam Objective: Configure, verify, and troubleshoot RSTP operation



Contents

  • Introduction
  • Technology Background
  • Lab Scenario
  • Lab Objectives
  • Lab Solution

Introduction

Loops on a layer 2 network can be very dangerous. Spanning Tree Protocol (STP) is used to make the layer 2 network loop free. There are two STP standards defined by IEEE - 802.1d (STP) and 802.1w (Rapid STP). As per IEEE standards, a switch can run one STP instance only. Cisco implements a changed to this by allowing one STP instance per VLAN. 802.1w on Cisco Switches is also known as Per VLAN Rapid Spanning Tree Protocol (PVRST).

Technology Background

STP works by identifying all the links in the network and then blocking all redundant links. To do this STP first elects a Root Bridge. Root bridge is the bridge with the best Bridge ID. Bridge ID is a combination of priority and the base MAC address of the switch. Priority is a configurable value between 0 to 61440 in increments of 4096. The default priority on Cisco switches is 32768. The lower the priority and MAC address the better.
The root bridge is the center of the network. All decisions are taken from the prespective of the root bridge. Switches send Bridge Protocol Data Unit (BPDU) out every port. The BPDUs contain amongst other information the BridgeID. By comparing the BridgeIDs the root bridge is selected.
Once the root bridge is elected the rest of the switches in the network (called Non-root Bridge) will select one port which is their lowest cost way to the Root bridge - This port is called the root port.. The cost is determined by the bandwidth. Then port cost is used to find the lowest cost port connecting a network segement to the switch - This port is called the designated port. Root ports, designated ports and all port on the root bridge are in Forwarding mode. Rest of the ports go into a blocked or alternate mode.
Ports in Forwarding mode will send and receive data and BPDUs. Blocked ports will not send or receive data but will receive BPDUs. Alternate ports are redundant root ports which can be used as soon as the root port goes down.
In Figure 1, if bridge priorities are left at default then, Switch1 will become the root bridge because of the lowest base MAC address. Switch2's root port will be fa0/2 due to lower path cost. Switch3's root port will be fa0/1. Switch2's fa0/1 and Switch3's fa0/2 ports will be the alternate ports.

 

Figure 1
If we need to get Switch2 elected as the root bridge then we will need to lower its priority.
If a host is connected to a host then STP can be disabled on that port by enabling Portfast mode on it. This will ensure that the port goes into forwarding as soon as it comes up.
By default IEEE 802.1d is enabled on most Cisco switches. It can be changed to RSTP with the following global configuration mode command:
spanning-tree mode rapid-pvst
The priority of a Switch can be changed for a VLAN to make it the root bridge of the VLAN using the following command:
spanning-tree vlan <vlan#> priority <priority>
The cost of port can also be modified by using the following interface command:
spanning-tree cost <cost>

To enable portfast on a port use the spanning-tree portfast command on the interface mode.
Spanning tree operation can be verified using the show spanning-tree vlan <vlan#> command

Lab Scenario

We have a network running 802.1D. We need to make the following changes in the network:
  • Use 802.1w instead of 802.1d
  • Make SwitchC the root bridge for VLAN 2
  • There will be a host connect to SwitchB on port fa0/10. Disable STP on this port.
The network is shown in Figure 2.


 

Figure 2

Lab Objectives

  • Enable Rapid PVSTP on all switches
  • Change the priority of SwitchC for VLAN 2
  • Enable Portfast on fa0/10 on SwitchB

Lab Solution

First STP mode needs to be changed on all switches:
SwitchA(config)#spanning-tree mode rapid-pvst
SwitchB(config)#spanning-tree mode rapid-pvst
SwitchC(config)#spanning-tree mode rapid-pvst
SwitchD(config)#spanning-tree mode rapid-pvst
To make SwitchC the root bridge let's change its priority to 4096
SwitchC(config)#spanning-tree vlan 2 priority 4096
Since the rest of the switches are at default priority (32768) SwitchC will become the root bridge for VLAN 2.
To disable STP on fa0/10 on SwitchB, we will need to enable Portfast on it:
SwitchB(config)#interface fa0/10
SwitchB(config-if)#spanning-tree portfast
Let's verify the spanning-tree operations on SwitchC and SwitchA:
SwitchC#show spanning-tree vlan 2
VLAN0002
  Spanning tree enabled protocol rstp
  Root ID    Priority    4098
             Address     0014.a93f.8380
             This bridge is the root
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
  Bridge ID Priority    4098   (priority 4096 sys-id-ext 2)
             Address     0014.a93f.8380
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
             Aging Time 300
Interface           Role Sts Cost      Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Fa0/1               Desg FWD 19        128.17   P2p
Fa0/2              Desg FWD 19         128.20   P2p
SwitchA#show spanning-tree vlan 2
VLAN0002
  Spanning tree enabled protocol rstp
  Root ID    Priority    4098
             Address     0014.a93f.8380
             Cost        23
             Port        1 (FastEthernet0/1)
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
  Bridge ID Priority    32770 (priority 32768 sys-id-ext 2)
             Address     0013.c3e8.2500
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
             Aging Time 300
Interface           Role Sts Cost      Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Fa0/1              Root FWD 19         128.15   P2p
Fa0/2              Altn BLK 100        128.19   P2p
Note in the output that SwitchC is the root bridge and SwitchA's fa0/1 is the root port since its cost is lower that fa0/2's cost.


References:
Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide - Configuring STP
http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/software/release/12.1_22_ea5/configuration/guide/swstp.html