Software update and initial setup instructions for Nokia 7750 (SR-7 | SR-12)

This article continues the theme of the initial setup of Nokia equipment (formerly Alcatel-Lucent). It will be useful to those who do not have much experience in operating this equipment, but in the short term, plans to link their working hours with the Nokia 7750 (SR-7 | SR-12)

I will try to help understand the primary integration of the 7750 SR on the network, but I will immediately note that no instruction can replace the official documentation from the manufacturer, especially since the new versions of the software can be changed. I plan to limit myself to the minimum information required to run the 7750 and provide it with remote access. Nevertheless, I will willingly supplement this article (or write a new one, if the questions go beyond its scope) with information to which interest will be shown.

If you are interested in the theme of the initial configuration of the Nokia 7210 SAS-M, then you can read about it in the corresponding article .

1. Software update on 7750 SR

First of all, I recommend upgrading the software (TiMOS) to the current version. I want to immediately note that in the case of using the 5620SAM control system, it is necessary to consider which maximum version of TiMOS it supports.

1.1 Preparation for work

What is needed for the work:

1) Laptop with a COM port or usb-com adapter;
2) Serial cable. I use a Cisco rollover cable with an additional adapter, since the 7750 console is a DB9 connector (unlike the 7210, which uses RJ45)

3) Terminal client (Putty, SecureCRT or equivalent);
4) TFTP server (tftp32 or equivalent);
5) The presence of current TiMOS (as an example, used TiMOS 13.0R10).

1.2 Fill software

To download software, you need to connect to the Console port and configure session parameters as follows:

Baud Rate 115,200
Data Bits 8
Parity None
Stop Bits 1
Flow Control None

Direct cable connect Management Port 7750 to the network card of the computer. Set IP to the local computer (in the example 192.168.1.10/24). Start the TFTP server and select the directory with TiMOS as the working folder.

If the TiMOS is already installed on the SR, then skip point 1.3 and go directly to 1.4.

1.3 There is no TiMOS on the equipment (monitor mode)

Press any key to start changing the boot parameters. When requesting a password, enter: “password”. Next, follow the dialogue:

tftp://192.168.1.10/7750/TiMOS-SR-13.0.R10/both.tim # Set the address of the operating system

tftp://192.168.1.10/7750/config.cfg # Set the address of the configuration file

We enable the eth-mgmt port by typing the enable command and assign an IP address from the same subnet as configured on the computer.
When prompted to save the configuration, we answer - yes.

After this step, the operating system should boot up.

1.4. Equipment loaded (TiMOS)

Login / password: admin / admin

bof # Go to the settings menu Boot Options File

no eth-mgmt-disabled # Enable eth-mgmt

eth-mgmt-address 192.168.1.1/24 # Assign an eth-mgmt address to our 7750

save # Save the Boot Options File

back

file dir # Check the free space on the memory card. In case of insufficient memory, files can be deleted with the command file delete "file name"

file md cf1:\TiMOS-13.0.R10 # Create a folder for the new TiMOS on the memory card and load system files into it

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\both.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\cpm.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\iom.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\isa-aa.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\isa-tms.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\support.tim

file copy tftp://192.168.1.10/both.tim cf3:\TiMOS-13.0.R10\boot.ldr

file copy tftp://192.168.1.10/boot.tim cf3:\boot.ldr # Download (overwrite) boot loader

bof primary-image cf3:\TiMOS-13.0.R10\ # Specify the main TiMOS image to load

bof secondary-image cf3:\< TiMOS, > # Optional

bof primary-config cf3:\config.cfg # Specify the configuration file

bof no eth-mgmt-address 192.168.1.1/24 # Delete the address eth-mgmt

bof eth-mgmt-disabled # Disable eth-mgmt

bof save

admin save

The file was successfully copied when the equipment displays the following information in the console:

Copying file tftp://192.168.1.10/both.tim ... OK
1 file copied.

After saving the configuration (admin save), you need to reboot the 7750 with the admin reboot upgrade command and make sure that the equipment has been successfully loaded.

1.5 Standby processor module (standby CPM)

If a backup CPM is installed in the 7750, then the system needs to transfer the system files and configurations to its memory card (in the cf3-b system) using the admin redundancy synchronize boot-env command

Attention! Since the 11th release, a new support.tim file has appeared. If the update is performed from a version less than 11th, then this file must be copied to the backup CPM manually copy cf3:\TiMOS-13.0.R10\support.tim cf3-b:\TiMOS-13.0.R10\support.tim

You must also run the /configure redundancy synchronize config command. If this configuration is not applied, then when the admin save command is executed, the configuration will not be saved to the backup CPM.

Having a backup module allows you to perform the procedure In-Service Software Upgrade (ISSU). This option is not available in the initial minor versions of TiMOS, before updating it is necessary to familiarize yourself with the software release notes of the corresponding software version.

