Release Notes

SP Guru Network Planner 17.5

Release Notes

Release 17.5 June 27, 2013

Riverbed Technology 199 Fremont St. San Francisco, CA 94105 USA SP Guru Network Planner Release Notes Copyright and Contacts Copyright and Contacts

Document Copyright Title: SP Guru Network Planner Release Notes Version: 17.5 6/27/13

Contacts Riverbed Technology 199 Fremont St. San Francisco CA, 94105 USA

General Telephone: 415.247.8800 E-mail: [email protected] Web: http://www.riverbed.com

Technical Support Telephone: 240.497.1200 Fax: 240.497.1064 E-mail: [email protected]

This Documentation and Riverbed This document and the accompanying product documentation describes the functions of the Riverbed software product(s) (“SOFTWARE”) identified above (this document and the product documentation are collectively referred to as “DOCUMENTATION”). Riverbed Technology, 199 Fremont St., San Francisco, California 94105 is the sole owner of all rights, title, and interest to the DOCUMENTATION and SOFTWARE. Nothing herein shall grant or imply a license to the DOCUMENTATION or SOFTWARE. The right to use the DOCUMENTATION and SOFTWARE shall result only from entering into a Master Software License Agreement and a Software Usage Agreement, and paying the applicable license fees.

RN-ii SP Guru Network Planner Release Notes Copyright and Contacts

Terms and Conditions of Use

Eligible Users This document is subject to restrictions on use and distribution is intended solely for persons who are subject to the terms and conditions of Riverbed’s Software Master License Agreement or persons authorized by Riverbed (“Eligible Users”). As a condition of being granted access to and use of this document, each User represents that: i) the User is an Eligible User of a Licensee under a valid Riverbed Software Master License Agreement or the User is authorized by Riverbed and ii) the User accepts the terms and conditions of Riverbed’s Software Master License Agreement and the terms and conditions governing the use of this document.

Confidential Information The User agrees that the DOCUMENTATION, including this document, are the proprietary property of Riverbed and constitutes a trade secret of Riverbed. The User agrees that access to and use of this document does not grant any title or rights of ownership. The User shall not copy or reproduce, in whole or in part, disclose or permit third parties access to this document without the prior written consent of Riverbed. This document may not be stored, in whole or in part, in any media without the prior written consent of Riverbed. Any unauthorized use of this document will be subject to legal action that may result in criminal and/or civil penalties against the User.

Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein may not be used without the prior written consent of Riverbed Technology or their respective owners.

The absence of a patent or mark from the above notices does not constitute a waiver of intellectual property rights that OPNET Technologies, Inc. has established in any of its products, service names or marks in use. Alteration, removal, obscuring, or destruction of any proprietary legend, copyright, trademark, patent, or intellectual property notice contained in this document is prohibited.

Restricted Rights Legend The DOCUMENTATION and SOFTWARE are subject to the restrictions on use and distribution in the Riverbed Software Master License Agreement (for Agencies of the U.S. Government). Any use of the DOCUMENTATION or any SOFTWARE by an agency of the U.S. Government or a direct contractor of an agency of the U.S. Government requires a valid Riverbed Software Master License Agreement and Riverbed Software Usage Agreement.

For all users, this Software and Documentation are subject to the restrictions (including those on use and distribution) in Riverbed's Master License Agreement. Use of this Software or Documentation requires a current Riverbed license and shall be governed solely by the terms of that license. All other use is prohibited. For the U.S. Government and its contractors, the Software is restricted computer software in accordance with Federal Acquisition Regulations as applied to civilian agencies and the Defense Federal Acquisition Regulation Supplement as applied to military agencies. The Software and Documentation qualify as “commercial items,” “commercial computer software,” and “commercial computer software documentation.”

No Warranty and Limitation of Liability ALL INFORMATION PROVIDED IN THIS USER MANUAL IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON- INFRINGEMENT. No representations by Riverbed, such as statements of capability, suitability for use, accuracy or performance, shall be a warranty by Riverbed, or bind Riverbed or vary any term or condition of any Software Master License Agreement, unless contained in written agreement and signed by Riverbed and any other party or parties to such Software Master License Agreement.

RN-iii SP Guru Network Planner Release Notes Copyright and Contacts

In no event shall Riverbed be liable for any incidental, indirect, special, or consequential damages whatsoever (including but not limited to lost profits arising out of or relating to this document or the information contained herein) even if Riverbed has been advised, knew, or should have known of the possibility of such damages.

THE USER UNDERSTANDS AND ACCEPTS THAT RIVERBED SHALL NOT BE LIABLE FOR DAMAGES WHICH ARE: (i) INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR CONSEQUENTIAL, OR (ii) THE RESULT FROM LOSS OF USE, DATA, OR PROFITS, OR (iii) FROM THE USE OF THE SOFTWARE AND DOCUMENTATION, WHETHER BROUGHT IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, EVEN IF RIVERBED WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Export Controls Any User of the DOCUMENTATION including this document shall comply with the laws of the United States, including the provisions of the U.S. Department of Commerce, Bureau of Industry Security (“BIS”), Export Administration Regulations (EAR), the U.S. Department of State, International Traffic in Arms Regulations, and the U.S. Department of Treasury, Office of Foreign Assets Control, regarding the export, re-export and disclosure of the DOCUMENTATION or the SOFTWARE. Any export, re-export or disclosure of the DOCUMENTATION or the SOFTWARE shall be subject to the prior written consent of Riverbed. Users shall not remove any Destination Control Notices provided by Riverbed from the DOCUMENTATION or the SOFTWARE.

Destination Control Statement The DOCUMENTATION and the SOFTWARE were manufactured in the United States by Riverbed. The initial export of the DOCUMENTATION and the SOFTWARE from the United States, and any subsequent relocation or re-export to another country shall comply with the laws of the United States relating to the export of technical data, equipment, software, and know-how. Any diversion contrary to the laws of the United States is prohibited.

RN-iv SP Guru Network Planner Release Notes Contents Contents

Release Notes RN-1 Important Notes for SP Guru Network Planner ...... RN-1 Licensing Transactions ...... RN-1 Updated Web Report Style—NetDoctor, Network Difference, Inventory, and OS Compliance Reports ...... RN-2 New Preference to Remove Un-Printable Characters in Web Reports ...... RN-2 OS Compliance Reports and the Sentinel Advisory Service (SAS) ...... RN-3

Project Editor Enhancements RN-4 Visualizing IPv4 Process Tags ...... RN-4 Huawei Device Support ...... RN-4

Project Editor Enhancements for PL3 RN-5 Enhancements to Paste Operation for Creating New Links ...... RN-5 New Snap-to-Grid Layout Options ...... RN-7

Network Topology and Configuration Import Enhancements RN-8 Enhanced Support for Juniper Networks Devices ...... RN-8 Importing Juniper Service Delivery Gateway and MX Devices ...... RN-8 Importing Juniper EX Devices ...... RN-9 Importing Juniper Configlets ...... RN-9 Enhanced Support for Juniper Routing Instances ...... RN-9 Support for Routing Table Groups (RIB Groups) ...... RN-10 Support for IPv6 VPN Provider Edge (6VPE) for MPLS ...... RN-10 Improved IP Traffic Flow Mapping ...... RN-10 Using Forwarding Tables to Map Flows ...... RN-10 Mapping Source-Only Flows for Imported Networks Without Forwarding Tables ...... RN-11 Traffic Import Automation ...... RN-11

Network Topology and Configuration Import Enhancements for PL3 RN-13 New Support for Import from CSV Text Files ...... RN-13 Support for Juniper SRX Firewall ...... RN-14 Enhanced Support for F5 Big-IP Load Balancers ...... RN-15 IP SLA and Packet Loss Metrics from Juniper and Cisco Devices ...... RN-15 Expanded Parser Support ...... RN-16 Interface Load on Unmodeled Links ...... RN-17 What do each of the Interface Loads options mean? ...... RN-18 How do I decide on which link load traffic option to use? ...... RN-18

RN-v SP Guru Network Planner Release Notes Contents

Using the Endpoints of Existing Flows for Loads to Flows ...... RN-19 Traffic Flow Import from AppResponse Xpert ...... RN-20

NetDoctor Enhancements RN-21 Support for Cisco Nexus OS ...... RN-21 New Rules ...... RN-23 Wireless LAN Auditing ...... RN-24 Hardware End-of-Life Rules ...... RN-25 Sentinel Advisory Rules ...... RN-33

NetDoctor Enhancements for PL3 RN-36 New Rules ...... RN-36 Cisco IOS XE Operating System ...... RN-36 Administration Support for Oversubscription ...... RN-37 Enhanced Rules ...... RN-38 Show Command Output Validation ...... RN-38 New Attributes and Tags for Template Specification File v2 ...... RN-39

Network Capacity Reports Enhancements RN-41 Reporting Based on Time Zones ...... RN-41 Forecasting ...... RN-42 Reporting on Interface Metrics ...... RN-44 Using Interface Names and Descriptions as a Filter ...... RN-45 Grouping Interfaces and Devices by Device Roles ...... RN-45

Network Capacity Reports Enhancements for PL3 RN-46 New Metrics Available for Reporting ...... RN-46 Where can I import these Network Capacity Planning metrics from? ...... RN-46 Site-Based Reporting ...... RN-47 Application Trends Reporting ...... RN-48 Links with Sustained Capacity Violations ...... RN-49 Using “Nth” Percentile Statistics for Reporting ...... RN-50 Projection Curve in Growth Analysis Output ...... RN-51 Enhanced Filtering Options ...... RN-53 Supplemental Data Reporting ...... RN-54 CSV File Only Output ...... RN-54

Planning and Design Enhancements RN-55 IP Fast Reroute with Loop Free Alternate ...... RN-55 Network Changes ...... RN-56 Loop Free Alternate Reports ...... RN-56 Design Action Reports ...... RN-56 Flow Analysis Reports ...... RN-57 LFA Visualization ...... RN-58

RN-vi SP Guru Network Planner Release Notes Contents

Enhancement to Link Dimensioning ...... RN-59

Planning and Design Enhancements for PL3 RN-62 IGP Metric Optimization with Delay Constraints ...... RN-62 Setting Delay Constraints ...... RN-62 Using the Delay Constraints Files ...... RN-63 MPLS LSP Sizing with Option to Create LSP Bundles ...... RN-64

Peering Center Enhancements RN-65 New Peering Wizards ...... RN-65

Inventory Report Enhancements RN-68 Trend Line in Reports ...... RN-68 Do I have to configure Trending to see the results in my report? ...... RN-68 Cisco IOS Running on Cisco IOS XE devices ...... RN-70 Private and Public IPv4 Address Prefixes Rules ...... RN-70 Configuring the Public IPv4 Prefixes Rule ...... RN-71 Configuring the Private IPv4 Prefixes Rule ...... RN-71

NetMapper Enhancements RN-72 DMVPN Tunnels ...... RN-72 New Layout Schemes ...... RN-73

NetMapper Enhancements for PL3 RN-74 New Web Report Output Format ...... RN-75 How do I generate a NetMapper Web Report? ...... RN-75 Supported Web Browser for Web Reports ...... RN-77 Using the Magnify Options for Viewing Web Reports ...... RN-78 Enhanced Layout Strategies ...... RN-79 New Variable Page-Size Options ...... RN-81 When do I use the new variable page option? ...... RN-81 New Wizard Options ...... RN-82 New “Filter options by” Selection List ...... RN-82 New Option for Determining Device Management Addresses ...... RN-82 Link Scaling Factor ...... RN-83 Flexible Column and Row Spacing and Connected Device Promotion ...... RN-83 New Device Layout Scheme Options ...... RN-84 New Market Diagrams ...... RN-85 Configuring a Market Diagram ...... RN-85 Visualize Roles ...... RN-87 Managing Roles on Selected Objects ...... RN-88 Color Options with Non-Default Settings in Wizard ...... RN-89 Clean Up Document Sets ...... RN-90 New Manage Options ...... RN-90 Additional Chassis Icons for Diagrams ...... RN-91 New Support for Devices and Modules ...... RN-91 Diagrams of VMWare ESX Servers ...... RN-91

RN-vii SP Guru Network Planner Release Notes Contents

Cisco IOS on Cisco IOS XE ...... RN-92 Cisco Nexus 2000 Series Fabric Extenders ...... RN-92 Alcatel-Lucent IPSec SAs and Cisco Tunnel-based IPSec SAs ...... RN-94 Virtual Private LAN Service (VPLS) and Virtual Private Wire Service (VPWS) ...... RN-95

Network Differences Enhancements for PL3 RN-96 Huawei VRF Table Differences ...... RN-96 Differences in BGP RIB Tables ...... RN-100 Cisco IOS XE Differences ...... RN-101

Flow Analysis Enhancements RN-102 Enhanced Support for Juniper Routers ...... RN-102 Support for Forwarding and No Forwarding Routing Instances ...... RN-102 Support for Routing Table Groups (RIB Groups) ...... RN-103 Analyzing Routing Instances for Juniper Routers ...... RN-103 Support for Juniper Service Delivery Gateway and MX Devices ...... RN-104 Support for IP Fast Reroute Loop-Free Alternate ...... RN-107 Enhancements to IPv6 Support in Flow Analysis ...... RN-107 IPv6 VPN Provider Edge (6VPE) ...... RN-107 Support for BGP Peering in IPv6 ...... RN-108 IPv6 Support for MPLS Inter-AS VPNs ...... RN-108 Enhancement to Route Visualization for IPv6 ...... RN-109 Reporting Enhancements for IPv6 ...... RN-110 Global Report Enhancements ...... RN-110 Node-Level Reports ...... RN-110 Support for Additional Service Level Agreement (SLA) Criteria ...... RN-111

Flow Analysis Enhancements for PL3 RN-112 Auto-Assign IP Addresses Utility Enhancements ...... RN-112 Specifying Starting Subnets for IPv4 and IPv6 Auto-Addressing ...... RN-112 Support for vPC Configurations on Cisco Nexus Devices ...... RN-113 Support for F5 Load Balancers ...... RN-113 Layer-3 VPN-Centric Reports and Visualization ...... RN-115 Layer-3 VPN-Centric Flow Analysis Reports ...... RN-116 Layer3 VPN Performance per Node Report ...... RN-116 Layer3 VPN Status Report ...... RN-117 Layer3 VPN Traffic ...... RN-118 Demand Routing Report for VPNs ...... RN-118 Layer-3 VPN-Centric Traffic Center Enhancements ...... RN-119 Layer-3 VPN-Centric Link Usage View Enhancements ...... RN-120 Layer-3 VPN Survivability Analysis ...... RN-122

RN-viii SP Guru Network Planner Release Notes Release Notes

SP Guru Network Planner 17.5 is a software update to the 17.0 release. This release contains new features and enhancements to existing capabilities. This release also implements suggestions and fixes.

Note—Visit the OPNET Support Center (www.opnet.com/support) for updated release notes and system requirements.

Important Notes for SP Guru Network Planner Licensing Transactions Starting with this release, express license registration between SP Guru Network Planner and the license registration server at OPNET Technologies, Inc., is encrypted by default, using HTTP Secure (HTTPS). Previously, all express licensing communication was over HTTP.

The following new license preference was added:

• Enable HTTPS for Express License Registration—Enables secure communication with the OPNET license registration server. The default value is TRUE. In rare cases, you may wish to disable HTTPS (e.g., when you are using a web proxy), though this is not recommended.

Note—If you set this preference to FALSE, you must also set the preference License HTTP Server to “licensing.opnet.com”. Otherwise license registration will fail with an error message. If you set licensing to use HTTP, communications will be conducted over an unencrypted channel and may expose sensitive information during the transaction.

Figure 1-1 New Licensing Preferences

RN-1 SP Guru Network Planner Release Notes If express license registration fails, a dialog box lets you choose to continue by using the Web Browser registration.

For more information on licensing, please see Licensing in the User Guide.

