Dyna SNMP

C32390.
20--B0
Dyna SNMP
User Manual, v.2
DN70553464
Issue 2-0
Nokia Siemens Networks
1 (126)
Dyna SNMP
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for
the use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The documentation has been prepared to be used by professional and properly
trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given as is and all
liability arising in connection with such hardware or software products shall be defined
conclusively and finally in a separate agreement between Nokia Siemens Networks and the
customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that
the instructions contained in the document are adequate and free of material errors and
omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,
explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2009. All rights reserved.
2 (126)
DN70553464
Issue 2-0
Contents
Contents
1
1.1
1.2
1.3
Introduction ............................................................................................5
General ....................................................................................................5
Mechanical construction...........................................................................5
Identification .............................................................................................7
2
2.1
2.2
2.3
2.4
Installation ..............................................................................................8
Management addresses...........................................................................9
Step-by-step installation .........................................................................10
Default settings ......................................................................................25
LEDs and rack alarms ............................................................................27
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
Command line interface.......................................................................28

List of commands ...................................................................................29
Commands related to CLI session .........................................................29
Commands related to Dyna SNMP settings...........................................29
Commands related to IP settings ...........................................................30
Commands related to SNMP settings ....................................................30
Commands related to element management .........................................31
Command descriptions...........................................................................31
Commands related to CLI session .........................................................31
Commands related to Dyna SNMP settings...........................................36
Commands related to IP settings ...........................................................42
Commands related to SNMP settings ....................................................50
Commands related to element management .........................................54
SNMP .....................................................................................................62
Nokia Siemens Networks Q1 Management pipe ...............................63

Appendix A: Cabling in a Dynanet environment ...............................64
Appendix B: Download and tips .........................................................79
Appendix C: Dyna SNMP applications ...............................................82
Appendix D: Q1 interface signal names.............................................93
Appendix E: MIB...................................................................................95
Glossary ..............................................................................................125
DN70553464
Issue 2-0
3 (126)
Dyna SNMP
4 (126)
DN70553464
Issue 2-0
Introduction
Introduction
Dyna SNMP is a plug-in unit that can be used for collecting Q1 alarms
and other messages from Nokia-Siemens Networks Q1-managed nodes
PDH/PRE equipment, while mediating between these, and a supervising
management system as HP open view. The unit does not support the
other Q1 managed equipment, like Hopper, Flexi radios. It is not
compatible with E/ND generation equipment.
1.1
General
The purpose of this document is to give the information needed for
installation, operation, and maintenance of the Dyna SNMP.
Caution
The equipment is sensitive to static electricity. When handling units
removed from their anti-static packaging, you should wear wrist
grounding or take other corresponding precautions.
Caution
Do not leave or lay unpacked units on conducting materials, for
example, on metallic shelves or folios. Storing unpacked units on
metallic surfaces may discharge the unit battery.
1.2
Mechanical construction
DN70553464
Issue 2-0
Dyna SNMP plug-in unit (see the following figure)
5 (126)
Dyna SNMP
The plug-in unit can be installed, for example, in a DYNANET subrack.

In the subrack, Dyna SNMP occupies one plug-in unit space (5T). For
information about the cabling, refer to Appendix A.
The mechanical construction of the plug-in unit is shown in the figure
below.
Figure 1.
6 (126)
Mechanical construction of the Dyna SNMP unit (plug-in unit)
DN70553464
Issue 2-0
Introduction
1.3
Identification
The equipment is identified with stickers. The identification sticker
contains the product code, product version, and serial number. The
identification stickers are shown in Figure 2. The location of the stickers
is shown in Figure 1.
Figure 2.
DN70553464
Issue 2-0
Identification stickers of Dyna SNMP unit (example)
7 (126)
Dyna SNMP
Installation
The Dyna SNMP can be installed as follows:
The plug-in unit can be installed, for example, in a DYNANET

subrack. In the subrack the Dyna SNMP occupies one plug-in unit
space (5T).
Figure 3 shows the cables needed in the installation of the Dyna SNMP
Adapter plug-in unit. For more information on cables see Appendix A.
Before installing, make sure that you have the right equipment and
cables.
Note
The cables needed depend on the configuration of your system. Not all
cables are needed in every installation.
For the Local Management Interface (LMI), use the LMI cable only at the
initial installation stages. See also Appendix A.
8 (126)
DN70553464
Issue 2-0
Installation
Figure 4.
Cables needed with the Dyna SNMP Adapter plug-in unit
If you are managing multiple subracks with one Dyna SNMP, you will
also have to build or order a Q1 cable to connect the DI interfaces of the
Dyna SNMP to Q1 equipment.
The Dyna SNMP contains parameters that must be set in the
commissioning of the unit. These settings include IP, SNMP, and Q1
settings. A basic step-by-step installation procedure is described in
section Step-by-step installation.
2.1
Management addresses
The Dyna SNMP uses Q1 management bus and Q1 physical addresses
for accessing the network elements.
The physical Q1 addresses of the network elements are the same as the
addresses that the Dyna SNMP uses to handle the element. In addition
to the backplane Q1 interface, there are three Q1 extension interfaces
(DI), which can be used to extend the Dyna SNMP management bus to
other units. The physical Q1 addresses of the network elements are
configured manually.
DN70553464
Issue 2-0
9 (126)
Dyna SNMP
2.2
Step-by-step installation
Installing process
1.
Identify the unit
Make sure that you have the correct unit by checking the identification
sticker on the unit (see section Mechanical construction). Check also
that there are two flash memory units present (see Figure 5.), and that
there is a program in the Bank A flash (check the sticker on the chip).
10 (126)
DN70553464
Issue 2-0
Installation
Figure 5.
2.
DN70553464
Issue 2-0
Flash locations
Check the jumper settings
11 (126)
Dyna SNMP
Note
In the subrack, there are jumper settings that extend the Q1 bus in the
backplane. Make sure that these jumpers are properly set. See the
subrack manual for details.
On the unit, there are five jumper settings that are used for cable
terminating of the V.11 DI and SI interfaces. By default, these jumpers
are not connected. The jumper location and setting options are
presented in Figure 6.
12 (126)
DN70553464
Issue 2-0
Installation
Figure 6.
3.
DN70553464
Issue 2-0
Jumper location
Set jumper S1 to ON position
13 (126)
Dyna SNMP
Make sure that both jumpers are in ON position. Jumper NR1B S1 is

located between the DI3(J7) and V24 async(J1) connectors (see Figure
7).
14 (126)
DN70553464
Issue 2-0
Installation
Figure 7.
4.
DN70553464
Issue 2-0
S1 jumper location
Insert the card into the subrack slot
15 (126)
Dyna SNMP
When the Dyna SNMP is inserted into a slot, it performs power-up and
start-up tests. The three service LEDs light up and then go off in the
following sequence: green, yellow, and red. After successful tests, the
service LEDs should remain unlit. If any of the three service LEDs
remains lit, the unit is defective.
If the power-up test fails, the service LEDs start to blink. There can be
two reasons for the failure:
there is only one flash installed and it has a defective program
there are two flashes installed, both of which have defective

programs.
In such situations, at least the bank A flash must be changed.

If the start-up test fails, the red service LED lights up. There are three
possible reasons for this:
defective flash chip has been installed in the bank A or B
the battery of the real time clock is empty
the EEPROM is defective.
However, you can still start the CLI session to check the start-up test
results.
If the unit passes the power-up and start-up tests, the unit is ready for
configuration.
Note
When the application software is running OK, one of the LEDs is blinking
with green colour
5.
Connect the local management cable
Connect your terminal (for example, laptop computer) with the local
management cable to the LMI connector. The terminal configuration is:
16 (126)
VT100
async
9600
8 data bits
1 stop bit
no parity
no flow control
6.
Connect the extension cables
DN70553464
Issue 2-0
Installation
Dyna SNMP plug-in unit
Constructing the management cables for the Dyna SNMP Adapter plugin unit is explained in Appendix A. The recommended way of connecting
the cables is shown in Figure 8, an alternative way is given in Figure 9.
DN70553464
Issue 2-0
17 (126)
Dyna SNMP
Figure 8.
18 (126)
Recommended way of connecting the Q1 cables for the Dyna

SNMP Adapter plug-in unit
DN70553464
Issue 2-0
Installation
Figure 9.
7.
Alternative way of connecting the Q1 extension (MI/DI) cables

for the Dyna SNMP plug-in unit
Start the CLI session
Start the CLI session by pressing ENTER. The default password is

admin. When the correct password has been entered, the green service
DN70553464
Issue 2-0
19 (126)
Dyna SNMP
LED should be lit. You can check the results of the start-up test and the
software version by entering the show test and show software
commands.
If you have forgotten the password, you can bypass the password by
connecting the jumper shown in Figure 10. When the jumper is
connected, the default password admin applies.
Note
Remember that you must change the password, remove the jumper and
reboot the Dyna SNMP to use your own password again.
20 (126)
DN70553464
Issue 2-0
Installation
Figure 10.
Password jumper location
To be able to change the settings of the Dyna SNMP, you must switch to
the superuser level. This is done with the su command. The CLI prompts
DN70553464
Issue 2-0
21 (126)
Dyna SNMP
for the default superuser password, which is admin. You can also enter
su admin at once.
The default settings are shown in Table 1 in section Default settings The
CLI commands are listed in section List of commands.
8.
Configure Dyna SNMP
An example configuration presented in Figure 11 is given with the

corresponding commands.
Figure 11.
Example configuration
There are three groups of settings that must be configured when the
Dyna SNMP is commissioned: Q1 settings, IP settings, and SNMP
settings.
Dyna SNMP settings
Passwords
CLs> set passwd
sets the user password
22 (126)
DN70553464
Issue 2-0
Installation
CLs> set spasswd
sets the superuser password
CLI session time-out (in minutes)

CLs> set timeout 5
Real time clock
CLs> set clock 2008-1-21,02:14:00.0,-2:0

IP settings
Port configurations
CLs> set ethernet ipaddress 192.168.50.10
255.255.255.0
sets IP address and IP mask for Ethernet interface

CLs> enable ethernet
enables Ethernet interface

CLs> set ppp ipaddress 10.10.10.112 255.255.255.0
sets IP address and IP mask for PPP interface

CLs> set ppp async 19200 hw
sets PPP interface configuration (asynchronous mode). The hw

parameter sets the RTS/CTS flow control.
IP access table
CLs> set ipfilter 192.168.50.0 255.255.255.0
sets IP filter configuration (Dyna SNMP unit accepts packets only

from specified IP addresses)
CLs> set ipfilter 192.220.64.0 255.255.255.0
sets IP filter configuration

CLs> set ipfilter 172.16.54.0 255.255.255.0
sets IP filter configuration

CLs> disable ipfilter 0.0.0.0 0.0.0.0
disables IP filter configuration (denies universal access from any

IP address)
CLs> show ipfilter
IP filters
IP Address
DN70553464
Issue 2-0
IP Mask
Status
192.168.50.0 255.255.225.0
Enabled
10.10.10.0
255.255.255.0
Enabled
172.16.54.0
255.255.255.0
Enabled
23 (126)
Dyna SNMP
0.0.0.0
0.0.0.0
Disabled
displays IP filter configuration
IP routing table
CLs> set iproute 192.168.50.0 255.255.255.0 192.168.51.10
sets a static IP route

CLs> set iproute 0.0.0.0 0.0.0.0 198.168.50.1
sets the default gateway

SNMP settings
Community strings
CLs> set commstr rd manager1
sets an SNMP community string for read" operations

CLs> set commstr rw manager2
sets an SNMP community string for read/write" operations
Note
There can only be three community strings. If more are added, the last
one will be replaced by the new one.
Trap settings CLs> set trap 192.168.51.10 remote_mngmt

sets and enables the trap IP address and defines the community
string to be used in traps (SNMP traps will be sent to this address)
After Step 8, you can connect to the IP network via Ethernet or PPP
interfaces. To check whether the configuration was done successfully,
you can try to ping from the management computer: ping <IP address>.
9.
Configure Q1 settings
Q1 settings
Q1 bus parameters
CLs> set q1bus 9600 600 ,3
sets Q1 bus configuration for the selected port (baud rate, time out
and port). The port number can be 0, 1, 2, or 3; the default port is
0, which is the backplane Q1 bus.
10.
Add and register new managed elements
Disable the poller.

CLs> disable poller
24 (126)
DN70553464
Issue 2-0
Installation
Insert new units to the subrack. The units will go through their normal
startup procedures. Configure the following network element
parameters:
Network element Q1 address according to the subrack slot.
Network element Q1 data routes: Q1 management from subrack

backplane, data hybrid ON.
Network element Q1 bus speed according to Dyna SNMP unit Q1

bus speed.
Remote end Q1 address according to the subrack slot.
For more information, see the corresponding equipment manuals.
Note
Each Q1 element must have a unique address.
Q1 element registration
CLs> add q1element 1020 ,3
adds a Q1 element to the selected port.

The port number can be 0, 1, 2 or 3; the default port is 0.
Poller status
CLs> enable q1element 1020
enables Q1 element to be polled

CLs> enable poller
enables Q1 polling
11.
Check configuration
CLs> show q1elements
shows the addresses that have been enabled

CLs> show alarm
shows whether the equipment is operative.
2.3
Default settings
The default settings are shown in the table below.
DN70553464
Issue 2-0
25 (126)
Dyna SNMP
Table 1.
Default settings
Parameter
Default value
Timeout
5 minutes
Ethernet settings
IP address: 0.0.0.0, mask:

255.255.255.255, status: inactive:
physical address: nn:nn:nn:nn:nn:nn
PPP settings
IP address: 0.0.0.0, mask:

255.255.255.255
Status:inactive
Async HW configuration
9600
DTE
Flow control none
IP filter
Address: 0.0.0.0, Mask 0.0.0.0
IP routing table
Empty
Real time clock
2008-1-1, 12:00:00.0, +0:0
SNMP community string
public SEC
Trap address
Empty
Q1 bus settings
8 data bits, no parity, 1 stop bit

Q1 bus data transfer rate: 4800 for port 0,
9600 for ports 1, 2 and 3
Q1 bus timeout: 500 ms
Q1 bus retry count: 2
Q1 poller list
Empty
Q1 polling parameters
Q1 polling retry count: 1

Q1 loss threshold: 2
Q1 fault status consistency checks: 1
Poller status
Q1 element clock refresh period: 3600 sec

(i.e. refresh disabled)
Disabled
26 (126)
DN70553464
Issue 2-0
Installation
2.4
LEDs and rack alarms

The service LED indications are the following:
Start-up test.
The LEDs turn off in the following sequence: red+yellow+green
red+yellow red none
Red LED is lit.

There is a hardware failure.
Yellow LED is lit.

The activated PPP interface is down.
Green LED is lit.

CLI session is open.
There are three rack alarms (A, B and D). They are OFF during the startup.
DN70553464
Issue 2-0
A-alarm indicates a hardware failure in Dyna SNMP (EEPROM

failure or a memory failure).
B-alarm indicates that the activated PPP interface of the Dyna

SNMP unit (WAN or Ethernet) is down.
D-alarm is not used in the Dyna SNMP unit.
27 (126)
Dyna SNMP
Command line interface

The CLI is locally available over Local Management Interface (LMI).
Remotely, the CLI can be accessed through a telnet session.
The CLI can be used to:
configure the Dyna SNMP
configure the Q1 elements in the system
monitor the alarm status of the Q1 elements in the system.
The fault management of the Dyna SNMP and Q1 elements is done

through SNMP.
The CLI uses dynamic parsing, and you thus need to enter command
characters only to the extent that the command can be unambiguously
identified, that is, the whole command does not have to be entered.
The following concepts are used in this chapter:
28 (126)
User terminal: The user terminal is a telnet or asynchronous

terminal.
CLI session: You can initiate a CLI session by pressing ENTER on

the asynchronous terminal or by opening a telnet connection to the
Dyna SNMP unit. Only one CLI session can be run at a time.
Privilege level: There are two privilege levels: USER and

SUPERUSER. There are CLI commands that are available only at
the SUPERUSER level, and to access these commands you must
know the SUPERUSER password. You can switch back to the
USER level by using the EXIT command.
STE session: At the SUPERUSER level, you can initiate an STE

session to a selected network element. Only the EXIT and HELP
CLI commands can be used in STE sessions.
Syntax: Commands may be composed of multiple command words

and they may require arguments.
Error messages: If you give a wrong or incorrect command, an