The following key commands are present in this procedure (we assume that at the time of the start of the update, the CPM in slot A is active):

1. Copy the software on cf3 of the main CPM to the cf3 folder: \ TiMOS-13.0.R10 \
2. We are overwriting boot.ldr in the root (cf3 :)
3. Change the path to the main and backup TiMOS image in BOF
4. admin redundancy synchronize boot-env # Synchronize the main and backup CPM cards (not forgetting to manually back up support.tim on older releases)
5. admin reboot standby now # Restart the backup module.
6. show card # Check that the CPM-B has rebooted and has the status of up ISSU/standby
7. admin redundancy force-switchove # Making the updated backup module active. After this, the second (formerly active) module will begin the update process.
8. show card # Check that all cards are up.

2. Installation and initialization of cards

Line cards must be installed in different parts of the chassis (for SR-7, if there are two line cards, they should be placed in slots 1 and 5, not in 4 and 5). This is due to restrictions on the use of Timing References. Ref1 can be used on the map in 1-2 / 1-5 slot, and Ref2 on the map in 3-5 / 6-10 slot for SR-7 / SR-12, respectively.

2.1 Map Definition

Maps and modules installed in the 7750 must be defined in the configuration, until their state is unequipped

configure card < >
card-type <equipped card-type>
mda < mda >
mda-type <equipped mda-type>

The correct status in the show card and show mda output is Admin up, Operational up. For more detailed information about the map (P / N, S / N, temperature, etc.), you must add detail to the specified commands.

2.2 Chassis-mode

The configure system chassis-mode <> command allows you to configure the set of features available in the chassis. This parameter depends on the type of cards used:

a (default): corresponds to the set of functions associated with the iom-20g.
b: corresponds to the set of functions associated with the iom-20g-b.
c: corresponds to the set of functions associated with iom2-20g.
d: corresponds to the set of functions associated with iom3-xp

For example, if you have iom3-xp cards installed, then you need to enter the configure system chassis-mode d command

3. Example of initial setup 7750 SR

/configure system name ""

Prepare the port, create and associate an interface with it:

/configure port 1/1/1
description " "
no shutdown

/configure router
interface "system”
address <IP >/32 # Create a system virtual interface
no shutdown
exit

interface " "
address <IP >/30 # interface ip address
port 1/1/1 # Port on our equipment from which the link goes
no shutdown
exit

/configure router ospf
area 0.0.0.0 # The area number in which will be 7750
interface "system" # Be sure to include the "system" interface in this aria
exit
interface " " # Specify the names of all interfaces included in this aria
interface-type point-to-point # Specify interface type
exit

If 7750 participates in more than one aria, then it is necessary to prescribe the second aria and all its interfaces. If the interface participates in the non backbone area as secondary, then it is configured as follows:

area 0.0.0.1 interface "system" secondary exit

This configuration is the minimum that will allow remote access to the 7750 SR on a network with configured OSPF protocol.

4. Useful notes

• You can view the configuration using the “admin display-config” command. If it is necessary to execute the command (any) from the location of your location in the console, then set the prefixed "/".
• By executing the “info” command, you can see the configuration that belongs to the branch of your location. If it is necessary to view the values ​​of the “default” parameters, then use “info detail”
• With the “show chassis” and “show card” commands you can find out the chassis temperature and the FAN mode of operation. If the fans operate in full speed mode, this indicates an increased temperature condition of the unit.
• On the Nokia licensed CF card, the TiMOS is stored and the configuration is installed in the cf3 processor card. A good solution would be to install an additional Sandisk memory card (officially supported by the manufacturer) in the cf2 or cf1 slot and use it as a log repository.
• With the “show chassis” command, you can get information about the power supply and its output outside the allowable limits.
• The commands “show log log-id 100” and “show log log-id 99” will allow you to view the Default Serious Errors Log and the Default System Log, respectively.
• The "show port" command allows you to check the status of ports
• The show router route-table command will reflect the routing table
• In the cf3: /bootlog.txt file you can find the 7750 download log. If the equipment cannot load TiMOS (for example, goes into a cyclic reboot), then the information from this file can help with the diagnostics.
• IOS (Cisco): “ping 1.1.1.1 size 1500 df-bit”, in this case 1500 bytes is the size of the datagram already with IP and ICMP headers.
• TiMOS (Nokia): "ping 1.1.1.1 size 1472" - 1472 bytes indicate the size of the data field in ICMP. In other words, we add another 8 bytes of ICMP and 20 bytes of IP and we get the same 1500 bytes as on Cisco.
• When contacting Nokia technical support, you will need to provide two tech-support files, shot with the command "/ admin tech-support cf3: <file name> .bin" with a minimum time difference of 15 minutes. Unfortunately, unlike many other vendors, these files are encrypted and only Nokia engineers will be able to read them. In case of any problems or accidents, first of all I recommend removing the first tech-support file, and then proceed to solve the problem.