mate release 5 - cisco

17
Release Notes © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential Proprietary Information 1 MATE Release 5.6 Previous Release Support Release Supported Until MATE 5.3 03/05/2015 MATE 5.2 08/30/2014 MATE 5.1 04/23/2014 MATE 5.0 and previous EOL Note that JunosE is no longer supported. How to Upgrade Plan Files Plan files from previous versions are read and upgraded automatically on opening in release 5.6. MATE Live To upgrade the datastore from a previous release, contact your support representative. MATE Collector You can use the snapshot from a previous release without having to upgrade. However, if the configuration you have can be handled by the new MATE Collector server, using the server is the preferred option because it is easier to maintain. For information on configuring the MATE Collector server, see the MATE Collector Guide. For information on augmenting the server collection or on configuring only snapshots (manual collection), see the Advanced MATE Collector Configuration Guide. If using an upgraded snapshot process, run archive_init -upgrade on individual archive repositories before adding them to the server. This ensures that the internal archive database schema is current, but does not upgrade the underlying plan files. The archive_insert tool does not automatically run a simulation before inserting a plan file. To check in a plan file containing a simulation, run mate_sim on the plan file before running archive_insert. Add-Ons and Scripts Add-ons and scripts may be affected by the schema changes and CLI tool changes that are described in their respective sections.

Upload: others

Post on 23-Jan-2022

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: MATE Release 5 - Cisco

Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 1

MATE Release 5.6

Previous Release Support

Release Supported Until

MATE 5.3 03/05/2015

MATE 5.2 08/30/2014

MATE 5.1 04/23/2014

MATE 5.0 and previous EOL

Note that JunosE is no longer supported.

How to Upgrade

Plan Files

Plan files from previous versions are read and upgraded automatically on opening in release 5.6.

MATE Live

To upgrade the datastore from a previous release, contact your support representative.

MATE Collector

You can use the snapshot from a previous release without having to upgrade. However, if the

configuration you have can be handled by the new MATE Collector server, using the server is the

preferred option because it is easier to maintain. For information on configuring the MATE Collector

server, see the MATE Collector Guide. For information on augmenting the server collection or on

configuring only snapshots (manual collection), see the Advanced MATE Collector Configuration Guide.

If using an upgraded snapshot process, run archive_init -upgrade on individual archive repositories

before adding them to the server. This ensures that the internal archive database schema is current, but

does not upgrade the underlying plan files. The archive_insert tool does not automatically run a

simulation before inserting a plan file. To check in a plan file containing a simulation, run mate_sim on

the plan file before running archive_insert.

Add-Ons and Scripts

Add-ons and scripts may be affected by the schema changes and CLI tool changes that are described in

their respective sections.

Page 2: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 2

Enhancements

MATE Design

Simulation enhancements—For more information, see the MATE Design User Guide.

o L1 circuits have a Reroutable property that simulates rerouting of the circuit ("optical restoration") in

the event of a failure when there is no available backup L1 circuit.

Reporting enhancements—For more information, see the MATE Design User Guide.

o More refined reporting on demand groupings to include QoS bound, QoS violation, capacity bound,

and capacity violation. These QoS values have the same meaning as in past releases.

Capacity Bound—The maximum amount that the sum of the demands in the demand grouping can

be without causing over 100% utilization on any interface in the network. The calculation is based

on the assumption that all demand traffic increases proportionally.

Capacity Violation—Total traffic minus the capacity permitted for the demand grouping (Capacity

Bound). A violation occurs if the Capacity Bound is exceeded.

o Bulk reporting of LSP simulations and LSP path simulations is now available. (Previously you could

report on one LSP or LSP path at a time.)

Visualization enhancements—For more information, see the MATE GUI Visualization Guide.

o The process of defining node-to-site mappings is automated through the MATE GUI Assign Sites to

Nodes tool, and is stored within the plan file. It is recommended that this method be used to define