Updated Web Report Style—NetDoctor, Network Difference, Inventory, and OS Compliance Reports NetDoctor, Network Difference, Inventory, and OS Compliance Reports have a new web reports style, as shown in the following figure.

Figure 1-2 Example Updated Web Report Styles

New Preference to Remove Un-Printable Characters in Web Reports Device configuration files sometimes include un-printable characters that can cause problems when generating Web Reports—typically the entire report (or sections of the report) might fail to generate.

You can now set the preference “Remove Un-Printable Characters from Report” to TRUE to pre-process the report content and remove the un-printable characters. This pre-processing slows down a report run and is turned off by default (FALSE). You should turn this on only if you are encountering this problem.

Note—This preference applies only to NetDoctor, Network Difference, Inventory, and OS Compliance Reports.

RN-2 SP Guru Network Planner Release Notes OS Compliance Reports and the Sentinel Advisory Service (SAS) Starting with this release, generating OS Compliance reports requires a Sentinel license and using the Sentinel Advisory Service (SAS) requires both a Sentinel license and a current maintenance contract for OPNET Technical Support.

Note—Although IT Guru Network Planner includes options in the software for both OS Compliance reports and for the Security Advisory Rules included with the Sentinel Advisory Service (SAS), they are not supported and might not be included in future releases.

RN-3 SP Guru Network Planner Release Notes Project Editor Enhancements Project Editor Enhancements

The following enhancements are available:

• Visualizing IPv4 Process Tags on page RN-4

• Huawei Device Support on page RN-4

Visualizing IPv4 Process Tags You can now include protocol process tags when you visualize IPv4 interior gateway protocols (IGP). Support is included for the following:

• IGP lowest administrative distance

• IGRP autonomous systems

• EIGRP autonomous systems

• OSPF process ID

• IS-IS process ID

To visualize the routing protocols, choose View > Visualize Protocol Configuration > IPv4 Process Tags. For more information, see Visualizing Protocols Configured in a Network in the user guide.

Huawei Device Support This release includes an expanded set of Huawei node models in the object palette. For more information about using the object palette, see Object Palettes in the user guide.

Figure 2-1 Huawei Models in the Object Palette

RN-4 SP Guru Network Planner Release Notes Project Editor Enhancements for PL3 Project Editor Enhancements for PL3

The following enhancements are available:

• Enhancements to Paste Operation for Creating New Links on page RN-5

• New Snap-to-Grid Layout Options on page RN-7

Enhancements to Paste Operation for Creating New Links This release includes an enhancement to the default behavior of the paste operation, which makes it easier to create links in the network model. When you copy and paste links in the project editor, SP Guru Network Planner will now paste the link object and the endpoint configuration (including routing protocols and other attributes) to an available port of the same technology and type as the copied link. If no port of the same technology and type is available, SP Guru Network Planner creates the port before pasting the endpoint configuration.

You can change the default paste behavior by using the Paste Special dialog box (Edit > Paste Special). The Paste Special dialog box (shown in the figure below) lets you specify how you want to paste links, as well as how you want the paste operation to behave in the future. For example, if you want the paste operation to paste link objects only, without configurations, you can change the option to “Paste objects only” and set the checkbox “Use this option for future pastes”.

Figure 2-2 Paste Special Dialog Box

Choose whether to paste link objects with or without endpoint configurations that match the copied links (default).

If you do not select “Use this Set global options that will apply to this and future paste special operations. If option for future pastes”, the “Always create new ports for links” is selected, the operation will not use existing options you select will apply to ports on end devices. If “Use this option for future pastes” is selected, the option this paste operation only. you chose will be automatically selected during any future paste operation, thereby saving time.

RN-5 SP Guru Network Planner Release Notes Project Editor Enhancements for PL3

Special Notes About Device Type When the new port type is not supported in the destination device Port Creation for (e.g., if you are pasting a link with IP endpoints to a Layer-2 switch), the device Pasted Links type will be upgraded (in such a case, from a switch to a router-switch). During this operation, the upgrade attempt may fail, in which case the device will not be upgraded and the new link will not be connected correctly. When an upgrade attempt fails, a message is written to the message buffer indicating the failure.

IP Address If the copied link's endpoint has a valid IP address, the pasted link will have its IP address set to “Auto-assigned”. If the source link has “No IP Address” or “Unnumbered”, the pasted link will use the same value. In the former case, you will need to auto-assign addresses using the Protocols > IP menus or run Flow Analysis to auto-assign IP addresses.

RN-6 SP Guru Network Planner Release Notes Project Editor Enhancements for PL3 New Snap-to-Grid Layout Options You can now define and use the new “Snap-to-Grid” layout option to manually position nodes in the Project Editor, as shown in the following figure.

Figure 2-3 Defining and Using the Snap-to-Grid Layout Option

Step 1 Choose View > Layout > Define Snap-to-Grid and then draw a diagonal line that defines the grid . . .

Step 2 Move nodes so that they “snap” to the grid lines

Step 3 Continue moving nodes to snap sets of objects on grid lines horizontally or vertically until you the layout you want

Note—Choosing “Define Snap-to-Grid” automatically enables this layout option. When you finish moving around nodes, turn off the snap-to-grid feature.

Key Concept—This option provides support for a more organized display of network objects when you use the NetMapper option to “Preserve Relative Positions in Layout” in Network Hierarchy as Displayed in Project Editor diagrams.

RN-7 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements Network Topology and Configuration Import Enhancements

The following enhancement is available.

• Enhanced Support for Juniper Networks Devices on page RN-8

• Support for IPv6 VPN Provider Edge (6VPE) for MPLS on page RN-10

• Improved IP Traffic Flow Mapping on page RN-10

• Traffic Import Automation on page RN-11

Note—Unless otherwise specified, “import” refers to both eXpress Data Import and import from VNE Server.

Enhanced Support for Juniper Networks Devices The following enhancements are available.

• Importing Juniper Service Delivery Gateway and MX Devices on page RN-8

• Importing Juniper EX Devices on page RN-9

• Importing Juniper Configlets on page RN-9

• Enhanced Support for Juniper Routing Instances on page RN-9

• Support for Routing Table Groups (RIB Groups) on page RN-10

Importing Juniper Service Delivery Gateway and MX Devices You can now import Juniper Networks’ Service Delivery Gateway (SDG) and MX series devices. The following features are supported:

• Layer-2 bridging over Layer-3

• Service Network Address Translation (NAT)

• Application Delivery Controller (ADC) for load balancing

For information on analyzing the traffic flows for imported Juniper SDG and MX devices, see Support for Juniper Service Delivery Gateway and MX Devices on page RN-104.

RN-8 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements Importing Juniper EX Devices You can now import Juniper Networks’ EX series Layer-3 switches. Previously, all Juniper devices were imported as routers. Now the model is determined based on the configuration files (e.g., router, switch, Layer-3 switch). The following functionality is supported in this release.

• Spanning Tree Protocol

• Named VLANs

• Logical Interfaces — Routed VLAN interface (RVI)

• Aggregate interfaces

• Virtual chassis

Importing Juniper Configlets SP Guru Network Planner now includes limited JUNOS command support for configlet import. Previously, configlets were only supported for Cisco Systems devices. Specifically, a subset of the “set” and “delete” commands are supported.

Note—While the original configuration file for a Juniper router is in a hierarchical format, the configlet file is a flat file that has commands shown just as they would be entered from the command line.

You can import configlets in two ways:

1) For multiple devices in a network, choose the following: Topology > Import Topology > From Configlets...

2) For an individual device, right-click on the device and choose the following: Post Import Operations > Import Configlet...

For more information, see Import from Configlets in the User Guide.

Enhanced Support for Juniper Routing Instances Import now supports the following routing instance types for Juniper routers:

• Forwarding—A routing instance that has its own forwarding plane but runs no protocols and has no interfaces. Best routes are only shared to or from this forwarding plane by using filters.

• No Forwarding—A routing instance that has its own interfaces and can run routing protocols but does not have its own forwarding plane. Best routes are automatically sent to the global forwarding plane.

RN-9 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements Routing instances are defined in IP > IP Routing Protocols > Protocol Parameters > Processes, and are configured as either “Forwarding” or “No Forwarding” in VPN > Network-Based > VRF Instances > Instance Type.

For information about Flow Analysis support for routing instances, see Support for Forwarding and No Forwarding Routing Instances on page RN-102.

Support for Routing Table Groups (RIB Groups) Juniper routers use RIB groups to move (export or import) routes between routing instances. For example, a forwarding instance will determine best routes but does not have a method for moving those routes to the global routing table. In this case, a RIB group is defined and use to move the routes. RIB groups can also be used to define policies for route sharing between routing instances. RIB groups are defined in the following attributes.

• RIB groups are defined in IP > IP Routing Parameters > RIB Groups.

• RIB groups are assigned to a given address family in IP > IP Routing Parameters > Interface Routes RIB Groups.

• RIB groups are applied to routing instances in IP > IP Routing Protocols > Protocol Parameters > Process Parameters > RIB Group

For information about Flow Analysis support for RIB groups, see Support for Routing Table Groups (RIB Groups) on page RN-103.

Support for IPv6 VPN Provider Edge (6VPE) for MPLS SP Guru Network Planner now imports IPv6 and VPNv6 address family information using either eXpress Data Import or import from VNE Server. After import, you can analyze 6VPEs using Flow Analysis.

For information about 6VPE analysis, see Enhancements to IPv6 Support in Flow Analysis on page RN-107.

Improved IP Traffic Flow Mapping Using Forwarding Tables to Map Flows Imported traffic flow records can include source or destination IP addresses for nodes outside the imported network model. This release now supports better success at mapping these flows to specific nodes in the network by using the imported operational forwarding tables from all the devices in the network.

If known, the import process uses the forwarding tables from the device that reports the IP traffic flow records as its “probe” device—mapping the traffic flow according to a graph walk towards the flow endpoint.

RN-10 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements When a device that reports the traffic flow records is either not known at all, or if it is known but does not exist in the modeled network, the import process now uses the first device it finds with the source or destination IP address in its forwarding tables as its “probe” device to map the traffic flow based on a graph walk towards the flow endpoint.

Note—The preference, Automatically Select Probe For Offnet Mapping must be set to TRUE (default) for the import process to automatically select a device as the probe source.

Mapping Source-Only Flows for Imported Networks Without Forwarding Tables In some cases, importing the forwarding tables from the devices in the network is not practical and can be too resource-intensive for the traffic studies that you plan to do.

Instead of relying on forwarding tables to map traffic to endpoints, there is now an option to consider the node reporting the traffic flow record as the source of the IP traffic flow. This option requires representing the flow as a source-only flow—that is, only the source endpoint is pinned to a node in the model. You can then run a flow analysis to route the traffic for your traffic routing and planning analysis.

Note—The preference, Use Probe As Source of the Flows must be set to TRUE, and you must set the traffic import Advanced Flow Import Option to Represent Source-Only IP traffic flows without mapping destinations, as Always to map flows as source-only flows without forwarding tables.

Traffic Import Automation You can now configure importing the following traffic flows as an Automation step:

• AppResponse Xpert: IP Flows

• AppResponse Xpert: Business Group Flows

• Cisco NetFlow

• Fluke Networks OptiView Console

• Text (.tr1,.tr2) Files

RN-11 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements Choose “Import Traffic Flows” and then “New” to select the Traffic Flows Source, as shown in the following figure.

Figure 3-1 Import Traffic Flows Step

New Interface Loads options

Alternatively, you can create an automation (.af) file when you configure the settings from the Traffic menu. For example, choose Traffic > Import Traffic Flows > From AppResponse Xpert: IP Flows, configure your setttings and then choose the “gear” icon to save the automation file for use in the settings of an Import Traffic Flows step, as shown in the following figure.

Figure 3-2 Automation Gear Icon

RN-12 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 Network Topology and Configuration Import Enhancements for PL3

The following enhancements are available:

• New Support for Import from CSV Text Files on page RN-13

• Support for Juniper SRX Firewall on page RN-14

• Enhanced Support for F5 Big-IP Load Balancers on page RN-15

• IP SLA and Packet Loss Metrics from Juniper and Cisco Devices on page RN-15

• Expanded Parser Support on page RN-16

• Interface Load on Unmodeled Links on page RN-17

• Using the Endpoints of Existing Flows for Loads to Flows on page RN-19

• Traffic Flow Import from AppResponse Xpert on page RN-20

New Support for Import from CSV Text Files SP Guru Network Planner includes new support for importing topologies from comma-separated values (CSV) text files.

Use the following steps to import the topology from CSV text files:

1) Define the nodes in one CSV text file and the links in another CSV text file.

2) Save both of them to a directory that SP Guru Network Planner can access.

3) Specify the “Directory Containing Source CSV” files by choosing: Topology > Import Topology > From CSV Text Files.

RN-13 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 The following figure shows an example of the format for CSV Text Files used for import.

Figure 3-3 CSV Text Files for Importing Network Topologies

Node Definitions

Link Definitions

For more information, see Importing Topologies from CSV Text Files in the Importing Topologies section of the User Guide.

Note—This release also provides support for specifying interface naming conventions and custom names for interface types. You can base them on the vendor devices and network interface technology configurations you want to import from CSV text files.

For more information, see Specifying Interface Naming Conventions and Custom Names for Interface Types in the Main Documentation.

Support for Juniper SRX Firewall You can now import configurations for Juniper SRX firewalls using eXpress Data Import or import from VNE Server. For more information, see Importing Juniper SRX Firewalls in the User Guide. Supported features include:

• Virtual routers

• Security zones

• Layer-2 forwarding

• Route- or Policy-based VPNs

RN-14 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 • Transparent or NAT interface mode

• Multicast routing

• NAT/PAT

• Tunnel mode

For more information, see Analyzing Network Models Containing Juniper SRX Firewall in the User Guide.

Enhanced Support for F5 Big-IP Load Balancers Starting with this release, you can import F5 device configurations from VNE Server for devices running TMOS version 10.x and higher. Device configurations are collected by VNE Server from the command line interface (CLI). Previously, you could import only MIB data collected from F5 devices.

After the import, F5 configuration files are available from the Post Import Operations menu (see View and Edit Configuration Files in the Importing Topologies section of the User Guide).

New attributes in this release include the following:

• Load Balancer Configuration

• System Management > Redundancy Parameters > High Availability

After import you may run a flow analysis on a network model containing F5 load balancers. For more information about Flow Analysis support, see Support for F5 Load Balancers on page RN-113.

IP SLA and Packet Loss Metrics from Juniper and Cisco Devices You can now import IP SLA and Packet Loss metrics from VNE Server that provide “normalized” performance reporting for Cisco and Juniper devices. Use the Metrics tab when you choose Topology > Import Topology > From VNE Server and select the metrics shown in the following figure.

Figure 3-4 Metrics Tab—IP SLA and Packet Loss Metrics

Packet Loss—Interface Error and Discards IP SLA—Latency and Jitter

RN-15 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 To view the metric data, choose Traffic > Network Capacity Report > Configure/Generate Report, and then select the Network Capacity Report for Device Pairs Performance, as shown in the following figure.

Figure 3-5 Reporting on IP SLA and Packet Loss Metrics

Expanded Parser Support You can now import configuration files for Cisco NX-OS-based and Cisco IOS-XR based devices when using eXpress Data Import. The following table lists the “show” commands supported for Nexus 7000 and 5000 devices.

Note—VNE Server already supports the commands listed in the following table.

Table 3-1 Supported Show Commands for NX-OS in eXpress Data Import

Show Command Nexus 7000 Nexus 5000

show running-config X X

show running-config vdc-all X

show version X X

show cdp neighbors detail X X

show vlan X X

show interface X X

show spanning-tree brief X X

show ip route X X

RN-16 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 The following list of “show” commands is supported for Cisco IOS-XR:

• show running-config

• show version

• show mpls traffic-eng tunnels

• show ip route

• show cdp neighbors detail

• show aps

• show arp

• show interfaces

• show hsrp

• show igmp groups detail

• show mrib route

