Home > Articles > Cisco > CCIE

CCIE Routing & Switching v4.0 Quick Reference: Network Optimization

  • Print
  • + Share This
This quick reference for CCIE Routing and Switching exam-takers covers SLAs, NetFlow, SPAN, RSPAN, and RITE, and Cisco IOS EEM.
This chapter is from the book

IP Service Level Agreement (SLA)

One of the most important aspects in maintaining a network is providing a guarantee of a specific level of service to customers. To ensure that such an agreement is met at all times, IOS provides a mechanism to actively test specific metrics, called IP SLA. When configured, the IP SLA service actively monitors a specific aspect of the network, such as UDP VOIP jitter, DNS response time, ping latency, and so on. If the IP SLA thresholds are not met, IOS sends a notification, such as an SNMP trap or syslog message.

To create a basic IP SLA monitor, the type, options, and frequency must be specified. After the monitor has been created, a schedule is build that kicks off the monitor. To monitor the round-trip response time between a router and an IP, you can use the ICMP Echo Operation:

Router(config)# ip sla monitor <OPERATION #>
Router(config-sla-monitor)# type echo protocol ipIcmpEcho <DESTINATION>
Router(config-sla-monitor)# frequency <SECONDS>
Router(config-sla-monitor)# exit
Router(config)# ip sla monitor schedule <OPERATION #> [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss] [ageout seconds] [recurring]

Some monitors require that a responder be configured (UDP Jitter, UDP Echo, and TCP Connect) on one router:

Router(config)# ip sla monitor responder

Following are other IP SLA monitor operations:

UDP Jitter: type jitter
VOIP Jitter: type
VOIP Gatekeeper Delay: type voip delay gatekeeper registration
UDP Echo: type udp echo
HTTP Connect: type http operation
TCP Connect: type tcpConnect
ICMP Echo: type echo protocol ipIcmpEcho
ICMP Path Echo: type pathEcho protocol ipIcmpEcho
ICMP Path Jitter: type pathJitter
FTP Operations: type ftp
DNS Operations: type dns
DHCP Operations: type dhcp

NetFlow

As packets are sent through router interfaces, they can be classified into flows. This information can be sent from the router to a monitoring server that can provide valuable information about the traffic traversing the network. A flow can be described by a number of fields:

  • Source IP address
  • Destination IP address
  • Source port
  • Destination port
  • Protocol type
  • Type of Service
  • Interface

To determine if a packet belongs in a particular flow, the seven packet fields are inspected. If any one of the fields is different, the packet in question can be considered a new flow. NetFlow statistics can be collected on the following types of networks: IP, Frame Relay, MPLS, and ATM.

To enable NetFlow on an interface, the ip flow command set is used. To configure NetFlow on an interface:

Router(config-if)# ip flow ingress
Egress support can also be added:
Router(config-if)# ip flow egress

To configure the router to export the NetFlow data to a NetFlow server

Router(config)# ip flow-export {destination {ip-address | hostname} udp-port | source {interface-name} | version {1 | [{5 | 9} [origin-as | peer-as] [bgp-nexthop]]} | template {refresh-rate packets | timeout-rate minutes} [options {export-stats | refresh-rate packets | sampler | timeout-rate minutes}]}

To be exported to the NetFlow collection server, the flow must have been exported from the flow cache. Active flows (when there is an ongoing conversation) live for 30 minutes by default before they are exported. Inactive flows, those that have been terminated, are sent after 15 seconds. These values are configurable:

Router(config)# ip flow-cache timeout [active minutes | inactive seconds]

The number of flows that can be collected can be modified with:

Router(config)# ip flow-cache entries <#>

SPAN, RSPAN, and Router IP Traffic Export (RITE)

Viewing the packets between two devices is often the best way to troubleshoot a networking issue. Many organizations deploy network monitoring servers for both network functionality and security purposes. To provide these servers a stream of data from all segments of the network, the Switched Port Analyzer (SPAN) mechanism built into Cisco switches can be used. A SPAN port is a physical port that is configured to send data received on other ports or VLANs. When the data is sent out the SPAN port, it is simply a copy of all the data that has been sent through the configured source ports.

