Sie sind auf Seite 1von 6

Versa Networks

Release Notes
Product Name Versa FlexVNF 20.1.0
Release Date September 27, 2018
Document revision 1.2
Last Updated October 8, 2018
2

Index of Release Notes

Release notes provide information about a specific release of Versa FlexVNF software. This
document provides feature descriptions, enhancements, and fixes contained in a specific
release. Known issues and limitations are listed separately.

Table of Contents
Index of Release Notes ................................................................................................................................... 2

Table of Contents ........................................................................................................................................... 2

1. Versa FlexVNF 20.1 General Reference .................................................................................................. 3

2. Versa FlexVNF 20.1.0 New Features ....................................................................................................... 5

3. Versa FlexVNF 20.1.0 Enhancements ..................................................................................................... 5

4. Versa FlexVNF 20.1.0 Fixes ..................................................................................................................... 5

5. Limitations and Behavior Changes. ........................................................................................................ 5

6. Known issues .......................................................................................................................................... 6

Copyright Versa Networks, Inc. All rights reserved


3

1. Versa FlexVNF 20.1 General Reference


This section applies to all Versa FlexVNF 16.1 releases.
Product Documentation
The Product documentation for Versa FlexVNF can be accessed at this location:
https://docs.versa-networks.com
Software Upgrade Information
Please refer to the Appliance Installation Guide for installing the Versa FlexVNF
software. Versa FlexVNF can be installed on a standard Intel server or as a Virtual
Machine (VM) based on ESXi or KVM.
The FlexVNF software comes in two flavors – one with the *–wsm.bin suffix which
would be the image one would install on the physical CPE branch devices using the
Atom based processors (Versa 1xx, 5xx). The other package without the –wsm suffix,
would be used for installation on all virtual machine and high-end CPEs (Versa 8xx and
Versa 1000) and bare metal servers with Xeon or better class of CPU.

Instructions on upgrading Versa FlexVNF instances to 20.1 version


Upgrade of VNF instances is supported from previous version of 16.1R1 and above.
Upgrade from any version prior to 16.1R1 is not supported. In such cases we
recommend upgrading to the latest 16.1R2 Service release and then upgrading to 20.1.0
version of the software.
Note: If requirement is to load complete image include OS fixes and package upgrades
please use qcow2, iso or ova packages instead of .bin package.
Instructions on upgrading FlexVNF instances from earlier version using CLI:
1. Ensure the current running package is present under /home/versa/packages/
2. Save the existing version of the configuration via CLI config mode command. For
example:
admin@vnf-cli(config)% save /var/tmp/backup.cfg

3. Copy the appropriate package .bin package file to the FlexVNF node
/home/versa/packages/ directory and make sure the file has +x execute
permission. Alternatively you can use the below command to transfer the file
which will get copied to the above directory automatically.
admin@vnf-cli> request system package fetch uri <URI>

4. Install the new software package from the CLI shell. For example:

Copyright Versa Networks, Inc. All rights reserved


4

admin@vnf-cli> request system package upgrade <.bin>

Follow the prompts and wait till the upgrade status is displayed on the shell.
5. After the upgrade, issue the following command to confirm that the new
software was loaded.
admin@vnf-cli> show system package-info

Instructions on downgrading Versa FlexVNF instances to earlier version


If you have to downgrade to the installed image immediately prior to the upgrade then
the recommended way is to issue the CLI command:
admin@vnf-cli> request system rollback to PRE-UPGRADE-1

If you wish to install an older image that does not have the Spectre/Meltdown fix then
please follow the steps outlined below.
1. Save the current config of the FlexVNF instance to a file.
admin@vnf-cli(config)% save CPE.cfg

2. Issue the package downgrade command. This command will delete the current config
admin@vnf-cli> request system package downgrade <versa-flexvnf…bin>

3. After the services are restarted, reload the saved config from the file CPE.cfg
admin@vnf-cli(config)% load override CPE.cfg

If you forget to follow the above instructions and indeed land into a state where the
FlexVNF package is incompatible with the current version of the kernel, then please
reinstall the last known good FlexVNF image that worked with the current version of the
kernel and follow the rollback method described above to move to an earlier version of
the software.

Installing Software License for Versa-OS