Interface Load on Unmodeled Links In most cases, network traffic collected by VNE Server or a third-party traffic collection tool includes interface load traffic data from all interfaces available on a per-device basis. Your traffic analysis might require all or part of this collected traffic in SP Guru Network Planner.

In this release, you can import interface load traffic based on the options shown in the following figure.

• Import loads for interfaces with unmodeled links

• Import loads on VLAN, tunnel, and aggregate interfaces

Figure 3-6 Interface Load Import Options

New Interface Loads options

Note—You can select the new Interface Loads options in the Traffic tab when you choose Topology > Import Topology > Import from VNE Server or when you choose Traffic > Import Baseline Loads and select one of the traffic sources.

RN-17 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 What do each of the Interface Loads options mean? When you select “Import loads for interfaces with unmodeled links,” SP Guru Network Planner imports all available interface traffic data collected from the devices in your network. Otherwise, only the interface traffic for the links modeled in your network scenario gets imported.

When you select “Import loads on VLAN, tunnel, and aggregate interfaces,” SP Guru Network Planner imports all available VLAN, tunnel, and aggregate traffic data collected from the devices in your network. Selecting this option imports traffic loads from logical interfaces. Otherwise, this traffic data does not get included in your network model.

Key Concept—LSP traffic data collected always gets imported with interface link load traffic data regardless of the options selected for Interface Loads.

How do I decide on which link load traffic option to use? Most traffic analysis works best by importing only the traffic necessary for your network planning goal.

Case 1—Capacity Management

In some cases, all collected traffic available is required for your planning studies. For example, you might need to generate a Network Capacity Report for trending analysis or capacity management. Having all of this traffic in your network model as a current snapshot of the operational traffic in your network makes the most sense.

In this case, make sure you select the option “Import loads for interfaces with unmodeled links” when importing link loads.

Note—Traffic loads for interfaces with unmodeled links are currently used only for generating Network Capacity Reports.

Case 2—Routing Analysis and Survivability

In this case, you might want to only include traffic collected from the interfaces that are connected to the links present in your network model. For example, you might want to convert some specific link load data to flow data for route analysis and survivability studies. In this case, it only makes sense to import the traffic from specific interfaces associated only with the modeled links in your network.

RN-18 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 Make sure you clear the option to “Import loads for interfaces with unmodeled links” when importing link loads in this case.

Case 3—VLAN, Tunnel, and Aggregate Interface Traffic

You might want to generate Network Capacity reports using traffic loads on logical (sub-interfaces, VLANs, tunnels, or aggregate interfaces).

In this case, you can select “Import loads on VLAN, tunnel, and aggregate interfaces.”

Note—Traffic loads for interfaces with unmodeled links are currently used only for generating Network Capacity Reports.

Using the Endpoints of Existing Flows for Loads to Flows In some cases when you convert loads to flows, using one or more flows of interest that already exist in your network as endpoints provides a more effective way to model traffic in your network.

Tip—Create test flows by choosing Traffic > Create Traffic Flows and then configuring one or more traffic flows that you would like to analyze based on the interface loads in your network.

Using these test flows—along with any other flows of interest that exist in your scenario—you define the endpoints of your “Loads to Flow” conversion.

Choose Traffic > Convert Link Loads To Flows > Configure/Convert, click Advanced Options, and then select the “Computed flows will have endpoints restricted by existing flows” option, as shown in the following figure.

Figure 3-7 Flows with Endpoints Restricted by Existing Flows

Use existing flows as endpoints for the flows that you define using the loads to flows conversion

Key Concept—Using the endpoints of existing flows helps you efficiently model the imported operational traffic load data with one or more specific flows of interest in your network.

RN-19 SP Guru Network Planner Release Notes Network Topology and Configuration Import Enhancements for PL3 Traffic Flow Import from AppResponse Xpert Traffic import from AppResponse Xpert supports Type of Service (ToS) beginning with SP Guru Network Planner 17.0 PL7.

Note—You must make sure that a 1.0.11 (or newer) version of the ExportToITGuru script has been installed on the AppResponse Xpert appliance.

You can check if a new version of the script is available on the appliance by opening the AppResponse Xpert console and going to the Insight Update Center. If a new version of the script is available, you are prompted to download it on the appliance.

RN-20 SP Guru Network Planner Release Notes NetDoctor Enhancements NetDoctor Enhancements

This release has the following enhancements:

• Support for Cisco Nexus OS on page RN-21

• New Rules on page RN-RN-116 — Wireless LAN Auditing on page RN-24 — Hardware End-of-Life Rules on page RN-25 — Sentinel Advisory Rules on page RN-33

Support for Cisco Nexus OS This release includes new support for Cisco Nexus OS for the following rules by rule Suite:

• AAA — Verify Login Authentication — Verify Accounting Configuration — AAA Not Enabled — Verify Methods for Login Authentication

• Administration — Verify Permitted Incoming Services — Verify Permitted Outgoing Services — Verify Blocked Incoming Services — Verify Blocked Outgoing Services — Virtual Line Not Using Local Authentication — EXEC Passwords Not Using Type 5 Encryption — Services on Virtual Lines — Auxiliary Port Enabled — Verify Local Usernames — Verify SSH for Remote Device Access — Verify Timeout for Login Sessions — Verify SSH and Telnet Access Control — EXEC Mode Password Not Set — Local User Password Not Encrypted — Verify Login Banner — Verify TCP Synwait Time — Verify Number of Local Users

RN-21 SP Guru Network Planner Release Notes NetDoctor Enhancements — Verify MOTD Banner

• Configuration Consistency Validation — Devices With Differences Between Running and Startup Configurations — Cisco NX-OS Running Configuration Differs from Startup Configuration

•NTP — Authenticated NTP Not Used

• Route Maps and ACLs — Deny All ACL — Verify Permitted Source Addresses In Extended ACLs — Verify Inbound Traceroutes Denied — Verify Explicit Deny Any in Extended ACLs — Verify Denied Source Addresses in Inbound Extended ACLs — Verify ICMP Message Filters — Verify Access Control Lists

•SNMP — SNMP Write Access Enabled — Verify SNMP Community Strings and Access Control

•Services — Gratuitous ARP Enabled — IP Source Routing Enabled — Password Encryption Service Not Enabled — ICMP Unreachables Not Disabled on Null Interface

• System Logging — Logging Without Timestamps — Logging Disabled —Servers — ACL Deny Statement Not Logged — Verify Internal Buffer Size — Verify Console Logging Severity — Verify Syslog Trap Severity — Debug Messages Not Timestamped

RN-22 SP Guru Network Planner Release Notes NetDoctor Enhancements • TACACS+ — Invalid Source Interface — No Route to Server — Verify TACACS+ Servers — Unused TACACS Servers — Server Group References Undefined Server

The release supports a new rule in the Configuration Consistency Validation suite for Cisco Nexus OS.

• Configuration Consistency Validation — Cisco NX-OS Running Configuration Differs from Startup Configuration

New Rules This release supports a number of new wireless LAN auditing rules, and over 200 new Hardware End-of-Life rules that now provide more complete coverage of Cisco Series Modules, Aironet, Catalyst, PIX, and XR devices. This release also supports the cumulative updates to the Sentinel Advisory rules for OS Compliance Reports:

• Wireless LAN Auditing on page RN-24

• Hardware End-of-Life Rules on page RN-25

• Sentinel Advisory Rules on page RN-33

RN-23 SP Guru Network Planner Release Notes NetDoctor Enhancements Wireless LAN Auditing The following new rules for wireless LAN auditing are now available in the following rules suites:

• Wireless LAN — Verify Broadcasted SSIDs — Broadcasted SSIDs are Revealing — Local EAP Authentication is Enabled — Verify Cipher in Wi-Fi Protected Access — Access Points do not have Redundant Network Connectivity — Verify AAA Authentication Methods — Telnet Access to WLAN Controller is Permitted — HTTP Access to WLAN Controller is Permitted — CAPWAP Protocol Not Used by WLAN Controller — Verify NTP Servers — Verify Syslog Servers — Verify WLAN Controller Traps

• TACACS+ — Verify TACACS Authentication Servers on Wireless LAN Controllers — Verify TACACS Accounting Servers on Wireless LAN Controllers

• Administration — Telnet Enabled on Wireless Access Point — SSH Enabled on Wireless Access Point

Note—Wireless LAN rules operate on Cisco Wireless LAN Controllers only.

RN-24 SP Guru Network Planner Release Notes NetDoctor Enhancements Hardware End-of-Life Rules The following new Hardware End-of-Life rules support more comprehensive coverage of Cisco hardware:

• Hardware End-of-Life — Cisco Catalyst 3550 Series Switches — Cisco CRS-1 Series Modular Services Card — Cisco XR 12000 and 12000 Series Performance Route Processor-2 and Associated Memory Cards — Cisco CRS-1 Series 16-Slot Fabric Card/Multi — Cisco Catalyst 3560E-12D-E and 3560E-12D-S Switches — Cisco 12000 Series Legacy Fabric Cards — Cisco 12000 Series Legacy Clock Scheduler Card — Cisco CRS-1 Series 4X10GE Interface Module — Cisco CRS 8-Slot Chassis Fixed Configuration Power System — Cisco ASR 9000 Series 2TB Flash Storage Service Acceleration Module — Cisco Catalyst 6500 Series Intrusion Detection System (IDSM-2) Services Module — Cisco CRS 1-Port OC-768C/STM-256C DPSK+ Tunable Offset WDMPOS Interface Module — Cisco 7600 Bundles Containing Supervisor Engine 2 and 720 — Cisco 3700 Series — Cisco 2600XM Series and the Cisco 2691 Multiservice — Cisco PIX 501 Security Appliance — Cisco MDS 9140 1/2-Gbps 40-Port Fibre Channel Intelligent Fabric Switch — Cisco ASA 5580 Adaptive Security Appliance — Cisco Catalyst 3750 Metro Series Switches — Cisco Integrated Services Router G1 Modules — Selected Catalyst 6500 Series Line Cards and PoE Daughter Cards — Catalyst 6500 Series Components — Cisco Catalyst 6500 Product series — Cisco Catalyst 6500 10/100 Line Cards, GE Line Cards — POS/DPT Enhanced Optical Services Modules — Compact Flash Memory Card for Cisco Catalyst 6500 Supervisor Engine 720/32 — Cisco Catalyst 6500 Series Supervisor Engine 2 — Catalyst 6509 NEB Chassis Upgrade Kit

RN-25 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco Catalyst 6500 Series DFC and DFC3A Distributed Forwarding Cards — 8-Port Classic Gigabit Ethernet Interface Module for theCisco Catalyst 6500 Series Switches — Cisco Catalyst 6500 Series Line Cards — Series Supervisor Engine 720-3A and CEF 720 Distributed Forwarding Engine DFC3A — Cisco Catalyst 6500 Series Line Cards and Power over Ethernet (PoE) Daughter Cards — Cisco Catalyst 3550 24-Port 10/100 DC, and 2950G 24-Port 10/100 DC Switches — Cisco Catalyst 3750G-16TD Switch — Cisco GigaStack Gigabit Interface Converter — Cisco CRS 8-Slot Line-Card Chassis Route Processor — Cisco Catalyst 2950 Series Switches — Select Cisco Catalyst 2950G and Catalyst 2950T Series — 1-Port ISDN BRI S/T WAN Interface Card — Cisco Service Selection Gateway (SSG) — 1-Port ADSL-over-POTS and ADSL-over-ISDN WAN Interface Cards — Cisco 2800 Series Integrated Services Routers - Select Accessories and Bundle — Cisco 3G Wireless WAN High-Speed WAN Interface Cards (HWICs) for Cisco 1800/2800/3800 Series — Cisco 64-MB USB Flash Token for theCisco 1800/2800/3800 Series — Cisco 4- and 8-Port Asynchronous/Synchronous Network Modules — Cisco 16-Port EtherSwitch Prestandard Power over Ethernet Network Modules — Cisco 6-Access-Point Wireless LAN Controller Network Module — AIM-VPN-II Modules — Cisco 1700 Series — Cisco POS Enhanced Optical Services Modules — 64MB Compact Flash for Cisco Catalyst 6500 Supervisor Engine 720/32 — Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches — Cisco Catalyst 3750G-24TS 15 Rack-Unit Stackable Switch — 1803W and 1811W ISRs andCisco 80211g/a High-Speed WAN — Cisco 2800 Series Integrated Services Routers — Cisco 1-Port and 2-Port V90 Modem WAN Interface Cards

RN-26 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco Digital T1, E1 and J1 Packet Voice Trunk Network Modules — 2-Port OC-12 POS Line Card for Cisco 7304 with Single-Mode IR — 1-Port OC-48 POS Line Card for Cisco 7304 with Single-Mode SR Optics — Cisco 1-Port ATM 25 Network Module — Cisco 7206VXR Router NPE-400 Bundles (Non-Security) — Cisco 7600 Series Router 1900-Watt AC and DC Power Supplies — Selected Enhanced Digital Voice Port Adapters for Cisco 7000 Series Routers — Cisco 2600/3600/3700 Series ATM OC-3 155-Mbps Network Modules — Cisco CIGESM Blade Switch for IBM — 128 MB Memory for Cisco 7200 Series NPE-400 — Select Cisco Catalyst 6500 Series Voice Daughter Card — MPF on Cisco 7200 NPE-G1 and Cisco 7301 for Broadband LAC, LNS, PTA — Cisco 7500 Series Router — Cisco 10GBASE-LR XENPAK Module — Cisco Catalyst 2950 LRE Switch, Customer Premise Equipment and POTS Splitter — Cisco OC-12/STM-4 ATM Enhanced Optical Services Module — Cisco VPN Encryption Modules for the Cisco 2600/3600/3700 Routers — Cisco 10000 Series 6 Port Channelized T3 Interface Module — Cisco 10000 Series Gigabit Ethernet Interface Module — Cisco 10000 Series Performance Routing Engine — Cisco PA-POS-OC3 Select Models — Cisco 7304 128MB Compact Flash Memory — Cisco 2612 Multiservice Access Router Platform — Cisco Gateway GPRS Support Node 50 — Cisco 7200 Series Router NPE-225 Network Processing Engine and Respective Bundles, and C7200-I/O Controller — 128 MB DRAM Memory Spare for NPE-400 inCisco 7200 Series — AON Module for theCisco 2800/3700/3800 Series — Cisco CRS-1 CSR 16-Slot Line Card Chassis Route Processor — MobileAccessVE — Cisco Catalyst 2948G-GE-TX Switch — Cisco Catalyst 4500 Series 48-Port 100Base-LX10 FE Line Card — Cisco Digital Modem Network Modules

RN-27 SP Guru Network Planner Release Notes NetDoctor Enhancements — Elements ofCisco CRS-1 Series — 2-Port OC-3 POS Line Cards for Cisco 7304 with Multi and Single-Mode IR — Cisco AS5350 Universal Gateway — AS5400 Universal Gateway — Cisco AS5400HPX Universal Gateway — Cisco 3662 Telco Versatile DCN Access Platform — 6-Port T3 for Cisco 7304/6-Port E3 Line Card for Cisco 7300 with DSU — 1-Port OC-12 POS Line Card for Cisco 7304 with Single-Mode IR — 4-Port OC-3 POS Line for Cisco 7304 with Single-Mode IR — DC Power Supply ofCisco PIX 525 Security Appliance — VPN Services Module and Associated Catalyst 6500 Series Security Bundles — Cisco 1-PORT GSHDSL WAN Interface Cards — Cisco 7603 Router — Cisco FlexWAN Module — Cisco 2600, 2800, 3700 and 3800 Series Content Engine Network Modules — Cisco VAM and VAM2 and Associated Integrated Security Bundles — 256 MB SDRAM for Cisco 7304 NSE-100, Spare — Cisco Catalyst 4000 Chassis, Supervisor Engine I and III DC Power Supplies — Cisco Catalyst 4006 Switch and Catalyst 4000 SUP II — Cisco Fibre Channel Over IP Port Adapter — Cisco 7200 Series Router I/O 48-MB PCMCIA Flash Disk Memory — Cisco OC-12C/STM-4 Port Adapter — Low Density Voice/FAX Network Mod and Voice Interface Cards for Cisco Routers — Original Low-Speed Fan Modules for Cisco 7603 and 7606 Routers — Cisco ONT 1031 Gigabit Ethernet Series — Cisco Catalyst 3508G XL Switch andCisco IOS Software 120WC — Cisco 7304 Compact Flash Memory, 64MB — Cisco Catalyst 2950 LRE 997 Switch — Cisco 2600/3600 Series Alarm Interface Controller Network Module — Cisco Catalyst 4912G, 2948G, AND 2980G-A Switches — AIM-COMPR2 Data Compression AIM for theCisco 2600XM Series — Cisco 3631