node-to-site mappings in the template copying process instead of the -site-mapping-table

option in copy_from_template.

o You can hide and show nodes in the same manner as sites. Both the Nodes and Sites tables have a

Shown column to make is easy to find nodes and sites that are hidden.

Add-on enhancements—For more information, see the MATE Integration and Development Guide.

o Improved user customizations include the ability to add tabs and to group sections of a dialog box

with an outline.

Usability enhancements

o User-defined tables and columns are viewable from the MATE GUI tables. You can show, hide, and

save their visibility settings just like MATE tables.

o The context menus that filter to shortest paths for circuits and for LSPs now give the option to filter

to shortest IGP paths, shortest latency paths, and/or shortest TE paths. The results appear in the

Shortest Paths table. Exporting routes gives you similar options for exporting shortest IGP, latency,

or TE paths.

o Places in the MATE GUI that previously said "shortest path," now say "shortest IGP path" where

relevant. For example, the View->Demands menu specifies "IGP" to make the route type clearer.

Page 3: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 3

MATE System

MATE now offers a common landing page across all web applications, a System UI, and a MATE

Collector Server UI.

The System UI provides access to license administration, user management, and LDAP server setup.

Additionally, it enables you to configure the SMTP server used for emailing MATE Live reports. For

more information, refer to the MATE System Administration Guide.

For information on the new MATE Collector UI and the updates to MATE Live, refer to their

respective sections.

A new mate_tech_support tool creates a tar file of both MATE Collector server and MATE Live

diagnostics. This can help you troubleshoot issues, or you can email the file to Cisco support when you

need assistance.

MATE Collector

MATE Collector continues to support snapshots, which are referred to as manual snapshots. Additionally,

you can collect network information using the new MATE Collector server or through augmented

snapshots. The Overview chapter in both MATE Collector guides provides guidance on how to choose

the collection method best suited for your needs.

MATE Collector server—The MATE Collector server, which is configurable through the new MATE

Collector UI, produces a plan file that can be retrieved directly by MATE Live or further processed

using the augmented method. This collection method enables you to set up OSPF or IS-IS collection by

defining a set of nodes that can be accessed through a seed router. Both SNMPv2c and login access are

available, as is the ability to use regular expressions to further refine the list of nodes to be included or

excluded. Once this base set of nodes is determined, you can further expand or refine this list of nodes

using per-node rules that override the global ones. Within this workflow, you always have the ability to

test the rules to see what your collected nodes would be prior to committing them to the collection

process. The UI also enables you to define what to collect from these nodes, such as interfaces, LSPs,

and BGP connectivity, and schedule a one-time or ongoing collection. Error and warning messages are

viewable, and a diagnostic feature enables you to download the information about the state of the

server for the last collection. For more information, see the MATE Collector Guide.

Augmented snapshots—The augmented collection method is primarily for preparing the plan file for

use in MATE Design and MATE Design Archive. This method retrieves a plan file from the MATE

Collector server, optionally enhances the plan file with additional collection, and enhances the plan file

with modeling information, such as demands. If parsing configurations for explicit LSP paths or

collecting Multicast, VPN, LDP, or flow traffic, use the augmented method of collection. For more

information, see the Advanced MATE Collector Configuration Guide.

SAM integration with snapshots—A new MATE Collector snapshot feature is now available for

integrating the existing sam_getplan tool into the snapshot files. Part of the discovery is performed in

an Alcatel-Lucent network through the 5620 SAM server. The result of this discovery is fed into the

snapshot process that collects network data using other MATE CLI tools. The resulting plan file can be

inserted into an archive for use with the applications. This integration enables you to more easily use

MATE Collector in environments containing both Alcatel and non-Alcatel networks. This is only

supported using manual snapshots. For information on how to configure this integration, see the

Advanced MATE Collector Configuration Guide, SAM Integration chapter.

Manual snapshots—The workflow of <DISCOVERY_TASKS> within the snapshot.txt file was

