Archive for January, 2010

Frequently Used UPS Technologies

As we discussed in a previous post, an Uninterruptible Power Supply (UPS) is an electrical apparatus that provides emergency power to a load when the input power source fails. It does this by means of one or more attached batteries and associated electronic control circuitry. A UPS differs from an auxiliary or emergency power system in that it provides instantaneous (or nearly so) protection from input power interruptions. However, the on-battery runtime of most UPS systems is relatively short, with 5-15 minutes being typical for smaller units. Although this period seems relatively short, it is sufficient to allow time to bring an auxiliary power source on line or to properly shut down the protected equipment.

UPS units are divided into categories that are based on what type, and in some cases the number of different power related problems they address. The general categories of modern UPS systems are online, line-interactive, and standby.

Online
The Online UPS is ideal for environments where electrical isolation is necessary or for equipment that is very sensitive to power fluctuations. Although this technology was once previously reserved for very large installations of 10 kW or more, advances in technology have permitted it to now be available as a common consumer device, usually supplying 500 watts or less. Continue reading ‘Frequently Used UPS Technologies’

Tame the Smartphone Monster

Cisco’s online TechWise TV channel tackles making smartphone users more productive by giving them access to powerful unified communications and collaboration tools on virtually any mobile device. Take control of the mobility revolution and support your smartphone users while maintaining security policies and reducing mobile communications expenses.

Live Cisco WebCast on TelePresence

Cisco is holding a live, 1 hour webcast on Thursday, February 18 to discuss the “Engineering Behind TelePresence”. According to their site:

“If you are like many IT professionals, you might be under the impression that this newest collaboration solution requires that you add tons of bandwidth or overhaul your entire network.

“TechWiseTV shatters these and other myths and reveals the realities of TelePresence deployment. Gain the engineering insights and the technical know-how you need for a smooth and successful implementation. Discover the latest innovations behind the technology and why these have made widespread adoption much simpler than you might have thought.”

Register for free at Cisco’s web site.

The Importance of a UPS

In light of the recent tragic events in Haiti, it might be a good time to review some of the requirements for a well designed Uninterruptible Power Source (UPS) to be included in all of our critical network installations. As a CCNA, we are called upon to help maintain the continued operation of networks during any type of power outage caused by either supplier failures or what is often referred to as “Acts of God,” such as tornados, hurricanes or, in this case, a 7.0 earthquake.

After the devastating earthquake in Haiti, it became obvious that the country had lost most of its ability to provide any type of communications, either within the country or with the rest of the world. This blackout covered all of the most commonly used media, including the Internet, telephone, or radio. Although there were isolated instances of messages getting out, Haiti was essentially isolated, even though surrounded by neighboring countries and possible first responders.

Although we are usually only faced with incoming power source problems, they can, by themselves, bring down any normal network operation. Depending on where we live, we normally refer to our power sources as coming from household power, household electricity, power lines, domestic power, wall power, line power, AC power, city power, street power, and grid power. No matter what we call the “power source”, the loss of any normal supply can leave us with dead equipment. It is important to understand the most commonly used terminology when discussing UPS capability. Continue reading ‘The Importance of a UPS’

Quality of Service Part 8: Congestion Management

In part 8 of this series we are going to unravel the mysteries of congestion management and its four main queuing methods.

Congestion is the result of many factors and can occur in many places on the network. A few of the reasons for congestion are traffic aggregation points, network transit points, speed mismatches, oversubscription, and insufficient packet buffers. Aggressive traffic can fill interface queues and starve more time sensitive flows such as voice and video. Increasing bandwidth is not an adequate fix to solve these issues. By using queuing algorithms to sort traffic and determine a method of prioritizing traffic, the routers can solve specific network traffic issues which in turn can increase network performance.

There are two hardware components; hardware and software. Hardware queuing always uses FIFO queueing, and software queueing is used if the hardware queue is full. A full hardware queue indicates interface congestion and a software queue is used to manage that congestion.

To control congestion, the device using the congestion management tools must determine the buffer queues the packets are to be queued in and what order in which packets are sent out an interface based on the priority assigned to those packets. Congestion management tools must perform these tasks to function as suggested.

  • Create Queues
  • Assign packets to queues based on the packet classification
  • Schedule the packets for transmission

There are four types of queuing mechanisms in the congestion management feature set. Each mechanism is fully customizable to specify different number of queues and the order in which the traffic is serviced. Only one queueing mechanism type is allowed to be configured on each interface.

Continue reading ‘Quality of Service Part 8: Congestion Management’

Quality of Service Part 7: Service Policy

In part six of this blog series we discussed that Marking was considered to be what will be done with the traffic after it has been classified. Now, we will talk about service policy which are considered as the part of QoS where the policy is implemented.

Service Policy
Once you have defined the class-maps, and policy-maps, the policy is attached to the inbound or outbound packets using the service-policy command. It is possible to assign a single policy map to multiple interfaces or assign multiple policy maps to a single interface. There is a maximum of one service-policy command in each direction, inbound and outbound.

Example 1

Class-map ef
      Match access-group 10
!
Class-map af11
      Match access-group 20
!
Class-map af21
      Match access-group 30
!
Policy-map mark_traffic
      Class ef
      Set ip dscp ef
!
      Class af11
      Set ip dscp af11
!
      Class af21
      Set ip dscp af21