RN-28 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco 1710 Security Access Router — Cisco Catalyst 4003 Chassis, Supervisor Engine I and III — Cisco 7505 Series Router Chassis — Cisco Catalyst 2900 Series LRE XL Switch — Cisco 7100 Series — Cisco Catalyst 4000 Series 650 Watt DC — Cisco 7600 Optical Services Modules — Cisco 3600 Series Routers — Cisco NM-1FE2W and NM-2FE2W Network Modules — NM-1E1R2W, NM-1E2W, NM-2E2W Network Modules for Cisco 3600 Series — Selected Cisco 3600 Network Modules and Dial Bundles — Cisco 2525 Router — Fast Ethernet Interface Processors (FEIP2-DSW-2TX and FEIP2-DSW-2FX) for the Cisco 7500 Series Router — Cisco 7500 Series Channel Router — Cisco 10005 Internet Router Chassis — Intrusion Detection System (IDSM-1) Services Module for the Cisco Catalyst 6000 and 6500 Series — Cisco 2600 Series — Cisco Catalyst 5000 and 5500 Series — Route Switch Processor 2 for Cisco 7500 Series — Cisco VG200 Access Gateway — Cisco Catalyst 2900 XL Expansion Kit — Cisco 3600 Series Single Port OC-3 ATM Network Modules with Circuit Emulation Service (CES) — Cisco 1720 Modular Access Router — Cisco Catalyst 3524-PWR XL Inline Power Switch — Network Module NM-1FE-FX for the Cisco 3600 Series Routers — Cisco 2600 (Non XM) VPN Bundles — Cisco 1720 VPN Security Bundles — Cisco 3640 Router — Network Module NM-1FE-TX for the Cisco 3600 Series — Cisco 2613 Modular Router — Select Cisco 1900 Components — Cisco Catalyst 2900 Series XL ATM Switch

RN-29 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco Catalyst 3512 XL, 3524 XL, 3548 XL Switches — Cisco AS5300 Access Server — Versatile Interface Processor 2, Model 50 — Cisco 2501 and 2514 Routers — Cisco Catalyst 5000 Token Ring Switch Modules — Cisco 1000BaseT Gigabit Interface Connector (GBIC) — Cisco 7200 PWR-7200-DC Power Supply — NPE-200 and Cisco 7206 Router Chassis — Cisco 1700 Bundle: Firewall IPSec 3DES, Memory — Cisco 7200 NPE-300 and C7200-I/O-FE — Cisco 1700 Security Bundle: VPN Module, Firewall IPSec 3DES, Memory — Cisco 7200 Series Bundles — Cisco Catalyst 2900 Series XL Fixed-Configuration Switches — Cisco 7576 Router — Select Modules onCisco Catalyst 5000 — Cisco Catalyst 2948GL3-DC DC Power — Versatile Interface Processor 2, Model 15 — Cisco 2500 Series — PA-2FEISL-TX and PA2FEISL-FX Token Ring Switch Adapters — Cisco 2500 Low-Volume Models Only — Selected Cisco Catalyst 6500 Series Modules — Select Cisco Catalyst 5000 Modules — Cisco Catalyst 5000 Family Supervisor Engine III with NFFC I and II — Cisco Catalyst 2926G Switches — Cisco 7200 Series Network Processing Engine-175 — Route Switch Processor 4+ and 4 for Cisco 7500 Series Routers — One Port FDDI Single and Multimode Port Adapters — Cisco Catalyst 2926 Switches — LegacyCisco Catalyst 2980G Switch — Token Ring Adapters — NPE-200 for Cisco uBR7200 Series — Cisco Catalyst 2900 XL and 3500 XL Standard Edition Switches — Cisco 7200 Network Processing Engines NPE-100, NPE-150, and 7204 Series Router — Cisco Catalyst 5000 Supervisor Engine III

RN-30 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco 7505 Route Switch Processor 1 — Cisco 7500 Systems Legacy Interface Processors — Cisco 1700 Bundle: Firewall, Memory — Cisco Catalyst 2901 and 2902 — Cisco Catalyst 2822 Standard and Enterprise Edition Switches — Cisco Catalyst 1700, 2100, and 2800 — Cisco 2517, 2518, and 2519 Routers — Cisco Catalyst 1900 and 2820 Series Switches — Cisco ASM — Selected Cisco 3700 Series Router Parts — Cisco 7600 and Cisco Catalyst 6500 Gigabit Ethernet Enhanced Optical Services Modules — Cisco 10720 DPT Uplink Modules — Cisco 7206VXR Security Router Bundle with Network Processing Engine NPE400 — Cisco 7304 NSE-100 Network Services Engine — Cisco Gigabit Ethernet Switch Module for the HP Blade System — Cisco PIX 525 Security Appliance — Cisco 7600 and Cisco Catalyst 6500 Channelized OC-12 Optical Services Modules — Cisco 7600 and Cisco Catalyst 6500 Channelized DS3 Optical Service — Cisco Catalyst 4500 Access Gateway Module — Cisco Cat 4500 Series 48-Port 1000Base-LX Line Card and Cat 4000 POE — Catalyst 4500 Prestandard PoE linecard — Cisco Catalyst 4500 Series 32-Port 10/100BASE-T Line and 4-Port 100BASE-FX Cards — Cisco Catalyst 4500 Series 48-Port 10/100/1000-Mbps — Cisco Catalyst 4500 Series 48-port 100BASE-BX10-D Fast Ethernet Line Card — Cisco Catalyst 4500 Auxiliary Power Shelf — Cisco Catalyst 4500 Non-E-Series Chassis — Cisco Catalyst 4500 Non-E-Series Supervisor Engines — Cisco Catalyst 4500 Non-E-Series Line Cards — Cisco Catalyst 4500 Non-E-Series Fiber Line Cards and NetFlow Daughter Card — Cisco Catalyst 4500E Series Chassis

RN-31 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco Catalyst 4500E Series Supervisor Engine V-10GE and Select Line Cards — Cisco Catalyst 2960G 24 and 48-Port Switches — Cisco OSR-7609 Chassis — Cisco Catalyst 6500 Series Modules — Cisco Catalyst 6509-NEB Chassis and Fan Tray — Catalyst 6500 Sup Engine 1A and Switch Fabric Module — Cisco Catalyst 6500 Series OC-12 ATM Module — Catalyst 6500 Series Security System Bundles for Non-Enhanced Chassis — Catalyst 6500 10- and 100-Mbps Ethernet Fiber-Based Line Cards — Cisco Catalyst 6500 Series Supervisor Engine 2 and Switch Fabric Module 2 — Cisco Catalyst 6500 1300W DC Power Supply — Cisco CRS-1 Fabric Chassis Shelf Controller Card — Firewall Feature Set on the Cisco Catalyst 6500 — Cisco Catalyst 6500 1300W AC Power Supply — Cisco Catalyst 6000 24-Port FXS Analog Module — Select Catalyst 4900 Series Switches — Cisco ASR 5000 Series Release 7 — Cisco ASR 5000 Series Release 8 — Cisco ASR 5000 Series Release 9 — Cisco ASR 5000 Series Release 10 — Cisco ACE Application Control Engine Module Software Licenses — Cisco Catalyst 6500 and 7600 Series Firewall Services Modules — Select Cisco Catalyst 4500E Series Chassis — Cisco 7200 Series Routers — Cisco Aironet 1520 Series — Cisco 3G Wireless WAN High-Speed WAN Interface Cards for Cisco 1800/2800/3800 Series — Cisco 3G Wireless WAN PCI Express Card for the Cisco 880G Series Integrated Services Router — Cisco 881G Global 3G Fast Ethernet Security Router Bundle with Advanced IP Services — Cisco 850 Integrated Services Router for Small Offices Cisco 857 ADSL Router — Cisco 880 Integrated Services Router for Small Offices Cisco 887 ADSL

RN-32 SP Guru Network Planner Release Notes NetDoctor Enhancements Router — Cisco 880 Integrated Services Router for Small Offices Cisco 886 ADSL Router — Cisco 878 Integrated Services Router for Small Offices Cisco 878 G.SHDSL Router — Cisco 870 Series Integrated Services Routers for Small Offices Cisco 877 ADSL Router — Cisco 870 Integrated Services Router for Small Offices Cisco 876 ADSL — Cisco 871 Integrated Services Router — Cisco 867 Integrated Services Router for Small Offices — Cisco Catalyst 4500E Series Supervisor Engine V-10GE and Select Line Cards — Cisco 7600 Series Supervisor Engine 720 and Supervisor Engine 720 Bundles — Cisco 881 Ethernet Security Router with 802.11n for FCC, ETSI, and Japan — Cisco XR 12000 Series Router Multi-Service Blade

Sentinel Advisory Rules This release supports all the cumulative updates to the Sentinel Advisory Services rules, including:

• Security Advisory Rules — Cisco Security Advisory -Cisco ASA 5500 MSN IM Inspection DoS Vulnerability (cisco-sa-20111005-asa) — Cisco Security Advisory -Cisco ASA 5500 TACACS+ Authentication Bypass Vulnerability (cisco-sa-20111005-asa) — Cisco Security Advisory -Cisco ASA 5500 SunRPC Inspection DoS Vulnerabilities (cisco-sa-20111005-asa) — Cisco Security Advisory -Cisco ASA 5500 ILS Inspection DoS Vulnerability (cisco-sa-20111005-asa) — Cisco Security Advisory -Cisco ASA 5500 DHCP Memory Allocation DoS Vulnerability (cisco-sa-20121010-asa) — Cisco Security Advisory -Cisco ASA 5500 SIP Inspection Media Update DoS Vulnerability (cisco-sa-20121010-asa) — Cisco Security Advisory -Cisco ASA 5500 DCERPC Inspection DoS Vulnerabilities (cisco-sa-20121010-asa) — Cisco Security Advisory -Cisco IOS Malformed BGP Attribute Vulnerability (cisco-sa-20120926-bgp) — Cisco Security Advisory -Cisco IOS SIP DOS Vulnerability (cisco-sa-20120926-sip)

RN-33 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco Security Advisory -Cisco IOS SIP DoS Vulnerabilities (cisco-sa-20110928-sip) — Cisco Security Advisory -Cisco IOS IPv6 DoS Vulnerability (cisco-sa-20110928-ipv6) — Cisco Security Advisory -Cisco IOS IPS and Zone Based Firewall Vulnerabilities (cisco-sa-20110928-zbfw) — Cisco Security Advisory -Cisco IOS Tunneled Traffic Queue Wedge Vulnerability (cisco-sa-20120926-c10k-tunnels) — Cisco Security Advisory -Cisco IOS XR SSHv1 Dos Vulnerability (cisco-sa-20110525-iosxr-ssh) — Cisco Security Advisory -Cisco IOS XR IP Packet Vulnerability (cisco-sa-20110525-iosxr) — Cisco Security Advisory -Cisco Nexus 5000 and 3000 Series Switches ACL Bypass Vulnerability (cisco-sa-20110907-nexus) — Cisco Security Advisory -Cisco IOS RADIUS Authentication Bypass Vulnerability (cisco-sa-20050629-aaa) — Cisco Security Advisory -Cisco IOS IKE Vulnerability (cisco-sa-20130327-ike) — Cisco Security Advisory -Cisco IOS NAT Vulnerability (cisco-sa-20130327-nat) — Cisco Security Advisory -Cisco IOS RSVP DoS Vulnerability (cisco-sa-20130327-rsvp) — Cisco Security Advisory -Cisco IOS IP SLA Vulnerability (cisco-sa-20130327-ipsla) — Cisco Security Advisory - Multiple SNMP Vulnerabilities inCisco NX-OS Based Products (cisco-sa-20130424-nxosmulti)

• Operating System End-of-Life Rules — Cisco End-of-Life Notice -Cisco IOS XR Release 4.1 (EOL8684) — Cisco End-of-Life Notice -Cisco IOS Release 12.2(53)SG — Cisco End-of-Life Notice -Cisco IOS XE Release 3.8S — Cisco End-of-Life Notice -Cisco IOS Release 12.2(52)SG for Catalyst 4500 Series — Cisco End-of-Life Notice -Cisco IOS Release 12.2(50)SE for Catalyst 3750, 3560, 2960, and ME 3400 Series Switches — Cisco End-of-Life Notice - NX-OS Release 4.2 for Nexus 7000 Series — Cisco End-of-Life Notice - NX-OS Release 5.0 for Nexus 7000 Series — Cisco End-of-Life Notice - PIX OS Release 8.0 for PIX 515, 525, 535 — Cisco End-of-Life Notice - NX-OS Release 6.0 for Nexus 7000 Series — Cisco End-of-Life Notice -Cisco IOS Release 12.2(28)SB

RN-34 SP Guru Network Planner Release Notes NetDoctor Enhancements — Cisco End-of-Life Notice -Cisco IOS Release 12.3(7)XI for Cisco 10008 Router — Cisco End-of-Life Notice -Cisco IOS Release 15.1(2)EY for ME 3600X Switches and 3800X Routers — Cisco End-of-Life Notice -Cisco IOS Release 15.3(1)S for ME 3600X Switches and 3800X Routers — Cisco End-of-Life Notice -Cisco IOS Release 15.2(2)S for ME 3600X Switches and 3800X Routers — Cisco End-of-Life Notice - IOS XE Release 3.6S for ASR 903 Routers — Cisco End-of-Life Notice - IOS Release 15.3(1)S for Cisco 7600 Routers — Cisco End-of-Life Notice - IOS XE Release 3.9S for ASR 903 Routers — Cisco End-of-Life Notice - IOS Release 15.3(2)S for Cisco 3600X and 3800X ME Series Switches — Cisco End-of-Life Notice -Cisco IOS XR Release 4.1 — Juniper End-of-Life Notice - JUNOS 12.3 — Juniper End-of-Life Notice - JUNOS 13.1

RN-35 SP Guru Network Planner Release Notes NetDoctor Enhancements for PL3 NetDoctor Enhancements for PL3

The release the following enhancements:

• New Rules on page RN-36 — Cisco IOS XE Operating System on page RN-36 — Administration Support for Oversubscription on page RN-37

• Enhanced Rules on page RN-38 — Show Command Output Validation on page RN-38

New Rules Cisco IOS XE Operating System This release now supports theCisco IOS XE operating system with the following new rules for Configuration Consistency Validation and Operational Show Command Validation:

• Configuration Consistency Validation — Verify Identical Configuration Sections in IOS running onCisco IOS XE Devices — Mismatched Configuration Sections in IOS running onCisco IOS XE Devices — Cisco IOS (on IOS XE) Show Command Output Differs from Archived Show Command Output — Cisco IOS (on IOS XE) Show Command Outputs Differ

• Operational Show Command Validation — Cisco IOS (on IOS XE) Show Command Output Differs from Template File

Note—Beginning with this release, all existing rules that operate onCisco IOS have been updated to also operate onCisco IOS XE.

RN-36 SP Guru Network Planner Release Notes NetDoctor Enhancements for PL3 Administration Support for Oversubscription The following new Administration rules have been added to this release.

• Administration — Verify Client Bandwidth Oversubscription on Device — Verify Bandwidth Oversubscription on Ethernet Interfaces — Verify Bandwidth Oversubscription on ATM Interfaces — Unused Timeslots on Channelized Interfaces