changed to move GET_CONFIGS and PARSE_CONFIGS before SNMP_FIND_NODES and

Page 4: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 4

SNMP_FIND_INTERFACES. Note that both previous and current snapshot.txt workflows are valid,

depending on your discovery needs. Refer to the snapshot.txt file in $CARIDEN_HOME/etc.

Troubleshooting—sam_getplan now queries for the SAM server version and stores this information

in the Comments column of the <NetIntHistory> table.

MATE Live

Configuration enhancements—The ml.conf configuration file was replaced with the ability to

configure the following through the web UI. For information, see the MATE Live Administration

Guide.

o Map health panels, including the Peering panel and the Events panel. (Note that the Events panel is

only partially configurable through the web UI.)

o Collection of plan files from the MATE Collector server, an external archive (produced through

augmented or manual snapshots), or none at all. In prior releases, plan files were pushed into the

datastore and archive. In 5.6, MATE Live gets the plan files, rather than having them pushed to it.

MATE Live then internally determines where to place the collected data.

Template Management—MATE Live applies a local template that contains visual elements to the

plan files that it receives. As in past releases, use the MATE GUI to visualize the file and re-insert it

into MATE Live. Until such visualization occurs, plan files are rendered in their unprocessed state.

Schema Changes

Please consult the $CARIDEN_HOME/docs/table_schema.html file for a complete reference.

New Tables

Product New Table Description

MATE Design <NodeSiteMappingRules> This table is created using the MATE GUI (Assign Sites feature). It defines the rules used to place nodes into sites.

Order (key) - Defines the order in which the rules are applied.

Node Matches (plan) - Regex matching node names.

Site Expression (plan) - Regex to identify site names. May use references in "Node Matches" column.

MATE Collector <NetIntPlanFileGenerationTime> Stores the modified time and creation time of plan files.

Page 5: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 5

New Columns

Product Table New Column Description

MATE Design <Circuits> LastTemplateUpdate Last time the template file was updated with the circuit.

<L1Circuits> RerouteOnFailure F (false, default) - If an L1 link fails, the circuits corresponding to the L1 circuits through that link are down due to failure.

T (true) - The L1 circuit will attempt to reroute on the next best path. If it fails to reroute, behavior is as in the F setting.

<Nodes> LastTemplateUpdate Last time the template file was updated with the node.

Shown Identifies whether the node is hidden or shown in the current layout.

<Sites> Shown Identifies whether the site is hidden or shown in the current layout.

CLI Changes

Note: For MATE Design and MATE Collector, the differences are between release 5.5 and 5.6. For

MATE Live, however, the differences are between release 5.4 and 5.6.

For more information on any CLI tool, execute it with the -help option.

Removed and Deprecated CLI Tools

Deprecated tools will be removed in the next release.

Product Tool Deprecated or Removed?

MATE Design db_dep_graph Deprecated

db_merge Deprecated

mate_service Removed

mate_update Removed

plan_summary Deprecated

MATE Live ml_compare Removed

ml_edit Removed

ml_insert_many_plans Removed

ml_update Removed

ml_version Removed

Page 6: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 6

New CLI Tools

Product New Tool Description

MATE Live ml_insert_ctl View, modify, and schedule the collection of data from MATE Collector.

MATE Collector collector_getplan Get the latest plan file from the MATE Collector server. This is a required tool when using augmented snapshots and is only applicable to augmented collection.

MATE System mate_cfg Manage the web configuration of MATE Live and MATE Collector (for MATE Live, this replaces the ml.conf file).

mate_tech_support Create a tar file of support information for the MATE Live application and for the MATE Collector server.

New CLI Options

MATE Design

CLI Tool New Option Description

copy_from_template -out-template-file Update the template file. New nodes and circuits in the plan file are added to the template. Nodes and circuits that have not been in the plan file longer than the value

set by -remove-after are removed.

