vBRANCH Release 1.0.0 Release Notes
Introduction
The vBranch Core Function Pack (FP) is a compilation of packages to maximize reusability. This FP is organized in
layers for better flexibility: This FP supports on boarding of physical and virtual infrastructure. It allows services
to be built on top of the function pack using the strongly types service models. The function pack itself supports
pushing of the day1 configurations on the VNFs using the generic key-value based mechanism. It follows the ETSI-MANO
specification compliant VNF descriptors to deploy VMFs.
Cisco End User License Agreement
This software is governed by the Cisco End User License Agreement available at the following URL:
http://www.cisco.com/c/en/us/td/docs/general/warranty/English/EU1KEN_.html
System Requirements
+----------------+--------------+--------------+-----------------+
| OS
| Ubuntu
| Red Hat
| CentOS
|
+----------------+--------------+--------------+-----------------+
| Minimum Server | CPU-8 Cores | CPU-8 Cores | CPU-8 Cores
|
| RAM-32GB | RAM-32GB | RAM-32GB
|
|
| Disk- 300GB | Disk- 300GB | Disk- 300GB |
+----------------+--------------+--------------+-----------------+
| Scale Server | CPU-32 Cores | CPU-32 Cores | CPU-32 Cores
|
| RAM-256GB | RAM-256GB | RAM-256GB
|
|
| Disk- 1TB | Disk- 1TB | Disk- 1TB
|
+----------------+--------------+--------------+-----------------+
| Version
| 14.04
| 7.3 (Maipo) | 7.3.1611 (Core) |
|
| 16.10
|
|
|
+----------------+--------------+--------------+-----------------+
|
|
Installation Guidelines
For detailed information about installing this release of vBranch Core Function Pack, see the
vBRANCH Core Function Pack Installation Guide Version 1.0.0 document.
Supported NSO Version: 4.4
Supported Packages:
--------------------------------------------------NAME
VERSION
--------------------------------------------------branchInfra
1.0.0
branchInfra-nfvo
1.0.0
cisco-pnp
1.2.1
core-fp-common
1.0.0
day1-templates
1.0.0
nfvis
1.0.0
pnp-manager
1.0.0
release
1.0.0
tailf-etsi-rel2-nfvo
1.1.1
tailf-etsi-rel2-nfvo-nfvis
1.0.0
tailf-etsi-rel2-nfvo-nfvis-staged-delete 1.0.0
---------------------------------------------------
vBRANCH 1.0.0 VNFs and Release Versions Used during Testing
+-----------------------------------------------------------------------+
| VNF
| File Name
|
+------------+----------------------------------------------------------+
| NFVIS
| Cisco_NFVIS-3.5.1-FC4.iso
+------------+----------------------------------------------------------+
|
| ISRv
| isrv-universalk9.16.03.01.tar.gz
|
+------------+----------------------------------------------------------+
| ASAv
| asav951-201.tar.gz
|
+------------+----------------------------------------------------------+
| WAASv
| Cisco-KVM-vWAAS-200-6.2.0-b88npe-nfvis.tar.gz
|
+------------+----------------------------------------------------------+
| Ubuntu | ubuntu-14.04.3-server-amd64-disk1.tar.gz
|
+------------+----------------------------------------------------------+
| Win2K
| win2k.tar.gz
|
+------------+----------------------------------------------------------+
| CentOS | CentOS-7-x86_64-Everything-1511.tar.gz
|
+------------+----------------------------------------------------------+
| FTD
| Please contact ENFV sales/marketing teams for assistance |
+------------+----------------------------------------------------------+
Features Supported:
* Catalog of Profile Design
* Plug and Play
* Group attribute automation
* Virtual branch service chaining
* Physical branch provisioning
* Deployment and Diagnostics status
* Allows changes to multiple devices in multiple branches at the same time
* Allows spin-up of supported VNFs given ETSI MANO compliant VNF descriptors.
* Integration with external systems using Network CLI, NetConf, REST, NetConf Notifications
* Seamless integration with IWAN Core Function Pack 1.1.0
* External PnP Server [experimental]
* HA Support
Known Issues & Workaround
+------------+----------------------------------------------------------------------------------------------+
| CSCvd31369 | Create, delete and then create branch service with certificate install does not connect
|
+------------+----------------------------------------------------------------------------------------------+
Workaround: delete the branch service. Set "Transport" to HTTP, "PNP Server Port" to a different port and
then stop and start pnp from NVIS GUI to clear out certificate. You can try certificate install again.
+------------+----------------------------------------------------------------------------------------------+
| CSCvd92235 | vnfd cannot be deleted if vnfd creation fails due to TIMEOUT
|
+------------+----------------------------------------------------------------------------------------------+
Workaround: If vnfd cannot be deleted, please use "request branch-infra service-cleanup branch-cpe xxx" to
delete failed vnfd. This CLI will clean up whole service including CPE, vnfd's, vnf's, and networks.
+------------+----------------------------------------------------------------------------------------------+
| CSCvd92476 | CPE names starting with numeric value cannot be onboarded
+------------+----------------------------------------------------------------------------------------------+
Workaround: No workaround. Please use CPE name that starts with alphabet.
+------------+----------------------------------------------------------------------------------------------+
| CSCvd98528 | ISRv deletion fails if day 1 variable values are not set
+------------+----------------------------------------------------------------------------------------------+
Workaround: Please ensure that day 1 variables have proper values set.
|
|
+------------+----------------------------------------------------------------------------------------------+
| CSCvd98616 | Discovery-device fails when username on ISRv is not admin, but plan shows Ready
|
+------------+----------------------------------------------------------------------------------------------+
Workaround: Either login to ISRv using username admin, or if your ISRv username is not admin, manually onboard
ISRv using CLI, "admin@ncs% request branch-infra:branch-infra branch-cpe xxx discover-service deployment-type
ISR deployment-name 1489775570 no-onboarding".
+------------+----------------------------------------------------------------------------------------------+
| CSCve08870 | Confusing error message when CPE is deleted: *** ALARM connection-failure:
+------------+----------------------------------------------------------------------------------------------+
Workaround: even though delete is successful, error message, "*** ALARM connection-failure: Failed to
|
connect to device ENCSS_sjc: closed" shows up. If you check the plan status again, then you will see that
the delete was successful by issueing CLI, "show branch-infra:branch-infra-status branch-cpe xxx plan component
state | tab"
+------------+----------------------------------------------------------------------------------------------+
| CSCvd31369 | First failed VDU entities show up in northbound branch-infra plan
|
+------------+----------------------------------------------------------------------------------------------+
Workaround: No workaround. If there are multiple failures, only the first failure shows up in nitification.
+------------+----------------------------------------------------------------------------------------------+
| CSCve10991 | ${NICID_0_GATEWAY}needs to be changed to ${USER_NIC_ID1_GW} on Day0 file in ASA
+------------+----------------------------------------------------------------------------------------------+
Workaround: Instead of using NICIF_x_GATEWAY, please use USER_NIC_IDx_GW instead.
+------------+----------------------------------------------------------------------------------------------+
| CSCve07123 | Error message "Exception in callback: Could not instantiate service - could not update plan" |
|
| when differnet CPE name is used for a same serial number.
+------------+----------------------------------------------------------------------------------------------+
Workaround: Either use same CPE name for identical serial number, or use CLI "request branch-infra
service-cleanup branchcpe <branch-cpe-name>" to clear the error and redeploy CPE.
+-----------------------------------------------------------------------------------------------------------+
| With external PnP [Experimental Feature] setup, services sometimes fail to redeploy
+-----------------------------------------------------------------------------------------------------------+
Workround: Please contact Cisco service for instruction.
|
|
© Copyright 2026 Paperzz