Geekly Articles each Day
📜 ⬆️ ⬇️

Software update and initial setup instructions for Nokia 7210 SAS-M

This article is intended for those who want to understand the procedure for the initial commissioning of Nokia (formerly Alcatel-Lucent) 7210 SAS-M equipment. The only correct approach when working with any equipment is preliminary reading of the documentation. But the reality is that a person can be given the task of urgently launching equipment without preparing him for his future work. The deadlines are burning, there is no documentation, the setting is carried out “on a whim”. Unfortunately, this is not a rare life situation, but the results of it, in most cases, are pitiable.



I will try to help understand the procedure of the primary integration of 7210 SAS-M 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 restrict myself to the minimum information that is required to run the 7210 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 Nokia 7750 primary configuration theme (SR-7 | SR-12), then you can read about it in the corresponding article.


1. Software update on 7210 SAS-M


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) Console cable for 7210. I am using a Cisco rollover cable;
3) Terminal client (Putty, SecureCRT or equivalent);
4) TFTP server (tftp32 or equivalent);
5) The presence of current TiMOS (as an example, used TiMOS 7.0R12, but the instruction is relevant for all versions).


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 7210 to the computer network card. 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 TiMOS is already installed on the SAS-M, 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/7210/TiMOS-7.0.R12/both.tim # Set the address of the operating system


tftp://192.168.1.10/7210/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 7210


save # Save the Boot Options File


back


file dir # Check the free space on the memory card. At the time of writing, two versions of TimOS can be loaded onto the card. In case of insufficient memory, files can be deleted with the command file delete "file name"


file md cf1:\TiMOS-7.0.R12 # Create a folder for the new TiMOS on the memory card


file copy tftp://192.168.1.10/both.tim cf1:\TiMOS-7.0.R12\both.tim # Load the TiMOS image


file copy tftp://192.168.1.10/boot.tim cf1:\TiMOS-7.0.R12\boot.tim # Save the boot loader to a folder with the corresponding TiMOS (this is done with the goal of saving this file for when it will be overwritten The new version. Boot boot loader is loaded from cf1 :)


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


bof primary-image cf1:\TiMOS-7.0.R12\both.tim # Specify the main TimOS image to load


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


bof primary-config cf1:\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


After saving the configuration (admin save), you need to restart 7210 with the admin reboot upgrade command and make sure that the equipment has been successfully loaded. I want to note that the addition of "upgrade" in the command indicates to SAS-M the need to upgrade CPLD (Complex Programmable Logic Device). You can find out the version of CPLD with the show boot-messages . At the time of writing, the current version is 2.9


After the reboot, you must complete the procedure by updating the Golden BOOT Loader with the admin update-golden-bootstrap command admin update-golden-bootstrap


1.5 Checking the update

show version # Checking the version of TiMOS, which runs 7210;
admin check-golden-bootstrap # Check bootloader version;
show boot-messages # Check the version of CPLD;
file dir # Check for free space on the memory card.


2. Initialization of Media Dependent Adapter (for example, m2-xfp)


image


In the 7210 SAS-M, it is possible to install an optional MDA module, which requires the following configurations:


2.1 Initialize the card in bof: use-expansion-card-type m2-xfp


2.2 Exclude two existing ports from operation (for example, 23 and 24) in bof: no-service-ports 1/1/23 1/1/24
Important! The configuration of the excluded ports must be completely cleared:


port 1/1/23
shutdown
ethernet
exit
exit


Otherwise, after a reboot, the application of the configuration on these ports will stop.


2.3 Initialize the map in the configuration:


card 1
mda 2
mda-type m2-xfp
sync-e # If we plan to use sync-e sync transfer
no shutdown
exit
no shutdown
exit


2.4 Restart 7210.


2.5 Checking the MDA definition with the show mda 1/2 detail command


Note: mda 1/1 we will not be able to pull out, our "fixed" ports are attached to it. But sync-e also needs to be forcedly reflected in the mda 1/1 configuration if we want to use this technology on SAS-M ports.


3. Example of initial setup 7210 SAS-M


/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 7210
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 7210 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 7210 SAS-M on a network with configured OSPF protocol.


4. Useful notes



UPD: In 2014, an article on setting 7210 SAS-M was posted on Habré. In it, the author (YangAngel) made a number of gross errors, the consequences of which I wrote , responding to the received "feedback". If you used (use) the YangAngel article to configure the 7210 SAS-M, then I strongly recommend to pay attention to the specified comment and clause 1.5 of my article.


')

Source: https://habr.com/ru/post/306030/

More articles:


All Articles