-remove-after The amount of time, in days, that nodes and circuits are kept in the template if their "Last Template Update" time in the template file is greater than this value.

insert_demand_group

ing_mesh

-dest-external-

endpoint-table

File containing <ExternalEndpoints> table of destination

external endpoints. Used if -dest-selection is

externalendpoint. Default is all.

-source-external-

endpoint-table

File containing <ExternalEndpoints> table of source external endpoints. Used if

-source-selection is externalendpoint.

Default is all.

lsp_diagnostics -lsppaths-table File containing the <LSPPaths> table. Required option

if -report-type uses lsppaths value.

-lsps-table File containing the <LSPs> table. Required option if -

report-type uses lsps value.

-out-file Name of the output plan file containing LSP diagnostics reports.

-report-type Comma-separated list of LSPs and LSP paths. Values

are lsps and lsppaths. Default is none.

Page 7: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 7

MATE Live

CLI Tool New Option Description

ml_insert_plan -conn ODBC database connection string for connecting to another database (on the same or different device).

mld -backup Directory where automatic backups are sent. Default is

$CARIDEN_ROOT/data/mldata/backup.

-mld MATE Live server installation directory. Default is

$CARIDEN_ROOT/software/mld/current.

-mldata Directory where all application data is stored. Default is

$CARIDEN_ROOT/data/mldata.

Removed CLI Options

Unless otherwise noted, all options were removed, rather than deprecated. Deprecated options will be

removed in the next release.

Product CLI Tool Removed Option

MATE Design copy_from_template -include-extras (deprecated)

-site-assign-by-neighbor

-site-assign-delimiters

-site-assign-external-as

-site-assign-format

lsp_diagnostics -lsp-name

-lsp-path-option

-lsp-source

MATE Live ml_backup -dest

-dry-run

-logfile

-no-global-options

-options-file

-simple-txt-out-file

-suppress-progress

-verbosity

-version

ml_insert_plan -columns-file

-exclude-columns

-include-columns

ml_read -csv

-datastore

-logfile

-no-global-options

-options-file

-series-ids

-simple-txt-out-file

Page 8: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 8

Product CLI Tool Removed Option

-suppress-progress

-version

ml_restore -logfile

-no-global-options

-options-file

-simple-txt-out-file

-source

-suppress-progress

-version

mld -logfile

-no-global-options

-options-file

-simple-txt-out-file

-suppress-progress

New Values for CLI Options

MATE Design

CLI Tool Option New Value Description

export_routes -object shortestIGPpath

Creates <ShortestIGPPathHops> table

shortestTEpaths Creates <ShortestTEPathHops> table

shortestLatencypaths

Creates <ShortestLatencyPathHops> table

insert-demand-

grouping-mesh

-dest-selection externalendpoint

Group by demand destination external endpoint

-source-selection externalendpoint

Group by demand source external endpoint

MATE Live

CLI Tool Option New Value Description

mld -action start Start the mld server.

status Show the mld server status.

restart Restart the mld server.

upgrade Upgrade an existing datastore.

install Create a new datastore installation, and thus, a new datastore.

uninstall Deletes all datastore data and datastore installation files.

Page 9: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 9

Changed CLI Behavior

MATE Design

CLI Tool Option Value Changed Behavior

copy_from_template -method visual Copies visual layout information, but no longer does site assignments for nodes

-method missing

Checks for visual layout information, including site assignments for nodes

-site-mapping-table

Previously read the <SiteMapping> to determine node-to-site mapping. Now this option looks for this mapping in the following sequence.

<NodeSiteMappingRule> table internal to the plan file. Note the recommended method is to create this table in the plan file using the Arrange Sites feature.

User-provided file containing a <SiteMapping> table.

export_routes -hop-type

Type of hop in route representation.

lsp: LSP hops

lsp_interface: LSP and interface

hops

interface: interface hops

l1link: L1 link hops

-object-table

