Home > CCNP, ONT > ONT – AutoQoS

ONT – AutoQoS

As I mentioned in my previous post, I’ve completed my QoS video series and summarize the QoS part of my studies with two posts: QoS over VPN and AutoQoS.

AutoQoS is an easier way to deploy QoS to your router without knowing everything about QoS. Once again I have flashbacks from the ISCW exam – when you hit the SDM part of the ISCW exam one of the options is AutoSecure. Like with AutoQoS, it is a feature that allow entry-level administrators to apply complex security options and does not require any command line or in-depth knowledge.

AutoQoS present two types of implementation:

  • VoIP – this is a predefined template for voice.
  • Enterprise – the router monitors the network for 3 days and prepare a recommended policy after categorizing the traffic.

When using AutoQoS, NBAR is a key component. On a production router it can be processor intensive and you should consider performance before you apply the command.

Another important configuration with major performance consideration is bandwidth per Interface. QoS templates depend on the configured bandwidth per Interface to perform, correct bandwidth configuration is critical!

These are the requirements for AutoQoS implementation:

  • Recent IOS (12.1\12.2 and later) – later IOS versions have better AutoQoS capabilities
  • CEF must be enabled (ip cef command on global config mode)
  • Bandwidth must be configured on the Interface
  • IP address must be assigned to the Interface
  • Interface must not be shutdown, that is not administratively shutdown.
    The Interface can be in up or down status.
    If the Interface is down the autoqos command will not show up

Implementation for each AutoQoS type is different.
VoIP uses the following command:

auto qos voip

The router will pause for 5-10 seconds to apply the list of commands, adding about 50 commands. Once the process complete the list of new commands can be viewed via show run.

Enterprise uses the following command:

auto discovery qos trust

After three days of monitoring the discovery process has enough data to build the list of commands.
The trust option on this command tell if the router should trust incoming marking.

The command show auto discovery qos has a great useful output that show the results of the collected data. This is like a live data feed you can use to understand what’s going on in your network.

This post conclude the QoS topic of ONT. There are many more details in the book that I did not post here but you should not skip any of them. I’m now moving on to the third and last exam topic: Wireless. Access Points are not as new to me as QoS and they relate to some of my past security related experience so I expect some fun for a change 🙂

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: