Management Guide

If a module that is entered in the planned configuration must be replaced

(for example, because it is damaged), the new module is automatically
configured the same as the removed module.

The main part of the NEMI configuration is done now. Exit netconfig by
selecting [OK]. In most cases you will be asked to reboot. Confirm this
reboot message with <Enter>. After rebooting you should reconnect to
the NEMI and execute netconfig once more to save the settings made.
This saved information can be transferred to a new unit in case of a NEMI
swap, which make a new configuration much easier.
Software Control The Software Control menu allows you to update software for the NEMI
and Micro Controller. This menu is described in detail in 3.4 “Software
Control/Update for NEMI”, p. 3-33.
System Startup The System Startup menu is used to set which services are started after
power-on. In an environment requiring high security, it is recommended
that as few services as possible are started. When a check box field is
ticked, the corresponding service will be started after power-on.

Disabling a service guarantees that no unauthorized person can misuse

this service. When you disable the Telnet Server you will not be able to
enable it again remotely except via the SSH.
+-----------System Startup------------+
| |
| [X] Start SNMP |
| |
| [X] Start Telnet Server |
| [X] Start SSH Server |
| |
| [X] Start FTP Server |
| |
| [ ] Start TL1 |
| on TCP Port [2037 ] |
| [ ] TL1 on serial Line |
| [ ] TL1 with local Echo |
| [ ] TL1 full mode |
| |
| |
| [ OK ] [ Cancel ] |
| |
+-------------------------------------+

Start SNMP SNMP is used for network management systems as HP Openview or the
ADVA Network and Element Manager.
Start Telnet Server Telnet is used for an interactive command line interface.
Start SSH Server SSH is used for remote logins. The method of information transfer is more
secure than telnet because communication and login is encrypted.
Start FTP Server FTP is used to transfer files to the NEMI (e.g. software update) or from
the NEMI (e.g. store log files on a central backup server).
Start TL1 TL1 stands for Transaction Language 1 and is a network management pro-
tocol used mostly for North American telecommunication equipment.
FSP3_MG_03_Getting_Started_A_3_4.fm

Information about TL1 can be found at http://www.tl1.com/

Save Settings This command allows you to save the NEMI configuration. This command
will be used if the NEMI configuration was completed.

Page 3-28 FSP 3000 User Manual

 TM

Getting Started
Optical Networking

Step 1 From the Main Configuration Window use the tab or cursor keys to move
to “Save Settings”. Press <Enter> to open the following menu:
+-----------------------Main Configuration Window-----------------------+
| |
| +-----------------Save NEMI Settings-----------------+ ] |
| | | ] |
| | This will save your actual Settings in the file |Protocol ] |
| | /home/netadmin/NEMISAVE.TGZ | |
| | | ] |
| | You can restore these settings when pressing | |
| | the Button “Restore Settings”. | ] |
| | | |
| | (Tip: You can install multiple NEMIs by completing |-------------- |
| | one NEMI-Master Installation, saving these |l ] |
| | Settings, moving them to another NEMI and using | ] |
| | the “Restore Settings” function on the next NEMI.) | |
| | | ] |
| | |s ] |
| | [ OK ] [ Cancel ] |y Defaults ] |
| | | |
| +----------------------------------------------------+ |
| |
+-----------------------------------------------------------------------+

Step 2 Confirm the Setting Saved information with [OK]. Select [OK] in the
netconfig main window and quit the program with <Enter>.

After this procedure a file called NEMISAVE.TGZ can be found in the

/home/netadmin directory. This file contains all the main settings done
before.
Step 3 Open an ftp session to the NEMI from your Management PC. Login as user
netadmin with a valid password, set the binary mode and transfer the
NEMISAVE.TGZ file to your Management PC.
• ftp 172.16.34.5
• user (172.16.34.5:(none))>: netadmin
• 331 Password required for netadmin
• password: valid password for netadmin
• 230 User netadmin logged in
• ftp> bin #to set binary mode
• 200 Type set to I
• ftp> mget /home/netadmin/NEMISAVE.TGZ
• 200 Type set to I.
• mget /home/netadmin/NEMISAVE.TGZ? y #Confirm with y
• 200 PORT command successful.
• 150 Opening BINARY mode data connection for /home/netadmin/
NEMISAVE.TGZ (16782 bytes).
• 226 Transfer complete.
• FTP: 16782 Bytes received in 0,02seconds 839,10KB/s
• ftp>bye # quit ftp
FSP3_MG_03_Getting_Started_A_3_4.fm

The file will be transferred to the working directory of your Management

PC. Give the file a unique filename like NEMISAVE_172_16_34_5.TGZ to
identify the node the file belongs to. Store the file in a safe place.
If you swap the NEMI on this node, this NEMISAVE file can be used to
restore the former configuration.

Version 3.4 Page 3-29

Management Guide

Restore Settings This command allows you to semi-automatically restore settings that you
saved before. Use the following procedure to restore the NEMI setting:

• Rename the NEMISAVE_172_16_34_5.TGZ back to NEMISAVE.TGZ