To configure the source of the data to be sent out the SPAN port

Router(config)# monitor source <#> source {interface interface-id | vlan vlan-id} [, | -] [both | rx | tx]

Either a source interface or entire VLAN can be specified. You can use the command multiple times with the same session number if multiple sources are used.

To configure the destination of the data to be sent:

Router(config)# monitor destination <#> destination interface <INT>

The data received in the source interface is sent to the specified destination interface.

The SPAN functionality assumes that the destination of the traffic is directly connected to the switch. If the network is large, it might not be possible to wire a single monitoring station to multiple switches with SPAN ports. Fortunately a special remote SPAN (RSPAN) VLAN can be created that transports the SPAN port information to another switch. This enables an aggregation of monitoring data into a single VLAN that can be sent to the monitoring station.

To configure the RSPAN VLAN, the remote-span command must be specified within the VLAN configuration mode:

Router(config-vlan)# remote-span
Specify the destination of the SPAN port as the remote-span VLAN:
Router(config)# monitor session <#> destination remote vlan <VLAN>

This is great for switches, but is there a similar technology for a router? Yes! The Router IP Traffic Export (RITE) mechanism can export traffic to specific devices defined by the MAC address. To configure, a RITE profile is created and then it’s applied to an interface. The traffic that RITE applies to can be limited by ACLs.

To configure the profile

Router(config)# ip traffic-export profile <PROFILE NAME>
Specify the outgoing interface:
Router(config-rite)# interface <INT>
Specify the MAC address to send the traffic to:
Router(config-rite)# mac-address <MAC>

Specify whether bidirectional traffic is necessary. Without this command, only packets incoming to the router are sent:

Router(config-rite)# bidirectional

Optionally, ACLs can limit the traffic sent:

Router(config)# incoming {access-list {standard | extended | named} | sample one-in-every packet-number}
Router(config)# outgoing {access-list {standard | extended | named}| sample one-in-every packet-number}

Apply the RITE policy to an interface:

Router(config-if)# ip traffic-export apply <POLICY NAME>

Cisco IOS Embedded Event Manager (EEM)

In the normal operations of the switch or router, events such as a CLI command, a syslog message, or an SNMP trap, for example, are constantly occurring. These events are detected by the EEM Event Detectors that send their information to the EEM server. The EEM server can then be programmed to implement an EEM policy. The two different types of EEM policies are applets and TCL scripts, which can be programmed to perform a variety of tasks, such as send syslog messages and SNMP traps, fire off emails, and even open raw sockets.

An applet can be configured directly within the IOS CLI by first creating a policy and registering it:

Router(config)# event manager applet <APPLET NAME>

The applet must be configured to detect a specific event. There are a number of different event detectors, each with their own syntax:

Router(config-applet)# event <EVENT DETECTOR>
  • application: Application-specific event

  • cli: CLI event

  • counter: Counter event

  • interface: Interface event

  • ioswdsysmon: IOS WDSysMon event

  • none: Manually run policy event

  • oir: OIR event

  • snmp: SNMP event

  • syslog: Syslog event

  • timer: Timer event

The actions of the applet that are performed when the programmed event occurs are entered line by line:

Router(config-applet)# action <LABEL> <ACTION>

Some of the actions are predefined within IOS:

  • Executing a Cisco IOS command-line interface (CLI) command (cli)
  • Setting or modifying a named counter (counter)
  • Switching to a secondary processor in a fully redundant hardware configuration (force-switchover)
  • Requesting system information when an event occurs (info)
  • Sending a short e-mail (mail)
  • Manually running an EEM policy (policy)
  • Publishing an application-specific event (publish-event)
  • Reloading the Cisco IOS software (reload)
  • Generating an SNMP trap (snmp-trap)
  • Generating prioritized syslog messages (syslog)

Unfortunately, a TCL script cannot be created on the CLI, it must be uploaded to the router. When uploaded, it must be registered:

Router(config)# event manager policy <FILENAME>
  • + Share This
  • 🔖 Save To Your Account

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Pearson IT Certification products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.pearsonitcertification.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020