error message is displayed. The format of the error messages is
DN70553464
Issue 2-0
Error: <explanation>, where <explanation> is a short
description of the error.
Command prompt: Each privilege level has its own command

prompt: CLu> for the USER level, CLs> for the SUPERUSER level.
For a service terminal emulation session, the prompt is STE>.
3.1
List of commands
3.1.1
Commands related to CLI session
3.1.2
DN70553464
Issue 2-0
Open CLI session
Switch to superuser privilege level
Show
Open STE session to Q1 element
Execute embedded STE command
Logout
Exit
Display help
Commands related to Dyna SNMP settings
Set user password
Set superuser password
Set customised command line prompt
Display startup test results
Display flash software versions
Set time-out parameter
Display time-out parameter
Set real time clock
Display real time clock value
Display checksum
Switch
Software download
29 (126)
Dyna SNMP
3.1.3
3.1.4
30 (126)
Reboot
Commands related to IP settings
Set IP filter configuration
Delete IP filter configuration
Enable IP filter configuration
Disable IP filter configuration
Display IP filter configurations
Set Ethernet IP configuration
Enable Ethernet interface
Disable Ethernet interface
Display Ethernet interface configuration
Display Ethernet interface statistics
Set PPP IP configuration
Disable PPP interface
Display PPP interface statistics
Enable PPP interface in asynchronous mode
Set PPP interface configuration in asynchronous mode
Display PPP interface configuration
Set IP route
Enable IP route
Disable IP route
Delete IP route
Display routing table
Display ARP (address resolution protocol) table statistics
Commands related to SNMP settings
Set SNMP community string
Display SNMP community string
Set Q1 alarm trap format
Display q1 alarm trap format
DN70553464
Issue 2-0
3.1.5
Set trap
Enable trap
Disable trap
Delete trap
Display traps
Display SNMP statistics
Commands related to element management
Set Q1 bus configuration
Enable poller
Disable poller
Refresh
Display poller status
Add Q1 elements to list of polled Q1 nodes
Delete Q1 elements from list of polled Q1 nodes
Enable Q1 elements to be polled
Disable Q1 elements to be polled
Display Q1 poller list
Display alarm status for polled Q1 nodes
Display alarms only
Display Q1 bus configuration
Set polling parameters
Display polling parameters
Show uptime
3.2
Command descriptions
3.2.1
Commands related to CLI session
DN70553464
Issue 2-0
31 (126)
Dyna SNMP
Command
Open CLI session
Description
The user presses the ENTER key of the terminal. The CLI requests for password,
which is an alphanumeric string of 6 - 12 characters. After login, the CLI displays a
command prompt if no CLI sessions are already running. If there already is another
CLI session running, the CLI displays an error message and quits.
Privilege level
USER
Syntax
<ENTER> (asynchronous terminal) or TELNET <IP_ADDRESS>
Arguments
None
Examples
<ENTER>
Password: *******
CLu>
Command
Switch to superuser privilege level
Description
The user enters the su command. The CLI requests for the superuser password.
After login, the CLI displays a superuser command prompt. If the user gives the
password together with the command, the CLI performs the validation without
prompting the password.
Privilege level
USER
Syntax
su <password>
Arguments
Optional parameter: password
Examples
CLu> su admin
CLs>
Command
Show
Description
This command can be used to view the existing configuration information in the
Dyna SNMP unit as well as to troubleshoot possible problems.
Privilege level
USER
Syntax
show [<command>]
Arguments
List of all possible arguments can be viewed by typing show ? (see the example
below). There can be one or two arguments. In some cases you also need to type
the actual port number after the argument. Most of the possible arguments are
defined in detail in the following command descriptions.
Examples
Example 1.
CLu> show ?
show ethernet
32 (126)
DN70553464
Issue 2-0
Command
Show
show ppp
show ipfilter
show iproute
show trap
show q1afmt
show commstr
show download
show stat ethernet
show stat ppp
show stat arp
show stat snmp
show stat iproute
show q1bus [,port]
show polling ,port
show poller
show q1elements
show alarm [only]
show timeout
show clock
show checksum
show software
show test
show uptime
CLu>
Example 2.
CLu> sh ethernet
Ethernet port operational status: Active.
Ethernet port IP configuration
IP Address: 192.168.50.10 IP
Mask: 255.255.255.0
Ethernet port physical address: 00 40 43 03 dd 95
CLu>
DN70553464
Issue 2-0
33 (126)
Dyna SNMP
Command
Show
Example 3.
CLu> sh q1b ,1
Q1 bus data transfer rate: 4800
Q1 bus timeout: 700
CLu>
Command
Open STE session to Q1 element
Description
The Dyna SNMP unit starts a service terminal emulation session with a specified
network element / functional entity.
Privilege level
SUPERUSER
Syntax
ste <Q1 _address> [functional_entity]
Arguments
Q1 addresses and functional entities are identified with numbers in the range 14094.
Examples
CLs> ste 70
Menu: (...)
ste: 70. 0>top>4
Command
Execute embedded STE command
Description
Performs a service terminal emulator command with the selected element directly
from the CLI command line
Privilege level
SUPERUSER
Syntax
ste <Q1 address> [functional entity]
Arguments
Q1 elements and functional entities are identified with numbers in the range 1 4094.
Messages
After successfully connecting and executing the STE command, the CLI shows the
response of the Q1 element.
Examples
CLs> ste 70 0 4,2

DATA:
(...)
CLs>
34 (126)
DN70553464
Issue 2-0
Command
Logout
Description
Terminates the CLI session (both privilege levels). Shortcut: Ctrl-D
Privilege level
USER
Syntax
logout
Arguments
None
Examples
CLs> logout
Session closed.
Command
Exit
Description
In STE sessions, the command switches back to the superuser level. At

superuser level, the command switches back to user level. At user level, the
command terminates the CLI session.
Privilege level
USER
Syntax
exit
Arguments
None
Examples
Example 1.
CLs> exit
CLu>
Example 2.
CLu> exit
Session closed.
Example 3.
STE> exit
CLs>
Command
Display help
Description
If no argument is given, this command displays general help information,

that is, syntax of commands related to the privilege level the user is logged
in. Further help on a particular command can be seen by entering command
?.
If the help command is given with an argument, help on the provided
command is displayed. If the user gives an invalid argument, the CLI
searches through the help database and displays the help item which
matches the argument best or, if nothing matches, does nothing.
Privilege level
DN70553464
Issue 2-0
USER
35 (126)
Dyna SNMP
Command
Display help
Syntax
help [<command>]
Arguments
Optional argument <command> is a CLI command or the first part of the

command.
Examples
Example 1.
CLu> help
Help entries:
su
logout
exit
show
help
Clu>
Example 2.
CLs> set ipr ?
set ip route
Privilige level: SUPERUSER
Syntax: set iproute <ip_dest> <ip_mask> <next_hop>
CLs>
3.2.2
Commands related to Dyna SNMP settings
Command
Set user password
Description
Changes the user level password. The command is effective only at

superuser level. The user must first enter the old password and then the new
password twice. After checking the new password, the CLI encrypts it and
stores it as a user password. The new password can be provided in the
command line too. The optional password string must be different from the
CLI command words.
Privilege level
SUPERUSER
Syntax
Set password [password]
Arguments
Optional password string [<old password> <new password>]
Examples
Example 1.
36 (126)
DN70553464
Issue 2-0
Command
Set user password

CLs> set passwd
Old user password:
New password:*******
Retype new password:*******
CLs>
Example 2.
CLs> set passwd admin kilo
CLs>
Command
Set superuser password
Description
Changes the superuser level password. The command is effective only at

superuser level. The user must first enter the old password and then the new
password twice. After checking the new password, the CLI encrypts it and
stores it as a superuser password. The new password can be provided in the
command line too. The optional password string must be different from the
CLI command words.
Privilege level
SUPERUSER
Syntax
set spasswd [password]
Arguments
Optional password string [<old password> <new password>]
Examples
CLs> set spasswd

Old superuser password:*****
New password:******
Retype new password:******
CLs>
Command
Description
The CLI default command prompt is CLu> for user level, CLs> for superuser
level, and STE> for an STE session. The customised CLI command prompt
is of the following formats: CLu: location> for the user level, CLs:
location for the superuser level, and STE: location: Q1address for
the STE session. The Q1 address is automatically added to the customised
STE command prompt. If no argument is provided, then location" is an
empty string. If an optional argument is supplied, it must be different from the
reserved command words.
Privilege level
SUPERUSER
Syntax
set prompt [<location>]
DN70553464
Issue 2-0
37 (126)
Dyna SNMP
Command
Arguments
Argument <location> is an ASCII string (max 12 characters).
Examples
CLs> set prompt Kilo

CLs:Kilo> STE 70 0
STE:Kilo:70. 0>top>exit
CLs: Kilo>
Command
Display startup test results
Description
Displays startup test results
Privilege level
USER
Syntax
show test
Arguments
None
Examples
CLu> sh test
Startup status
Bank A flash status:
OK.
Bank B flash status:
OK.
RTC battery:
OK.
EEPROM:
OK.
CLu>
Command
Display flash software versions
Description
Displays bank A and bank B flash software versions and the active bank.
Priviledge level
USER
Syntax
show software
Arguments
None
Examples
CLu> sh so
Bank A software id: S21720.02 - 00 - 29 / 11.04.2008
10:34:07
Bank B software id: <not operational>
Active bank: Bank A.
Boot software id: S66342.01 - A1 - 10 / 08.10.2001
15:25:39
CLu>
38 (126)
DN70553464
Issue 2-0
Command
Set timeout parameter
Description
Sets the CLI session time-out parameter. When providing the command
prompt, the CLI starts a timer that measures idle time. After the idle time
reaches the time-out value, the CLI terminates the session and displays the
message: CLI session timeouted.
Privilege level
SUPERUSER
Syntax
set timeout <value>
Arguments
The time-out value is an integer in the range 0 - 255. It is the number of

minutes before the idle CLI session is terminated.
0 = session always open.
Note: It is strongly recommended that the value 0 is not used. If the value 0 is
used, those sessions that are not properly closed will prevent you to open new
CLI sessions.
Examples
CLs> set timeout 4

CLs>
Command
Display timeout parameter
Description
Displays the CLI session time-out parameter. When providing the command
prompt, the CLI starts a timer that measures idle time. After the idle time
reaches the time-out value, the CLI terminates the session and displays the
message: CLI session timeouted. This command displays the time-out
parameter value.
Privilege level
USER
Syntax
show timeout
Arguments
None
Examples
CLu> sh timeout
CLI session timeout [minutes] : 6
CLu>
Command
Set realtime clock
Description
Sets real time clock parameter value.
Privilege level
SUPERUSER
Syntax
set clock <value>
Arguments
Value is specified as a formatted string of the following format:

YYYYY-MM-DD, hh:mm:ss.ds, <d>hb:mb
YYYYY is the year [0.. .65535].
DN70553464
Issue 2-0
39 (126)
Dyna SNMP
Command
Set realtime clock

MM is month [1...12].
DD is day [1 ...31 ].
hh is hours [0...23].
mm is minutes [0...59].
ss is seconds [0...59].
ds is deciseconds [0. ..9].
<d> expresses direction from UTC and is either '-' or '+'.
hb is the time bias from the UTC for hours.
mb is the time bias for minutes.
For example, Tuesday May 26, 2008, 1:30:15 PM EET would be 2008 -5-26,
13:30:15.0+0:0.
Note: Use of UTC time is recommended, since the clock does not recognise
daylight saving time.
Examples
CLs> set clock 2008-1-21,02:14:00.0,+0:0

CLs>
Command
Display realtime clock value
Description
Displays the real time clock value
Privilege level
USER
Syntax
show clock
Arguments
None
Examples
CLu> sh clock
2008-2-10,11:29:07.6,+0:0
CLu>
Command
Display checksum
Description
Displays the checksum for the Dyna SNMP configuration
Privilege level
USER
Syntax
show checksum
Arguments
None
Examples
CLu> sh checksum
13041
40 (126)
DN70553464
Issue 2-0
Command
Display checksum
CLu>
Command
Switch
Description
Switches between banks A and B: after rebooting, makes the inactive software
active and vice versa.
Privilege level
SUPERUSER
Syntax
switch
Arguments
None
Examples
CLs> switch
Command
Software download
Description
Downloads software file to the inactive bank (A or B).

Note: you can terminate downloading by pressing CTRL-B.
After the termination, the inactive bank cannot be used.
Privilege level
SUPERUSER
Syntax
download <IP_address> <file_full_pathname>
Arguments
IP address of the TFTP server is an IP string. The maximum file name length is 40
characters.
Examples
CLs> download 172.16.1.1 /pub/software/v102.bin Received

blocks: 896
Transfer completed.
CLs>
Command
Reboot
Description
Reboots the system.
Privilege level
SUPERUSER
Syntax
reboot
Arguments
None
Examples
CLs> reboot
DCN Adapter unit reset.
Session closed.
DN70553464
Issue 2-0
41 (126)
Dyna SNMP
3.2.3
Commands related to IP settings
Command
Set IP filter configuration
Description
Sets the IP filter configuration. Incoming IP packets that do not match the source IP
address filter are discarded. The filter becomes active (enabled) after the command has
been accepted. The CLI performs parameter type and range prevalidation but does not
check the validity of the supplied arguments.
Privilege level
SUPERUSER
Syntax
set ipfilter <IP_address> <IP_mask>
Arguments
Both arguments are specified as IP strings. An IP string consists of four decimal numbers
separated by dots with values between 0 and 255.
Examples
CLs> set ipfilter 192.168.50.0 255.255.255.0

CLs>
Command
Delete IP filter configuration
Description
Deletes an existing IP filter configuration.
Privilege level
SUPERUSER
Syntax
delete ipfilter <IP_address>
Arguments
The argument is an IP string consisting of four decimal numbers separated by dots with
values between 0 and 255.
Examples
CLs> del ipfilter 192.168.50.0

CLs>
Command
Enable IP filter configuration
Description
Enables IP filter configuration. It is possible to have multiple IP configurations, but they

must be enabled one filter at a time. The enabled configuration is identified by IP address
and IP mask.
Privilege level
SUPERUSER
Syntax
enable ipfilter <IP_address> <IP_mask>
Arguments
The argument is an IP string consisting of four decimal numbers separated by dots with
values between 0 and 255.
Examples
CLs> ena ipfilter 192.168.50.0 255.255.255.0

CLs>
Command
42 (126)
DN70553464
Issue 2-0
Command
Description
Disables the IP filter configuration.
Privilege level
SUPERUSER
Syntax
disable ipfilter <IP_address> <IP_mask>
Arguments
The argument is an IP string consisting of four decimal numbers separated by

dots with values between 0 and 255.
Examples
CLs> dis ipfilter 192.168.50.0 255.255.255.0

CLs>
Command
Display IP filter configurations
Description
Displays IP filter configurations and their current states (enabled/disabled).
Privilege level
USER
Syntax
show ipfilter
Arguments
None
Examples
CLs> sh ipfilter
IP address
IP mask
Status
192.168.50.0
255.255.255. 0
enabled
172.16.54. 0
255.255.255. 0
disabled
CLs>
Command
Set Ethernet IP configuration
Description
Sets Ethernet IP configuration. The IP address and the IP mask must be supplied.
The interface must be separately enabled so as to be activated.
Note : If Ethernet and PPP interfaces have the same address, even if the other one
is disabled, the interfaces do not work.
Privilege level
SUPERUSER
Syntax
set ethernet ipaddress <IP_address> <IP_mask>
Arguments
Both arguments are IP strings consisting of four decimal numbers separated by

Examples
CLs> set ethernet ipaddress 192.168.50.10 255.255.255.0
Command
Description
Enables Ethernet interface.
Privilege level
SUPERUSER
DN70553464
Issue 2-0
43 (126)
Dyna SNMP
Command
Syntax
enable ethernet
Arguments
None
Examples
CLs> ena ethernet

CLs>
Command
Disable Ethernet interface
Description
Disables Ethernet interface.
Privilege level
SUPERUSER
Syntax
disable ethernet
Arguments
None
Examples
CLs> dis ethernet

CLs>
Command
Display Ethernet interface configuration
Description
Displays Ethernet interface configuration: IP address, IP mask, operational status

