On Cisco Learning Labs you can find a couple of self-paced trainings consisting of videos and hands on exercises. Cisco also offers several training courses on NSO. Please use this link to see what training courses that are offered. ... View more

In the NFV architecture NSO, with the NSO NFVO component, fulfills the NFV orchestrator (NFVO) role, and also partially replaces the EMS/OSS layer. The Tail-f NSO architecture enables it to act as the central orchestrator and has the ability to control both SDN Controllers and NFV Managers. Tail-f NSO interfaces to SDN Controllers and NFV Managers via Network Equipment Drivers (NEDs). Similar to packages, NEDs are decoupled from the Tail-f NSO product and have its own release cycle enabling agile feature growth. ... View more

NSO requires a standard Unix box Medium (< 1000 devices): 4 Core CPU and 32 GB RAM Large (> 1000 devices): 8 Core CPU and 64 BG RAM Linux/x86 – Linux/x86 64 MacOS 10.6/x86 64 ... View more

NSO can be configured to run in HA mode: one master and several slaves. All slaves are updated at every transactional border. The slaves can be used for reading data. The slaves are hot-standby and a fail-over to a slave can be made at any time. In the clustered solution described above, each cluster node is typically a HA configuration. ... View more

NSO is designed from the ground up to provide carrier-grade scalability and reliability. As part of release testing, Tail-f performs automated scalability testing of NSO managing 10,000 network devices on a "single" server. On top of this NSO can be configured to run in a Layered Services Architecture (LSA) or in clusters where the network is partitioned across several NSO servers. Tail-f’s core engineering team has their roots at a Tier 1 telecom device vendor. The experience which they gained working on managing scalable carrier grade network devices has gone into the design and implementation of NSO. NSO is designed so that processor power and available memory are the only limitations on how large NSO can scale. Internally, NSO is massively multi-threaded and designed to allow for concurrent processing and operator sessions. Execution threads are dynamic and come and go as processing needs dictate. NSO also provides support for multi-core processors. The user can configure NSO for how many cores of a multi-core processor it may execute on at once. ... View more

NSO contains a rich AAA engine that spans all interfaces. NSO supports role-based access control lists providing different access privileges to different users. These privileges may apply to a group of devices, or to individual devices, or to a any subset of any device configuration. External authentication can be used via Pluggable Application Module (PAM). ... View more

Developer logs, audit trail logs, web interface logs, device communication logs, XPath logs. ... View more

NSO supports generating BSD and RFC 5424 syslog messages. ... View more