RN-37 SP Guru Network Planner Release Notes NetDoctor Enhancements for PL3 Enhanced Rules Show Command Output Validation The Show Command Output Validation rules now provide the option to include their results “in line” in the show output itself, as shown in the following figure.

Figure 4-1 Example Details from Show Output Results

Click Detail . . . and then Additional Detail

Note—You can use new tag specifications for ignoring statements globally or by section

RN-38 SP Guru Network Planner Release Notes NetDoctor Enhancements for PL3

Key Concept—You can use new tag specifications for ignoring statements globally or by section.

New Attributes and Tags for Template Specification File v2 The following new attribute has been added to report results in the show command output for both the Group and Section tags:

• report_results_in_show_command_output = “True”

The following new tags have been added to specify which statements to ignore globally or by section:

• Specify an ignore template file for statements you want to ignore in your global configuration:

• Specify an ignore template file for statements you want to ignore in your section configurations:

See the next section for a configuration example.

RN-39 SP Guru Network Planner Release Notes NetDoctor Enhancements for PL3 For more information, see the example rule file, as shown in the following figure:

Figure 4-2 Report Results in Show Command Output Attribute Examples

Look at the Example Rule Parameter Files shipped with NetDoctor

[Install_Dir]\models\module_ref\netdoctor\Example_Rule_Parameter_Files\Operational_Show_Command_Validation

RN-40 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements Network Capacity Reports Enhancements

The following enhancements are available:

• Reporting Based on Time Zones on page RN-41

• Forecasting on page RN-42

• Reporting on Interface Metrics on page RN-44

• Using Interface Names and Descriptions as a Filter on page RN-45

• Grouping Interfaces and Devices by Device Roles on page RN-45

Reporting Based on Time Zones Beginning in this release, you can now:

• Specify different time zones for devices and use that information while analyzing various performance metrics

• Use different analysis hours for each time zone For example, specify M-F 9AM to 5PM for devices in New York and then Sat-Thu 8AM to 4PM for devices in Egypt.

For more information, see Setting the Time Frame for Analysis in the Network Capacity Reports section of the User Guide.

RN-41 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements Forecasting Now you can analyze metrics for user-specified forecast periods such as 12, 18, and 24 months. The capacity reports engine uses historical data to analyze the trend and determines the values for a future time period.

For example, the new Projected Link Utilization page includes 12, 18, 24 months intervals set in the analysis profile. A report with this page includes a bar chart of the multi-metric results as shown in the following figure.

Figure 5-1 Example LInk Utilization Forecast Page

You can now visualize information from multiple forecast periods on a single chart for purposes of comparing metric ranges You can now visualize the projection curves along with historical data in a single chart

You can now visualize the projection curves along with historical data in a single chart

RN-42 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements

Note—In previous releases, the capability to determine time duration for when a metric would reach a certain threshold was available as shown in the following diagram.

Figure 5-2 Example Number of LInks by Time to Reach Full Capacity

RN-43 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements Reporting on Interface Metrics This release now supports reporting on physical and logical interfaces such as VLAN, tunnel, and subinterface metrics. Pages that report on these metrics have been included in the new Interface Metrics Report, as shown in the following figure:

Figure 5-3 Example Top Interfaces by Load Page in New Interface Metrics Report

For more information about how to prepare the model for enabling this analysis, see Interface Load on Unmodeled Links in the User Guide.

The following metric is now available for analysis in Network Capacity Reports:

• Interface Availability

This metric can be viewed in the "Top Interfaces by Hourly Availability" page.

RN-44 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements Using Interface Names and Descriptions as a Filter

You can now use a filter profile to organize your reporting based on interface descriptions to target a subset of interfaces in a report such as WAN interfaces only. You can use plain text or regular expression based filters to match a substring in the interface descriptions. This filter can be used in combination with other filters to obtain the target set.

Key Concept—The available text in device configuration files for interface descriptions allows you to use a strategy for filtering specific interfaces using the description text.

For more information, see Filter Interfaces in the Network Capacity Reports section of the User Guide.

Grouping Interfaces and Devices by Device Roles You can now use device roles to group devices and interfaces to organize your reporting. In many cases, you already have user groups specified on VNE Server for the devices in your network.

Device roles can be used to specify an arbitrary membership of a device to any logical group such as an access-device or eastern-region. The capacity reports can be used to report on all (by default) or a filtered list (user-specified) of groups that a device belongs to.

For more information, see Using Group Profiles in the Network Capacity Reports section of the User Guide.

RN-45 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Network Capacity Reports Enhancements for PL3

The following enhancements are available:

• New Metrics Available for Reporting on page RN-46

• Site-Based Reporting on page RN-47

• Application Trends Reporting on page RN-48

• Links with Sustained Capacity Violations on page RN-49

• Using “Nth” Percentile Statistics for Reporting on page RN-50

• Projection Curve in Growth Analysis Output on page RN-51

• Enhanced Filtering Options on page RN-53

• Supplemental Data Reporting on page RN-54

New Metrics Available for Reporting The following metrics are now available for analysis in Network Capacity Reports:

• Device Availability

• CoS Discards

• Interface Errors and Discards

• VNES Round Trip Delay

• Latency

• Jitter

• Application Throughput

Where can I import these Network Capacity Planning metrics from? Import all metrics except Application Throughput from VNE Server.

Import Application Throughput related metrics from AppResponse Xpert as NetFlow data.

Key Concept—Using Network Capacity Reporting metrics, you can do analyses such as TopN, Trending, and Atypical deviation.

RN-46 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Site-Based Reporting You can now include “site-based pages” in your Network Capacity Reports that help you quickly identify sites with problematic links within and across the sites in your network.

Figure 5-4 Example Top Sites by Links with Highest Utilization

Key Concept—Site-based reports show analyses of intra-site and inter-site traffic as an aggregate—for example, all traffic in/out of a remote office in an Enterprise network or all traffic between city pairs in a Service Provider network

For more information, see Site-Based Reporting in the Network Capacity Reports User Guide.

RN-47 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Application Trends Reporting Using the Application Trends report template for Network Capacity Reports, you can report on NetFlow data imported from an AppResponse Xpert appliance.

The reports provide the following analysis output:

• Top Applications contributing to Link Throughput and Utilization

• Top Application Sources and Destinations by Throughput

• Fastest Growing Applications by Throughput

• Top Applications by Volume

Key Concept—Using Network Capacity Application Trends reports, you can correlate issues with the performance of network elements and specific application traffic.

For example, you can pinpoint the applications contributing to highly utilized links, as shown in the following figure.

Figure 5-5 Example Top Links by Utilization with Application Breakdown

View a breakdown of applications contributing to your link utilization

Determine if contributing applications are business critical or not

RN-48 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Links with Sustained Capacity Violations You can now define sustained violations for metrics. A sustained violation occurs when a metric exceeds a threshold over n consecutive time intervals—for example, when a link exceeds 75% utilization for more than 15 consecutive minutes.

Network elements can be categorized based on the severity of their violation occurrence rate—for example links with an average of 2 sustained violations per day are critical, as shown in the following figure.

Figure 5-6 Example Top Links by Utilization with Application Breakdown

Links with Capacity Violations by severity Sort columns in the table below for more details

RN-49 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Using “Nth” Percentile Statistics for Reporting This release now provides for more flexibility to set the “Nth” percentiles for reporting, as shown in the following figure. You can set up to four different percentile values for each metric.

Figure 5-7 Example 98th Percentile Reporting

For more information, see Using “Nth” Percentile Statistics for Reporting in the Network Capacity Planning User Guide.

RN-50 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Projection Curve in Growth Analysis Output Growth Rate and Time Until Saturation Statistics now include a projection curve as part of the drill-down chart, as shown in the following figure.

Figure 5-8 Show Projection Curve in the Output Example

Drill down to two Tabs of time series data that show the Link Load with a Trend Line and the Capacity with a Projection Curve

A projection curve shows from the start of the reporting period to the time when the link is expected to reach the capacity threshold. The capacity threshold is shown in a green line while the purple line is the projection curve. The time when the capacity would be reached can be obtained from the time-axis.

MPFIT uses the Levenberg-Marquardt technique to solve the least-squares problem. In its typical use, MPFIT will be used to fit a user-supplied function (the "model") to user-supplied data points (the "data") by adjusting a set of parameters. It is used by Network Capacity Reports feature for linear and non-linear curve fitting.

RN-51 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3

MPFIT ------MPFIT: A MINPACK-1 Least Squares Fitting Library in C

Original public domain version by B. Garbow, K. Hillstrom, J. More' (Argonne National Laboratory, MINPACK project, March 1980) Copyright (1999) University of Chicago (see below)

Tranlation to C Language by S. Moshier (moshier.net) (no restrictions placed on distribution) Enhancements and packaging by C. Markwardt

