P2P Protocol Detection Software Versions - Cisco ASR 5000 series Product Overview

Hide thumbs Also See for ASR 5000 series:
Table of Contents

Advertisement

Peer-to-Peer Overview
In the earlier releases, the P2P detection logic was part of the chassis software load (ASR 5000 software), to continue to
detect new traffic patterns based on the changing traffic characteristics, operators needed to upgrade the complete
software with the updated logic.
This release supports dynamic upgrades of the P2P detection logic (signatures) alone on an active ASR 5000 without
warranting a full software upgrade, and hence without a software restart or reboot. This is implemented through
signature files.
Important:
Bittorrent, DirectConnect, eDonkey, Gnutella, Skype, and Yahoo.
Important:
update the detection logic in use on a system.
In an initial software build, all the detection logic is embedded in the code. If in a subsequent software build, there are
updates to the detection logic, the changes are made available as a P2P signature file. If the initial build supports the
Dynamic Signature Updates feature, this signature file can be loaded on the system to update the detection capability.
In case a P2P signature file is already available for a software build, when the configuration file is loaded on the system,
it will take the lastest version. If a different P2P signature file is manually loaded on that system, every time the system
reboots, it will load the default version.
A P2P signature file can support upgrade for multiple P2P protocols that are enabled for dynamic upgrade. Operators
can selectively upgrade the detection for specific protocol(s). Patches can be rolled down with out any negative impact
to the system. If an incorrect signature file is loaded by mistake, the version information in signature file will not match
the current protocol detection version and the system will not be affected.
The signature files are provided on a need basis, or periodically whenever a new P2P detection software version is
integrated with the software. A signature file can contain the rules for several protocols. The P2P signature file is
packaged as a delivery kit for release. For more information, contact your local sales representative.

P2P Protocol Detection Software Versions

Every released signature file has a file version. This version number is used to determine which file is the latest and
newest to load during upgrade or reboot. On the boxer, the signature file version and the syntax is validated, in case of
failure, the signatures will not be loaded into memory.
Enabling and Disabling P2P Dynamic Signature Updates
The P2P Dynamic Signature Update feature can be enabled and disabled from the CLI.
Disabling the P2P Dynamic Update feature instructs the system not to load and apply the signature files. An already
loaded signature file can be unloaded (removed) from the system's memory too.
CLI show commands can be used to view details of loaded signature file, and the P2P as well as the individual protocol
detection software versions.
OL-22938-02
This release supports dynamic upgrades of detection logic for the following P2P protocols:
Dynamic signature updates may not work in all situations, and software updates may be required to
Cisco ASR 5000 Series Product Overview ▄
P2P Overview ▀

Advertisement

Table of Contents
loading

Table of Contents