(active/ inactive) and physical address.
Privilege level
USER
Syntax
show ethernet
Arguments
None
Examples
CLu> sh ethernet
Ethernet port operational status: Inactive. Ethernet port IP
configuration:
IP address: 192.168.50.10
IP mask: 255.255.255.0
Ethernet port physical address:00 40 43 F7 7F 25
CLs>
Command
Description
Displays Ethernet interface statistics
Privilege level
USER
Syntax
show stat ethernet
Arguments
None
44 (126)
DN70553464
Issue 2-0
Command
Examples
CLu> sh stat ethernet

Ethernet interface statistics:
operStatus
up
lastChange
12
inOctet s
10
inUcastPkts
10
inNUcastPkts
10
inD is cards
10
inErrors
10
inUnknownProtos
10
outOctets
10
outUcastPkts
10
outNUcastPkts
10
outDiscards
10
outErrors
10
outQLen
10
CLu>
Command
Set PPP IP configuration
Description
Sets PPP IP configuration. IP address and IP mask have to be supplied. The

interface must be separately enabled so as to be activated.
Note : If Ethernet and PPP interfaces have the same address, even if the other one
was disabled, the ports do not work.
Privilege level
SUPERUSER
Syntax
set ppp ipaddress <IP_address> <IP_mask>
Arguments
Both arguments are IP strings consisting of four decimal numbers separated by

Examples
CLs> set ppp ipaddress 10.10.10.112 255.255.255.0

CLs>
Command
Description
Disables the PPP interface
DN70553464
Issue 2-0
45 (126)
Dyna SNMP
Command
Privilege level
SUPERUSER
Syntax
disable ppp
Arguments
None
Examples
CLs> dis ppp

CLs>
Command
Display PPP interface statistics
Description
Displays PPP interface statistics
Privilege level
USER
Syntax
show stat ppp
Arguments
None
Examples
Example 1.
CLu> sh stat ppp
PPP interface statistics:
operStatus
up
lastChange
inOctet s
inUcastPkts
inNUcastPkts
inD is cards
inErrors
inUnknownProtos 0
outOctets
outUcastPkts
outNUcastPkts
outDiscards
outErrors
outQLen
CLu>
46 (126)
DN70553464
Issue 2-0
Command
Enable PPP interface in asynchronous mode
Description
Enables PPP interface in asynchronous mode
Privilege level
SUPERUSER
Syntax
enable ppp async
Arguments
None
Examples
CLs> ena ppp async

CLs>
Command
Set PPP interface configuration in asynchronous mode
Description
Sets hardware configuration to PPP interface in asynchronous mode.
Privilege level
SUPERUSER
Syntax
set ppp async <baudrate> <flow_control>
Arguments
Valid baud rates are: 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600.
Equipment mode is always DTE
Flow control is either None or HW.
Examples
CLs> set ppp async 2400 none

CLs>
Command
Description
Displays PPP interface configuration: IP address, IP mask, operational status

(active/ inactive) and hardware configuration: (asynchronous) mode, baud rate,
equipment type and flow control.
Priviledge level
USER
Syntax
show ppp
Arguments
None
Examples
CLs> sh ppp
PPP operational status: active in asynchronous mode PPP port
IP configuration
IP address: 192.168.50.10
IP mask: 255.255.255.0
PPP port asynchronous hardware configuration:
Equipment mode: DTE
Baudrate: 2400
DN70553464
Issue 2-0
47 (126)
Dyna SNMP
Command

Flow control: None
CLs>
Command
Set IP route
Description
Sets static IP route. IP packets that are destined for <IP_dest> are routed through
<next_hop> after enabling the new route. The default gateway must be set to the
network that is associated with the active management interface. <IP_dest> and
<IP_mask> for the default gateway are 0.0.0.0 and 0.0.0.0, respectively.
Privilege level
SUPERUSER
Syntax
set iproute <IP_dest> <IP_mask> <next_hop>
Arguments
All arguments are IP strings consisting of four decimal numbers separated by dots
with values between 0 and 255.
Examples
CLs> set iproute 192.168.50.0 255.255.255.0 192.168.51.10

CLs>
Command
Enable IP route
Description
Enables IP route.
Privilege level
SUPERUSER
Syntax
enable iproute <IP_dest> <IP_mask> <next_hop>
Arguments
All arguments are IP strings consisting of four decimal numbers separated by dots
Examples
CLs> ena iproute 192.168.50.0 255.255.255.0 192.168.51.10

CLs>
Command
Disable IP route
Description
Disables static IP route
Privilege level
SUPERUSER
Syntax
disable iproute <IP_dest> <IP_mask> <next_hop>
Arguments
The argument is an IP string consisting of four decimal numbers separated by dots

Examples
CLs> dis iproute 192.168.50.0 255.255.255.0 192.168.51.10

CLs>
48 (126)
DN70553464
Issue 2-0
Command
Delete IP route
Description
Deletes static IP route.
Privilege level
SUPERUSER
Syntax
delete iproute <IP_dest>
Arguments
The argument is an IP string. An IP string consists of four decimal numbers

separated by dots with values between 0 and 255.
Examples
CLs> del iproute 192.168.50.0

CLs>
Command
Display routing table.
Description
Displays routing table
Privilege level
USER
Syntax
show stat iproute
Arguments
None
Examples
CLs> sh stat iproute

IP routing statistics:
dest 123.145.110.0
if Index
123.145.111.0
ethernet
ppp
next hop 123.145.111.112 23.145.111.112

type
proto
age
6231
4176
mask
255.255.255.0
255.255.255. 0
metric1
10
10
CLs>
Command
Display ARP (Address Resolution Protocol) table statistics
Description
Displays ARP table.
Privilege level
USER
Syntax
show stat arp
Arguments
None
CLs> sh stat arp
Examples
ARP table:
DN70553464
Issue 2-0
49 (126)
Dyna SNMP
Command
Display ARP (Address Resolution Protocol) table statistics

If Index
Network address Physical address
Ethernet
176.123.111.13 3d 45 2a 47 87
Ethernet
176.123.111.14 21 78 09 34 83
Ethernet
176.123.111.15 00 32 2c 67 27
CLs>
3.2.4
Commands related to SNMP settings
Command
Set SNMP community string
Description
Sets new community string to get transactions.
Privilege level
SUPERUSER
Syntax
set commstr <mode> <string>
Arguments
set commstr <mode> <string><mode> may be rd" (read) or rw" (read-write) or sec"
(secure)
<string> may be an alpha numeric string (max 16 characters).
Note: There can be only three community strings. If more are added, the last one will
be replaced by the new one. To show the existing community strings, use the
command sh com. If you want to change other community strings than the third one,
you must first remove one of the first two, and then set another one.
Examples
CLs> set co rw
rw
SNMP community strings (3)

RD
rd
SEC
sec
RW
rw
CLs> set com sec huomenta

CLs> sh com
SNMP community strings(3)
50 (126)
RD
rd
SEC
sec
SEC
huomenta
DN70553464
Issue 2-0
Command
Display SNMP community string
Description
Displays community string for get transactions
Privilege level
USER
Syntax
show commstr
Arguments
None
Examples
Example 1.
CLu> sh commstr
SNMP community string(s):
SEC public
CLu>
Command
Set Q1 alarm trap format
Description
Sets the format used for Q1 alarm traps to one of the predefined formats.
Privilege level
SUPERUSER
Syntax
set q1afmt <format>
Arguments
The argument is integer 0 or 1. When the value is set to 0, the trap will be compatible
with Nokia Siemens Networks NMS/10. When the value is set to 1, the Q1 bus and
Q1 address are added to the trap.
Examples
CLs> set q1afmt 0

CLs>
Command
Display Q1 alarm trap format
Description
Displays the currently used Q1 alarm trap format.
Privilege level
USER
Syntax
show q1afmt
Arguments
None
Examples
CLu> sh q1afmt
Q1 Alarm Trap Format: 0
CLu>
Command
Set trap
Description
Sets and enables the trap destination IP address.
Privilege level
SUPERUSER
DN70553464
Issue 2-0
51 (126)
Dyna SNMP
Command
Set trap
Syntax
set trap <I P_address> <SNMP community string>
Arguments
The arguments are an IP string and an ASCII string. The IP string consists of four
decimal numbers separated by dots with values between 0 and 255. The SNMP
community string can be 1-16 characters long
Examples
CLs> set trap 192.168.51.10 public

CLs>
Command
Enable trap
Description
Enables the trap destination IP address.
Privilege level
SUPERUSER
Syntax
enable trap <IP_address> <SNMP community string>
Arguments
community string can be 1-16 characters long.
Examples
CLs> ena trap 192.168.51.10 public

CLs>
Command
Disable trap
Description
Disables the trap destination IP address.
Privilege level
SUPERUSER
Syntax
disable trap <IP_address> <SNMP community string>
Arguments
Examples
CLs> dis trap 192.168.51.10 public

CLs>
Command
Delete trap
Description
Deletes the trap destination IP address.
Privilege level
SUPERUSER
Syntax
delete trap <IP_address> <SNMP community string>
Arguments
52 (126)
DN70553464
Issue 2-0
Command
Delete trap
Examples
CLs> del trap 192.168.51.10 public

CLs>
Command
Display traps
Description
Displays all the trap destination IP addresses
Privilege level
USER
Syntax
show trap
Arguments
None
Examples
CLs> sh trap
SNMP traps:
IP address
Community string Status
123 .111.123 .12
public
disabled
123 .111.123 .13
public
disabled
123.111.114.96
public
disabled
Cls>
Command
Description
Displays SNMP service statistics.
Privilege level
USER
Syntax
show stat snmp
Arguments
None
Examples
CLs> sh stat snmp

SNMP statistics:
enableAuthenTraps
DN70553464
Issue 2-0
enabled
inPkts
outPkts
inBadVers ions
inBadCommunityNames
inBadCommunityUses
53 (126)
Dyna SNMP
Command

inASNParseErrs
inTooBigs
inNoSuchNames
0
0
inBadValues
CLs>
3.2.5
Commands related to element management
Command
Set Q1 bus configuration
Description
Sets configuration to Q1 bus
Privilege level
SUPERUSER
Syntax
set q1bus <baudrate> <timeout> [,bus]
Arguments
Valid baud rates are: 300, 600,1200, 2400, 4800, 9600, 19200.
Timeout is an integer between 10 and 10000. It shows in milliseconds when the
timeout occurs. Valid bus numbers are 0, 1, 2, and 3. The default bus value is 0,
which is the backplane bus. The values 1, 2, and 3 indicate the corresponding DI
ports. Disable the poller before changing the Q1 baud rate.
Examples
CLs>set q1bus 9600 100 ,3

CLs>
Command
Enable poller
Description
Enables the polling of Q1 elements.
Privilege level
SUPERUSER
Syntax
enable poller
Arguments
None
Examples
CLs> ena polle

enabling. . done
CLs>
Command
Disable poller
Description
Disables the polling of Q1 elements.
54 (126)
DN70553464
Issue 2-0
Command
Disable poller
Privilege level
SUPERUSER
Syntax
disable poller
Arguments
None
CLs> disa polle
Examples
disabling. . done
CLs>
Command
Refresh
Description
Synchronises the data maintained by the Dyna SNMP unit with the data of the
network elements under it.
Privilege level
USER
Syntax
refresh
Arguments
None
Examples
CLu> ref
disabling..done
enabling..done
CLu>
Command
Display poller status
Description
Displays poller status (enabled/disabled).
Privilege level
USER
Syntax
show poller
Arguments
None
Examples
CLu> sh poller
Poller status: enabled.
CLu>
Command
Description
Adds Q1 elements identified by their Q1 address to the list of polled nodes. The
poller will effectively poll the recently added Q1 elements after they have been
enabled.
Privilege level
SUPERUSER
DN70553464
Issue 2-0
55 (126)
Dyna SNMP
Command
Syntax
add q1element <Q1_address> <Q1_address> [,port]
Arguments
The Q1 address is a (list of) 4-digit decimal number(s) in range [1. ..4094]. The Q1
addresses can be given as one or more individual addresses or as a range. If
individual addresses are given, the addresses are separated from each other by a
space. If a range is given, the first and last items in the range are separated from
each other by a hyphen and spaces around it. The Q1 address value may optionally
be followed by , and the bus number.
Valid ports are 0, 1, 2 and 3; the default port is 0, which is the backplane bus
element.
Examples
Example 1.
CLs> add q1el 80 90 ,3
adding..done
CLs>
Example 2.
CLs> add q1e 50 - 55 ,2
adding..done
CLs>
Command
Delete Q1 elements from list of polled Q1 nodes
Description
Deletes Q1 elements identified by their Q1 address from the list of polled nodes.
Privilege level
SUPERUSER
Syntax
delete q1element <Q1_address> ...
Arguments
Argument is a (list of) 4-digit decimal number in range [1 ...4094] indicating the Q1
elements (addresses) to be removed from the polling list. The Q1 addresses can be
given as one or more individual addresses or as a range. If individual addresses are
given, the addresses are separated from each other by a space. If a range is given,
the first and last items in the range are separated from each other by a hyphen and
spaces around it.
Examples
Example 1.
CLs> del q1el 2345 1234 ,0
deleting..done
CLs>
Example 2.
CLs> del q1e 50 - 55
deleting..done
CLs>
56 (126)
DN70553464
Issue 2-0
Command
Enable Q1 elements to be polled
Description
Enables the polling of the Q1 elements identified by their Q1 address
Privilege level
SUPERUSER
Syntax
enable q1element <Q1_address>, ...
Arguments
elements (addresses) to be enabled on he polling list. The Q1 addresses can be
spaces around it.
Examples
Example 1.
CLs> ena q1el 80 90
enabling..done
CLs>
Example 2.
CLs> ena q1e 50 - 55
enabling..done
CLs>
Command
Disable Q1 elements to be polled
Description
Disables the polling of Q1 elements identified by their Q1 address and bus. Disable
the poller before changing the Q1 baud rate.
Privilege level
SUPERUSER
Syntax
disable q1element <Q1_address>, ...
Arguments
elements (addresses) to which polling shall be disabled. The Q1 addresses can be
spaces around it.
Examples
CLs> disable q1el 80 90

disabling..done
CLs>
Command
Description
Displays the poller list, that is, shows the elements and ports that are subject to
DN70553464
Issue 2-0
57 (126)
Dyna SNMP
Command

polling.
Privilege level
USER
Syntax
show q1elements
Arguments
None
CLs> sh q1el
Examples
List of registered Q1 nodes:

Q1 adress [Port]
Polling status
0020 [0] D/ND
enabled
0021 [1] D/ND
enabled
0022 [1]
enabled
CLs>
Command
Display alarm status for polled Q1 nodes
Description
Displays the alarm status of all Q1 elements included in the poller list. Alarm status
is shown as follows:
Q1_address Status Equipment type Time stamp
Privilege level
USER
Syntax
show alarm
Arguments
None
Examples
CLs> sh alarm
General alarm status of Q1 node(s)
Q1 address Status Equipment type
Time stamp
0001
FAIL
DN 2
2008-6-11,13:44:48.6,+0:0
0002
FAIL
DN 2
2008-6-11,13:44:49.2,+0:0
0003
FAIL
DN 2
2008-6-11,13:44:49.7,+0:0
0004
OK
DN 2
0005
OK
DN 2
0006
OK
DN 2
CLs>
Command
Display alarms only
Description
Displays only those nodes that currently have an alarm status on. Alarm status is
shown as follows:
58 (126)
DN70553464
Issue 2-0
Command
Display alarms only

Q1_address Status Equipment type Time stamp
Privilege level
USER
Syntax
show alarm only
Arguments
None
Examples
CLs> sh alarm only

General alarm status of Q1 node(s)
Q1 address Status Equipment type Time stamp
0001
FAIL
DN 2
2008-6-11, 13 : 44 : 48 6,+0:0
0002
FAIL
DN 2
2008-6-11, 13 : 44 : 49.2,+0:0
0003
FAIL
DN 2
2008-6-11, 13 : 44 : 49.7,+0:0
CLs>
Command
Display Q1 bus configuration
Description
Displays Q1 bus configuration (speed and timeout)
Privilege level
SUPERUSER
Syntax
show q1bus [,port]
Arguments
Valid ports are 0, 1, 2 and 3. The default port is 0, which is the backplane bus.
Examples
CLu> sh q1b
Q1 bus timeout: 1000
Command
Description
Sets various polling parameters
Privilege level
SUPERUSER
Syntax
set polling <parameter> <value> <,port>
Arguments
Valid bus numbers are 0, 1, 2, and 3. The parameter can be: speed, pollretry,
cmdretry, lossthreshold, packetout, fscc, erefresh.
If the parameter is speed, the possible values are: 300, 600, 1200, 2400, 4800,
9600, 19200.
If the parameter is pollretry, the value takes an integer between 0 and 10,
corresponding to the maximum number of immediate fault polling retry attempts
after a network element has failed to respond.
DN70553464
Issue 2-0
59 (126)
Dyna SNMP
Command