• Open ftp session to the NEMI from your Management PC. Login as user
netadmin with a valid password, set the binary mode and transfer the
NEMISAVE.TGZ file to the NEMI. The following procedure assumes the
file is stored on c:\NEMIbackup.
• ftp 172.16.34.5
• user (172.16.34.5:(none)): netadmin
• 331 Password required for netadmin.
• password: valid password for netadmin
• 230 User netadmin logged in.
• ftp> bin #to set binary mode
• 200 Type set to I.
• ftp> mput c:\NEMIbackup\NEMISAVE.TGZ
• mput c:\NEMIbackup\NEMISAVE.TGZ? y #Confirm with y
• 200 PORT command successful.
• 150 Opening BINARY mode data connection for NEMISAVE.TGZ.
• 226 Transfer complete.
• FTP: 16815 Bytes transmitted in 0,01seconds 1681,50KB/s
• ftp>bye # quit ftp
Login to the NEMI via telnet and reenter the main configuration window
as before. Open the [Restore Settings] field.
+---------------Restore NEMI Settings----------------+
| |
| This will restore the Settings from the file |
| /home/netadmin/NEMISAVE.TGZ |
| |
| You can edit them. At the End you must reboot |
| the NEMI. |
| |
| (Tip: You can install multiple NEMIs by completing |
| one NEMI-Master Installation, saving these |
| Settings, moving them to another NEMI and using |
| the “Restore Settings” function on the next NEMI.) |
| |
| |
| [ OK ] [ Cancel ] |
| |
+----------------------------------------------------+

Select [OK] and confirm this screen with <Enter>. The following screen
will appear. You can choose between configuring NEMI-Slaves or Nemi-
Masters. Specify the node number, host name and external IP address
(these should be the only differences between all NEMIs in an FSP 3000
FSP3_MG_03_Getting_Started_A_3_4.fm

Network):

Page 3-30 FSP 3000 User Manual

 TM

Getting Started
Optical Networking

+-----Restore from saved Configuration-----+

| |
| Configure NEMI-Master or Slave ? |
| (X) NEMI-Master ( ) NEMI-Slave |
| |
| Node Number |
| typ. 1 to 10 [5 ] |
| |
| Host Name |
| e.g. “node1” [Node5 ] |
| |
| External IP Address [172. 16. 34. 5 ] |
| |
| |
| [ OK ] [ Cancel ] |
| |
+------------------------------------------+

Select [OK] and press <Enter>. The following screen will appear:
+----------Restore Saved Settings----------+
| |
| The restore file contains the |
| following Data: |
| |
| [X] Configuration Data |
| |
| [X] Passwords |
| |
| [X] Cardspecific Values |
| |
| |
| [ Restore ] [ Cancel ] |
| |
+------------------------------------------+

Select [Restore] and press <Enter>. You will be asked to confirm the IP
settings as shown here:
+-----Restore from saved Configuration-----+
| |
| Configure NEMI-Master or Slave ? |
| (X) NEMI-Master ( ) NEMI-Slave |
| |
| Node Number |
| typ. 1 to 10 [5 ] |
| |
| Host Name |
| e.g. "node1" [Node5 ] |
| |
| External IP Address [172. 16. 34. 5 ] |
| |
| |
| |
| [ OK ] [ Cancel ] |
| |
+------------------------------------------+

Verify the correctness. Select [OK] and press <Enter>.

Reboot After “Restore Settings” and exiting the configuration window, you will
be forced to reboot the NEMI. After the reboot, the saved configuration
will be restored. Make sure that configuration backups are up-to-date.
+-------------------Information-------------------+
| |
| Now we need a Reboot to make the Changes active |
| |
| [ OK ] |
| |
+-------------------------------------------------+
FSP3_MG_03_Getting_Started_A_3_4.fm

Version 3.4 Page 3-31

Management Guide

Verify the Correct After “Reboot”, the correct operation should be checked. This should
NEMI/DEMI include the following steps:
Operation
Step 1 Login to the system via telnet -> Login should be possible.
Step 2 Login to the system via serial line -> Login should be possible.
Step 3 Login to the system remotely from the NMS station via telnet -> Login
should be possible.
Step 4 Execute the command traptest on the NEMI command line -> each trap
receiver should get an "login detected" trap.
Step 5 Execute a ping on the NEMI command line to the Broadcast address of the
internal IP address range and verify that all NEMI modules of the system
are responding. The following screen shows a 5 node ring with an internal
IP address range of 192.168.132.0/24 and node numbers 1 to 5.

Node3:/# ping 192.168.132.255

PING 192.168.132.255 (192.168.132.255): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=2.7 ms Master Node 3
64 bytes from 192.168.132.4: icmp_seq=0 ttl=64 time=6.7 ms (DUP!) Slave Node 2
64 bytes from 192.168.132.3: icmp_seq=0 ttl=64 time=5.4 ms (DUP!) Master Node 2
64 bytes from 192.168.132.2: icmp_seq=0 ttl=64 time=6.7 ms (DUP!) Slave Node 1
64 bytes from 192.168.132.1: icmp_seq=0 ttl=64 time=6.7 ms (DUP!) Master Node 1
64 bytes from 192.168.132.6: icmp_seq=0 ttl=64 time=6.7 ms (DUP!) Slave Node 3
64 bytes from 192.168.132.7: icmp_seq=0 ttl=64 time=8.1 ms (DUP!) Master Node 4
64 bytes from 192.168.132.9: icmp_seq=0 ttl=64 time=9.4 ms (DUP!) Master Node 5

If all these tests are successful, the NEMI works fine.

3.3.4 FSP 1000/FSP 2000 Main Configuration Window Look

For users familiar with the FSP 1000 or FSP 2000, the “Main Configuration
Window” may be presented in another form. Log into the NEMI and type
setup instead of netconfig. The “Main Configuration Window” is present-
ed as follows:
- Master - Main Configuration Window
c . Change Password
i + IP Configuration
m . Advanced OSCM Options
n + SNMP Configuration
s . Serial Settings
a . Alarm Severities
h . Thresholds
v . Provisioning
d + Date and Time
l . View Logfiles
. ----------
. Install/Deinstall Software
. System Startup
+ Save/Restore Settings
. ----------
q . quit
FSP3_MG_03_Getting_Started_A_3_4.fm

Use the cursors or hotkeys to navigate.

Page 3-32 FSP 3000 User Manual