Versa FlexVNF does not require a license if it is managed by Versa Director. The software
will continue to operate after the initial trial period of 45 days if it is not subjugated to a
functioning Versa Director. However, the number of data path sessions will be limited to
30 sessions until it is actively managed by a licensed Versa Director.
Support
For all support queries, please visit http://support.versa-networks.com. Please register
and create an account if you are visiting the support site for the first time. Alternatively,

Copyright Versa Networks, Inc. All rights reserved


5

you may send us an email to support@versa-networks.com or contact your Versa


Networks’ Sales Account team.

2. Versa FlexVNF 20.1.0 New Features


• Please refer to Versa-New-Features-20.1 document available along with the
software link.

3. Versa FlexVNF 20.1.0 Enhancements


• Please refer to Versa-New-Features-20.1 document available along with the
software link.

4. Versa FlexVNF 20.1.0 Fixes


The table below lists all the critical and major defects that were fixed in this release of
the software. These are issues that were present in the 16.1R2.S5 release.
Bug ID Summary
34319 Fixed an issue where authentication page is not redirected when application filter is applied in
authentication policy.

34408 Fixed an issue where VRRP backup router loses tunnel connectivity to controller when VRRP is
configured in Physical MAC address mode on WAN interface.

5. Limitations and Behavior Changes.


1. Multicast Forwarding performance testing is in progress.
2. 802.1x Device ID logging feature will log only IP and MAC addresses. Rest of the
device details like Vendor, Model, OS etc. will be supported in future releases.
3. SaaS Path Selection features are not all fully operational and in early test quality.
4. Under Class of Services, app-qos-policies, 'deny' action is not supported. One
must configure access-policy rules under Security to achieve any 'deny' action.
5. The number of source addresses, the destination addresses, the source address
ranges, and the destination address ranges that can be specified in a CGNAT
match rule is limited to 16 ranges, and 16 addresses of each type. If you have a
need to specify more than these values, then you must create a new rule and
specify the additional addresses in the new rule.
6. The destination port range that can be configured in CGNAT pool has been be
constrained to be within 1..65535.
7. The FlexVNF CLI show command “show orgs org <org-name> sd-wan site” has
been deprecated. All prior commands and output are now re-organized under
the same hierarchy.

Copyright Versa Networks, Inc. All rights reserved


6

8. Remote users who login to FlexVNF will now be presented with the FlexVNF CLI
as login shell (prompt) and not rbash.
9. In 16.1R1, TACACS+ on FlexVNF was supported on port 2024 and not on the
standard port 22. With 20.1.0, FlexVNF now supports TACACS+ on native SSH
port 22. TACACS+ has to be deployed using workflow (i.e. delete old config and
then redeploy using workflows). With workflows, FlexVNF can send TACACS+
Auth requests to server reachable on either LAN, WAN (or) SDWAN.

6. Known issues
1. Intel Quick Assist (QAT) feature is not currently supported on platforms with
Intel CPU C2758, namely Versa 120 and Versa 520 models.
2. SNMP traps are not reaching the trap receiver.
3. If a CPE is using a USB based LTE Modem, then the mobile carrier information is
not shown in either the CLI or monitor screen. There is no fix for this since it is
not possible to fetch the information from a USB based LTE modem.
4. Full firewall pinholes are not created when tuple of responses are different from
the request in the SIP protocol. This issue is seen with a specific version of Cisco
VOIP gateway. Bug # 30126
5. SNMP in the FlexVNF will only function on the standard SNMP port – UDP 161. A
future release will support configuring a user-defined port.
6. The following parameters of an existing routing-instance cannot be changed:
• instance-type
• mpls-vpn-core-instance
• global-vrf-id
The work around is to first delete the existing routing-instance, commit the
configuration and reconfigure the routing instance with the new attributes (Bug
10367)
7. When configuring the appliance name under System->Identification, please
make sure that the hostname contains a combination of only alpha-numeric
characters and the ‘-‘character in accordance with RFC 1123.
8. If graceful restart is configured on a BGP speaker with dynamic peers, there will
be a traffic drop from the time it restarts until all of the dynamic peers connect
back to the BGP speaker. The traffic will not be affected as long the BGP speaker
is down for a period less than its configured recovery time.

Copyright Versa Networks, Inc. All rights reserved