Motorola 6806800C08B User Manual

The following table provides more details. 

For further details about the System Description refer to the System Description Programmer’s 
Reference. 

NCS provides two ways to access the Avantellis system for managent purposes: via CLI 
interface and via SNMP.  

Both management access points resolve to a common managed object definition. This 
common definition allows the system managed objects to be distributed throughout the NCS 
services. These objects may be owned (implemented) by NCS, PCS and user applications as 
long as they have been properly integrated with the NCS Management Access Service (MASv). 
All NCS configuration parameters are managed by this service.

The flow is roughly as follows:

1.

A MASv client, such as a CLI or SNMP Agent, translates a transaction request to a MASv 
format

2.

The MASv client then initiates a transaction via the Management Access Agent (MAA) API 
library, which always forwards the transaction to the Management Access Server (MAS), 
where a repository of object locations is maintained.

Validation Description

This describes all possible ATCA-blade population profiles 
for a particular product. The description explains the 
inventory and legal combinations of hardware resources, 
primarily those hosting one or more SAF AMF nodes. 
Hardware resources are identified by HPI Entity Path names 
with key 'identifier' attributes called out. 

NCS Deployment description

This identifies the actual ATCA-blade configuration and NCS 
Middleware deployed for this device in the network. For 
example, it identifies the actual blade type expected in a slot 
from among the 'valid blades' expressed in the Validation 
Description. This Description also identifies which NCS 
middleware pieces live where (which blade) and the 
redundancy models used by those NCS middleware pieces 
(since the NCS Middleware is itself HA). 

This portion of the description will likely require some 
adjusting at deployment time. This depends on how many 
plausible (and used) configurations there are for a particular 
product,

Customer deployment description

This identifies how customer application SW is distributed 
(deployed) for this device in the network. Just as with the 
NCS Middleware, this description identifies which application 
sub-parts live where (which AMF node) and the redundancy 
models used by those application sub-parts (as it is generally 
expected that customer applications shall be HA).