-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
SDNC Dublin Spr 3 3/11 - 3/29
As a SDN system, I want to trigger the global/initial/base configuration.
Scope: Global configuration, Interface configuration routing configuration for Cisco and Juniper routers
Backend impacts: will be triggered based on the inputs via SO, scripts.
Example from Cisco, Juniper templates
For PNF systems
For PNF systems – go to individual vendor N/W elements
SDN-C will interface with legacy systems
PNFs support D1. When the routers are created use SDN-C for the respective formats of the vendors N/W elements
Network elements accept – CLIs, scripts, SNMP commands, SSH, CLI interface, SNMP interface
Create scripts
Universal settings ---- PE routers, CE routers.
All the routers where customer interface, before going to MPLS backbone.
SDNC will interface Physical network elements
The different modes of collecting configuration is via CLI interface, script interface, For YANG and Netconf we can use API interface. Configuration is standard across all product types for a particular vendor. The scripts are developed to configure the YANG model into respective ( router, etc) configuration. Once the configuration scripts are run, the underlying interface is built per VNF. The SDN-C is invoked from the North bound interface and is provided with the YANG model/ and or directed graph template. The common data model mapping shall be used to provide the configuration irrespective of which network element type is used. The standard protocol conversion formats will be used.
Acceptance Criteria: As an SDN user, I should be able to configure the basic config. On vendors PNF.