!
Interface serial0/0<
      Service-policy input mark_traffic
!
Access-list 10 permit 192.168.100.0 0.0.0.255
Access-list 20 permit 192.168.101.0 0.0.0.255
Access-list 30 permit 192.168.103.0 0.0.0.255

In the next part of this series on QoS we will look at congestion avoidance.

Author: Paul Stryer

References

UCM IP Phone Services, Part 2

One of the most interesting concepts Cisco came up with is to provide the ability to advertise services to all Cluster IP Phone users without requiring them to subscribe to that service. So, if you company has an “all employee” web service, you can quickly setup the service, and then magically have it automatically show up when the employees search for services by selecting the service button on their respective IP Phones.

But, in order to do this, you must select a box at the beginning of the web service creation to enable it for “Enterprise Subscriptions’. We are going to step through how to configure extension mobility service for all IP Phones in the cluster.
Continue reading ‘UCM IP Phone Services, Part 2′

Routing Protocol Families

In packet switching networks, routing directs packet forwarding, the transit of logically addressed packets from their source toward their ultimate destination through intermediate nodes. These nodes are typically hardware devices called routers, bridges, gateways, firewalls, or switches. General-purpose computers with multiple network cards can also forward packets and perform routing, though they are not specialized hardware and may suffer from limited performance.

The routing process usually directs forwarding on the basis of routing tables that maintain a record of the routes to various network destinations. Thus, constructing routing tables, which are held in the routers’ memory, is very important for efficient routing. Most routing algorithms use only one network path at a time, but multipath routing techniques enable the use of multiple alternative paths.

The decision of which routing protocol to configure and use must consider many different factors. One of those factors is which branch or family of routing protocols to implement. There are three main branches or families of routing protocol algorithms; Distance Vector, Link-State, and Balanced Hybrid. Each family has distinct functions and features that can provide a desired functionality. Each family also presents certain deficiencies that may preclude its use in modern networks.

Continue reading ‘Routing Protocol Families’

Routing Protocols Overview

Internet Protocol (IP) routing protocols have one primary goal: to fill the IP routing table with the current best routes it can find. The goal is simple, but the process and options can be complicated. Routing protocols define various ways that routers chat among themselves to determine the best routes to each destination.

As networks grew more complex over time, routers gained both processing power and Random Access Memory (RAM). As a result, engineers designed newer routing protocols, taking advantage of faster links and faster routers, transforming routing protocols.

Routing protocols help routers learn routes by having each router advertise the routes it knows. Each router begins by knowing only directly connected routes. Then, each router sends messages, defined by the routing protocol, that list the routes. When a router hears a routing update message from another router, the router hearing the update learns about the subnets and adds routes to its routing table. If all the routers participate, all the routers can learn about all subnets in an internetwork.

When learning routes, routing protocols must also prevent loops from occurring. A loop occurs when a packet keeps coming back to the same router due to errors in the routes in the collective routers’ routing tables. These loops can occur with routing protocols, unless the routing protocol makes an effort to avoid the loops.

As you pursue your CCNA studies you will find that different authors mix and match the terms routing protocols, routed protocols, and routable protocols. The concepts behind these terms are not difficult but because the terms are so similar, they can be a bit confusing. In all of my posts, as well all Cisco documentation, these terms are generally defined as follows:

  • Routing Protocol – A routing protocol is defined as a set of messages, rules, and algorithms used by routers for the overall purpose of learning routes. This process includes the exchange and analysis of routing information. Each router chooses the best route to each subnet in a process known as path selection and finally places those best routes in its IP routing table. Examples of a routing protocol include RIP, EIGRP, OSPF, and BGP.
  • Routed Protocol and Routable Protocol – Both of these terms refer to a protocol that defines a packet structure and logical addressing, allowing routers to forward or route the packets. Routers forward or route packets defined by routed and routable protocols. Examples include IP and IPX. IPX is a part of the Novell NetWare protocol model.

Even though routing protocols such as RIP are different from routed protocols such as IP, they do work together very closely. The routing process forwards IP packets, but if a router does not have any routes in its IP routing table that match a packet’s destination address, the router discards the packet. Routers need routing protocols so that the routers can learn all the possible routes and add them to the routing table so that the routing process can forward routable protocols such as IP.

A routing protocol’s underlying algorithm determines how the routing protocol does its job. The term routing protocol algorithm simply refers to the logic and processes used by different routing protocols to solve the problem of learning all routes, choosing the best route to each subnet, and converging in reaction to changes in the internetwork. There are three main branches or families of routing protocol algorithms; Distance Vector, Link-State, and Balanced Hybrid.

Continue reading ‘Routing Protocols Overview’

Trunk Groups with Digital Ports

Last blog we looked at how we can use Trunk groups to ease the configuration of dial-peers and digit manipulation using analog FXO ports for an E911 solution. Now let’s take a look on how it can be used for T-1 CAS configurations and ISDN channel selection.

The first example will be T-1 CAS configuration with a provider. Here we want to associate T1 0/0/0 first 12 ports for low priority for outbound calls and last 12 ports for high priority outbound calls. In other words channels 13-24 should be used first to make our outbound calls and the lower channels reserved in case more than 12 outbound calls are needed. Starting with the exhibit below let’s look at a configuration to support this on GW1.

Continue reading ‘Trunk Groups with Digital Ports’

Next Page »