If the parameter is cmdretry, the value takes an integer between 0 and 10,
corresponding to the maximum number of retry counts for all commands except the
fault polling.
If the parameter is lossthreshold, the value takes an integer between 0 and 10,
corresponding to the number of allowed connection failures before the connection
to a network element is considered lost.
If the parameter is packetout, the value takes an integer between 2 and 600 in
100ms units, corresponding to the timeout in waiting for a Q1 packet level
response.
If the parameter is fscc, the value takes an integer between 1 and 100,
corresponding to the number of NEs polled for full fault status after each fault
polling cycle.
If the parameter is erefresh, the value is given in seconds, corresponding to the
clock refresh rate in the E generation NEs.
Examples
CLs> set polli pollr 3 ,2

CLs> set polli loss 3 ,2
CLs> set polli fs 3 ,2
CLs> set polli ere 3600 ,2
CLs> set polli spe 4800 ,2
CLs> set polli pack 1500 ,2
CLs> set polli cmd 3 ,2
CLs>
Command
Description
Shows Q1 polling configuration
Privilege level
SUPERUSER
Syntax
show polling [,port]
Arguments
Valid Q1 bus values are 0, 1, 2 and 3. The default value is 0, which is the
backplane bus. Values 1, 2, and 3 indicate the corresponding DI port.
Examples
CLs> sh polli ,2
PORT DI2:
Q1 polling retry count: 3
Q1 loss threshold: 3
Q1 fault status consistency checks: 3
Q1 element clock refresh period: 3600 sec
60 (126)
DN70553464
Issue 2-0
Command

Q1 bus timeout: 1500
Command
Show uptime
Description
Shows how long Dyna SNMP unit has been running since the last reset or reboot.
Privilege level
SUPERUSER
Syntax
show uptime
Arguments
None
CLs> sh uptime
Examples
up 2 days, 19:18:48,112
DN70553464
Issue 2-0
61 (126)
Dyna SNMP
SNMP
The SNMP functionality can be used to:
monitor the faults of the Q1 elements
update the PDH current alarms list from the Dyna SNMP unit
update the PDH nodes list from the Dyna SNMP unit.
To be able to use the SNMP functionality, you need the following files:
62 (126)
DynaSNMPMIB file
MIB-2 (RFC1213) file.
DN70553464
Issue 2-0
Nokia Siemens Networks Q1 Management pipe
Nokia Siemens Networks Q1

Management pipe
The Q1 Management pipe allows you to use node managers. By using
node managers you can communicate with the Q1-managed network
elements connected to the Dyna SNMP.
The node managers use General Communication Service (GCS) as the
communication stack. The Nokia Siemens Connection Tool which is a
part of GCS allows you to define Q1 connections that are saved in the
node manager address database. These connections are required to
enable a node manager to connect to a node via the Dyna SNMP unit. A
connection type, Nokia Siemens Networks Q1 Connection Pipe, must be
selected for communicating with the Dyna SNMP unit (Nokia Siemens
Networks Q1 Connection Pipe refers to the LAN connection to the Dyna
SNMP).
GCS is connected to the Nokia Siemens Networks Q1 Management pipe
of the Dyna SNMP unit. When you create Q1 connections (of the type
Nokia Siemens Networks Q1 Connection Pipe), you need to have the
Dyna SNMP superuser password. The username must be PAM.
The bus and ID are 0. The port is 27500, allowing four simultaneous
connections.
DN70553464
Issue 2-0
63 (126)
Dyna SNMP
Appendix A: Cabling in a Dynanet environment

This appendix describes how to do the cabling in a DYNANET
environment when using the Dyna SNMP plug-in unit (without the 19
rack mounting kit).
A.1 EMC compatibility and cabling
Electromagnetic compatibility is achieved by using shielded cables in the

front panel connectors and securing the cable shields to the subrack
grounding gaskets with cable ties. The subrack front cover must be
closed.
The shielded cables utilise double-foil shielded MMHS cables, where the
shielding in the connector end is equipped with a copper sleeve for
reliable grounding and mechanical strength. Instructions on how to
construct shielded cables can be found below.
Figure 12.
Attaching the shielded cables
The grounding screen of the cable must be in good electrical contact

with the conductive EMC gaskets of the cable grounding assemblies.
64 (126)
DN70553464
Issue 2-0
Proper electrical contact must be ensured, for example by measuring the

resistance. During the measurement, the ends of the cable must not be
in contact with anything. The resistance between the cable screen of
one connector to the body of the subrack must be less than 1 ohm .
When constructing the cables, follow the guide-lines below to meet the
specified EMC compatibility.
MMHS cables should be used. These cables have a double foil

shield. When the outer foil is stripped, the inner foil presents a
conductive surface to an additional copper sleeve.
Copper grounding sleeve must be used to protect the MMHS foil

shield. If the shield is connected to the terminal end connector
casing, the grounding sleeve must be used in that end too. If a
thickening is required for proper strain relief, it can be built of
copper tape on the copper sleeve.
Differential data and timing signals must be connected to the

internally twisted pairs of the cable.
A.1.1 EMC
Table 2.
Specifications for EMC requirements
Specification
Applies for
EN 50081-1 (1992)
Generic emission, residential, commercial, light industry
EN 50082-1 (1997)
Generic immunity, residential, commercial, light industry
EN 50082-2 (1995)
Generic immunity, industry
EN 300386 (2008)
EMC requirements, telecommunication network equipment

ETSI EMC requirements, telecommunication network equipment
ETS 300386 (2008)

normal priority of service
C.I.S.P.R. 22 Class B
Emission, information technology equipment
Special structures, such as DYNANET 19" EMC subrack and shielded

cables according to these structures, must be used.
DN70553464
Issue 2-0
65 (126)
Dyna SNMP
A.1.2. Management cable (Ethernet 10Base-T)
66 (126)
Figure 13.
Ethernet 10Base-T cable
Table 3.
Ethernet cable part information
Part name
Part type
Quantity
Cable
Telecom cable 4-pairs ALshielded (EMC), e.g.

MMHS 4x2x0.4+0.4
3m
Copper sleeve
d4 mm tinned Cu tol. 3.7/9
0.44 m
DN70553464
Issue 2-0
Part name
Part type
Quantity
mm, e.g. Raychem RAY 101 - 4.0

Shrinking sleeve
6.4 - 4.0 mm polyolef.

black, e.g. Raychem RNF 100 1/4-0
0.05 m
Bunch clip
100x2.5 mm PA black, e.g.

Panduit PLT 1M - 0 black
5 pcs
Modular plug
Shielded RJ45 for solid

conductor, e.g. Stewart
940-SP-36-08-08
2 pcs
Copper tape
12.7 mm x 32 m s75mm
pretinned, e.g. Chomerics
CCK-36-101 -0050
0.28 m
Figure 14.
DN70553464
Issue 2-0
Structure of Ethernet cable
67 (126)
Dyna SNMP
Figure 15.
68 (126)
Work order for EMC contact section in the management cable
DN70553464
Issue 2-0
A.1.3. Local management interface cable (LMI cable)
Use the Local Management cable E64320.01 to connect your PC's serial
port to the local management console interface.
Note
The LMI cable is a non-EMC compatible cable and should therefore be
disconnected from a final installation. An EMC compatible cable may be
constructed based on instructions in this Appendix.
Figure 16.
DN70553464
Issue 2-0
Local management interface cable
69 (126)
Dyna SNMP
Figure 17.
Work order for the EMC contact section in the euroconnector

end.
A.1.4 Interface cable, asynchronous PPP
An EMC-compatible cable can be constructed from the management

cable (see section A.1.2) by replacing either end with the desired
connector. A non-EMC compatible installation may use the local
management interface cable according to section A.1.3 and a 9-to-25
pin D-connector converter for, for example, a standard modem interface.
A.1.5 Q1 cable
A ready-made EMC-compatible interface cable (T66340.5 5) is available

for connecting one unit to Dyna SNMP.
70 (126)
DN70553464
Issue 2-0
Figure 18.
Q1 cable
A.1.6 Connectors and pin numbering
This section describes the connectors and their pins in detail.
DN70553464
Issue 2-0
71 (126)
Dyna SNMP
Figure 19.
Connectors of Dyna SNMP
A.1.6.1 Subrack connector P4 (3 x 32; euro; male)
Table 4.
PIN
Pin configuration for connector P4
ROW C
ROW B
ROW A
GND
GND
GND
1
2
72 (126)
DN70553464
Issue 2-0
PIN
ROW C
ROW B
ROW A
3
4
5
6
7
8
9
10
11
Q1 bus 0 (Out)
12
Q1 bus 0 (In)
GND
13
14
15
MP5V (Out)
16
17
UA0 (In)
18
UA1 (In)
19
UA2 (In)
AA (Out)
20
UA3 (In)
AB (Out)
21
UA4 (In)
AD (Out)
22
VAP5 (In)
23
GND
24
25
26
27
28
29
30
VNB (In)
VNB (In)
31
VPB (In)
VPB (In)
32
DN70553464
Issue 2-0
73 (126)
Dyna SNMP
Abbreviations used in the previous table:

Q1
Q1 bus, master
MP5V
Unit voltage (+5 V)
AA, AB, AD
Rack Alarm A/B/D
UA0 .. UA4
Unit address, UA4 on MSB (No. of unit location in

subrack)
VNB, VPB
Negative and positive battery voltages
VAP5
External auxiliary voltage +5 V
GND
Ground
A.1.6.2 Q1 extension connector J5-J7 (RJ45)
Figure 20.
Q1 extension connector pin numbering
Table 5.
Pin configuration for connector J5-J7
PIN
Name
1
2
3
DOB (Out)
DIB (In)
DIA (In)
DOA (Out)
7
8
74 (126)
DN70553464
Issue 2-0
Abbreviations used in the previous table:

DI1A, DI1B, DO1A,
DO1B
Data interface 1, asynchronous, V.1 1/RS-422
DI2A, DI2B, DO2A,

DO2B
DI3A, DI3B, DO3A,

DO3B
GND
Ground
A.1.6.3 Async PPP and LMI J1, J2 connectors (8-pin RJ-45), Dyna SNMP
unit is DTE
Figure 21.
RJ-45 connector pin numbering
Table 6.
Connecting the Dyna SNMP to modem (DCE)
DCN Adapter
Modem (DCE)
(DTE) RJ-45
DB-25
2 DSR
7 DTR
3 RXD
6 TXD
1 CTS
8 RTS
4 GND
DN70553464
Issue 2-0
6 DSR
20 DTR
3 RXD
2 TXD
5 CTS
4 RTS
7 GND
75 (126)
Dyna SNMP
Table 7.
PIN
Pin configuration for connectors J1 and J2 when Dyna SNMP