(comparable to IDL fitting routine MPFIT see http://cow.physics.wisc.edu/~craigm/idl/idl.html)

Copyright (C) 2003, 2004, 2006, 2007 Craig B. Markwardt This software is provided as is without any warranty whatsoever.Permission to use, copy, modify, and distribute modified or unmodified copies is granted, provided this copyright and disclaimer are included unchanged.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:

"This product includes software developed by the University of Chicago, as Operator of Argonne National Laboratory.”

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. WARRANTY DISCLAIMER. THE SOFTWARE IS SUPPLIED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE COPYRIGHT HOLDER, THE UNITED STATES, THE UNITED STATES DEPARTMENT OF ENERGY, AND THEIR EMPLOYEES: (1) DISCLAIM ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT, (2) DO NOT ASSUME ANY LEGAL LIABILITY OR RESPONSIBILITY FOR THE ACCURACY, COMPLETENESS, OR USEFULNESS OF THE SOFTWARE, (3) DO NOT REPRESENT THAT USE OF THE SOFTWARE WOULD NOT INFRINGE PRIVATELY OWNED RIGHTS, (4)DO NOT WARRANT THAT THE SOFTWARE WILL FUNCTION UNINTERRUPTED, THAT IT IS ERROR-FREE OR THAT ANY ERRORS WILL BE CORRECTED.

5. LIMITATION OF LIABILITY. IN NO EVENT WILL THE COPYRIGHT HOLDER, THE UNITED STATES, THE UNITED STATES DEPARTMENT OF ENERGY, OR THEIR EMPLOYEES: BE LIABLE FOR ANY INDIRECT,INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES OF ANY KIND OR NATURE, INCLUDING BUT NOT LIMITED TO LOSS OF PROFITS OR LOSS OF DATA, FOR ANY REASON WHATSOEVER, WHETHER SUCH LIABILITY IS ASSERTED ON THE BASIS OF CONTRACT, TORT (INCLUDING NEGLIGENCE OR STRICT LIABILITY), OR OTHERWISE, EVEN IF ANY OF SAID PARTIES HAS BEEN WARNED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGES.

RN-52 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Enhanced Filtering Options You can now use a CSV file to filter interfaces that you would like to consider for reporting. You must specify a comma separated tuple for each interface you want to report on and then set the filtering profile, as shown in the figure below.

Figure 5-9 Using a Filter by Interface List Example

Click Add and then choose Filter type: “Filter by Interface List”

Note—The list of interfaces in the file can be connected or unconnected

RN-53 SP Guru Network Planner Release Notes Network Capacity Reports Enhancements for PL3 Supplemental Data Reporting This release now includes a Supplement step in the Report Entry Specification Wizard. You can add supplemental data to each network element and view that information in tables and CSV files.

Figure 5-10 Adding Supplemental Data Example

Add supplemental data to the Details or All Links table or to the new CSV table shown below

Note—This example shows the Top Links by Load Details, which includes the available Supplemental details by default

CSV File Only Output In addition to charts and table, you can now direct analysis output to CSV files with user-specified files names. The CSV files can be accessed from the web report.

Note—Loads on both connected and unconnected interfaces are considered in Network Capacity Report. For more information, see Interface Load on Unmodeled Links on page RN-RN-57.

RN-54 SP Guru Network Planner Release Notes Planning and Design Enhancements Planning and Design Enhancements

The following enhancement is available:

• IP Fast Reroute with Loop Free Alternate on page RN-55

• Enhancement to Link Dimensioning on page RN-59

IP Fast Reroute with Loop Free Alternate This release supports a new Fast Reroute design action (“ip_frr_lfa”) that performs Loop Free Alternate (LFA) coverage analysis. LFA coverage provides for fast rerouting of traffic when the primary next hop becomes unavailable and prevents traffic from being forwarded back along the same path from which it originated. The new design action and its attributes are shown below.

Figure 6-1 ip_frr_lfa Design Action

Note that Flow Analysis is run as a sub-action when you run this design action.

For detailed information about the attributes of this design action, see Configuring the ip_frr_lfa Design Action in the Planning & Design user guide, or go to the design action in the Configure/Run Design Action dialog box, click Edit Attributes, as shown above, and then click on the question mark next to the attribute of interest.

RN-55 SP Guru Network Planner Release Notes Planning and Design Enhancements Network Changes When run, the design action enables LFA on the interfaces connected to the target links for the IGP you selected (OSPF or IS-IS). The following figure shows the interfaces that are running OSPF. Notice that LFA is set to “Enabled” on some of the interfaces.

Figure 6-2 LFA Enabled on OSPF Interfaces by ip_frr_lfa Design Action

After you run the design action, notice that LFA is now set to “Enabled” on the selected interfaces.

Note—The design action cannot be used to disable LFA on an interface.

Loop Free Alternate Reports New reports are available in this release for the analysis of loop free alternate routes in the network. The following sections provide a list of the reports.

• Design Action Reports on page RN-56

• Flow Analysis Reports on page RN-57

Design Action Reports The design action produces the following reports under Global Tables, available in the Results Browser. For more information about these reports, see Available Reports in the Planning & Design user guide.

• Inspection Summary

RN-56 SP Guru Network Planner Release Notes Planning and Design Enhancements • Interfaces with LFA Enabled

• LFA Coverage Violations

• Nodes with LFA Enabled

Flow Analysis Reports This design action runs Flow Analysis as a sub-action. Attributes are pre-configured to produce the following reports.

• Performance.Loop Free Alternate.IS-IS

• Performance.Loop Free Alternate.OSPF

For more information about these reports, see Flow Analysis Reports in the Planning & Design user guide.

Note—If you run a flow analysis independently of the design action, the value of the Loop Free Alternate attribute is not changed on any interface (see Network Changes on page RN-56). Visualization will not be launched at the end of a flow analysis, unless the flow analysis was run as part of the design action.

RN-57 SP Guru Network Planner Release Notes Planning and Design Enhancements LFA Visualization You can visualize the LFA coverage in a network after running the ip_frr_lfa design action. Visualization appears immediately upon completion of the design action if you have the LFA Coverage Visualization attribute set to “Yes”. Alternatively, you may use the menu option View > Set View for Network > LFA Coverage.... The following figure shows an example of LFA visualization and the LFA Coverage View Configuration dialog box, which is described in Visualizing Loop Free Alternate Routes in the Planning & Design user guide.

Figure 6-3 LFA Visualization Example

RN-58 SP Guru Network Planner Release Notes Planning and Design Enhancements By checking “Show LFA coverage values on links”, you can see the values (rounded to the nearest whole number) on the links in the project editor. Clicking on a link will bring up a balloon with more information, as shown below.

Figure 6-4 Viewing LFA Coverage on Links

Enhancement to Link Dimensioning The link dimensioning design action now lets you add ports. This lets you increase the number of ports available on a device for link creation and traffic distribution. A new attribute (“Allow Adding Ports”) is included, as shown below.

Figure 6-5 New Design Action Attribute for Adding Ports

When “Allow Adding Port” is set to Yes, the design action will create ports where necessary to add links and improve link utilization.

RN-59 SP Guru Network Planner Release Notes Planning and Design Enhancements After you run the design action, newly created ports are labeled as “new_” on upgraded devices, as shown in the figure below.

Figure 6-6 New Port Label—Default

RN-60 SP Guru Network Planner Release Notes Planning and Design Enhancements Design action results show the network changes made. The Summary Statistics report, shown below, shows that maximum link utilization in the network has dropped from 96% to 48% (half) because three new ports (supporting two new links) were added.

Figure 6-7 Summary Statistics Report for link_dimensioning

After you run the design action, you can use the reports to determine which nodes require additional ports to support the new links and reduced utilization.

• Link Bundle Summary—Displays the link bundles that are part of the network, along with the link count, link utilization, and cost of the links. The report shows whether links were upgraded, downgraded, or unchanged.

• Link Change Summary—For individual links, displays the initial and final utilization and cost, as well as any changes made to the link.

• Node Upgrade Summary—Lists the nodes that were upgraded, including the initial port count, number of ports added, and final port count.

RN-61 SP Guru Network Planner Release Notes Planning and Design Enhancements for PL3 Planning and Design Enhancements for PL3

The following enhancements are available:

• IGP Metric Optimization with Delay Constraints on page RN-62

• MPLS LSP Sizing with Option to Create LSP Bundles on page RN-64

IGP Metric Optimization with Delay Constraints This release supports setting the propagation delay constraint between node pairs for running an IGP Metric Optimization design action. You can also control whether you want the user-defined delay constraints written to the “SLA parameters Delay” attribute on flow objects.

Note—Writing to the “SLA parameters Delay” attribute only takes effect in either the "Repair" or "Optimization" mode of the IGP Metric Optimization design action—SLA parameters on flow objects are not changed in the "Inspection" mode.

Setting Delay Constraints Using the Delay Constraints Settings attribute, you can set a global value for delay between all node pairs or you can specify a settings file in “.gdf” format that will provide specific delay constraint values between specific nodes for the design action.

Figure 6-8 Symmetric Delay Constraints File in “.gdf” Format

Specify a global value for delay

Specify a file for Delay Constraints asym = Asymmetric

RN-62 SP Guru Network Planner Release Notes Planning and Design Enhancements for PL3

Using the Delay Constraints Files You can specify unique delay value between specific node pairs of interests using one of the following delay constraints files—one for symmetric delay and the other for asymmetric delay, as shown in the following examples.

Figure 6-9 Symmetric Delay Constraints File in “.gdf” Format File header (required): • Line 1: Title • Line 2: Node 1,Node 2,Delay

User-defined node pairs (nodes are specified using their hierarchical names): Beginning with Line 3, specify as many node pairs as you want to consider: ,,

Figure 6-10 Asymmetric Delay Constraints File in “.gdf” Format File header (required): • Line 1: Title • Line 2: Node 1,Node 2,Forward Delay, Backward Delay

User-defined node pairs (nodes are specified using their hierarchical names): Beginning with Line 3, specify as many node pairs as you want to consider: ,, ,

Save your configured Delay Constraints File in “.gdf” format in one of your model directories such as op_models. You can then specify the file in the Delay Constraint Settings compound attribute, as described in Table 10-1 of the Using IGP Metric Design Actions for Traffic Engineering section of the Planning and Design User Guide.

RN-63 SP Guru Network Planner Release Notes Planning and Design Enhancements for PL3 MPLS LSP Sizing with Option to Create LSP Bundles In some cases, you can significantly improve the survivability and load balancing of some of the traffic flowing through the LSPs in your network by “splitting” the LSPs into LSP bundles.

For example, you might have traffic flowing at a rate of 1 Gbps between two sites in your network. A single LSP may not be able to carry the traffic if a 1 Gbps path is not available end to end. However there may be paths available than can individually support lesser bandwidth requirements. By setting the new attributes in the MPLS Sizing design action, you can configure LSP bundling with the maximum bandwidth set for each LSP.

In the following scenario, the new attribute “Split LSPs” has been enabled, the “Maximum LSP Bandwidth” has been set to 500 Mbps, and the “Maximum Bundle Size” has been set to 4. These settings accommodate a traffic flow that has over 1Gbps.The MPLS LSP Sizing results show that two LSPs have been created: LSP_Charlotte -> Sacramento1 LSP_Charlotte -> Sacramento2

Figure 6-11 LSP Splitting Attributes Example Set the following: Maximum Bandwidth: 500,000,000 Split LSPs: Yes Maximum Bundle Size: 4

Two new LSPs

Key Concept—By configuring and running the MPLS LSP Sizing design action to consider LSP splitting, you can analyze the results of LSP bundling changes in your network and determine whether or not you want to configure them on your operational network.

RN-64 SP Guru Network Planner Release Notes Peering Center Enhancements Peering Center Enhancements

New Peering Wizards Using the new Peering Center wizards, you can configure IP connectivity to a new external AS (Autonomous System) or link to an existing AS and compare “before” and “after” results of your exit traffic flows by running a flow analysis. From the Protocols menu, choose BGP > Open Peering Center and then use the right-click menu as shown in the following figure.

Figure 7-1 The New Peering Wizards

Use the right-click menu to: • Add Peerings • Add a Peer

RN-65 SP Guru Network Planner Release Notes Peering Center Enhancements

Key Concept—The two wizards are very similar—Add a Peer creates an external AS node and creates links between the specified border routers and the external AS node—Add Peerings only creates links between the specified border routers and the external AS node because the external AS would already be present in the network model.

The main steps to configure and run the wizard are shown in the following figure.

Figure 7-2 The Main Steps for the Add a Peer Wizard

Step 1—Configure

Step 2—Commit

Step 3—Analyze

Step 4—Report

RN-66 SP Guru Network Planner Release Notes Peering Center Enhancements

Note—When you use the wizard, you can duplicate the existing scenario as a backup while you consider the changes in a new scenario with the proposed peering, as shown in the following figure.

Figure 7-3 Duplicate Current Scenario as a Backup

Check “Duplicate current scenario” to preserve the peerings of the current scenario as test alternatives by completing the steps of either wizard

RN-67 SP Guru Network Planner Release Notes Inventory Report Enhancements Inventory Report Enhancements

The following enhancements are available:

• Trend Line in Reports on page RN-68

• Cisco IOS Running on Cisco IOS XE devices on page RN-70

• Private and Public IPv4 Address Prefixes Rules on page RN-70

Trend Line in Reports Inventory reports now include a trend line based on the current and historical data—providing a quick analysis of the growth rate of key elements in your network, as shown in the following figure.

Figure 8-1 Example Trend Line

The red trend line shows the linear growth rate as an overlay on the inventory data reported over time

Do I have to configure Trending to see the results in my report? No, when you run an Inventory report, trending data is saved to a database by default and the trending graphs display the historical data based on each previous run of your Inventory report.

Key Concept—You can control whether you want a specific Inventory analysis run considered for trending data by using the “Save trending data option.” For example, you might want to run a report without this option selected to get report results without adding the results to the trending database.

RN-68 SP Guru Network Planner Release Notes Inventory Report Enhancements Configure Inventory report trending by choosing Topology > Inventory Reports > Configure/Run Inventory Report and selecting the Settings tab, as shown in the following figure.

Figure 8-2 Trending Settings

Control the way you want consider trending data

After generating reports that have saved trending data, you can manage what data you want considered by choosing Topology > Inventory Reports >

Figure 8-3 Trending Settings

Manage trend data that you wan to exclude for your Inventory reports

RN-69 SP Guru Network Planner Release Notes Inventory Report Enhancements Cisco IOS Running on Cisco IOS XE devices Inventory Reports now report on IOS running as a process on IOS XE devices in the following sections:

• OS Inventory Tables

• Per Device Module Information Page

Figure 8-4 Example OS Inventory Table Entry and Per Device Module Information Page

OS Inventory Table

Per Device Module Information Page

Private and Public IPv4 Address Prefixes Rules Inventory Reports can now provide the private and public IPv4 address prefixes for specific “Markets” in your network. The following example Inventory Report shows the Report Summary section for the output of the new private and public IPv4 address prefixes rules.

Figure 8-5 Public and Private IPv4 Prefixes in Example Inventory Report

RN-70 SP Guru Network Planner Release Notes Inventory Report Enhancements

Note—NetMapper now includes a Market Diagram that shows each Market as a section of the network. For more information about this diagram, see New Market Diagrams on page RN-85.

Configuring the Public IPv4 Prefixes Rule The following parameter must be defined for the "Public IPv4 Prefixes" rule:

• Market-to-Prefixes Mapping File—This is the same .csv file described in Configuring a Market Diagram on page RN-85.

Note—Any market that is not listed in this file will not be included in the "Public IPv4 Prefixes" Inventory Report.

Configuring the Private IPv4 Prefixes Rule The following parameters must be defined for the "Private IPv4 Prefixes" rule:

• Group Hierarchy File—This is the standard group hierarchy file which is used for Inventory and NetDoctor reports. (Please see the section on “Using the Group Hierarchy File” in the SP Guru Network Planner user guide for more information.)

An example of this file can be found in your SP Guru Network Planner installation, in the models directory: /models/module_ref/sentinel/grouping-example.xml

Note—Note that one group must be defined for each market; any markets which do not have a corresponding group defined will not be included in the "Private IPv4 Prefixes" Inventory Report.

• Market-to-Prefixes Mapping File—This is the same .csv file described in Configuring a Market Diagram on page RN-85.

Note—Any market which is not listed in this file will not be included in the "Private IPv4 Prefixes" Inventory Report.

Run the Inventory report as specified in the “Inventory Reports” section of the SP Guru Network Planner User Guide.

RN-71 SP Guru Network Planner Release Notes NetMapper Enhancements NetMapper Enhancements

The following enhancement is available for PL5.

• DMVPN Tunnels on page RN-72

• New Layout Schemes on page RN-73

DMVPN Tunnels The following diagrams now support including DMVPN tunnels as shown in the figure:

• Layer 3

• Layer 2-3

• Network Hierarchy as Displayed in the Project Editor

Figure 9-1 Example DMVPN Tunnels in a NetMapper Web Report

DMVPN

Use the following two options in Step 2 of the NetMapper wizard to configure DMPVPN tunnels in your diagrams:

• Content Tab—Include DMVPN Tunnels (Default value: Yes)

• Layout Tab—DMVPN Tunnel Color (Select color)

RN-72 SP Guru Network Planner Release Notes NetMapper Enhancements New Layout Schemes The release includes the following new layout schemes:

• Exact Project Editor Layout

• Dispersed Project Editor Layout

These options can be used in conjunction with the snap-to-grid feature in the projector editor to layout the devices in the network and then generate a NetMapper diagram that has the same layout—either exact or dispersed.

For more information about laying out devices in the project editor, see New Snap-to-Grid Layout Options on page RN-7.

Note—Dispersed in this case means that NetMapper will adjust the positions of devices to have uniform link spacing for the diagram. In some cases, it will layout devices to avoid any overlap between them and in other cases might reduce the distance between devices.

RN-73 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 NetMapper Enhancements for PL3

The following enhancements are available:

• New Web Report Output Format on page RN-75

• Enhanced Layout Strategies on page RN-79

• New Variable Page-Size Options on page RN-81

• New Wizard Options on page RN-82

• New Market Diagrams on page RN-85

• Visualize Roles on page RN-87

• Color Options with Non-Default Settings in Wizard on page RN-89

• Clean Up Document Sets on page RN-90

• New Manage Options on page RN-90

• Additional Chassis Icons for Diagrams on page RN-91

• New Support for Devices and Modules on page RN-91 — Diagrams of VMWare ESX Servers on page RN-91 — Cisco IOS on Cisco IOS XE on page RN-92 — Cisco Nexus 2000 Series Fabric Extenders on page RN-92 — Alcatel-Lucent IPSec SAs and Cisco Tunnel-based IPSec SAs on page RN-94 — Virtual Private LAN Service (VPLS) and Virtual Private Wire Service (VPWS) on page RN-95

RN-74 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 New Web Report Output Format This release supports generating diagrams as Web Reports. You can view these diagrams in a Web Browser that supports HTML 5 (Internet Explorer 9 and above and Firefox 4 and above) without the need for Visio. You have the option to generate diagrams in both Web and Visio formats.

The new NetMapper Web Reports include a comprehensive navigation panel to help you pinpoint sections of a diagram easily and then quickly navigate to other sections, as shown in the following figure.

Figure 9-2 New Web Report Format Example

Select a node and then hover to view more details

Tip—Use the scroll wheel of your mouse to zoom in or out while viewing objects in the main window of a NetMapper Web Report.

How do I generate a NetMapper Web Report? NetMapper now generates a set of web report files by default—you control the behavior of how and when you want to publish or view them. In Step 2 of the wizard, make sure that you select the option “Use web-oriented defaults,” as shown in the following figure.

Figure 9-3 Web-Oriented Defaults

The Web Sensitive settings provide visual display settings for web viewing as opposed to viewing or printing from a Visio diagram

RN-75 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3

Note—For more information about the “Filter options by” setting, see New “Filter options by” Selection List on page RN-82.

NetMapper publishes the web report format when you select either Diagram and Web Report Files or Web Report Files Only in the “Publish Behavior” option of Step 2 of the Wizard. When you click Finish, the Web Report diagram gets generated and published to the “Copy Diagram Files to Directory” location and the Report Server if selected.

Figure 9-4 Generating a NetMapper Web Report

Select Diagram and Web Report Files or Web Report Files Only in the Publish Behavior option

Choose the directory where you want to access your Web Report

When you generate diagrams interactively using the NetMapper wizard, the diagram opens in a new web browser window Alternatively, you can open the file NetMapper_Report.html in the directory you specify

RN-76 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3

Note—You can also view or publish a NetMapper Web Report after you generate any diagram using the following steps:

1) Choose NetMapper > Manage, and select your generated diagram from the menu list.

2) In the Individual Document Operations section of the Manage window, click “Open Web Report” to view or “Export Web Report” to specify the directory where you want to save the Web Report and then click OK to export the diagram.

Figure 9-5 Export Web Report from the Manage Window

Select “Open Web Report” to view and “Export Web Report” in the NetMapper > Manage window to publish

Supported Web Browser for Web Reports NetMapper uses scalable vector graphic (SVG) content to generate the web output for network topologies, which can only be viewed in web browsers that support HTML5. We currently support and recommend using Microsoft Internet Explorer 9 or Firefox 10 and greater.

RN-77 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Using the Magnify Options for Viewing Web Reports The new Web Report format includes options to view diagrams using the Magnify styles, as shown in the following figure.

Figure 9-6 Example Diagram View Options Overlapping Right

Non-overlapping

Bottom

Corner

RN-78 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Enhanced Layout Strategies Use the following table as a guide for your diagram layout strategy.

Table 9-1 Layout Strategies Examples

Strategy What to consider . . . Example

Device Promotion The default settings for initial NetMapper diagrams now use the following Device Promotion and flexible spacing Most Connected options in the Layout tab of Step 2 in the wizard: • Use Flexible Column Spacing • Use Flexible Row Spacing • Promote Most-Connected Devices Flexible Columns The example shows the devices with the most connections at the top of the diagram and the space between rows and columns varies. You must have the “Device Scheme Layout” set to Flexible Rows Row-based Grid Layout. For more information, see Flexible Column and Row Spacing and Connected Device Promotion in the NetMapper User Guide.

Device Layout Select one of the pre-configured layout schemes Schemes available in the Layout tab of Step 2 of the wizard to generate an organized display without having to adjust too many options:

The example shows the Circular Free Layout scheme.

Role-Based Configure the settings in Step 4 of the wizard to specify Layout the devices you want to display by roles—Core, Core Distribution, Access.

Distribution

Access Note—The example shows the three rows specified by roles. Alternatively, you can specify devices using other criteria such as device names or selecting them. You must have the “Device Scheme Layout” set to Row-based Grid Layout. For more information, see Step 4—Layout Groupings in the NetMapper User Guide.

RN-79 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3

Table 9-1 Layout Strategies Examples

Strategy What to consider . . . Example

