maintenance:releases:7.0.2_20171010
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
maintenance:releases:7.0.2_20171010 [2019/12/23 15:55] – yspeerte | maintenance:releases:7.0.2_20171010 [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{indexmenu_n> | ||
+ | |||
+ | ===== NetYCE 7.0.2 Build_20171010 ===== | ||
+ | ===== Release notes ===== | ||
+ | Date: 2017-10-10 | ||
+ | |||
+ | |||
+ | \\ | ||
+ | <WRAP widths 60% box safety> | ||
+ | ==== Enhancement ==== | ||
+ | </ | ||
+ | |||
+ | === Job parameter handling === | ||
+ | <WRAP indent> | ||
+ | Added transparent handling of the job variables set in the [parameter] and [scenario] sections of | ||
+ | each command-job. The [parameter] variables are defined at job-submission while the scenario variables | ||
+ | are assigned at run-time resulting in confusing results and scenario command syntaxes. | ||
+ | By extending parameter substitution to a two-pass operation, the parameter handling has been made | ||
+ | mostly transparent. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === OS Upgrade Frontend === | ||
+ | <WRAP indent> | ||
+ | Some Vendors do not support OS Upgrades yet, yet the frontend made it seem like they did. | ||
+ | The frontend now shows it clearly when a Node's vendor type isn't supported yet. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Port Missing Template Message === | ||
+ | <WRAP indent> | ||
+ | In the switchportconfig form, whenever a port lacks a template, a popup now appears to warn the user. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === GNS3/IOU telnet support === | ||
+ | <WRAP indent> | ||
+ | The simulated Cisco devices under GNS3 generated login prompts with additional characters | ||
+ | preventing login using Telnet. Adding a special case to detect these unclean prompts and evoking | ||
+ | a new prompt resolved this issue. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Cramer Deltas === | ||
+ | <WRAP indent> | ||
+ | Part 1 of cramer deltas, comparing cramer output to netyce data. | ||
+ | A check for deleted nodes in Cramer has also been added. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Tweak ' | ||
+ | <WRAP indent> | ||
+ | The front-end and the Service-types do not allow a device port to have multiple topology connections | ||
+ | sice they are point-to-point by nature. | ||
+ | However, for migration purposes a feature to selectively allow multiple links per port is desirable. | ||
+ | For this purpose the Lookup tweak ' | ||
+ | behaviour per Client-type. The default denies it for all Client-types conform existing policies. | ||
+ | A tweak record with this name can be added for each Client-type, | ||
+ | the Num value. | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | \\ | ||
+ | <WRAP widths 60% box safety> | ||
+ | ==== Change ==== | ||
+ | </ | ||
+ | |||
+ | === Tasker logging === | ||
+ | <WRAP indent> | ||
+ | The tasker logs for an assignment always consisted out of two or three lines. This is now condensed into one line. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === User groups client level dropdown === | ||
+ | <WRAP indent> | ||
+ | Moved the client level dropdown in the user groups form to a better place. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Template remark field === | ||
+ | <WRAP indent> | ||
+ | Changed Scenario, Stored Job, Template and Template Revision Description size from 50 to 200 characters. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Scenario conversion === | ||
+ | <WRAP indent> | ||
+ | Version 7.0 uses different command names and options in its scenarios. Existing scenarios are | ||
+ | converted automatically although the old name and options are still supported. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Service Class Sort === | ||
+ | <WRAP indent> | ||
+ | Service classes in site types are now sorted by Hid | ||
+ | </ | ||
+ | |||
+ | === Task-logs form === | ||
+ | <WRAP indent> | ||
+ | The Task-id' | ||
+ | so that newer jobs appeared hundreds of pages lower than expected. The form also did not have an | ||
+ | option to filter or search by Task_id. | ||
+ | The sort order has been revised to deal with these large Task-ids and a search facility has been added. | ||
+ | The Timestamp column has been widened to show the full date and time. | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | \\ | ||
+ | <WRAP widths 60% box safety> | ||
+ | ==== Fix ==== | ||
+ | </ | ||
+ | |||
+ | === Net::IP Warning === | ||
+ | <WRAP indent> | ||
+ | Fixes the issue where any file that includes Common gave a list of warnings from the Net::IP module. | ||
+ | Overloaded the library Net::IP file with our own modified version. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Service-type Custom subnet attribute === | ||
+ | <WRAP indent> | ||
+ | Assigning a custom subnets network address and/or network prefix failed when using | ||
+ | the service-type: | ||
+ | The net_address value supplied can now also include the prefix (address/ | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Site relation update === | ||
+ | <WRAP indent> | ||
+ | The ' | ||
+ | This has been corrected by updating the ' | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Vendor Module fix === | ||
+ | <WRAP indent> | ||
+ | Fixed a patch with a typo in its sql statement, failing to create state actions for Avaya VSP | ||
+ | Added v7 functions to the Huawei module | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Ports not displayed === | ||
+ | <WRAP indent> | ||
+ | Ports with an invalid port-template were not displayed. This is now fixed along with a popup | ||
+ | to inform the user which ports must have their port-templates revised | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Service Class Permissions === | ||
+ | <WRAP indent> | ||
+ | Fixed bug where you cannot create, edit and delete service classes. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === HP_C5 OS Upgrades === | ||
+ | <WRAP indent> | ||
+ | Added OS Upgrade Support for HP_C5. Warning: still experimental so may experience bugs. Please contact NetYCE when encountering one. | ||
+ | Fixed squeeze issue in Cisco IOS | ||
+ | |||
+ | </ | ||
+ | |||
+ | === API IPv4 or dual stack support === | ||
+ | <WRAP indent> | ||
+ | The ' | ||
+ | available, the API failed to start. The ipv4-only or dual-stack support is now configured dynamically. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === HP_C7 OS Upgrades === | ||
+ | <WRAP indent> | ||
+ | Added OS Upgrade Support for HP_C7. Warning: still experimental so may experience bugs. Please contact NetYCE when encountering one. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Cisco_Nexus OS Upgrades === | ||
+ | <WRAP indent> | ||
+ | Added OS Upgrade Support for Cisco_Nexus. Warning: still experimental so may experience bugs. Please contact NetYCE when encountering one. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Cisco_XR OS Upgrades === | ||
+ | <WRAP indent> | ||
+ | Added OS Upgrade Support for Cisco_XR. Warning: still experimental so may experience bugs. Please contact NetYCE when encountering one. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Huawei OS Upgrades === | ||
+ | <WRAP indent> | ||
+ | Added OS Upgrade Support for Huawei. Warning: still experimental so may experience bugs. Please contact NetYCE when encountering one. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Domain Create Network === | ||
+ | <WRAP indent> | ||
+ | Fixed the issue where clicking on the create button of the domain networks form redirects you to a totally different form. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Forever ' | ||
+ | <WRAP indent> | ||
+ | Jobs hat were stopped or failed to finish properly were reported the be ' | ||
+ | Now, every five minutes the running jobs are examined and if dead are changed to the ' | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Command parsing template bug === | ||
+ | <WRAP indent> | ||
+ | Fixes an issue where command parsing templates are not selected properly | ||
+ | |||
+ | </ | ||
+ | |||
+ | === IPv4 Plan Delete bug === | ||
+ | <WRAP indent> | ||
+ | IPv4 Plans can now be deleted again. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Multiple command-jobs === | ||
+ | <WRAP indent> | ||
+ | Command-jobs issued for various nodes at the same time were using the same nodename for < | ||
+ | This issue was introduced after making the variable substitution in jobs more intuitive and transparent. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Client Type Variable Client Level === | ||
+ | <WRAP indent> | ||
+ | Support was built in for adding client types with variable client levels to user groups, in the | ||
+ | user groups form previously. Now the same support is implemented in the client types form. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Cisco-IOS ssh support === | ||
+ | <WRAP indent> | ||
+ | A bug was introduced forcing Telnet as the communication protocol on all the Cisco-IOS devices. | ||
+ | This was corrected so that ssh is the preferred and telnet the backup protocol. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Tasker Fix === | ||
+ | <WRAP indent> | ||
+ | A bug was encountered when processing the data from config parsing due to treating an array | ||
+ | reference as a hash reference. This is now fixed. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === NCCM logging failure messages === | ||
+ | <WRAP indent> | ||
+ | The NCCM logging will show " | ||
+ | each job will log into their own jobID-based log-files, but for NCCM the level of logging is reduced | ||
+ | and centralized. The error message was caused by trying to create a detailed log to an unavailable | ||
+ | job path. Setting the proper conditional resolved this issue. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === NCCM logging === | ||
+ | <WRAP indent> | ||
+ | The NCCM log file (yce_nccmd.log) was found to be growing very quickly in a busy environment. | ||
+ | By making much of the detailed logging dependent on the general NetYCE debugging flag | ||
+ | (~/ | ||
+ | result statuses. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Regions bug === | ||
+ | <WRAP indent> | ||
+ | Fixed a bug that prevented editing region names. | ||
+ | </ | ||
+ | |||
+ | === Subnet plan bug === | ||
+ | <WRAP indent> | ||
+ | Fixes the bug that prevented you from editing IP subnet plans | ||
+ | </ | ||
+ | |||
+ | === Command parse fix === | ||
+ | <WRAP indent> | ||
+ | Fixed a command parsing bug where complex command results weren' | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Slow NCCM Config-diffs form === | ||
+ | <WRAP indent> | ||
+ | The default filter of the ' | ||
+ | waiting for a report that probably would need a filter, only the top 200 nodes in the NCCM | ||
+ | repository were shown. | ||
+ | However, in larger environments, | ||
+ | for some optimizations so that the initial report will require minimal time. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === HP_C7 trying to run dir command in privileged mode === | ||
+ | <WRAP indent> | ||
+ | HP_C7 doesnt allow the ' | ||
+ | this cannot happen anymore, ensuring usable output from the ' | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Nccm debug logging === | ||
+ | <WRAP indent> | ||
+ | The yce_nccm_debug.log file was receiving very large amounts of log data regardless of | ||
+ | the debug or development flags. This behaviour is now keyed to the yce_development flag | ||
+ | file. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Relaunching disabled or ' | ||
+ | <WRAP indent> | ||
+ | The yce_setup.pl completed by relaunching the various daemons. It did so regardless of disabled | ||
+ | status or the ignore-flag being set. The ' | ||
+ | consideration when relaunching a daemon or binging ' | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Infoblox ipam/dns report === | ||
+ | <WRAP indent> | ||
+ | The Infobox reports for DNS and IPAM now have support to define the network-view. | ||
+ | And, to allow legacy requests without the network_view attribute, a default | ||
+ | could be specified. The issue was however, that an obsolete variable was used as the | ||
+ | default resulting in an empty report. An error message clarifying the missing view was absent. | ||
+ | The correct defaults are used nowi and error messages issued. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Region relation failed === | ||
+ | <WRAP indent> | ||
+ | The ' | ||
+ | custom attributes, but incomplete. The resulting values did often belong to a different region. | ||
+ | The relation query was updated to fix this issue. | ||
+ | |||
+ | </ | ||
+ | |||
+ | === Node rename check === | ||
+ | <WRAP indent> | ||
+ | When renaming a node with the Tweak ' | ||
+ | the new hostname was not in use. The rename would so result in database objects to become unrelated. | ||
+ | |||
+ | Renaming a node to an existing name will now result in a popup indicating the name clash. | ||
+ | |||
+ | </ | ||
+ | |||