Netman 4000 OMC-A
XML NBI Interface
UT斯达康大学客户技术培训中心
UT斯达康内部资料 1
Netman4000 NBI - Purpose
Provide programmatic interface to Netman4000
– Support industry standard protocols
– Stable Interfaces
– Impact-proof from internal design changes
– OSS need not have EMS design knowledge to perform business
operations
– Supports Configuration and Alarms
UT斯达康内部资料 2
Netman4000 NBI - Benefits
• Centralized authentication
• Supports multiple clients simultaneously
• Scalability to support big network requirement
• Stable interfaces
• Similar interfaces for multiple devices
• Logical business requirement based interfaces
UT斯达康内部资料 3
Netman4000 NBI - Framework
Third-party
NMS/OSS
Provisioning/Monitoring Alarm/Event Notification Interface
Interface
NM4000
North Bound Interface (NBI)
Device
Manager
iPlatform
Network Elements
(NE’s)
UT斯达康内部资料 4
Netman4000 NBI - Client Server
Model
• NBI client can be running on a
NBI client
NBI client PC/Unix sever
• NBI Server is part of the Netman
XML over
4000 system and runs on the Netman
XML over TCP/IP BE server.
TCP/IP • NBI client opens a socket with the
NBI server on preconfigured port, thus
establishes a session with it and is
NBI Server ready to issue commands.
• NBI server process the XML
command, does basic validation,
translate into relevant UNCP/SNMP
UNCP/SNMP
command and issue it to the relevant
UNCP/SNMP node.
• The response is processed and
MSAN
B1000 passed on in the reverse direction.
MSAN
B1000 • thus completing the request/response
interaction between the NBI client and
MSAN
B1000 server.
UT斯达康内部资料 5
Netman4000 NBI - Client Server
Interaction
• Steps to use NBI
– NBI client establishes a session with the NBI server. Open a
socket with the server on the preconfigured port
– Prepares an XML command using the interfaces available and
writes the command on the socket.
– Waits for the response for the command.
– Receives an XML response as per the interface definition and
processes the XML response using standard XML parser
– Based upon command success/failure does further action
UT斯达康内部资料 6
Netman4000 NBI - Comparison with CLI :
Similarities
• Both are request/response interactions. Operator issue a command/wait for
the response/based upon command success-failure issues further
command.
• Both are amenable to scripting and hence automation. Just like scripts can
be written for the CLI commands, the same can be done with the XML
commands.
• Both support User Authentication - CLI authenticates the user at node while
NBI authenticates at NMS server.
• Supports logging of commands.
UT斯达康内部资料 7
Netman4000 NBI - Comparison with CLI :
Potential Benefits
• Centralized login at Netman server No need to individually login to each
node (like CLI).
• Can connect to multiple nodes in single session.
• Supports multiple sessions simultaneously
• Standard XML based interface.
• Logically grouped, business requirement oriented command set
• Supports Alarm operations
UT斯达康内部资料 8
Netman4000 NBI - Configuration
Parameters
• The default NBI configuration parameters
– Default NBI Server Port: 8100
– Default maximal NBI client connections: 50
– Default NBI client idle timeout value: 6000,000
• The NBI configuration parameters file
– The NBI configuration parameters saved in Netman4000 OMC-A BE
server configuration file, it is under the directory of
“ WebNMS/NBIConfigParams.conf ”
– When change the NBI parameter default value, you should restart the
Netman4000 OMC-A BE server to take effect the new parameters.
• Where to check the NBI logs?
– WebNMS/logs/nbi
Note:
Although the parameters could be changed, but it is highly
recommended to consult with the vendor before making
the changes.
UT斯达康内部资料 9
Netman4000 NBI - NBI Client Demo
• Run the Demo program
c:> java -jar OssSim.jar
• Input the BE server’s IP address, click ‘connect’ button
• Input/copy the XML NBI command, then click ‘send’ button.
UT斯达康内部资料 10
Netman4000 NBI - Tiscali’s Requirement
Mapping
1. CONNECTION STATUS (PORT PARAMETERS)
– <get_request_adsl_port_info>
– <get_request_adsl_linestatus_info>
– <get_request_adsl_channelstatus_info>
2. PACKETS INFORMATION
– Not supported
3. VLAN INFORMATION
– Use <get_request_adsl_vlan_info>
UT斯达康内部资料 11
Netman4000 NBI - Tiscali’s Requirement
Mapping (…contd)
4. BOARD INFORMATION
– <get_request_adsl_board_info>
5. GLOBAL PORT INFORMATION (RELATED TO A SPECIFIC BOARD)
– <get_request_adsl_port_info>
6. ICM VERSION
– <get_request_icm_board_info>
UT斯达康内部资料 12
Netman4000 NBI - Tiscali’s Requirement
Mapping (DSL Provisioning)
1. LOCK/UNLOCK of a single port
– <set_request_adsl_lockunlock_port>
2. RESET of a single port
– <set_request_reset_node_card> will reset the board. There is no support for
individual port reset.
3. PRINT of all the profiles
– <get_request_ipadsl_profile_template>
– <get_request_service_profile>
– <get_request_spectrum_profile>
UT斯达康内部资料 13
Netman4000 NBI - Tiscali’s Requirement
Mapping (DSL Provisioning contd.)
4. PRINT of all the VLAN and untagged ports
– <get_request_adsl_vlan_info>
5. DELETE/ADD of PVC
– <set_request_ipadsl_atm_vc>
6. CHANGE PROFILE
– <set_request_adsl_assign_line_profile>
7. SAVE
– <set_request_flash_save_erase>
UT斯达康内部资料 14
Netman4000 NBI - Tiscali’s Requirement
Mapping (Alarms)
1. Collection of Alarms
– Register using < RegistrationDescriptor>.
– Notification received as < attributeDescriptors>
2. Aggregation/Statistics of the alarms (type, severity, NE, date, etc)
– Use <get_request_alarm_retireve_info>
3. CORRELATION of the alarms
– Out of NBI scope
4. Trap Forwarding of the alarms
– NE support two trap destinations. These can be configured by using:
<set_request_ip_addr_setup>
– Or we can also use the interface defined in #1 above to fetch XML formatted
alarms.
5. Acknowledge/Clear of the alarms
– Use <set_request_alarm_clear> to clear
UT斯达康内部资料 15
• Questions?
UT斯达康内部资料 16
UT斯达康大学客户技术培训中心
UT斯达康内部资料 17
Thank You
This presentation is provided by UTStarcom for planning purposes only. Changes in market conditions and/or other changes in circumstances,
can affect the assumptions upon which this presentation was based or otherwise impact the contents of this presentation and therefore such
contents cannot be guaranteed and are subject to change at any time without notice. Nothing contained in this presentation shall be deemed to
create, modify or supplement any commitments or warranty made by the company, whether expressed, implied or statutory, in connection with
the products, technology and/or services referenced herein.
*Some features may require addition development and may not be ready for immediate implementation.
UT斯达康内部资料 18