Project Editor Use the New Snap-to-Grid Layout Options to layout the Layout devices in your network in the Project Editor. The example shows a basic grid of devices that you can manually position. Note—Use this strategy for the Network Hierarchy as Displayed in the Project Editor Diagrams. For more information about generating the Network Hierarchy Diagram in an end-to-end workflow, see Network Projects for Network Hierarchy as Displayed in the Project Editor in the End-to-End Workflow for Automated Network Documentation NetMapper Workflow.

What to consider for all strategies . . .

In Step 2 of the wizard, select the page size option based on the following guidelines

Auto-Page Size Although auto-page sizing might provide less control of the placement of specific devices, the web report Based on becomes easier to view and navigate. letter-sized diagram area for Make sure you select “Use web-oriented defaults” in US, Europe, and Step 2 of wizard. Asia Select one of the “Variable size” options. For more information, see Step 2—Diagram Options in the Netmapper User Guide.

Set Page Size Determine the page size based on the number of devices you want on each uniform section or page in your Large numbers of diagram. devices on a Plotter Select one of the set page size options, such as an “E: 34 x 44 in.” size shown in this example. For more information, see Using Detailed Layout Options in the NetMapper User Guide.

RN-80 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 New Variable Page-Size Options The release supports generating diagrams with variable page sizes, as shown in the following figure.

Figure 9-7 Variable Page-Size Options

Select one of the “Variable size (based on. . .” options—NetMapper then sizes the area of the diagram view based on the number of objects

When do I use the new variable page option? Choose this new option in Step 2 of the wizard for diagrams that have multiple pages but the number of elements on each section or page varies quite a bit.

For example, the first page might have the most elements in the diagram but some of the subsequent pages might have only a few. NetMapper adjusts the page size to fit the objects without having a lot of white space for pages with fewer elements.

RN-81 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 New Wizard Options New “Filter options by” Selection List In Step 2 of the wizard, you can now display only the options based on a specific category, as shown in the following figure.

Figure 9-8 “Filter options by”

In this example, only the options for Interfaces display—an easy way to quickly configure or view options for interfaces only

New Option for Determining Device Management Addresses In Step 2 of the wizard, you can now specify how you want NetMapper to determine the management address of a device from the labels tab, as shown in the following figure.

Figure 9-9 Device Management Address Is Option

Select how you want NetMapper to infer the device management addresses in your network diagram—either by the device configurations or by using the address that VNE Server uses to collect data from the device

The options with (Highest) and (Lowest) in the names refer to the highest or lowest loopback address associated with a Layer 3 device—in other words, the Highest or Lowest is first selected from the loopbacks but if there are no loopback addresses to consider, NetMapper considers all interface addresses Note—The Lowest and Highest are the numerically highest or lowest address value not interface number

Key Concept—By specifying the IP addresses that VNE Server uses to access devices for data collection as the device management address labels in your diagrams—you can use these same IP addresses to SSH/Telnet to these devices and investigate any issues you find while viewing your diagrams.

RN-82 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Link Scaling Factor You can now use the NetMapper wizard Link Scaling Factor from the Layout tab to adjust the thickness of the links in your diagrams.

Figure 9-10 Link Scaling Factor Option

Use the Link Scaling Factor option to adjust the link thickness in your diagrams

Flexible Column and Row Spacing and Connected Device Promotion NetMapper now provides out-of-the box default layout options that better organize the display of your topology in network diagrams—taking into account the number of network connections for rows and columns as well as promoting well-connected devices to the top of your diagrams, as shown in the following figure.

Figure 9-11 Options for Flexible Column and Row Spacing and Connected Device Promotion

Most-Connected

Flexible Column

Flexible Row

RN-83 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 New Device Layout Scheme Options You can now select from a variety of device layout scheme to organize the display of your diagram elements by selecting one of the options as shown in the following figure.

Figure 9-12 Device Layout Scheme Options

Use the Device Layout Scheme options to select an auto-layout display—available for most diagrams when appropriate

RN-84 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 New Market Diagrams Using the new Market Diagram, you can now generate a Layer 2-3 network diagram that shows specific “markets” as sections. Markets are determined by the public and private IP addresses owned by that market.

The generated diagram includes a topology map of the interconnected Markets as well as a list of the Markets, as shown in the following diagram.

Figure 9-13 Market Diagram Example

Topology of the Market sections defined by private and public IP addresses owned by that Market

Table of Contents page includes a list of the Markets linked to Diagram Sections (pages)

Configuring a Market Diagram To generate a Market diagram specify the sections of the diagram using the "Market-to-Prefixes Mapping File" diagram option. Using this option, specify a comma-separated-values (CSV) file containing the mapping from market name to the config file types that contain the output of the show commands listing the public and private IP addresses owned by that market.

The Market-to-Prefixes Mapping File should include a row for each market in the network with the following entries:

• The market name

• The type of config file that contains the show command output listing public prefixes owned by that market

• The type of config file that contains show command output listing private prefixes owned by that market

RN-85 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Here are some example entries in the correct format for a Market-to-Prefixes Mapping File:

#Market Name, Public Prefix Config File Type, Private Prefix Config File Type Philadelphia, public_prefixes_PHILA, ospf_phila Harrisburg, public_prefixs_HARRIS, ospf_harris Portsmith, public_prefixes_Portsmith, private_prefixes_portsmith

Entries should be comma-delimited. If a market does not have show command output of a particular type—that is, no public prefix information was collected for that market—then this field can be blank.

Tip—Use the “#" character at the beginning of a row that you want use for commenting. NetMapper ignores any line in the file that begins with a "#" character.

Specify the path file to this file for the "Market to Prefixes Mapping File" option in the Documents tab of the NetMapper wizard, as shown in the following figure.

Figure 9-14 Specify a CSV File with Market Names and Config File Types

Use the Market-to-Prefixes Mapping File option to specify the mapping of the Markets to the Config File types in the show command output of device configurations in your network

RN-86 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Visualize Roles You can now quickly visualize the existing roles available for current objects in the network model. Choose Topology > Role Assignment > Scan Network For Roles. Check “Show Role Balloons” and then Select Nodes With Role, as shown in the following figure.

Figure 9-15 Using the Role Assignment Menu

RN-87 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Managing Roles on Selected Objects You can now manage roles on selected objects using the Role Assignment menu. For example, select one or more objects in the network scenario and then choose Topology > Role Assignment > Assign Roles To Selected Nodes or Remove Roles From Selected Roles, as shown in the following figure.

Figure 9-16 Managing Roles from Selected Objects

You can specify a role in the text field or you can select an existing role from the drop-down list

You can also remove roles from selected objects

Note—In this example, the new menu option “Show Role Balloons” has been selected.

RN-88 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Color Options with Non-Default Settings in Wizard Use the NetMapper UI preference “Color Options With Non-Default Values’’ to highlight settings that you have modified in the Wizard, as shown in the following figure.

Figure 9-17 Color Options with Non-Default Values Example

RN-89 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Clean Up Document Sets Choose NetMapper > Clean Up Document Sets to remove, compress, or keep documents sets stored locally on your system.You can specify how long you want documents to be stored and run an automation task to remove sets of documentation based on the Days Old setting, as shown in the following figure.

Figure 9-18 Clean Up Document Sets Example

Use the Exceptions column to leave the document sets you want to keep—click in any of the last four columns to select an option to except, compress, or delete a document set

New Manage Options Choose NetMapper > Manage and select the Document Set to view and use the new options, as shown in the following figure.

Figure 9-19 Color Options with Non-Default Values Example

Select a Document Set from the drop-down list

New manage options

Note—The “Generate New” option is useful when you do not want NetMapper to consider the previous version of the diagram when generating a new diagram but still want to use the current options specified in the wizard

RN-90 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Additional Chassis Icons for Diagrams

Note—With each release of NetMapper, additional Chassis Icons are available as stencils.

New Support for Devices and Modules Diagrams of VMWare ESX Servers NetMapper Layer 2, Layer 3, Layer 2-3, and Network Hierarchy diagrams have been enhanced to create diagrams of VM hosts and to list the VM hosts and their VMs in tables.

Figure 9-20 Example VMWare in Diagram

RN-91 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Cisco IOS on Cisco IOS XE This release includes support for devices running Cisco IOS on Cisco IOS XE. When you select the option to “Include Device OS Label” in the Label tab of Step 2 of the wizard, NetMapper displays the Cisco IOS daemon version running on the IOS XE version, as shown in the following figure.

Figure 9-21 Cisco IOS Running on Cisco IOS XE Device

IOS Daemon Version IOS XE Version

Cisco Nexus 2000 Series Fabric Extenders This release includes support for Cisco Nexus 2000 Series Fabric Extenders in Layer 2, Layer 2-3, and Network Hierarchy diagrams.

Key Concept—Fabric Extenders integrate with a parent switch, the Cisco Nexus 5000/7000 Series switch, to allow automatic provisioning and configuration taken from the settings on the parent switch. This integration allows large numbers of servers and hosts to be supported using the same feature set as the parent switch, including security and quality of service (QoS) configuration parameters, as shown in the next figure.

RN-92 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Fabric Extenders display in your diagrams with connections to your hosts and servers by selecting Yes to the “Include Fabric Extenders” in Step 2 of the wizard, and specifying the End System options shown in the following figure.

Figure 9-22 Cisco Nexus 2000 Series Fabric Extenders Example

Cisco Nexus Switches

Fabric Extenders

Connected as Individual Devices

Connected as Groups

End System Options with Fabric Extenders Connected as Hyperlinked Groups

Note—If you have Fabric Extenders in your network and select “No” for the NetMapper option “Include Fabric Extenders,” the end systems connect to the parent switches instead.

RN-93 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Alcatel-Lucent IPSec SAs and Cisco Tunnel-based IPSec SAs This release supports IPSec Security Associations (SAs) configured on Alcatel Lucent devices.

You can view the IPSec SAs in Layer 2, Layer 2-3, and Network Hierarchy as Displayed in the Project Editor diagrams, as shown in the following examples.

Figure 9-23 Alcatel-Lucent IPSec SA Example

Note—Cisco devices support Tunnel based IPSec SAs, as shown in the following figure.

Figure 9-24 Example with Alcatel-Lucent IPSec SAs and Cisco Tunnel-based IPSec SAs

RN-94 SP Guru Network Planner Release Notes NetMapper Enhancements for PL3 Virtual Private LAN Service (VPLS) and Virtual Private Wire Service (VPWS) Virtual Private Wire Service (VPWS) hierarchical and circular layouts are now suported in "MPLS LDP Layer 2 VPNs." diagrams.

Virtual Private LAN Service (VPLS) VPLS hierarchical and circular layouts in "MPLS LDP VPLS VPNs" diagrams.

RN-95 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3 Network Differences Enhancements for PL3

The following enhancements are available for PL3:

• Huawei VRF Table Differences on page RN-96

• Differences in BGP RIB Tables on page RN-100

• Cisco IOS XE Differences on page RN-101

Huawei VRF Table Differences Network Difference Reports now support reporting of the differences between Huawei VRF tables, as shown in the following figure.

Figure 10-1 Example Section of Network Difference Report for Huawei VRF Tables

Key Concept—You can generate a Network Difference report that shows these differences by collecting the Huawei VRF show output on VNE Server

Log on to the VNE Server console to set up the device driver as shown in the following sections.

RN-96 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3

Figure 10-2 Set Up Device Driver

Figure 10-3 Edit IP Route Command

Double click on the command to edit and include the specific vrf instance name, for example: display ip routing-table vpn-instance test_1 Click Next and Finalize the Device Driver

Once the Device Driver has been edited, go to "Mgmt" tab to edit the "Device Data Collection" adapter, as shown in the following figure.

RN-97 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3

Figure 10-4 Set the Huawei(VRF)

After importing a network from VNE Server that has the VRF information from Huawei devices, you can generate a Network Difference report with the VRF table differences.

Choose Scenario > Network Difference Report > Generate Report

Click Edit and then go to the Routing tab to select “Changes in VRF tables,” as shown in the following figure.

RN-98 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3

Figure 10-5 Example Section of Network Difference Report for Huawei VRF Tables

You must select the Changes in VRF Table rule, as shown here—you can optionally

Set the following parameters to Yes to include more than just the Next Hop differences

RN-99 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3 Differences in BGP RIB Tables This release now supports differences in the BGP RIB tables from your operational network by configuring the Rule and parameters as shown in the following figure.

Figure 10-6 Configuring Network Differences for BGP RIB Tables

Note—You must import the BGP RIB-in information as shown in the following figure.

Figure 10-7 Importing BGP RIB-in Information

RN-100 SP Guru Network Planner Release Notes Network Differences Enhancements for PL3 Cisco IOS XE Differences This release includes reporting differences on Cisco IOS running as a process on Cisco IOS XE devices. Network Difference Reports now report on both IOS version as well as IOS XE version of IOS XE devices, as shown in the following figure.

Figure 10-8 Cisco IOS XE Example Network Difference Reporting

For more information about configuring Network Difference Reports, see Network Differences in the SP Guru Network Planner User Guide.

RN-101 SP Guru Network Planner Release Notes Flow Analysis Enhancements Flow Analysis Enhancements

The following enhancements are available.

• Enhanced Support for Juniper Routers on page RN-102

• Support for IP Fast Reroute Loop-Free Alternate on page RN-107

• Enhancements to IPv6 Support in Flow Analysis on page RN-107

• Enhancement to Route Visualization for IPv6 on page RN-109

• Support for Additional Service Level Agreement (SLA) Criteria on page RN-111

Enhanced Support for Juniper Routers Several enhancements are included in this release that extend coverage for virtual routing and forwarding on Juniper Networks routers. You can import Juniper configuration files using either eXpress Data Import or import from VNE Server, and then run a flow analysis. The following enhancements are included:

• Support for Forwarding and No Forwarding Routing Instances on page RN-102

• Support for Routing Table Groups (RIB Groups) on page RN-103

• Analyzing Routing Instances for Juniper Routers on page RN-103

• Support for Juniper Service Delivery Gateway and MX Devices on page RN-104

Support for Forwarding and No Forwarding Routing Instances Juniper routers have the concept of routing instances, which can include virtual routing and forwarding (VRF), Layer-2/3 virtual private networks (VPN), or virtual routers. Most routing instances are already supported in SP Guru Network Planner In this release, two additional types of routing instances are supported: forwarding and no forwarding.

• The forwarding routing instance has its own forwarding plane, but you cannot configure any interfaces or routing protocols in this instance. However, routing information can be moved to a forwarding instance through the use of RIB groups. To make use of a forwarding instance, packet filters must be defined on interfaces. If a packet matches the filter, it is then forwarded to the defined forwarding routing instance.

• The no forwarding routing instance has interfaces and can routing protocols or use static routes. Once the routing instance determines the best routes, it passes those routes to the global forwarding plane.

RN-102 SP Guru Network Planner Release Notes Flow Analysis Enhancements For more information about importing routing instances, see Enhanced Support for Juniper Routing Instances on page RN-9.

Support for Routing Table Groups (RIB Groups) Juniper routers can use RIB groups to move (export or import) routes between routing instances. For example, a forwarding instance will determine best routes but does not move those routes to the global routing table by default. If desired, a RIB group can be defined and used to move the routes.

Policies can be used together with RIB groups to control which routes are to be moved across routing instances. Only the routes that pass the policies will be moved by the RIB group.

For more information about importing RIB groups, see Support for Routing Table Groups (RIB Groups) on page RN-10.

Analyzing Routing Instances for Juniper Routers After running flow analysis, you can use the following options to analyze the traffic flows over the routing instances.

• Show Routes—Right-click on a demand, and select Show Routes (Flow Analysis) to see the path taken by the traffic.

• Performance.Forwarding Instance Table or Performance.No Forwarding Instance Table—Right-click on a node, and select View Results. In the Results Browser, expand the Performance report tree.

• Performance. Demand Routing Report—Right-click on a demand, and select View Results. In the Results Browser, go to Performance > Demand Routing. Notice in the example below that the forwarding instance (“ISP1”) is shown in the VPN column. The Element column shows that the path for the demand is learned from the ISP1 forwarding plane.

Figure 11-1 Demand Routing Report for Routing Instances

RN-103 SP Guru Network Planner Release Notes Flow Analysis Enhancements • RIB Groups Report—In the Results Browser, choose Configuration.RIB Groups to view the RIB groups configured on a device, the export instance, import instance, import policies applied, and protocols applied to the routes. In the RIB Groups report shown below, notice that both the ISP2 and ISP1 routing instances are sending routes from their forwarding plane to the global forwarding plane.

Figure 11-2 RIB Groups Report

Support for Juniper Service Delivery Gateway and MX Devices

You can now perform a flow analysis on a network model that includes Juniper Networks’ Service Delivery Gateway (SDG) and MX devices. The following features are supported for the Juniper devices in this release.

• Layer-2 bridging over Layer-3 — Bridge domains are supported and are configured in the attribute Transparent Bridge Parameters > Bridge Groups. — Both enterprise and service provider style interfaces are configured in the attribute Transparent Bridge Parameters > Interface Information, as described in the figure below.

RN-104 SP Guru Network Planner Release Notes Flow Analysis Enhancements

Figure 11-3 Enterprise and Service Provider Style Interface Support in SP Guru Network Planner

Bridge domains are configured as Bridge Groups in

Each interface is configured for one or more supported VLANs. Enterprise style interfaces are configured with Supported VLANs in the main panel. Service Provider style interfaces are configured under Subinterface Information.

• Load balancing with the Application Delivery Controller (ADC) Load balancing is supported in a limited way. Traffic that is destined for a server beyond the SDG is routed to and terminated at the SDG virtual IP address. The virtual IP addresses are configured in the attribute Load Balancer Configuration > Virtual Addresses, as shown below.

RN-105 SP Guru Network Planner Release Notes Flow Analysis Enhancements

Figure 11-4 Load Balancing with Juniper ADC

• Adaptive Service Configuration Adaptive service sets that are configured on Juniper adaptive service interfaces appear in the IP > IP Routing Parameters > Adaptive Service Configuration attribute.

Note—Only Next Hop Based Adaptive Services are supported by Flow Analysis. Interface Based Adaptive Services are not currently supported.

• Service Network Address Translation (NAT) Service NAT is configured in IP > NAT Parameters > Translation Configuration.

In addition to the existing reports, the following Flow Analysis reports can be used to validate configurations and analyze the network containing Juniper SDG and MX devices:

• Configuration.Configuration Summary.Transparent Bridging

• Configuration.IP NAT Translation Summary

• Configuration.Virtual Servers

RN-106 SP Guru Network Planner Release Notes Flow Analysis Enhancements Support for IP Fast Reroute Loop-Free Alternate SP Guru Network Planner now provides support in Flow Analysis for IP fast reroute loop-free alternate in OSPF and IS-IS. When loop-free fast reroute is configured on a router, one loop-free alternate (LFA) backup path is calculated for each prefix and is installed into the routing information base (RIB). In this release, a new design action, “ip_frr_lfa”, lets you specify how you want to detect and visualize LFAs in the scenario.

For more information about the new design action, see IP Fast Reroute with Loop Free Alternate on page RN-55.

Enhancements to IPv6 Support in Flow Analysis In this release, the following support is included for IPv6.

• IPv6 VPN Provider Edge (6VPE) on page RN-107

• Support for BGP Peering in IPv6 on page RN-108

• Enhancement to Route Visualization for IPv6 on page RN-109

• Reporting Enhancements for IPv6 on page RN-110

IPv6 VPN Provider Edge (6VPE) IPv6 VPN Provider Edge over MPLS (6VPE) supports a VPN model for IPv6 networks (VPNv6) that is similar to MPLS VPN support for IPv4. VPNv6 is configured between PEs over an existing IPv4 MPLS network. 6VPE provides logically separate routing table entries for VPN member devices.

Figure 11-5 Address Family Attributes

Note that VPNv6 is now available as an address family for 6VPE’s between PEs.

RN-107 SP Guru Network Planner Release Notes Flow Analysis Enhancements

Note—Both eXpress Data Import and import from VNE Server support 6VPE. For more information, see Support for IPv6 VPN Provider Edge (6VPE) for MPLS on page RN-10.

Note—6VPE uses BGP, OSPFv3, or static routes between PE and CE nodes.

This release also adds support for IPv6 originated from Virtual Routing and Forwarding (VRF) tables, which is configured between PE and CE nodes.

Support for BGP Peering in IPv6 Reachability between PE and CE can be signalled through IPv6 BGP peering. Reachability between PEs can be signalled through VPNv6 BGP peering. A traffic flow is forwarded by IPv6 between CE and PE, and is sent via MPLS between local and remote PEs.

Figure 11-6 BGP Peering using VPNv6

Notice in the IPv6 VRF table for VPN_10 on PE1, the destination 2005:0:0:1:0:0:0:0/64 is learned through IBGP. Its next-hop node is PE2, which has an IPv4 address. VPNv6 handles the peering between the PEs.

IPv6 Support for MPLS Inter-AS VPNs Inter-AS MPLS VPNs are now supported for IPv6. The following options are supported:

•Option A

•Option B

•Option C

For more information about inter-AS VPNs, see MPLS.

RN-108 SP Guru Network Planner Release Notes Flow Analysis Enhancements Enhancement to Route Visualization for IPv6 You can now specify whether you want to visualize IPv4 or IPv6 routes between selected nodes in the network. In the following figure, you can see the visualization of a 6VPE between CE1 and PE2. Note that the VRF is selected as the source context, and IPv6 as the routed protocol. Previously, the source node was determined by what you selected in the project editor, and only IPv4 was supported.

Figure 11-7 Show IPv6 Routes Choose a “Source Context”. Choose a “Destination Interface” or “All” to show all physical and logical destinations.

Choose to visualize either IPv4 or IPv6 routes.

RN-109 SP Guru Network Planner Release Notes Flow Analysis Enhancements Reporting Enhancements for IPv6 Global Report Enhancements The following flow analysis reports now contain an Address Family column for ease of distinguishing IPv6 versus IPv4 configuration.

• Configuration.VRF Tables by Node

• Configuration.BGP Node Config

• Configuration.BGP Peer

Node-Level Reports The following node-level report is available when you right-click on a node and select View Results.

• Performance.IPv6 VRF Table

Note—This report is generated when you selected the Performance.VRF Table report when you run a flow analysis.

RN-110 SP Guru Network Planner Release Notes Flow Analysis Enhancements Support for Additional Service Level Agreement (SLA) Criteria You can now include jitter and packet loss as SLA criteria in a flow analysis, as shown below. Jitter is specified in seconds, while packet loss is specified as a percentage. These values are used when you select “Compute SLAs for IP traffic flows” on the Performance Metrics tab when running a flow analysis.

Figure 11-8 SLA Criteria for Flow Analysis

Previously, only hop count, delay, and link utilization parameters were available for SLAs.

RN-111 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Flow Analysis Enhancements for PL3

The following enhancements are available.

• Auto-Assign IP Addresses Utility Enhancements on page RN-112

• Support for vPC Configurations on Cisco Nexus Devices on page RN-113

• Support for F5 Load Balancers on page RN-113

• Layer-3 VPN-Centric Reports and Visualization on page RN-115

Auto-Assign IP Addresses Utility Enhancements Specifying Starting Subnets for IPv4 and IPv6 Auto-Addressing The auto-addressing feature in SP Guru Network Planner now allows you to specify a starting subnet address for both IPv4/IPv6 addresses. You can configure a starting IPv4 or IPv6 subnet address by clicking the “Start with network address,” as shown in the following figure.

Note—This utility does not create new interfaces (physical or logical) and only assigns IP addresses on those interfaces already present in the network model. Interfaces with addresses set to “Auto Assigned” are given new addresses. Shutdown interfaces and those with “No IP Address” are ignored.

Figure 11-9 Using the Auto-Assign IP Addresses Utility

Text

Choose “Clear IP Addresses” to clear addresses of all interface types

RN-112 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3

Key Concept—The Auto-Assign Utility assigns addresses to physical, loopback and aggregate interfaces and ensures that addresses assigned are not overlapping with existing addresses on any of the physical or logical interfaces.

When you specify a starting network address and a prefix length, the utility attempts to address the subnets starting from that network and increments for each subnet—adjusting the prefix length if needed. For example, if a specified prefix length is 30 and if there are 10 hosts in a given subnet, it would adjust that to use 28.

Loopback interfaces of all devices can be addressed with a separate network address—for example, 200.x.x.x, while using the “All loopback interfaces” option. A prefix length of 32 is honored while assigning addresses to loopback interfaces and interfaces on hosts.

Support for vPC Configurations on Cisco Nexus Devices You can now run flow analysis on network models that include virtual PortChannel (vPC) configurations on Cisco Nexus devices—that is, two Cisco Nexus peer devices that are physically connected and act as a logical endpoint for a port-channel having a single device as an endpoint on the other end.

During a flow analysis, the two devices—or multipoint connections—are seen as a single connection, and route traffic flows as if it were a point-to-point connection to the third device. The new support also honors the HSRP and peer-gateway configurations specific to vPC and the load balancing among member links in a vPC for data forwarding.

After running a flow analysis, you can view the reports for vPC configurations similar to those of the aggregate interfaces.

Support for F5 Load Balancers You can now perform a flow analysis on a network model that includes F5 BigIP load balancers.

Note—Currently, only the following load balancing methods are supported: round robin and Layer-3 forwarding.

RN-113 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Load balancing support in this release includes the following:

• High-availability (HA) groups—HA groups are sets of trunks, pools, or clusters (or any combination of these) that you want the system to use to calculate an overall health score for a unit in a redundant system configuration. A health score is based on the number of members that are currently available for any trunks or pools in the HA group, combined with a weight that you assign to each trunk or pool. The unit that has the best overall score at any given time becomes or remains the active unit.

• F5 floating addresses—Floating addresses are used by F5 load balancers to associate a single, public IP address with one or more interfaces. This is similar to the way in which other redundant, high-availability devices work with HSRP or VRRP.

• F5 virtual servers/virtual addresses—Virtual servers are advertised through the use of a virtual address such that traffic destined for real servers may be load balanced by the F5 load balancers.

• Failover—The failover mode allows for redundant systems to be in either active or standby mode. Failover mode may be specified in the device configuration by the use of Unit ID, HA Group Score, or HA Configuration. SP Guru Network Planner supports the following failover configurations in redundant systems: — Active/Active—Both systems are active and available, forwarding traffic based upon their configuration. For example, in a pair of F5 load balancers, Device_1 might be configured to receive and forward traffic for Server_1, while Device_2 is configured to receive and forward traffic for Server_2. — Active/Standby—One system is active for receiving traffic while the other acts as backup for the active system and only becomes active if the currently active system fails.

New Flow Analysis reports have been added to provide visibility into the operation of redundant systems:

• Performance.High Availability (includes information on load balancing, HSRP, and VRRP)

• Configuration.F5 Virtual Servers

• Configuration.F5 Floating Addresses

For more information, see the following topics:

• Enhanced Support for F5 Big-IP Load Balancers on page RN-15

• Viewing Reports in Modules > Flow Analysis

RN-114 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Layer-3 VPN-Centric Reports and Visualization Various improvements have been made to support analysis of MPLS-based Layer-3 VPN.

• Layer-3 VPN-Centric Flow Analysis Reports on page RN-116

• Layer-3 VPN-Centric Traffic Center Enhancements on page RN-119

• Layer-3 VPN-Centric Link Usage View Enhancements on page RN-120

• Layer-3 VPN-Centric Flow Analysis Reports on page RN-116

• Layer-3 VPN Survivability Analysis on page RN-122

RN-115 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3

Layer-3 VPN-Centric Flow Analysis Reports The following Flow Analysis reports are introduced in this release for the analysis of Layer-3 VPNs:

Note—You must select these reports and run a flow analysis before you can view the Layer-3 traffic in the Traffic Center. See Layer-3 VPN-Centric Traffic Center Enhancements in these release notes for more information.

• Performance > Layer3 VPN Performance per Node

• Performance > Layer3 VPN Status (global)

• Performance > Layer3 VPN Traffic (global)

Layer3 VPN Performance per Node Report The Layer 3 VPN Performance per Node report, shown below, provides you with specific information about each component that establishes the VPN (interface, remote peer, and the tunnel to the remote peer), the traffic routed, traffic delays, and loss ratio for traffic.

Figure 11-10 Layer3 VPN Performance per Node

RN-116 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3

Layer3 VPN Status Report The Layer3 VPN Status report, shown below, is a global report that lists all Layer-3 VPNs in the network along with their status, total traffic volume in the VPN, maximum delays, and maximum packet loss ratio in the VPN. For each one of the PEs participating in a VPN, a drill-down report is available to view the status of each component that establishes the VPN (interface, remote peer, the tunnel to the remote peer), traffic volume, packet delays, and loss ratio for traffic entering the VPN at that PE.

Figure 11-11 Layer3 VPN Status Report

RN-117 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3

Layer3 VPN Traffic The Layer3 VPN Traffic report, shown below, is a global report that lists all Layer-3 VPNs in the network along with all of the traffic that is going into (ingress) or out of (egress) the VPN, as well as traffic that is routed past the VPN (e.g., local switch traffic that is not forwarded to the peer).

Figure 11-12 Layer3 VPN Traffic Report

Demand Routing Report for VPNs The Demand Routing report has also been enhanced to show any Layer-2 or Layer-3 VPN associated with a demand in a new column, shown in the figure below.

Figure 11-13 Demand Routing Report for Layer-3 VPN

RN-118 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Layer-3 VPN-Centric Traffic Center Enhancements You can now view Layer-3 VPN traffic in the Traffic Center. New drop-down menu choices are shown in Figure 11-14

1) Open the Traffic Center by choosing Traffic > Open Traffic Center.