For shortestIGPpaths, shortestTEpaths, shortestlatencypaths, this is a <Nodes> table. Previously, shortestpaths was a <Nodes> table.

-routes-from-nodes

No user-specified change. However, now shortestIGPpaths, shortestTEpaths, and shortestlatencypaths are used to select route exported based on <Nodes> table.

Open Source

This product includes the following.

Software developed by MetaStuff ( http://www.dom4j.org)

Cryptographic software written by Eric Young ([email protected])

Software developed by the OpenSSL project for use in the OpenSSL Toolkit (http://www.openssl.org/)

Software written by Tim Hudson ([email protected])

Software developed by the University of California, Berkeley and its contributors

Page 10: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 10

Issues Fixed

Issues Fixed Since 5.5.2

MATE Design

Key Summary

CSCum54323 In multiple CLI tools, the help output for the -simple-txt-out-file option has typos

CSCum60554 Some LSPs not following the correct path in the LSP Capacity Planning Mode

CSCum68506 Running Tactical Explicit LSP Optimization with Enforce Latency Bounds option causes MATE Design to stop working

CSCum88903 Running Explicit LSP Optimization on inactive circuits causes MATE Design to stop working

CSCum97850 Running Simulation Analysis on SRLGs does not populate the Failure Impact column

CSCun11521 LSPs and demands configured for a specific IGP topology are not staying on the defined topology

CSCun24431 mate_sql -select-out-file-append overwrites the -select-out-file output file

MATE Design Archive

Key Summary

CSCum68474 SQL queries in default_timeplot_summary.txt returning unexpected result

MATE Live

Key Summary

CSCuj91990 Java error upon executing ml_read -help

CSCul51389 Error occurs with regular expression ^(?!.*lo)

CSCul51532 Running a traffic report causes a NullPointer exception error due to race condition

CSCul54286 Report page shows null value for start time

CSCul63992 Unable to filter Job Status field on "running"

CSCul85303 Health reports show more nodes than are in the datastore

CSCul90559 Java error upon executing ml_read -help

CSCul91170 Report aborts when using both Group By Overall and user-defined properties

CSCum06398 Graphing reports generated using Group By causes a time-out

CSCum41380 Map inaccurately rendering circuits

CSCum96415 Reports abort if based on Explore selections using “Select All”

CSCun10984 Ad Hoc LSPs report aborts when using cumulative sum and user-defined property measurements

CSCun11067 Ad Hoc LSPs report using user-defined properties generates errors

CSCun11732 Unable to filter using isNull or isNotNull on numeric fields

CSCun13275 "Show Only Selected" prevents filtering to an interface from an LSP

CSCze17738 Traffic report graph shows unwarranted spike in the trend line

CSCze19045 Help output is not clear for multiple CLI tools

Page 11: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 11

MATE Collector

Key Summary

CSCuj16787 Link metric value in plan file generated by sam_getplan deviates from the SAM server

CSCuj66254 Incorrect options listed in -help for multiple CLI tools

CSCuj86074 When poll_ldp is parsing configs, MATE stops running

CSCuj94808 parse_configs does not get Area ID of nodes

CSCul83640 snmp_find_vpn is not populating the <NetIntInterfaces> table VPNNode column with nodes

CSCul98457 snmp_find_bgp -min-IPv6-prefix-length and -min-prefix-length should have

a maximum value of 128 and 32, respectively

CSCul98491 snmp_find_bgp -min-IPv6-prefix-length fails to print in logs for dropped IPv6

subnets

CSCum09553 parse_configs does not detect Huawei routers

CSCum18520 snmp_find_ldp -help has inaccurate usage statement

CSCum21916 login_find_igp_db -igp-protocol isisv6 populates <Interfaces> table with two

instances of each interface when both IPv4 and IPv6 are configured on the routers

CSCum62548 sam_getplan -help lists -include-vpn-measurements twice

CSCum67881 Running parse_configs with SRLGs is not creating the mapping to circuits

CSCun00672 mate_access_test reports the timeout value in microseconds instead of seconds

CSCun02739 Running parse_configs with RSVP causes a java error

CSCun06105 parse_configs -lic-product design fails when there is a license for MATE Design,

but not MATE Collector

CSCun18264 snmp_find_interfaces sets circuits to Inactive on Alcatel networks

CSCun19430 SNMP discovery of Alcatel returns problematic interface names (inconsistent with other vendors)

CSCun24137 Sequence of PARSE_CONFIGS and SNMP_FIND_INTERFACES in snapshot.txt file is in

reverse order

CSCun31174 snmp_find_interfaces on an IPv6-only network aborts collection due to missing

IPv4Address column

CSCze17968 LAG Capacity Sim value is double the Capacity value

CSCze18782 sam_getplan -num-logged-measwin should create a Default traffic level

MATE System

Key Summary

CSCuj80097 License not available although it contains the feature

CSCum03275 embedded_web_server -action stop fails to display its completion

CSCum21060 embedded_web_server not responding due to insufficient heap memory

CSCum11124 MATE GUI tools not working when using floating license

CSCum36854 license_check aborts when using remote license server

CSCum37807 Dedicated license failed due to missing keyword

CSCum51323 Unable to install a Windows license

Page 12: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 12

Issues Fixed Since 5.5.1

MATE Design

Key Summary

CSCul29948 Plotting demands that have an “na” Path Metric renders an empty plot

CSCul62859 MATE Design stops when creating a demand to an external endpoint without a node

CSCul63064 Closing a plan file does not prompt user to save the file if only plot options have changed

CSCul70063 dmd_deduct -zero-bw-tolerance not working properly

CSCul78697 Incorrect "script missing" error when Add-On does not start

CSCul81549 Demands on P2MP LSPs are missing the LSP border

CSCul81650 Demo mode is not available without a license

MATE Design Archive

Key Summary

CSCul41043 The ADMIN link does not work.

MATE Live

Key Summary

CSCze16965 Unable to filter Explore data when using "Show Only Selected"

CSCze18069 Unable to select individual objects from Explore when using "Interface Type" option

CSCul18237 "Unable to create connection" error occurs when reporting on a large data set

CSCul47567 ml_insert_plan fails with stack overflow

CSCul48163 Running health reports gives "lock timeout" error when running with ml_insert_plan

CSCul55764 Errors occur when filtering on user-defined properties with an underscore ( _ ) in the name

CSCul57090 embedded_web_server -action stop does not stop the server

CSCul59493 Datastore connection failures result in lost data

CSCul61807 Unable to connect to the datastore after inserting plan files and generating reports

CSCul63927 Traffic reports abort with NullPointerException error

CSCul81410 Generating reports over several days causes an "out of memory" error

CSCul90491 Ad Hoc interface reports not working properly with user-defined properties

MATE Collector

Key Summary

CSCuj22393 parse_configs removes "re1-" from hostnames

CSCul41454 IGP Metric is not populated in the <NetIntInterfaces> table

CSCul56955 Errors occur when running snmp_poll -poll-function without the interface argument

Page 13: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 13

Issues Fixed Since 5.5

MATE Design

Key Summary

CSCuj04356 Filtering to external endpoints causes MATE Design to stop working

CSCul11059 Demand Deduction is removing some of the non-zero bandwidth multicast demands

CSCuj12269 exp_opt for optimizing LSPs stalls

CSCul17841 Period Increment field does not work when creating growth plans using demand groupings

CSCze18714 Renaming an interface does not work

CSCze18762 insert_demand_grouping_mesh does not have the ability to use external endpoints

CSCuj23000 Circuit Upgrade add-on produces a QT error in Windows 8

CSCuj39997 changeover tool, Max Utilization is not accurate

CSCuj40040 arrange_nodes only affects the default layout

CSCuj42178 import_layer1 does not import L1 circuit hops properly

CSCul44296 Missing ECMP shortest path when using VLAN pseudonode parallel path

CSCuj51013 insert_multicast_demands stops running

CSCuj60600 Resetting curves for Weathermap layouts does not work within sites

CSCuj80984 Curved circuits not maintaining curved shape when switching layouts

CSCui94763 AS properties do not show Name

CSCuj95478 Custom ASNs do not show up in the properties table

CSCui96615 MATE Design stops when running Simulation Analysis with worst-case latency

CSCuj97709 export_routes -out-file option does not accept STDOUT for output

CSCui98199 MATE Design stops when running Simulation Analysis with demands

MATE Design Archive

Key Summary

CSCze18363 Advancing plan files using next button when UTC offset is set does not work properly

CSCuj31859 When client is running newer version than server, the application freezes without giving errors

MATE Live

Key Summary

CSCul13652 Not all user-defined properties are filterable and sortable in Explore

CSCul16200 Cannot filter an exact pattern match for "Util Out" from Interface page

CSCze16964 Destination Node and Remote Node should have the same name

CSCze16966 Cancelling a running report marks the report as "Aborted"

CSCze17581 Plot Options settings are activated late

CSCze18078 mate_update does not properly show usage details

CSCze18093 Choosing Explore objects forgets the traffic report settings

CSCze18121 ml_props_import produces java.net.SocketException error

CSCze18144 Sorting utilization numbers are off by 100x

CSCze18495 Explore should allow "Go to... remote interface" from the Interfaces page

CSCze18559 Empty query results returned for user-defined property

Page 14: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 14

Key Summary

CSCze18751 Show Only Selected option when exploring demands gives an SQLite error

CSCze18759 MATE Live peer configuration default file should not show commented list within quotes

CSCze18811 Explore feature does not show individual hops

CSCze18963 Error occurs when changing the pixel value for circuit minimum width (in Plot Options)

CSCul22654 Selecting any or all Interface Types shows no interfaces

CSCuj24972 Map shows up briefly

CSCul39366 Sorting of AS Values (interfaces) not working

CSCuj60502 Explore Interfaces page is not functional and gives “unrecognized token: 1AND" error

CSCui92028 Unexpected warning message when adding user-defined properties

CSCui94375 Data not populated when applying filters to user-defined properties

CSCui94789 Map peering panel does not show interface graphs

MATE Collector

Key Summary

CSCuj12877 flow_manage does not accept IPv6 addresses

CSCuj13336 Juniper RSVP LSPs have a discrepancy between measured interface traffic statistics and the measured traffic statistics on LSPs over those interfaces

CSCul14274 parse_configs results in parsing error

CSCuj15385 flow_manage server-ip 0.0.0.0. causes a BGP error

CSCuj17701 snmp_find_interfaces is discovering different subnet masks for the same circuits

CSCze18744 Incorrect IPv6 topology in <Interfaces> table

CSCze18767 Error in parsing configuration files

CSCze18809 mate_auth_init -auth-file Help output clarification needed

CSCze18915 snmp_poll should populate MAC traffic statistics in the <InterfaceTraffic> table

CSCze19039 <NetIntInterfaces> table name properties are incorrect when the interface name contains a ":" (colon)

CSCuj28496 parse_configs error when loading Huawei routers files

CSCuj33798 Juniper RSVP LSP statistics do not update

CSCul41364 flow_get fails when importing out_matrix file

CSCuj77756 parse_igp and login_find_igp_db create invalid plan files

CSCuj91494 get_show does not properly handle the -command-table option

CSCuj91956 LAG interfaces between Juniper and Alcatel-Lucent nodes are created with incorrectly associated port members

MATE System

Key Summary

CSCze18804 Able to access traffic reports without a license

Page 15: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 15

Known Limitations

User Management

Both the System UI and the MATE Design Archive UI have user management capabilities. If both are

used to configure users, MATE uses the most recently updated information. The recommendation and the

workaround are to use only the System UI to manage users.

MATE Live

Datastore Installation

The MATE Live datastore installation fails if the server's username does not follow POSIX standards.

The workaround is to create a username that follows POSIX standards on the server device. This

username must be lowercase, alphanumeric, and the first letter must be an alphabetical character. Then re-

install the MATE package while logged in as that user on the server device. After re-installing the

package, you can install the mld server. For installation information, see the MATE Server Installation

Guide.

Interface Types

L2 interfaces are categorized incorrectly as "individual physical interfaces" on the Explore Interfaces

page.

The "Unknown" interface type is not used.

MATE Collector

MATE Collector Server

OSPF databases cannot be collected via SNMP.

If the network you are collecting from connects to a peering fabric that has prefixes larger than /24, you

cannot use the server to discover BGP.

The workaround for both of the above issues is to use a manual snapshot to collect the data.

SAM Interface

The sam_getplan tool does not populate the interface packet performance (drops, errors) and node

utilization (processor, memory) data in MATE tables that are used by MATE Live reports.

Since sam_getplan does not take a plan file as input, it must be the first specified task in the snapshot

workflow when collecting SAM information in a multi-vendor network.

Snapshot Configurations

Login tools support either Telnet or SSH network-wide, but not both concurrently on different nodes.

Flow Collection

Flow collection and integration tools assume BGP next-hop-self is configured on border routers

exporting flows to properly identify the egress interface.

<InterASFlows> and <Demands> tables are not fully populated when this feature is not configured

network-wide.

IPv6 Network Topology

MATE Collector does not populate IPv6 interface addresses or discover parallel interfaces after parsing

the IOS XR IS-IS link-state database. This information is only available when IS-IS IPv6 Traffic

Engineering extensions are supported by the platform and are enabled. Subsequent

Page 16: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 16

snmp_find_interfaces in the collection process collects this information and populates the

<Interfaces> table.

License Check Failures on Newer Linux Distributions

Some newer Linux distributions have started using a new way (via biosdevname) of naming hardware

devices, including the network interfaces. This causes some software that depends on the traditional

naming (for example, eth0, eth1) to fail on license checks, including MATE.

The workaround is to append biosdevname=0 to the kernel line of the grub configuration file and

reboot. (Syntax varies among distributions.)

After reboot, you should be able use ifconfig to verify that the NIC are named eth0 (or eth1, ...)

instead of the biosdevname names (such as p34p1).

Windows Memory

The Windows version of MATE is a 32-bit application, which means that it cannot use more than 4 GB of

memory even if that is available in the system. The implication is that tasks requiring large amounts of

memory, such as simulation and optimization of large networks, might fail on Windows even if they

succeed on other platforms.

Certain tools (such as sam_getplan and parse_configs, for example) may require more memory to

start than what is available. The symptom will be an error message similar to the following.

Error occurred during initialization of VM

Could not reserve enough space for object heap

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

The workaround is to set the maximum memory to a low enough value in the

CARIDEN_JAVA_OPTIONS variable before calling the tool. An example setting is as follows.

set CARIDEN_JAVA_OPTIONS=-Xmx1000m

/etc/hosts Requirements in Unix Systems

Various Web services require the server's hostname to be present in the /etc/hosts file. This is

standard configuration practice, but some systems do not have it. Both the unqualified and fully-qualified

hostnames must be present. Make sure that the following line is present in /etc/hosts.

<server IP address> <hostname> <fully-qualified hostname>

Example: 192.168.0.15 mate-server mate-server.my.company.com

Cariden Technologies is now part of Cisco Systems, Inc.

For further details, please visit www.cisco.com/go/quantum.

July 2014, Version: 3

Page 17: MATE Release 5 - Cisco

MATE 5.6 Release Notes

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential – Proprietary Information 17