acts as DTE
Signal
Direction DTEDCE
Signal name
106
Ready for sending (CTS)
107
Data set ready (DSR)
104
Received data (RxD)
102
Signal ground (GND)
102
Signal ground (GND)
103
Transmitted data (TxD)
108
Connect data set to line
105
Request to send (RTS)
A.1.6.4 Async PPP and LMI (J1, J2 connectors (8-pin RJ-45), Dyna SNMP
unit is DCE
Figure 22.
Table 8.
Connecting the Dyna SNMP terminal (DTE)
DCN Adapter
(DCE) RJ-45
Terminal (DTE) DB-25
Terminal (DTE)
DB-9
2 DSR
20 DTR
4 DTR
7 DSR
6 DSR
8 DCD
1 DCD
7 DTR
76 (126)
DN70553464
Issue 2-0
DCN Adapter
(DCE) RJ-45
Terminal (DTE) DB-25
Terminal (DTE)
DB-9
3 RXD
2 TXD
3 TXD
6 TXD
3 RXD
2 RXD
1 CTS
4 RTS
7 RTS
8 RTS
5 CTS
8 CTS
4 GND
7 GND
5 GND
Table 9.
PIN
Pin configuration for connectors J1 and J2 when SNMP Dyna

acts as DCE
Direction Dyna
SNMP-DCE
Signal
Signal name
105
Request to send (RTS)
108
Connect data set to line
103
Transmitted data (TxD)
102
Signal ground (GND)
102
Signal ground (GND)
104
Received data (TxD)
107
Data set ready (DSR)
106
Ready for sending (CTS)
A.1.6.5 Etherent connector J3, 10Base-T
Figure 23.
DN70553464
Issue 2-0
77 (126)
Dyna SNMP
Table 10.
78 (126)
Pin configuration for connector J3
PIN
Signal
Tx+
Transmit data +
Tx-
Transmit data -
Rx+
Received data +
Rx-
Received data -
Direction
MDI signal
DN70553464
Issue 2-0
Appendix B: Download and tips

Dyna SNMP software can be updated by downloading the new software
version from a TFTP-server to the inactive software bank of Dyna
SNMP. The configuration data is kept safe during the download.
The following instructions presume that you have a TFTP-Server running
with IP address 172.21.13.19 and it has dynasnmpa3.zbin file including
Dyna SNMP.
Updating Dyna SNMP
1.
Open telnet or hyperterminal connection to Dyna SNMP you want

to update
2.
Log in to superuser mode.
3.
The Active bank can be identified by command show software.
See the example below:

CLs> sh so
Bank A software id:

10:34:07
S21720.02 - 00 - 29 / 11.04.2008
Bank B software id:
<not operational>
Active bank:
Bank A.
Boot software id:

08.10.2001 15:25:39
S66342.01 - A1 - 10 /
CLs>
4.
Use the command download:
Syntax: download <ip_address> <file_full_path_name>

<ip_address> is the IP-address your TFTP-server.
<file_full_path_name> is the name of Dyna SNMP unit's software
package.
Example about using the command download:
CLs> do 172.21.13.19 dynasnmp_a3.zbin
Received blocks:
896
Transfer completed.
CLs>
When the download starts properly the received blocks value should
start to increase immediately after typing the command. If the value
remains 0 longer than a few seconds it's very probable that the
download will fail.
DN70553464
Issue 2-0
79 (126)
Dyna SNMP
The download has been successfully completed when received blocks

value reaches 896.
5.
The following is an example of a successful download.
CLs> sh so
Bank A software id:
11.04.2008 10:34:07
S21720.02 - 00 - 29 /
Bank B software id:

11.12.2008 10:34:07
S21720.02 A3 - 29 /
Active bank:
Bank A.
Boot software id:

08.10.2001 15:25:39
S66342.01 - A1 - 10 /
CLs>
6.
Before you can start to use new software you need to change the
bank that contains the new active software. This is done by using
the command 'switch'. After that use the command 'reboot' to
reboot the adapter. The changes in the new software will be taken
into use only after a reboot.
7.
The following is an example of a successful reboot.
CLs> sh so
Bank A software id:
11.04.2008 10:34:07
S21720.02 - 00 - 29 /
Bank B software id:

11.12.2008 10:34:07
S21720.02 A3 - 29 /
Active bank:
Bank B.
Boot software id:

11.12.2008 10:34:07
S21720.02 A3 - 29 /
CLs>
8.
The new software should also be loaded to Bank A. In order to do

this, repeat Steps 1-7. If there is any corruption in Bank B, the
software unit can start-up from Bank A with the new software
B Tips for help - known issues

B.1 Too fast input through LMP
Too fast input through Local Management Port can terminate a CLI
session. After CLI timeout CLI functionality can be continued.
80 (126)
DN70553464
Issue 2-0
B.2 Setting prompt does not propagate to SNMP interface
Dyna SNMP interface uses prompt as the station value. If the prompt is
changed the change does not propagate to the SNMP interface until the
card is rebooted.
B.3 Node Manager- or TELNET connection hang
The node manager and the telnet CLI connections may terminate under
some exceptional network conditions. Dyna SNMP unit must be
rebooted in order to recover from this situation.
In this case it is possible to reboot the card remotely by setting the
sysName.0 SNMP-variable first to value "18-007071" (without the double
quotes) and then to "03072001".
This does not change the real value of sysName.0.
With HP-OV NNM supplied command line tools the syntax of the
commands is (all on one line without single quotes):
'snmpset -v 1 -c <rw-community> -r 0 -t 100 <IP-address of the DCN-A>
sysName.0 octetstring 18-007071'
and
'snmpset -v 1 -c <rw-community> -r 0 -t 100 <IP-address of the DCN-A>
sysName.0 octetstring 03072001'
where <rw-community> is the read/write community string, <IP-address
of the DCN-A> is the IP-address of the hang Dyna SNMP unit.
B.4 Can not delete nodes
In some cases it is not possible to delete all nodes from the Dyna SNMP
unit by simply using NE-address. The solution is to add the Q1-port
information to delete command, e.g. del q1e 5 ,1 deletes node 5 that is
located behind port 1.
If this does not help, you can try to give a command: show software.
After this, try to delete the q1elements again.
If this does not help, then you need to reboot Dyna SNMP unit and then
delete the nodes.
B.5 Loss of Connection to Supervision Bus alarms may start to appear in
very rapid sequence with no known reason
It's possible that in some situations loss of connection to supervision bus

or loss of connection to node alarms start to appear in very rapid
sequence and with no imminent reason. Recovery operations are:
DN70553464
Issue 2-0
1.
Reboot the Dyna SNMP by CLI command
2.
If the problem persists, then change the polling parameters.
81 (126)
Dyna SNMP
Appendix C: Dyna SNMP applications

1. Dyna SNMP in fixed transmission networks
The DYNA SNMP-A is used in fixed transmission networks consisting of

Nokia Siemens Networks Q1 managed elements. The DYNA SNMP-A
collects fault management information from the network elements via the
V.11 buses and converts this information into SNMP format, which is
then forwarded via TCP/IP to the management station platform.
1.1 Dyna SNMP located with PC
The Dyna SNMP-A collects fault management information from the

Networks Elements via the V.11 buses. The V.11 bus is extended from
Site A to Site B by using data bits reserved for management traffic with
the optical frame of the DF2-8.
Figure 24.
Dyna SNMP located with PC
1.2 Dyna SNMP located at an equipment site
The Dyna SNMP-A collects Fault management information from the

network elements via the V.11 buses. The V.11 bus is extended from
Site A to Site B by using data bits reserved for management traffic within
the optical frame of the DF2-8.
82 (126)
DN70553464
Issue 2-0
Figure 25.
Dyna SNMP A located at the equipment site
The DYNA SNMP-A is located at the equipment site and the connection
to the PC is via the Customers corporate LAN/WAN or leased IP
network.
1.3 DNT2M used for transportation of TCP/IP Traffic
The options for transporting the SNMP traps from the remote equipment
site are wide and varied. In this case the DNT2M-G with Ethernet
interface is used.
DN70553464
Issue 2-0
83 (126)
Dyna SNMP
Figure 26.
DNT2M used for transportation of TCP/IP Traffic
The transmission link between PC and Site A is in this case achieved

using the DNT2M-G. The transmission link being G.703/704 offers the
Users multiple options when planning the SNMP network including:
PDH Transmission
SDH Transmission
Leased Line
1.4 Nokia Siemens Networks Transmission Equipment used for

transportation of V.11 Q1 Traffic
In cases where the DYNA SNMP-A adapter is located with PC, the V.11
buses must be transported to each site. In this case the V.11 bus is
transported by using a traffic channel of a V.11 Data Interface Unit.
Suitable Data Interface units for the transmission of V.11 buses include:
TU21122.5 V.11 48k..64K 10 Channel
TU21122.6 V.11 48k..64K 5 Channel
TU21128 X.21 300.. 19.2K 6 Channel
The above Data Interface units can also be used in conjunction with
other Nokia Siemens Networks multiplexers (DM2 and DB2) therefore
these multiplexers can also be considered when designing the SNMP
network.
84 (126)
DN70553464
Issue 2-0
Figure 27.
Nokia Siemens Networks Transmission Equipment used for

transportation of V.11 Q1 Traffic
The DN2 is a 40 x 2Mbit/s Port cross connect multiplexer which has the
ability to cross connect at the 8Kbit/s level. Primarily designed for the
cross connections of traffic channels, the DN2 can also be a useful aid
for the transportation of the management traffic. By using digital
summing cross connections (C-Branching) the DN2 is able to connect
the V.11 bus from an incoming direction to 2-4 other 2Mbit/s ports. Using
this feature a single V.11 bus can be branched to serve multiple sites.
2. Calculating capacity for the Dyna SNMP
When calculating capacity for the DYNA SNMP-A the planner should
always bear in mind that A single Dyna SNMP can support 126
Functional Entities (FE).
Each of Nokia Siemens Networks Q1 managed equipment contains a
Network Element (NE) and one or more FE's.
The following equipment's all contain one NE and one FE:
DN70553464
Issue 2-0
DNT128,
DNT1M,
DNT2M,
ACL2,
DM2,
DM8,
85 (126)
Dyna SNMP
DM34,
DM140,
DF2-8,
DF23,
DF140
The following equipment all contains one NE but multiple FE's:
ACM2 Normally one FE but when used with the Line Testing Unit
contains two FE's.
Supervisory Substation Each input/output is a single FE

therefore the maximum is 32 FE's.
3. Management buses in the management network
The management bus is a four-wire cable; two wires form the

transmitting channel for the master station (receiving channel for slave
stations) while the other pair acts as a receiving channel for the master
station (transmitting channel for slave stations). This management bus
arrangement only applies within a single equipment station.
The management bus may be extended to include several equipment
stations and on the same service bus, several pieces of equipment at
different stations may be connected. In this case, the management bus
need not necessarily go in 4-wire form, but it can be linked from station
to station using the following methods:
Use of leased-line modems
Overheads within the microwave radio frame
Overheads within timeslot 0 (bits 5,6,7 and 8) of Nokia Siemens

Networks primary rate equipment
Overheads within the frame of Nokia Siemens Networks PDH

equipment
Overheads with the frame of Nokia Siemens Networks optical line

equipment (DF2-8, DF34, DF140)
Overheads within an SDH frame
Use of traffic channels
4. Planning the management network
This chapter introduces the general aspects when planning the network
where the Dyna SNMP is implemented. It covers the following topics:
86 (126)
Planning the network element sites
Management bus configuration
DN70553464
Issue 2-0
Determination of address settings for NE's
Branching Units to assist the DYNA SNMP design
Modems as a transmission medium
Management bus cabling
Things to consider when designing a network
4.1 Planning the network element sites
The installation planning of the management network (remote equipment

sites) with network elements is based on the system plan. It is assumed
that the system plan provides the following things for each site:
List of transmission equipment (NE's) to be supervised, measured

or controlled
List of external objects to be supervised or controlled
List of Supervisory Substations for external alarms
Scheme of transmission management network
The purpose of the remote site planning is to determine the following

things for each site:
Various settings, manually or by Service Terminal / Node Manager
Bus configuration settings, manually or by Service Terminal / Node

Manager
Required branching units
Required modems
Required cabling and connectors
The following chapters give information to achieve the above

requirements.
4.2 Management bus configuration
The determination of the management bus configuration is made in

order to create a reasonable bus structure. The goal is to minimize the
need of additional components like modems and branching units.
The reliability and the performance of a transmission management
network must be taken into consideration also.
The first step is to find out what are the available data channels for the
transmission management network provided by existing transmission
equipment. Those channels are based on direct sampling in the free bits
of available frame structures and they are accessible via the service
interfaces. In the NE's there are two kinds of serial interfaces: service
interfaces (MI) and data interfaces (DI). The service interface is for
DN70553464
Issue 2-0
87 (126)
Dyna SNMP
connecting the equipment to a management bus. The data interface can

be used for extending a management bus.
The next step is to select the data channels for the management buses
and to determine the access points of the selected channels. The
following paragraphs pay attention to details, which must be taken into
consideration before determining how service interface points of the
equipment are allocated to management buses.
The number of different addresses on a management bus sets a limit to
the number of service interfaces, which can be connected to the same
bus. The number of management buses must be determined so that
every NE can be connected to a management bus with a unique
address.
If pieces of transmission equipment cannot provide the required number
of data channels for the management buses, additional components are
needed. A compromise between costs and reliability may be necessary
to get a reasonable bus structure.
The Dyna SNMP supports 126 FE's which can be either all on a single
bus or split between the four available buses.
4.3 Determination of address settings for NE's
All Network Elements (NE's) connected to the transmission management

system must be physically identified. This is done by means of address
settings. The settings by the Service Terminal or Node Manager for each
NE are described in the Operating Handbook for the equipment
concerned. Only the main principles are given here.
On the same bus there can be 1...126 addresses for the equipment and
each of them can be used only once. When the NMS/10 MF is used the
same addresses are allowed to be on different buses. It should be noted
that all addresses under a DYNA SNMP-A should be unique and can not
be replicated on the other buses. In a typical case one NE reserves one
address.
The equipment addresses should ideally start from the number 1 and be
continuous without breaks if possible. This will help with the speed of
connection from Node Manager applications, as they typically will search
for equipment in numerical order.
4.4 Branching Units to assist the DYNA SNMP Design
The Smart Branching Unit (21743.01) can be used to branch the V.11
bus into multiple directions in cases where the equipment being used
does not support this facility.
The Smart Branching Unit has the ability to split the V.11 bus into 12 x
V.11 data streams. In addition to this it also has the ability to branch to 2
x V.28 data streams which can be used for transmission via modems.
88 (126)
DN70553464
Issue 2-0
The Smart Branching Unit can be installed in Nokia Siemens Networks

DynaNet Subracks. For further information, see the Operating Manual
(C33448.20).
Figure 28.
Branching Units to assist the DYNA SNMP Design
4.5 Modems as a transmission medium
If existing data channel sections and local cabling cannot provide the
required management bus structures completely, missing parts may be
implemented by modem sections. A modem section consists of two
modems with four-wire connection between them. Modems are required
to have the following minimum characteristics: duplex, asynchronous
data at 600 bit/s and V.24/V.28 terminal interface.
DN70553464
Issue 2-0
89 (126)
Dyna SNMP
Figure 29.
Modems as a Transmission Medium
4.6 Management bus cabling
There are two variants of the Q1 in use within Nokia Siemens Networks
Equipment, these are "Classic or TMS4 Q1" and the newer "Nokia Q1".
The newer "Nokia Q1" protocol supports additional functionality and
allows features such as software download remotely.
With equipment's supporting the "Classic Q1" Service interfaces (MI) are
used to connect the processor to the management (service) bus by
means of a serial interface.
The service interface can be connected to the data channel via the data
hybrid by giving the data hybrid activation command. The service
interfaces (MI) of the NE's are connected in parallel.
Note
The maximum number of MIs to be connected in parallel is 32.
4.6.1 Connection to NE's (Classic Q1 equipment's e.g. DM2, ACM2,

DNT2M, DN2 and DF140)
The following principles should be applied when making management

bus connections.
90 (126)
DN70553464
Issue 2-0
DYNA SNMP-A (Bus 1) NE1 NE2 NE3 NE32

ID1A (In) MOA MOA MOA
ID1B (In) MOB MOB MOB
OD1A (Out) MIA MIA MIA
OD1B (Out) MIB MIB MIB
If the management bus is to be extended via the overhead in NE3 then
the connection should be made as follows.
DYNA SNMP-A (Bus 1) NE1 NE2 NE3 (Data Hybrid On)
ID1A (In) MOA MOA MOA
ID1B (In) MOB MOB MOB
OD1A (Out) MIA MIA MIA
OD1B (Out) MIB MIB MIB
4.7 Things to consider when designing a Q1 SNMP Network
DN70553464
Issue 2-0
Decide whether protected or un-protected buses are required. If

protected buses are essential the SCNA 4 is the only suitable
option. The Dyna SNMP when installed at the equipment site
removes the need for protecting the bus.
When designing the Q1 bus structure, which involves multiple sites

on the same bus, first consider how the bus is going to be
transported in and out of the site. Once this has been determined it
is generally relatively simple to add the additional network
elements within the site to the bus.
The maximum number of network elements that can be connected

locally via the "M" interface is 32. This number can be increased if
a Smart Branching Unit (21743.01) is used.
Minimize the need of additional devices / components such as

modems and protocol converters.
The slowest data channel section determines the maximum speed

for the bus.
Minimize asynchronous sampling channel sections in series;

distortion.
The more network elements (addresses) connected to one bus,

the longer the time between two successive pollings of one
address.
Delays do not usually cause any problems in a service network,

which is configured using digital transmission equipment.
However, if V.22 modems are used, the delays that may be
caused by these must be taken into account.
91 (126)
Dyna SNMP
92 (126)
The Smart Branching Unit (21743.01) and TMS-Adaptor

(21701.01) can be used to simplify complex Q1 bus solutions.
Do not forget to allow for the connectors and cabling when putting
together parts lists.
DN70553464
Issue 2-0
Appendix D: Q1 interface signal names
Appendix D: Q1 interface signal names

The following table presents the correspondence between different Q1
interface signal names.
Table 11.
Q1 interface signal names
Direction
General -
DI port of Dyna
SNMP or PDH -Port of Nokia Q1 NE
NE
Tx
DOA
OUT
Tx+
DOB
OUT+
IN to the element Rx-
DIA
IN-
Rx+
DIB
IN+
OUT of the
element
The DI port is the bus master port and the starting point of a
management bus, and the MI port is a slave port. The port in Nokia
Siemens Networks Q1 elements can be considered to be of type DI
although the element itself does not act as a bus master (it does not
poll).
When a PDH network is being built, the MOx signals of all elements are
connected in parallel to form a bus, and go to the DIx signals of the one
and only bus master. Similarly, the MIx signals are connected in parallel
and go to the DOx signals of the master. Signals of a DI port must never
be connected in parallel with another DI port.
In case the Nokia Siemens Networks Q1 elements have two ports, the
OUTx signals go to the INx signals of the next element and vice versa to
form a chain. The bus master is connected to the either end of the chain
with DOx going to INx of the first element in the chain and DIx going to
OUTx.
Caution
Nokia Siemens Networks Q1 elements should always be chained.
Connecting any DI port signals in parallel may inhibit all traffic. In
practice this means that only point-to-point cables can be used with
these elements. If a Nokia Siemens Networks Q1 element does not have
a second port, it must be at the end of the chain. Branching the cable is
not recommended. PDH elements and Nokia Siemens Networks Q1
elements must not be mixed on a same bus. Doing so may inhibit PDH
elements from answering to the bus master.
DN70553464
Issue 2-0
93 (126)
Dyna SNMP
For further information, refer to the user documentation of the network

element in question.
94 (126)
DN70553464
Issue 2-0
Appendix E: MIB
Appendix E: MIB
1 MIB description
1.1 MIB overview
Dyna SNMP MIB is based on two modules:
-mib-2
enterprise specific DynaSNMPMIB.
1.2 Support for mib-2
Dyna SNMP supports the following branches from the RFC1213 mib-2
module:
system
interface
ip
icmp
udp
snmp.
The first two branches system and interface are important from the Dyna
SNMP management point of view. The supported mib variables are
given in details in the following tables.
1.2.1 System
Table 12.
Support for system-branch
Label
OID
Access
Supported
sysDescr
.1.3.6.1.2.1.1.1
Yes
sysObjectID
.1.3.6.1.2.1.1.2
Yes
sysUpTime
.1.3.6.1.2.1.1.3
Yes
sysContact
.1.3.6.1.2.1.1.4
R/W
Yes
sysName
.1.3.6.1.2.1.1.5
R/W
Yes
sysLocation
.1.3.6.1.2.1.1.6
R/W
Yes
DN70553464
Issue 2-0
Default Value
1.3.6.1.4.1.28458.7.2.1.3
95 (126)
Dyna SNMP
Label
OID
Access
Supported
sysServices
.1.3.6.1.2.1.1.7
Yes
sysORLastChange
.1.3.6.1.2.1.1.8
No
sysORTable
.1.3.6.1.2.1.1.9
No
Default Value
1.2.2 Interface
Table 13.
Support for interface-branch
Label
OID
Access
Support
ifNumber
.1.3.6.1.2.1.2.1
Yes
ifTable.ifEntry
.1.3.6.1.2.1.2.2.1
Yes
Notes
See Table 14.
1.2.3 Interface table
Q1 managed elements added (with add q1e command) under Dyna

SNMP control are shown here in addition to the standard interfaces.
Note 1
The value returned is always zero for the interfaces representing Q1
managed elements.
Note 2
Contains the bus-number (1 byte), Q1-address (2 bytes) and the number
of FEs (1 byte) for the interfaces representing Q1 managed elements.
Note 3
Read-only for the interfaces representing Q1 managed elements.
96 (126)
DN70553464
Issue 2-0
Appendix E: MIB
Note 4
Indicates whether the Q1 managed element represented by the interface
has current alarms or not.
Table 14.
Support for interface.ifTable.ifEntry branch
Label
OID
Access
Support
Notes
ifIndex
.1.3.6.1.2.1.2.2.1.1
Yes
ifDescr
.1.3.6.1.2.1.2.2.1.2
Yes
ifType
.1.3.6.1.2.1.2.2.1.3
Yes
ifMtu
.1.3.6.1.2.1.2.2.1.4
Yes
see note 1
ifSpeed
.1.3.6.1.2.1.2.2.1.5
Yes
see note 1
ifPhysAddress
.1.3.6.1.2.1.2.2.1.6
Yes
ifAdminStatus
.1.3.6.1.2.1.2.2.1.7
Yes
ifOperStatus
.1.3.6.1.2.1.2.2.1.8
Yes
ifLastChange
.1.3.6.1.2.1.2.2.1.9
Yes
see note 1
ifInOctets
.1.3.6.1.2.1.2.2.1.10
Yes
see note 1
ifInUcastPkts
.1.3.6.1.2.1.2.2.1.11
Yes
see note 1
ifInNUcastPkts
.1.3.6.1.2.1.2.2.1.12
Yes
see note 1
ifInDiscards
.1.3.6.1.2.1.2.2.1.13
Yes
see note 1
ifInErrors
.1.3.6.1.2.1.2.2.1.14
Yes
see note 1
ifInUnknownProtos
.1.3.6.1.2.1.2.2.1.15
Yes
see note 1
ifOutOctets
.1.3.6.1.2.1.2.2.1.16
Yes
see note 1
ifOutUcastPkts
.1.3.6.1.2.1.2.2.1.17
Yes
see note 1
ifOutNUcastPkts
.1.3.6.1.2.1.2.2.1.18
Yes
see note 1
ifOutDiscards
.1.3.6.1.2.1.2.2.1.19
Yes
see note 1
ifOutErrors
.1.3.6.1.2.1.2.2.1.20
Yes
see note 1
ifOutQLen
.1.3.6.1.2.1.2.2.1.21
Yes
see note 1
DN70553464
Issue 2-0
97 (126)
Dyna SNMP
Label
OID
Access
Support
ifSpecific
.1.3.6.1.2.1.2.2.1.22
Yes
Notes
1.3 TRAP Scenarios
Supported events are described in this chapter.

1.3.1 dynaSNMPNodeAdded
oid: .1.3.6.1.4.1.28458.7.2.1.3.2.2.0.1
fields:
Table 15.
Subfields
Subfield
Description
dynaSNMPTrapCnt
The value of this counter (integer) is the number of traps sent including the
current trap. The counter is incremented every time before a
dynaSNMPNodeAdded, dynaSNMPNodeDeleted, dynaSNMPNodeFM or
dynaSNMPNodeFMSync trap is generated. The value is initialised to 0
when the agent starts.
dynaSNMPName
This field gives the name (string) assigned to the added node. The agent
makes no guarantee of the uniqueness of this name.
dynaSNMPType
This field gives the type (string) of the added node and optionally the node
version (string).
dynaSNMPFlags
This field (integer) gives the nodes specific information status of the added
node. This subfield can be interpreted as the 32-bit queue
dynaSNMPNodeFlags defined in dynaSNMPMIB.
dynaSNMPStatus
This field follows the syntax of RowStatus as defined in RFC 2579.

Supported values are 'active' and 'notReady'.
dynaSNMPBus
This subfield identifies the Q1 bus (integer) to which the added element is
attached to.
dynaSNMPAddress
This subfield identifies the Q1 address (integer) of the added element.
dynaSNMPGeneration
This subfield identifies the generation info for the added node. Possible
values are:
- 'D/ND' for D/ND (tms4-q1) nodes,
- 'E' for E (Nokia Siemens Networks Q1) nodes and
- '-' for not Q1 managed nodes.
dynaSNMPFEName
This subfield gives the FE name (string) from the node for D/ND generation
nodes.
98 (126)
DN70553464
Issue 2-0
Appendix E: MIB
Subfield
Description
dynaSNMPStation
This subfield gives the name (string) of station where the node added is
located
Description:
Sent when a new node is added with add q1e command.
1.3.2 dynaSNMPNodeDeleted
oid: .1.3.6.1.4.1.28458.7.2.1.3.2.2.0.2
fields:
Table 16.
Subfields
Subfield
Description
dynaSNMPTrapCnt
dynaSNMPNodeFMSync trap is generated. The value is initialised to 0 when
the agent starts.
dynaSNMPIndex
This subfield gives the unique value (integer) identifying the node entry in the
dynaSNMPNodeTable deleted. This value will be unique across all-time
instances of the agent.
Description:
Sent when a node is deleted with delete q1e command.
1.3.3 dynaSNMPNodeFM
oid: .1.3.6.1.4.1.28458.7.2.1.3.2.2.0.4
fields:
Table 17.
Subfields
Subfield
Description
dynaSNMPTrapCnt
dynaSNMPNodeFMSync trap is generated. The value is initialised to 0 when
DN70553464
Issue 2-0
99 (126)
Dyna SNMP
Subfield
Description
the agent starts.
dynaSNMPFlags
This field (integer) gives the nodes specific information status of the added
node. This subfield can be interpreted as the 32-bit queue
dynaSNMPNodeFlags defined in dynaSNMPMIB. This trap is sent whenever
the FM-bit in dynaSNMPNodeFlags is set or cleared.
Description:
Sent when node polling is enabled or disabled. At the same time the FMbit in dynaSNMPNodeFlags is set or cleared.
1.3.4 dynaSNMPAlarmRaised
1.3.4 oid: .1.3.6.1.4.1.28458.7.2.1.3.3 3 .0.1

fields:
Table 18.
Subfields
Subfield
Description
dynaSNMPAlarmInd
Index (integer) of the event given by Dyna SNMP automatically.
dynaSNMPNodeInd
Index (integer) of the node raising the alarm. Node index is originally given
by the Dyna SNMP controlling the PDH node. The corresponding node
index with node details can be found from the "PDH Nodes List" -window.
dynaSNMPTrapCnt
dynaSNMPAlarmRaised or dynaSNMPAlarmCleared trap is generated. The
value is initialised to 0 when the agent starts.
dynaSNMPSeverity
Severity of the alarm raised. Possible values are 'critical', 'major', 'minor',
'warning' or 'unknown'.
dynaSNMPTime
Time of the alarm raised. The time is given by Dyna SNMP when it receives
the alarm cleared event from the Q1 node. The format of the time is given in
the DateAndTime textual convention defined in RFC 2579.
dynaSNMPText
This subfield gives the human readable description of the alarm raised.
dynaSNMPNbr
This field gives the Q1 fault code (integer) of the alarm. Current the subfield
carries the same information as FC-subfield.
dynaSNMPFE
This field gives the number (integer) of the Q1 functional entity

corresponding to the alarm.
dynaSNMPSB
This field gives the number (integer) of the Q1 supervision block

corresponding to the alarm.
100 (126)
DN70553464
Issue 2-0
Appendix E: MIB
Subfield
Description
dynaSNMPFC
This field gives the Q1 fault code (integer) of the alarm. Current the subfield
carries the same information as Nbr-subfield.
dynaSNMPFEStatus
This field gives the status (integer) of the functional entity given in FEsubfield. This subfield can be interpreted as a 32-bit queue defined in Q1
protocol.
dynaSNMPSBName
This field gives the identification (text string) of the SB defined in SBsubfield.
dynaSNMPSevMask
This field gives the severity (integer) mask of the alarm. This subfield can
be interpreted as a 32-bit mask defined in Q1 protocol.
Description
Sent when agent detects a new alarm.
1.3.5 dynaSNMPAlarmCleared
oid: .1.3.6.1.4.1.28458.7.2.1.3.3 3 .0.2
Table 19.
Subfields
Subfield
Description
dynaSNMPAlarmInd
Index (integer) of the event given by DynaSNMP automatically.
dynaSNMPNodeInd
Index (integer) of the node clearing the alarm. Node index is originally given
by the DynaSNMP controlling the PDH node. The corresponding node
index with node details can be found from the "PDH Nodes List" -window.
dynaSNMPTrapCnt
dynaSNMPAlarmRaised or dynaSNMPAlarmCleared trap is generated. The
value is initialised to 0 when the agent starts.
dynaSNMPSeverity
Severity of the alarm to be cleared. Possible values are 'critical', 'major',

'minor', 'warning' or 'unknown'.
dynaSNMPTime
Time of the alarm cleared. The time is given by dynaSNMP when it receives
the alarm cleared event from the Q1 node. The format of the time is given in
the DateAndTime textual convention defined in RFC 2579.
dynaSNMPText
This subfield gives the human readable description of the original alarm
cleared by this event.
dynaSNMPNbr
This field gives the Q1 fault code (integer) of the alarm to be cleared.
Current the subfield carries the same information as FC-subfield.
dynaSNMPFE
This field gives the number (integer) of the Q1 functional entity

corresponding to the alarm to be cleared.
DN70553464
Issue 2-0
101 (126)
Dyna SNMP
Subfield
Description
dynaSNMPSB
This field gives the number (integer) of the Q1 supervision block

corresponding to the alarm to be cleared.
dynaSNMPFC
This field gives the Q1 fault code (integer) of the alarm to be cleared.
Current the subfield carries the same information as Nbr-subfield.
dynaSNMPFEStatus
This field gives the status (integer) of the functional entity given in FEsubfield. This subfield can be interpreted as a 32-bit queue defined in Q1
protocol.
dynaSNMPSBName
This field gives the identification (text string) of the SB defined in SBsubfield.
dynaSNMPSevMask
This field gives the severity (integer) mask of the alarm to be cleared. This
subfield can be interpreted as a 32-bit mask defined in Q1 protocol.
Description:
Sent when agents detects alarm cleared.
Note that the dynaSNMPAlarmTime value is the time of the cleared

event. the dynaSNMPAlarmSeverity has the value indicating the severity
of the original alarm (the one being cleared)
1.4 DynaSNMP MIB
The mib definition is given below:

-1
2
3
4
5
6
7
-- 4567890123456789012345678901234567890123456789012345678901234567890123456789
-- Keep the lines shorter than 80 chars
--DYNASNMPMIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
enterprises, Integer32
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, DisplayString, RowStatus, DateAndTime
FROM SNMPv2-TC; -- RFC 2579
dynaSNMPMIB MODULE-IDENTITY
LAST-UPDATED "0805300000Z"
ORGANIZATION "Nokia Siemens Networks"
CONTACT-INFO "Customer Services"
DESCRIPTION
"This document defines the MIB used for Q1 DCN Agent, DynaSNMP Agent
for fault management for Q1 equipment. MIB version is 101."
::= { dynasnmp 3 }
-- oid value for dynaSNMPMIB .1.3.6.1.4.1.28458.7.2.1.3
--
102 (126)
DN70553464
Issue 2-0
Appendix E: MIB
-- groups for this mib

-nsn
OBJECT
accessProducts
acc
OBJECT
dynasnmp
OBJECT
IDENTIFIER ::= { enterprises 28458 }

OBJECT IDENTIFIER ::= { nsn 7 }
IDENTIFIER ::= { accessProducts 2 }
IDENTIFIER ::= { acc 1 }
dynaSNMPGeneral
dynaSNMPNodes OBJECT
dynaSNMPFM
dynaSNMPPM
dynaSNMPAgent OBJECT
OBJECT IDENTIFIER ::= { dynaSNMPMIB 1 }

IDENTIFIER ::= { dynaSNMPMIB 2 }
IDENTIFIER ::= { dynaSNMPMIB 5 }
-- groups 6 to 8 and 10 to 15 reserved for future common use

dynaSNMPConformance OBJECT IDENTIFIER ::= { dynaSNMPMIB 9 }
--============================================================
--============================================================
-- Textual conventions
--============================================================
--============================================================
DynaSNMPMIBVersion ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-2"
STATUS current
DESCRIPTION
"Specifies the version number of the sub agent MIB.
The format is XXYY where the XX specifies the major
and YY the minor part of the version.
Major should be incremented when there is an incompatible
(not backwards compatible) change to this interface.
Minor should be incremented when there is any change to
this interface.
"
SYNTAX INTEGER (0..9999)
DynaSNMPNodeIndex
::= TEXTUAL-CONVENTION
DISPLAY-HINT "8x"
STATUS current
DESCRIPTION
"This value is unique within a given subagent.
Together with the subagent identity it uniquely identifies
nodes in the system.
"
DynaSNMPFlags ::= TEXTUAL-CONVENTION
DISPLAY-HINT "x"
STATUS current
DESCRIPTION
"Used together with DynaSNMPFlagsMask
All unused bits when read are 0.
Writes to bits that are unused or which have no corresponding
bit set in dynaSNMPFlagsMask are ignored.
Description of the object using this syntax must define
the bits.
"
DN70553464
Issue 2-0
103 (126)
Dyna SNMP
DynaSNMPFlagsMask
DISPLAY-HINT "x"
STATUS current
DESCRIPTION
"All valid flags have value 1 and all unused bits value 0.
See DynaSNMPFlags."
DynaSNMPAlarmIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS
current
DESCRIPTION
"This value uniquely identifies a fault change within a given
subagent alarm table instance. Initialized to 0 at sub agent
startup"
SYNTAX
INTEGER (0..2147483647)
DynaSNMPAlarmSeverity
STATUS current
DESCRIPTION
"Defines the alarm classification."
SYNTAX
INTEGER {
unknown(0),
critical(1),
major(2),
minor(3),
warning(4),
cleared(5)
}
DynaSNMPAlarmNbr
STATUS current
DESCRIPTION
"Alarm number for alarm
NOTE: Different types of agents may have a different
set of values for objects of this type.
NOTE: The numeric values of this type are NOT nesessary
as defined in X.733. The agent is allowed to use
suitable value from NE it manages without conversions
or mappings.
NOTE: This value is the Q1 FaultCode
"
DynaSNMPSWVersion ::= TEXTUAL-CONVENTION
DISPLAY-HINT "40a"
STATUS current
DESCRIPTION
"Identifies a software version."
SYNTAX OCTET STRING (SIZE (0..40))
-- END of textual conventions
--============================================================
--============================================================
-- dynaSNMPGeneral group
--============================================================
104 (126)
DN70553464
Issue 2-0
Appendix E: MIB
--============================================================
dynaSNMPTemplateVersion OBJECT-TYPE
SYNTAX
DynaSNMPMIBVersion
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"Version of the template MIB module.
This version is 1.01"
::= { dynaSNMPGeneral 1 }
dynaSNMPMIBVersion OBJECT-TYPE
SYNTAX
DynaSNMPMIBVersion
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"Version of the MIB module.
This version is 1.00"
::= { dynaSNMPGeneral 2 }
-- oids 3 to 15 reserved for future common use
-- END of dynaSNMPGeneral Group

--============================================================
--============================================================
-- dynaSNMPNodes group
--============================================================
--============================================================
dynaSNMPNodeInv
OBJECT IDENTIFIER ::= { dynaSNMPNodes 1 }
dynaSNMPNodeEvents OBJECT IDENTIFIER ::= { dynaSNMPNodes 2 }
-- oids from 3 to 15 reserved for future common use
-- New groups may be added beginning from 16
---=================
-- dynaSNMPNodeInv group
--=================
-dynaSNMPNodeTrapCnt OBJECT-TYPE
SYNTAX
INTEGER (0..2147483647)
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"The value of this counter is the number of traps sent
including the current trap.
The counter is incremented every time before
a dynaSNMPNodeAdded, dynaSNMPNodeDeleted,
dynaSNMPNodeModified, dynaSNMPNodeFM,
dynaSNMPNodeFMSync, dynaSNMPNodePM,
dynaSNMPNodePMSync trap is generated.
May be used by the manager to detect lost traps.
The correct procedure to upload dynaSNMPNodeTable is:
1. read this value
2. read the dynaSNMPNodeTable
3. compare this value with the value read at step 1
if the value are the same the upload was successful
NOTE: value will be reset to zero when agent starts.
"
DN70553464
Issue 2-0
105 (126)
Dyna SNMP
::= { dynaSNMPNodeInv 1 }
dynaSNMPNodeTable
OBJECT-TYPE
SYNTAX
SEQUENCE OF DynaSNMPNodeEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION "A list of node entries.
dynaSNMPNodeTrapCnt keeps track of the changes made to this
table.
Write access to the column is defined in the agent specific mib
except for the FM and PM flags which always have to be
writeable, if they are supported.
NOTE:
If the value of dynaSNMPNodeAddress is equal to 65535 the
row represents a Q1 management bus.
The bus object on bus 254 acts as a summary of the
internal fault objects, thus representing the whole DynaSNMP
equipment.
The values of dynaSNMPNodeIndexes of these special rows
may vary from one agent installation to another.
The rows in the table represent the Q1 functional entities
not the actual nodes.
"
::= { dynaSNMPNodeInv 3 }
dynaSNMPNodeEntry OBJECT-TYPE
SYNTAX
DynaSNMPNodeEntry
MAX-ACCESS not-accessible
STATUS
current
DESCRIPTION
"A node entry containing details of a node."
INDEX
{ dynaSNMPNodeIndex }
::= { dynaSNMPNodeTable 1 }
DynaSNMPNodeEntry ::= SEQUENCE {
dynaSNMPNodeIndex
DynaSNMPNodeIndex,
dynaSNMPNodeName
DisplayString (SIZE
dynaSNMPNodeType
DisplayString (SIZE
dynaSNMPNodeFlags
DynaSNMPFlags,
dynaSNMPNodeFlagsMask
DynaSNMPFlagsMask,
dynaSNMPNodeStatus
RowStatus,
dynaSNMPNodeBus
Integer32,
dynaSNMPNodeAddress
Integer32,
dynaSNMPNodeGeneration
DisplayString (SIZE
dynaSNMPNodeFEName
DisplayString (SIZE
dynaSNMPNodeStation
DisplayString (SIZE
}
(0..40)),
(0..40)),
(0..4)),
(0..40)),
(0..40))
dynaSNMPNodeIndex OBJECT-TYPE
SYNTAX
DynaSNMPNodeIndex
106 (126)
DN70553464
Issue 2-0
Appendix E: MIB
MAX-ACCESS read-only
STATUS
current
DESCRIPTION
"An unique value to identify a node entry in the
dynaSNMPNodeTable.
This value will be unique across all-time instances of the
subagent
"
::= { dynaSNMPNodeEntry 1 }
dynaSNMPNodeName OBJECT-TYPE
SYNTAX
DisplayString (SIZE (0..40))
STATUS
current
DESCRIPTION
"The name assigned to the node. The agent makes no guarantee
of the uniqueness of this name.
"
dynaSNMPNodeType OBJECT-TYPE
SYNTAX
STATUS
current
DESCRIPTION
"The type of the node and optionally the node version.
"
dynaSNMPNodeFlags OBJECT-TYPE
SYNTAX
DynaSNMPFlags
STATUS
current
DESCRIPTION
"The bits defined here may not be used in any other purposes.
However the support for a any single bit is optional.
.... .... .... .... 0000 (0x00000000) Indicated that the node is added under
FM but polling is not enabled.
1... .... .... .... 0000 (0x80000000) Not supported
.1.. .... .... .... 0000 (0x40000000) Indicates that the node is added under
FM and polling is enabled.
..1. .... .... .... 0000 (0x20000000) not supported
...1 .... .... .... 0000 (0x10000000) Indicates that the node is available
for polling.
The other unused bits reserved for future use.
"
dynaSNMPNodeFlagsMask OBJECT-TYPE
SYNTAX
DynaSNMPFlagsMask
STATUS
current
DESCRIPTION
"Not supported."
dynaSNMPNodeStatus OBJECT-TYPE
SYNTAX
RowStatus
STATUS
current
DESCRIPTION
DN70553464
Issue 2-0
107 (126)
Dyna SNMP
"
active(1): which indicates that the the node is
available for use by the managed device;
notReady(3): which indicates that the node in the agent,
but is not available in the bus
DynaSNMP Agent doesn't support other values.
"
-- oids 8 to 15 reserved for future common use
dynaSNMPNodeBus OBJECT-TYPE
SYNTAX
Integer32
STATUS
current
DESCRIPTION
"The Q1 bus this NE is on.
"
dynaSNMPNodeAddress OBJECT-TYPE
SYNTAX
Integer32
STATUS
current
DESCRIPTION
"The Q1 address of this element
"
dynaSNMPNodeGeneration OBJECT-TYPE
SYNTAX
STATUS
current
DESCRIPTION
"The generation info for this node.
'ND' for ND (tms4-q1) nodes
'E' for E (nokia Q1) nodes.
'-' for not Q1 managed nodes.
"
dynaSNMPNodeFEName OBJECT-TYPE
SYNTAX
STATUS
current
DESCRIPTION
"The FE name from the node for ND generation
nodes. (4kH command)
"
dynaSNMPNodeStation OBJECT-TYPE
SYNTAX
STATUS
current
DESCRIPTION
"The station name.
"
---==============
-- dynaSNMPNodeEvents
--==============
--
108 (126)
DN70553464
Issue 2-0
Appendix E: MIB
dynaSNMPNodeDefs
OBJECT IDENTIFIER ::= { dynaSNMPNodeEvents 0 }
dynaSNMPNodeAdded
NOTIFICATION-TYPE
-- 1. add node
OBJECTS {
dynaSNMPNodeTrapCnt,
dynaSNMPNodeName,
dynaSNMPNodeType,
dynaSNMPNodeFlags,
dynaSNMPNodeStatus,
dynaSNMPNodeBus,
dynaSNMPNodeAddress,
dynaSNMPNodeGeneration,
dynaSNMPNodeFEName,
dynaSNMPNodeStation
}
STATUS current
DESCRIPTION
"Sent when a new row to the node table is added.
Instances of dynaSNMPNodeName, dynaSNMPNodeFlags,
dynaSNMPNodeType and
dynaSNMPNodeStatus correspond to the changed conceptual row.
"
::= { dynaSNMPNodeDefs 1 }
dynaSNMPNodeDeleted NOTIFICATION-TYPE
-- 2. delete node
OBJECTS {
dynaSNMPNodeIndex
}
STATUS current
DESCRIPTION
"Sent when the dynaSNMPNodeStatus is set to destroy and
the agent
has removed the node from configuration.
"
dynaSNMPNodeModified
NOTIFICATION-TYPE
-- 3. edit Node
OBJECTS {
dynaSNMPNodeName,
dynaSNMPNodeType,
dynaSNMPNodeFlags,
dynaSNMPNodeStatus,
dynaSNMPNodeBus,
dynaSNMPNodeAddress,
dynaSNMPNodeGeneration,
dynaSNMPNodeFEName,
dynaSNMPNodeStation
}
STATUS current
DESCRIPTION
"Sent when existing row is changed except when a FM, PM,
FMSYNC or PMSYNC flag updated.
Instances of dynaSNMPNodeName, dynaSNMPNodeFlags,
dynaSNMPNodeType and
dynaSNMPNodeStatus correspond to the changed row.
"
DN70553464
Issue 2-0
109 (126)
Dyna SNMP
dynaSNMPNodeFM
NOTIFICATION-TYPE
-- 4. connecting to node for FM
OBJECTS {
dynaSNMPNodeFlags
}
STATUS current
DESCRIPTION
"Sent when the FM-bit in dynaSNMPNodeFlags is set or cleared
"
dynaSNMPNodeFMSync NOTIFICATION-TYPE
-- 5. Fully synced with node for FM
OBJECTS {
dynaSNMPNodeFlags
}
STATUS current
DESCRIPTION
"Sent when the agent system has syncronized with the FM
information on the node. Trap is sent only when FMSYNC flag
is changed from 0 to 1, and not when changed from 1 to 0.
"
-- END of dynaSNMPNodeEvents group
--============================================================
-- dynaSNMPFM group
--============================================================
--- GROUPS:
--- current alarms
dynaSNMPCurAlarm
OBJECT IDENTIFIER ::= { dynaSNMPFM 1 }
--- alarm log, implementation optional, defined in separate document
dynaSNMPAlarmLog
--- events
dynaSNMPAlarmEvents
--==================================
-- dynaSNMPCurAlarm Group
--==================================
dynaSNMPAlarmTrapCnt
OBJECT-TYPE
SYNTAX
INTEGER (0..2147483647)
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"Incremented every time there is a change in current alarm
situation. The value of this counter is the number of traps
sent including the current trap. The counter is incremented
every time before a dynaSNMPAgentAlarmRaised or
dynaSNMPAgentAlarmCleared trap is generated.
The value is initialized to 0 when the sub-agent starts.
"
::= { dynaSNMPCurAlarm 1 }
110 (126)
DN70553464
Issue 2-0
Appendix E: MIB
dynaSNMPAlarmTable OBJECT-TYPE
SYNTAX
SEQUENCE OF DynaSNMPAlarmEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
"Table for all current alarms under this
subagent indexed with nodeindex and alarmIndex.
Note that the the alarms in dynaSNMPAlarmTable need not
to be in chronological order.
"
::= { dynaSNMPCurAlarm 2 }
dynaSNMPAlarmEntry OBJECT-TYPE
SYNTAX
DynaSNMPAlarmEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
"entry in current alarm table"
INDEX
{ dynaSNMPAlarmNodeIndex, dynaSNMPAlarmIndex }
::= { dynaSNMPAlarmTable 1 }
DynaSNMPAlarmEntry ::= SEQUENCE {
dynaSNMPAlarmNodeIndex
DynaSNMPNodeIndex,
dynaSNMPAlarmIndex
DynaSNMPAlarmIndex,
dynaSNMPAlarmSeverity
DynaSNMPAlarmSeverity,
dynaSNMPAlarmTime
DateAndTime,
dynaSNMPAlarmText
DisplayString,
dynaSNMPAlarmNbr
DynaSNMPAlarmNbr,
dynaSNMPAlarmFE
Integer32,
dynaSNMPAlarmSB
Integer32,
dynaSNMPAlarmFC
Integer32,
dynaSNMPAlarmFEStatus
Integer32,
dynaSNMPAlarmSBname
DisplayString,
dynaSNMPAlarmESevMask
Integer32
}
OBJECT-TYPE
SYNTAX
DynaSNMPNodeIndex
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "index to the node table"
::= { dynaSNMPAlarmEntry 1 }
dynaSNMPAlarmIndex
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
DN70553464
Issue 2-0
OBJECT-TYPE
DynaSNMPAlarmIndex
read-only
current
"A unique Id of this alarm. The
value of dynaSNMPAlarmTrapCnt when was detected by the
111 (126)
Dyna SNMP
agent system"
OBJECT-TYPE
SYNTAX
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "The severity classification"
dynaSNMPAlarmTime
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
DateAndTime
read-only
current
"Best guess when this event happened
For TMS4-Q1 equipment this is the time when
the agent detected the fault.
For NokiaQ1 equipments this is the time the
node reported
"
dynaSNMPAlarmText
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
DisplayString
read-only
current
"Human readable description of this alarm.
The user should be able to identify the
alarm from the information in the text.
The alarm text has following
format:
<alarm text>, FE <FE number> (<FE name>),
SB <SB number> (<SB name>)
where <alarm text> is the english alarm decription,
<FE number> is the funtional entity number,
<FE name> is the name of the functional entity
as configured in the configuration.
<SB number> is the supervision bloxk number,
<SB name> is the identification of the
supervision block as read from the equipment.
NOTE the <SB name> can be empty if the equipment
did not answer to SB query.
"
dynaSNMPAlarmNbr
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
DynaSNMPAlarmNbr
read-only
current
"Alarm number for this alarm.
The value is same as that of dynaSNMPAlarmFC
"
dynaSNMPAlarmFE
SYNTAX
MAX-ACCESS
STATUS
112 (126)
OBJECT-TYPE
Integer32
read-only
current
DN70553464
Issue 2-0
Appendix E: MIB
DESCRIPTION
"The Q1 functional entity.

"
dynaSNMPAlarmSB
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
Integer32
read-only
current
"The Q1 supervision block.
"
dynaSNMPAlarmFC
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
Integer32
read-only
current
"The Q1 fault code
"
OBJECT-TYPE
SYNTAX
Integer32
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "The functional entity status
"
dynaSNMPAlarmSBname
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
OBJECT-TYPE
DisplayString
read-only
current
"The identification of the alarming SB
"
OBJECT-TYPE
SYNTAX
Integer32
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "The Nokia Q1 alarm severity.
Not supported by 'ND/D' generation elements.
"
--==================================
-- dynaSNMPAlarmEvents Group
--==================================
dynaSNMPAlarmDefs
OBJECT IDENTIFIER ::= { dynaSNMPAlarmEvents 0 }
dynaSNMPAlarmRaised NOTIFICATION-TYPE
-- 10. Raise Alarm
OBJECTS {
dynaSNMPAlarmTrapCnt,
dynaSNMPAlarmSeverity,
dynaSNMPAlarmTime,
dynaSNMPAlarmText,
dynaSNMPAlarmNbr,
dynaSNMPAlarmFE,
DN70553464
Issue 2-0
113 (126)
Dyna SNMP
dynaSNMPAlarmSB,
dynaSNMPAlarmFC,
dynaSNMPAlarmFEStatus,
dynaSNMPAlarmSBname,
}
STATUS
current
DESCRIPTION "Sent when agent detects a new alarm.
The instance for the objects is the one used
with the corresponding conceptual row.
Agent may (and should) put more varbinds after these,
"
::= { dynaSNMPAlarmDefs 1 }
dynaSNMPAlarmCleared
NOTIFICATION-TYPE
-- 11. Clear Alarm
OBJECTS {
dynaSNMPAlarmTrapCnt,
dynaSNMPAlarmSeverity,
dynaSNMPAlarmTime,
dynaSNMPAlarmText,
dynaSNMPAlarmNbr,
dynaSNMPAlarmFE,
dynaSNMPAlarmSB,
dynaSNMPAlarmFC,
dynaSNMPAlarmFEStatus,
dynaSNMPAlarmSBname,
}
STATUS
current
DESCRIPTION "Sent when agents detects alarm cleared.
Note the corresponding alarm row is removed
from the dynaSNMPAlarmTable.
NOTE: the dynaSNMPAlarmTime value is the time of
the cleared event.
the dynaSNMPAlarmSeverity has the value indicating
the severity of the original alarm (the one
being cleared)
"
::= { dynaSNMPAlarmDefs 2 }
--oids from 3 to 15 reserved for future common use
-- END of dynaSNMPAlarmEvents group

--============================================================
--============================================================
-- dynaSNMPAgent group:
--============================================================
--============================================================
--- GROUPS:
--
114 (126)
DN70553464
Issue 2-0
Appendix E: MIB
-- current alarms, implementation optional

dynaSNMPAgentAlarm
OBJECT IDENTIFIER ::= { dynaSNMPAgent 1 }
--- events
dynaSNMPAgentEvents
dynaSNMPAgentGeneral
-- dynaSNMPAgent oids from 4 to 15 reserved for future common use

--==================================
-- dynaSNMPCurAlarm Group
--==================================
dynaSNMPAgentAlarmTrapCnt OBJECT-TYPE
SYNTAX
INTEGER (0..2147483647)
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"Incremented every time there is a change in the agent alarm
situation"
::= { dynaSNMPAgentAlarm 1 }
dynaSNMPAgentAlarmTable
OBJECT-TYPE
SYNTAX
SEQUENCE OF DynaSNMPAgentAlarmEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
"Table for all current subagent alarms
Note that the the alarms in dynaSNMPAgentAlarmTable need not
to be in chronological order.
"
::= { dynaSNMPAgentAlarm 2 }
dynaSNMPAgentAlarmEntry OBJECT-TYPE
SYNTAX
DynaSNMPAgentAlarmEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
"entry in current alarm table"
INDEX
{ dynaSNMPAgentAlarmIndex }
::= { dynaSNMPAgentAlarmTable 1 }
DynaSNMPAgentAlarmEntry ::= SEQUENCE {
dynaSNMPAgentAlarmIndex
DynaSNMPAlarmIndex,
dynaSNMPAgentAlarmSeverity
DynaSNMPAlarmSeverity,
dynaSNMPAgentAlarmTime
DateAndTime,
dynaSNMPAgentAlarmText
DisplayString,
dynaSNMPAgentAlarmNbr
DynaSNMPAlarmNbr
}
OBJECT-TYPE
SYNTAX
DynaSNMPAlarmIndex
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "A unique Id of this alarm. The
value of dynaSNMPAgentAlarmTrapCnt when
DN70553464
Issue 2-0
115 (126)
Dyna SNMP
detected by the
agent system"
::= { dynaSNMPAgentAlarmEntry 2 }
OBJECT-TYPE
SYNTAX
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "The severity classification"
OBJECT-TYPE
SYNTAX
DateAndTime
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "Best quess when this event happened"
OBJECT-TYPE
SYNTAX
DisplayString
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "Human readable description of this alarm
"
OBJECT-TYPE
SYNTAX
DynaSNMPAlarmNbr
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION "Alarm number for this alarm.
<XXX: describe how the values are formed>
"
--=================================
-- dynaSNMPAgentControl Group
--=================================
--- To be defined later
-- oids from 0-15 reserved for common use
---==================================
-- dynaSNMPAgentEvents Group
--==================================
dynaSNMPAgentEventDefs
OBJECT IDENTIFIER ::= { dynaSNMPAgentEvents 0 }
dynaSNMPAgentAlarmRaised
NOTIFICATION-TYPE
OBJECTS {
dynaSNMPAgentAlarmTrapCnt,
dynaSNMPAgentAlarmSeverity,
dynaSNMPAgentAlarmTime,
dynaSNMPAgentAlarmText,
}
116 (126)
-- 10. Raise Alarm
DN70553464
Issue 2-0
Appendix E: MIB
STATUS
current
DESCRIPTION "Sent when agent detects a new alarm.
"
::= { dynaSNMPAgentEventDefs 1 }
dynaSNMPAgentAlarmCleared NOTIFICATION-TYPE
-- 11. Clear Alarm
OBJECTS {
dynaSNMPAgentAlarmTrapCnt,
dynaSNMPAgentAlarmSeverity,
dynaSNMPAgentAlarmTime,
dynaSNMPAgentAlarmText,
}
STATUS
current
DESCRIPTION "Sent when agents detects alarm cleared.
Note the corresponding for alarm row is removed
from the dynaSNMPAgentAlarmTable.
NOTE: the dynaSNMPAgentAlarmTime value is the time of
the cleared event.
the dynaSNMPAgentAlarmSeverity has the
value indicating
the severity of the original alarm (the one
being cleared)
"
dynaSNMPAgentRdy
NOTIFICATION-TYPE
-- 8. Agent fully synced with all nodes
OBJECTS {
dynaSNMPAgentAlarmTrapCnt
}
STATUS current
DESCRIPTION
"Sent when the subagent system has read its persistent
configuration and populated its MIB with persistent
information.
NOTE: The subagent MIB-tree might not be available until
this trap has been sent.
"
dynaSNMPAgentDown
NOTIFICATION-TYPE
-- 9. Agent Closing Down
OBJECTS {
dynaSNMPAgentAlarmTrapCnt
}
STATUS current
DESCRIPTION
"Sent when the subagent is shutting itself down.
"
DN70553464
Issue 2-0
117 (126)
Dyna SNMP
---=========================
--dynaSNMPAgentGeneral group
--=========================
-dynaSNMPAgentVersion OBJECT-TYPE
SYNTAX DynaSNMPSWVersion
MAX-ACCESS
read-only
STATUS current
DESCRIPTION "Version of the Agent"
::= {dynaSNMPAgentGeneral 1}
dynaSNMPAgentFlags
OBJECT-TYPE
SYNTAX
DynaSNMPFlags
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"
1... .... .... .... 0000 (0x80000000) AgentRdy
get: 1 if the subagent has read its persistent configuration and
populated its MIB. The dynaSNMPPSHAgentRdy notification is sent
when the value of this bit changes from 0 to 1.
The unused highest 16 bits are reserved for future common extensions.
The lowest 16 bits are available for subagent specific extensions.
"
::= { dynaSNMPAgentGeneral 2 }
dynaSNMPAgentFlagsMask OBJECT-TYPE
SYNTAX
DynaSNMPFlagsMask
MAX-ACCESS
read-only
STATUS
current
DESCRIPTION
"See dynaSNMPAgentFlags"
::= {dynaSNMPAgentGeneral 3 }
END
1.5 Support for dynaSNMP private mib
The supported mib variables are given in details in the following tables.
Table 20.
Support for dynaSNMPGeneral-branch
Label
OID
Access
Support
dynaSNMPTemplateVersion
.1.3.6.1.4.1.28458.7.2.1.3.1.1
Yes
dynaSNMPMIBVersion
.1.3.6.1.4.1.28458.7.2.1.3.1.2
Yes
118 (126)
Note
DN70553464
Issue 2-0
Appendix E: MIB
Table 21.
Support for dynaSNMPNodes.dynaSNMPNodeInv - branch
Label
OID
Access
Support
dynaSNMPNodeTrapCnt
.1.3.6.1.4.1.28458.7.2.1.3.2.1.1
Yes
dynaSNMPNodeTable.
dynaSNMPNodeEntry
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1
Table 22.
Yes
See
Table
17.
Support for dynaSNMPNodes.dynaSNMPNodeInv.

dynaSNMPNodeTable.dynaSNMPNodeEntry - branch
Label
OID
Access
Support
dynaSNMPNodeIndex
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
1
Yes
dynaSNMPNodeName
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
2
Yes
dynaSNMPNodeType
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
3
Yes
dynaSNMPNodeFlags
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
4
Yes
dynaSNMPNodeFlagsMask
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
5
Yes
dynaSNMPNodeStatus
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
6
Yes
dynaSNMPNodeBus
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
16
Yes
dynaSNMPNodeAddress
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
17
Yes
dynaSNMPNodeGeneration
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
18
Yes
dynaSNMPNodeFEName
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
19
Yes
dynaSNMPNodeStation
.1.3.6.1.4.1.28458.7.2.1.3.2.1.3.1.
20
Yes
DN70553464
Issue 2-0
Note
s
Notes
119 (126)
Dyna SNMP
Table 23.
Support for dynaSNMPNodes.dynaSNMPNodeEvents.

dynaSNMPNodeDefs - branch
Label
OID
Access
Support
dynaSNMPNodeAdded
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.1
Yes
dynaSNMPNodeDeleted
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.2
Yes
dynaSNMPNodeModified
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.3
No
dynaSNMPNodeFM
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.4
Yes
dynaSNMPNodeFMSync
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.5
Yes
dynaSNMPNodePM
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.6
No
dynaSNMPNodePMSync
.1.3.6.1.4.1.28458.7.2.1.3.2.2.0.7
No
Table 24.
Support for dynaSNMPNodes.dynaSNMPNodeEvents
Label
OID
dynaSNMPCurAlarm
.1.3.6.1.4.1.28458.7.2.1.3.3.1
dynaSNMPAlarmLog
dynaSNMPAlarmEvents.
dynaSNMPAlarmDefs
Support
Notes
Yes
Table
26
.1.3.6.1.4.1.28458.7.2.1.3.3.2
No
.1.3.6.1.4.1.28458.7.2.1.3.3.3.0
Yes
See
Table
28
Support
Notes
Table 25.
Support for dynaSNMPFM -branch
Label
OID
dynaSNMPAlarmTrapCnt
.1.3.6.1.4.1.28458.7.2.1.3.3.1.1
Yes
dynaSNMPAlarmTable.
dynaSNMPAlarmEntry
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1
No
120 (126)
Notes
See
Table
26
DN70553464
Issue 2-0
Appendix E: MIB
Table 26.
Support for dynaSNMPCurAlarm -branch
Label
OID
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
Yes
dynaSNMPAlarmIndex
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
2
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
3
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
4
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
5
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
Yes
Yes
Yes
Yes
Yes
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
16
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
17
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
18
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
19
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
20
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
21
Yes
Yes
Yes
Yes
Yes
Yes
dynaSNMPAlarmTime
dynaSNMPAlarmText
dynaSNMPAlarmNbr
dynaSNMPAlarmFE
dynaSNMPAlarmSB
dynaSNMPAlarmFC
dynaSNMPAlarmSBname
Table 27.
Support
Notes
see note
dummy
dummy
Support for dynaSNMPAlarmTable.dynaSNMPAlarmEntry branch
Label
OID
Support
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
1
Yes
dynaSNMPAlarmIndex
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
2
Yes
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
3
Yes
dynaSNMPAlarmTime
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
4
Yes
Note
See note
1
In DynaSNMP the severity of the trap is defined by the Q1 fault code, not by the
severity defined by the Q1 element.
DN70553464
Issue 2-0
121 (126)
Dyna SNMP
Label
OID
dynaSNMPAlarmText
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
5
Yes
dynaSNMPAlarmNbr
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
6
Yes
dynaSNMPAlarmFE
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
16
Yes
dynaSNMPAlarmSB
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
17
Yes
dynaSNMPAlarmFC
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
18
Yes
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
19
Yes
dynaSNMPAlarmSBname
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
20
Yes
.1.3.6.1.4.1.28458.7.2.1.3.3.1.2.1.
21
Yes
Table 28.
Support
dummy
dummy
Support for dynaSNMPAlarmEvents.dynaSNMPAlarmDefs branch
Label
OID
dynaSNMPAlarmRaised
.1.3.6.1.4.1.28458.7.2.1.3.3.3.0.1
Yes
dynaSNMPAlarmCleared
.1.3.6.1.4.1.28458.7.2.1.3.3.3.0.2
Yes
Table 29.
Support
Note
Support for dynaSNMPAgent. dynaSNMPAgentAlarm - branch
Label
OID
dynaSNMPAgentAlarmTrapC
nt
.1.3.6.1.4.1.28458.7.2.1.3.5.1.1
122 (126)
Note
Support
R
Note
Yes
DN70553464
Issue 2-0
Appendix E: MIB
Label
OID
dynaSNMPAgentAlarmTable.
dynaSNMPAgentAlarmEntry
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1
Table 30.
Support
Note
No
See
Table
30.
Support
Note
Support for dynaSNMPAgentAlarmTable

dynaSNMPAgentAlarmEntry - branch
Label
OID
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1.
2
No
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1.
3
No
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1.
4
No
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1.
5
No
.1.3.6.1.4.1.28458.7.2.1.3.5.1.2.1.
6
No
Table 31.
Support for dynaSNMPAgent. dynaSNMPAgentEvents.

dynaSNMPAgentEventDefs - branch
Label
OID
Support
dynaSNMPAgentAlarmRaised
.1.3.6.1.4.1.28458.7.2.1.3.5.2.0.1
No
dynaSNMPAgentAlarmCleared
.1.3.6.1.4.1.28458.7.2.1.3.5.2.0.2
No
dynaSNMPAgentRdy
.1.3.6.1.4.1.28458.7.2.1.3.5.2.0.3
Yes
DN70553464
Issue 2-0
Note
123 (126)
Dyna SNMP
Label
OID
Support
dynaSNMPAgentDown
.1.3.6.1.4.1.28458.7.2.1.3.5.2.0.4
No
Table 32.
Support for dynaSNMPAgent. dynaSNMPAgentGeneral branch
Label
OID
Support
dynaSNMPAgentVersion
.1.3.6.1.4.1.28458.7.2.1.3.5.3.1
Yes
dynaSNMPAgentFlags
.1.3.6.1.4.1.28458.7.2.1.3.5.3.2
Yes
dynaSNMPAgentFlagsMask
.1.3.6.1.4.1.28458.7.2.1.3.5.3.3
Yes
Table 33.
Note
Support for dynaSNMPConformance - branch
Label
OID
Support
dynaSNMPConformance
.1.3.6.1.4.1.28458.7.2.1.3.9
No
124 (126)
Note
Note
DN70553464
Issue 2-0
Appendix E: MIB
Glossary
ACL2i
Mbit/s G.SHDSL line terminal
ARP
Address Resolution Protocol
ASCII
American Standard Code for Information
CD-ROM
Compact Disc-Read-Only Memory
CLI
Command Line Interface
CTS
Clear to send
DCE
Data Communications Equipment
DCN
Data Communications Network
DI
Data Interface
DNT2M
2 Mbit/s HDSL network terminal
DSL
Digital Subscriber Line
DSR
Data Set Ready
DTE
Data Terminal Equipment
DTR
Data Terminal Ready
DYNANET
Nokia Siemens Networks family of primary rate equipment and their

tributaries used in access network. The family includes a wide range of
products: primary multiplexers, branching and cross-connect equipment,
line equipment for copper cables and optical fibres, HDSL line terminals,
and integrated multiplexing and line equipment.
EEPROM
Electrically Erasable Programmable Read-Only Memory
EMC
Electromagnetic Compatibility
ETSI
European Telecommunications Standards Institute
GND, gnd
Ground
HDSL
High-Speed Digital Subscriber Line
HW
Hardware
IP
Internet Protocol
IPCP
Internet Protocol Control Protocol
LAN
Local Area Network
LED
Light-Emitting Diode
LMI
Local Management Interface
MIB
Management Information Base
PDH
Plesiochronous Digital Hierarchy
DN70553464
Issue 2-0
125 (126)
Dyna SNMP
POP
Point-Of-Presence
PPP
Point-to-Point Protocol
PSTN
Public Switched Telephone Network
PVC
Polyvinyl Chloride
Q1
Nokia Siemens Networks proprietary management protocol
Rack alarm
An alarm in one of the equipment in the rack indicated by a common

alarm lamp. There are three types of rack alarms: A-alarms (prompt), Balarms (deferred) and D-alarms (reminders of alarm cancellation). Also
known as station alarm.
RTS
Request To Send
RxD
Received Data
SNMP
Simple Network Management Protocol
STE
Service Terminal Emulation
Subrack
A mechanical housing that fits in a rack and contains plug-in units
Unit of width, 5.08 mm (in mechanics)
TDM
Time Division Multiplexing
Telnet
Standard terminal emulation protocol defined in RFC 854.
TFTP
Trivial File Transfer Protocol
TxD
Transmitted data
Trap
Message sent by an SNMP agent to network management system.
WAN
Wide Area Network
10Base-T
10 Mbit/s Ethernet specification
126 (126)
DN70553464
Issue 2-0

Dyna SNMP

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Dyna SNMP

Transféré par

Droits d'auteur :

Formats disponibles

C32390.

Nokia Siemens Networks

Nokia Siemens Networks

Command line interface.......................................................................28

Nokia Siemens Networks Q1 Management pipe ...............................63

Nokia Siemens Networks

Nokia Siemens Networks

Dyna SNMP plug-in unit (see the following figure)

Nokia Siemens Networks

The plug-in unit can be installed, for example, in a DYNANET subrack.

Mechanical construction of the Dyna SNMP unit (plug-in unit)

Nokia Siemens Networks

Identification stickers of Dyna SNMP unit (example)

Nokia Siemens Networks

The plug-in unit can be installed, for example, in a DYNANET

Nokia Siemens Networks

Cables needed with the Dyna SNMP Adapter plug-in unit

Nokia Siemens Networks

Identify the unit

Nokia Siemens Networks

Check the jumper settings

Nokia Siemens Networks

Nokia Siemens Networks

Set jumper S1 to ON position

Nokia Siemens Networks

Make sure that both jumpers are in ON position. Jumper NR1B S1 is

Nokia Siemens Networks

Insert the card into the subrack slot

Nokia Siemens Networks

there is only one flash installed and it has a defective program

there are two flashes installed, both of which have defective

In such situations, at least the bank A flash must be changed.

defective flash chip has been installed in the bank A or B

the battery of the real time clock is empty

the EEPROM is defective.

Connect the local management cable

Connect the extension cables

Nokia Siemens Networks

Dyna SNMP plug-in unit

Nokia Siemens Networks

Recommended way of connecting the Q1 cables for the Dyna

Nokia Siemens Networks

Alternative way of connecting the Q1 extension (MI/DI) cables

Start the CLI session

Start the CLI session by pressing ENTER. The default password is

Nokia Siemens Networks

Nokia Siemens Networks

Password jumper location

Nokia Siemens Networks

Configure Dyna SNMP

An example configuration presented in Figure 11 is given with the

sets the user password

Nokia Siemens Networks

CLs> set spasswd

sets the superuser password

CLI session time-out (in minutes)

Real time clock

CLs> set clock 2008-1-21,02:14:00.0,-2:0

sets IP address and IP mask for Ethernet interface

enables Ethernet interface

sets IP address and IP mask for PPP interface

sets PPP interface configuration (asynchronous mode). The hw

sets IP filter configuration (Dyna SNMP unit accepts packets only