2) Select the desired “Arrange by:” option. Two new options are available in this release: a) PE -> Layer3 VPN b) Layer3 VPN -> PE

3) Select the desired view option. Six new options are available in this release: a) Top N Layer3 VPNs by Volume (Pie) b) Top N Layer3 VPNs by Volume (Bar) c) Top N PEs by Volume where traffic enters Layer3 VPN (Pie) d) Top N PEs by Volume where traffic exits Layer3 VPN (Pie) e) Top N PEs by Volume where traffic enters Layer3 VPN (Bar) f) Top N PEs by Volume where traffic exits Layer3 VPN (Bar)

Figure 11-14 Viewing Layer-3 VPNs in the Traffic Center

Select a Layer-3 option by which to arrange the displayed traffic, and select a Layer-3 view for how you want to see the traffic characterized in a chart.

RN-119 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Layer-3 VPN-Centric Link Usage View Enhancements You can now view Layer-3 VPNs when you visualize the link usage.

1) Right-click on a link and choose View Link Usage.

2) If desired, choose a preconfigured view, as shown below. A chart visualization appears.

Figure 11-15 Visualize Layer-3 VPN Link Usage

1 23New options let you show You can then graphically visualize the contributors Layer-3 VPNs by Volume in to the link, as shown below either a pie or bar chart.

RN-120 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Use the “View Traffic Details...” button to see further information, as shown below.

Figure 11-16 Visualize Layer-3 VPN Link Usage

RN-121 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Layer-3 VPN Survivability Analysis Survivability Analysis has been enhanced to include the analysis of Layer-3 VPNs in the network. The wizard now includes a report selection, “Affected Layer3 VPNs,” as shown below. You can enable or disable options and set thresholds to customize the results.

Figure 11-17 Layer-3 VPN Enhancements to Survivability Analysis Wizard

RN-122 SP Guru Network Planner Release Notes Flow Analysis Enhancements for PL3 Output in the report graphically displays the survivability of Layer-3 VPNs, as shown below.

Figure 11-18 Layer-3 VPN Survivability Analysis—Network Performance Details

Figure 11-19 Layer-3 VPN Survivability Analysis—Element Survivability

RN-123