Вы находитесь на странице: 1из 27

CONTENTS

I.

Stand-alone node set-up ......................................................................................................................... 2

II. Configure the software environment and load, and commit the software. ....................................... 5
1.

WebUI procedure: .............................................................................................................................. 6

2.

CLI procedure : .................................................................................................................................. 9

III.

Set the NE to operate in SDH mode ................................................................................................ 13

1.

CLI procedure : ................................................................................................................................ 13

IV.

Set the loopback IP address ............................................................................................................. 14

1.

WebUI procedure : ........................................................................................................................... 14

2.

CLI procedure : ................................................................................................................................ 14

V. Configure GNE for management system access ................................................................................ 15


1.

WebUI procedure : ........................................................................................................................... 15

2.

CLI procedure : ................................................................................................................................ 18

VI.

Complete connection of inventory cables ....................................................................................... 18

1.

WebUI Procedure : ........................................................................................................................... 18

2.

CLI procedure : ................................................................................................................................ 20

VII.

Insert duplicate equipment controller ............................................................................................ 21

VIII. Set the network element date and time ........................................................................................... 22


1.

WebUI procedure : ........................................................................................................................... 22

2.

CLI procedure : ................................................................................................................................ 23

IX.

Disable ES port monitoring ............................................................................................................. 23

1.

WebUI procedure : ........................................................................................................................... 23

2.

CLI procedure : ................................................................................................................................ 24

X. Update firmware on all circuit packs ................................................................................................. 24


1.

WebUI procedure : ........................................................................................................................... 24

2.

CLI procedure : ................................................................................................................................ 25

XI.

Configure additional system properties.......................................................................................... 25

1.

WebUI procedure : ........................................................................................................................... 26

2.

CLI procedure .................................................................................................................................. 26


1

I. Stand-alone node set-up


Connect one end of the Ethernet cable to the CIT port on the active EC card (indicated by green
Active LED) on the master shelf. Connect the other end of the cable to the Ethernet port on your
PC.
Open a PC command window and type ipconfig and <Enter>. Verify the IP address assigned
by the NE to your PC is 172.16.0.x.

Launch Internet Explorer and enter http://172.16.0.1 in the Address bar. This is the
default IP address of the CIT port.
Note: Make sure Internet Explorer is not using a proxy server to access this address.
Click Go. The browser connects to the network element and the WebUI login window is displayed.

Initialize the database


A warning message will indicating that the database is uninitialized.

If the warning message does not appear, this is an indication that there is a database already on the
EC.

USE:(
Use a telnet application on your PC and open a telnet session connected to the IP address of the
CIT port.
The default address for an uncommissioned NE is 172.16.0.1
Hit <Enter> and the login: prompt will appear. Type cli and <Enter>.
Type cli at the Password: prompt and <Enter>.
This starts the CLI, and another Username: prompt will appear. Type admin and
<Enter>.
Type config database clear.

)
Click OK and the system will automatically restart after initialization. A window will appear
showing the restart progress.

After the restart is complete, the system will prompt you for a new NE name. Type the NE name.

Click the Submit button and the system will restart once again. The restart will take
approximately 2 minutes.
After the restart is complete, the WebUI will open with the system properties view.

II. Configure the software environment and load,


and commit the software.
Start the FTP server application on your PC and create a user account. Record the userid and
password established for the account.
Establish a root directory for the server and make sure it has read and write privileges. You may
create a folder in the root directory that will contain the NE software.
Copy the folder and subfolders with the NE software into the FTP root directory
established above.
Note: The software folder name to be copied is 1830PSS32-3.0-00. There should

also be two subfolders named 1830PSS32 and 1830PSS32M as well as a


CATALOG file.
Open Windows Firewall from the Control Panel.

Select Off. Then click OK.


Open a PC command window and type ipconfig and <Enter>. Once again verify the IP address
assigned by the NE to your PC is 172.16.0.x.
5

Important!

If this is an Alcatel-Lucent 1830 PSS-16 shelf, use the CLI


(command) procedure.

1. WebUI procedure:
Select the Software menu item under Administration and then select FTP Server.

The FTP server settings window appear.

Enter NE IP address obtained earlier using ipconfig for the Server IP Address.
Enter the path to the NE software relative to the server root directory in the Root Directory field.
Note: If the software folder was copied directly into the root directory, enter / in

this field.
Enter the UserID and Password to match the account created on the FTP server.
Click the Apply button.
Select Administration -> Software -> Upgrade from the top menu.
The Software Upgrade window appears.
Note: The software release will be the current factory load.

Select Audit from the Action Type drop-down list.


Enter the folder name containing the NE software in the Release Directory field. The folder
name for Release 3.0 should be 1830PSS32-3.0-00.
Click Apply and the Status field will change to In Progress.
Periodically click the Refresh button until the Status field changes to Completed.Verify the
Result is Success and the Upgrade Path Available field indicates Yes.
Select Download for the Action Type and click Apply. The Status field will change
to In Progress.
Periodically click the Refresh button until the Status field changes to Completed.Verify the
Result is Success.

Select Activate for the Action Type and click Apply. The Status field will change to In
Progress. The NE will then reboot, and the WebUI will automatically logout.
Wait about 2 minutes after the fan speed drops back down to normal speed and log back into the
NE (typically 10 minutes after activate).
Return to the Software Upgrade window by selecting Administration -> Software -> Upgrade
from the top menu. Verify the Status field now indicates Completed, and verify the
Result is Success.
Select Commit for the Action Type and click Apply. The Status field will change to In
Progress.
Periodically click the Refresh button until the Status field changes to Completed.
Verify the Result is Success.
Verify the Active and Committed releases have changed to the new release.

2. CLI procedure :
Use a telnet application on your PC and open a telnet session connected to the IP address of the
CIT port.
The default address for an uncommissioned NE is 172.16.0.1
Hit <Enter> and the login: prompt will appear. Type cli and <Enter>.
Type cli at the Password: prompt and <Enter>.
This starts the CLI, and another Username: prompt will appear. Type admin and
<Enter>.
Type config software server ip <ip> and <Enter>.
Where <ip> is the ip address of the PC with the FTP server. This is the same ip address
obtained using the ipconfig command in the PC command window.
Type config software server userid <userid> and <Enter>.
Where <userid> is the user_id for the user account defined on the FTP server.
Type <pw> and <Enter>.
Where <pw> is the password for the user account defined on the FTP server.
Type config software server root <path> and <Enter>.
Where <path> is the path to the NE software relative to the server root directory.
Note: If the software folder was copied directly into the root directory, enter / for the

<path>.
Type config software server detail and <Enter>.
Sample output below.
Software
Software
Software
Software

Server
Server
Server
Server

Protocol
IP
Userid
Root Directory

:
:
:
:

FTP
172.16.0.2
sw1
/

Verify the server settings are correct.


Type config software upgrade status and <Enter>.

Sample output below.


Software Upgrade Information:
Software Server IP
Software Server Root Directory
Committed Release
Working Release Directory
Working Release
Active Release

:
:
:
:
:
:

Operation
Operation Status
Upgrade Path Available

:
:
:

172.16.0.2
/

1830PSS32-0.00-7
1830PSS32-0.00-7/

True

Software Download Script (Timezone: ):

Verify the current active software is an older release than software you are loading.
Type config software upgrade manual audit <releasedir> nobackup and <Enter>.
Where <releasedir> is the directory name on the PC containing the software. The folder
name for Release 3.0 should be 1830PSS32-3.0-00.
Type config software upgrade status and <Enter>.
A listing of packs will be displayed along with the status showing which packs need to be
upgraded. Sample output below.
Software Upgrade Information:
Software Server IP
Software Server Root Directory
Committed Release
Working Release Directory
Working Release
Active Release

:
:
:
:
:
:

172.16.0.2
/SVT/

Operation
Operation Status
Upgrade Path Available

:
:
:

Audit
Completed
True

1830PSS32-0.00-7/
1830PSS32-0.00-7
1830PSS32-0.00-7

Software Download Script (Timezone: ):


Stage=0 Step=1
SH/SL: 1/1
CARDTYPE: EC
ACTION: Audit node
Completed
100% complete
10

RESULT: Success
Stage=1 Step=0
SH/SL: 0/0
CARDTYPE: Empty
ACTION: Transfer to disk
Planned
0% complete
RESULT: None
Stage=2 Step=0
ACTION: Activate
RESULT: None

SH/SL: 1/1
CARDTYPE: EC
Planned

Stage=3 Step=0
ACTION: Activate
RESULT: None

SH/SL: 1/2
CARDTYPE: AHPHG
Planned
0% complete

Stage=3 Step=1
ACTION: Activate
RESULT: None

SH/SL: 1/3
CARDTYPE: CWR8
Planned
0% complete

Stage=3 Step=2
ACTION: Activate
RESULT: None

SH/SL: 1/7
CARDTYPE: 11STAR1
Planned
0% complete

Stage=3 Step=3
ACTION: Activate
RESULT: None

SH/SL: 1/13 CARDTYPE: 11STAR1


Planned
0% complete

Stage=3 Step=5
ACTION: Activate
RESULT: None

SH/SL: 1/15 CARDTYPE: CWR8


Planned
0% complete

Stage=3 Step=6
ACTION: Activate
RESULT: None

SH/SL: 1/17 CARDTYPE: ALPHG


Planned
0% complete

0% complete

Repeat config software upgrade status until the Operation Status indicates Completed. Verify the
Upgrade Path Available changes to True.
Type config software upgrade manual load and <Enter>. This will transfer the software to the NE.
Type config software upgrade status and <Enter>. Watch for the following lines.
...
Operation
Operation Status
...

:
:

Load
In Progress 0%

Continue to execute the status command until the Operation Status shows Completed.
11

Type config software upgrade manual activate and <Enter>.


This will activate the software on the EC card.
The NE will reboot and the telnet connection will drop. Wait about 2 minutes after the fan speed
drops back to normal speed and log back into the NE (typically 10 minutes after activate). Then
Connect to the NE for CLI access.
Type config software upgrade status and <Enter>.Watch for the following lines.
...
Operation
Operation Status
...

:
:

Activate
In Progress 0%

Continue to execute the status command until the Operation Status shows Completed.
Note: The output will also display the progress of the activation on each of the packs

in the NE. The Operation Status will not show completed until all packs have been
activated on the new release.
Type config software upgrade commit and <Enter>. This will commit the software to be the
primary release.
Type config software upgrade status and <Enter>. Watch for the following lines.
...
Operation
Operation Status
...

:
:

Commit
In Progress 0%

Continue to execute the status command until the Operation Status shows Completed.
After the last status command is executed, verify the new software release is displayed as the
committed, working and active release. See the sample output below.
Software Upgrade Information:
Software Server IP
Software Server Root Directory
Committed Release
Working Release Directory
Working Release
Active Release

:
:
:
:
:
:

172.16.0.2
/
1830PSS32-3.0-00
1830PSS32-3.0-00/
1830PSS32-3.0-00
1830PSS32-3.0-00/

Operation
Operation Status
Upgrade Path Available

:
:
:

Commit
Completed
False

Software Download Script (Timezone: ):


12

NOTE : If this is an Alcatel-Lucent 1830 PSS-16 shelf, the following command is required to
bring the node up as an Alcatel-Lucent 1830 PSS-16.
Type config database clear and <Enter>.
The shelf will reboot and when the reboot completes the shelf will be correctly configured
as an Alcatel-Lucent 1830 PSS-16 shelf.

III. Set the NE to operate in SDH mode


Background

The NE defaults to SONET mode. You need to perform this procedure only if you want
the NE to operate in SDH mode.

NOTICE
This procedure should only be executed when a system is first turned up.

1. CLI procedure :
Type show version and <Enter>.
Sample output:
Software Version: 1830PSS32-3.0-00

Copy the string after Software Version. This will be used as the password for the SDH mode
command.
Type config admin mode sdh <pw> and <Enter>.
Where <pw> is the password copied in the previous step.
The following warning will appear.
WARNING: Changing the SONET/SDH mode will cause the database to be
cleared, the node to be cold reset and all services to be
deleted.

Type yes and <Enter>. You will be logged out. This procedure is complete.

13

IV. Set the loopback IP address


1. WebUI procedure :
Select System from the tree and the Details tab.

At the Loopback IP Address field, enter the IP address designated in the site documentation.
At the Loopback Subnet Mask field, enter the subnet mask designated in the site documentation.
Click the Submit button.
Click OK. The system will reboot, and WebUI will automatically logout.
Wait for the system to reboot (watch for the CIT link light to turn green) and log back into the
WebUI.

2. CLI procedure :
Type config interface loop ip <address>/<mask> and <Enter>.
Where <address> is the IP address and <mask> represents the subnet mask following the
CIDR format. Obtain this information from the site documentation.

14

The following warning message will appear.


WARNING:

Changing the loopback IP address will result


in a warm reset of this network element.

Enter 'yes' to confirm, 'no' to cancel:

Type yes and <Enter>. The CLI session will be terminated.

V. Configure GNE for management system access


Purpose

This procedure will provision and enable the OAMP port so that the NE can act as a
Gateway Network Element. The procedure will also provision the IP route information to
allow connection to RNEs. Not all NEs (i.e. RNEs) require this provisioning. Refer to the
site documentation.

1. WebUI procedure :
Expand Shelf 1 in the equipment tree and then expand slot 40: USRPNL (slot 10 for PSS-16).
Select OAMP. The OAMP port provisioning window will appear.

15

Enter the IP address and subnet mask as indicated in the site documentation.
Check the Port Enabled checkbox.
Click the Submit button.
Select Administration -> Networking -> IP Routes from the top menu.

The IP Routes screen is displayed.

Click the Create button. The Create IP Routes screen is displayed.

16

Enter the parameters based on the site documentation.


Click the Apply button.
Verify the new IP route is now shown in the IP routes.

17

2. CLI procedure :
Type config interface usrpnl oamp ip <address>/<mask> and <Enter>.
Where <address> is the IP address and <mask> represents the subnet mask following the
CIDR format. Obtain this information from the site documentation.
Type config interface usrpnl oamp state up and <Enter>.
Type config cn routes default add <address> and <Enter>.
Where <address> is the gateway address from the site documentation
Type config interface usrpnl oamp rou en and <Enter>.

VI. Complete connection of inventory cables


Purpose

The inventory cables will be connected and DCM, SFD44, SFD44B, and ITLB units
discovered in this procedure following the site documentation.
Note: If the DCM, SFD44, SFD44B, and ITLB shelf numbering contains non

contiguous numbers (numbers are skipped), the shelves must be manually preprovisioned before the inventory cables are connected. This procedure takes care of
that case.

1. WebUI Procedure :
Observe the equipment tree in the left window of the system view and verify there are no shelves
numbered 25 or greater.

18

Refer to the site documentation to determine the shelf numbering of the DCM, SFD44,
SFD44B, and ITLB units. List them in order starting with 25.
Does the shelf numbering contain non contiguous numbers (numbers are skipped)?
If yes, skip to steps between two ().
If no, continue.
Determine the next sequential DCM, SFD44, SFD44B, or ITLB unit that has not been
discovered and connect the inventory cable to that unit.
Wait 2 minutes and click the refresh button (the double arrows located at the top of the
equipment tree).
The new shelf should appear in the tree with the appropriate shelf number. If not, repeat clicking
refresh If the shelf still does not appear, check the cable connection or replace the inventory
cable.
Are there additional DCM, SFD44, SFD44B, or ITLB units to be discovered?
If yes, repeat the last 3 steps.
If no, end of steps.

() In the System view, select the Create Shelf tab. The Create Shelf view will appear.

Enter the appropriate provisioned type and shelf ID number of the next DCM, SFD44, SFD44B,
or ITLB shelf to be added. Enter additional parameters as required, then click the Apply
button.
Repeat until all the DCM, SFD44, SFD44B, and ITLB shelves have been created.
Close the create shelf window and verify all the DCM, SFD44, SFD44B, and ITLB shelves now
appear correctly in the equipment tree.
19

Connect the inventory cables to all the DCM, SFD44, SFD44B, and ITLB units.
Check the alarms on the system and verify there are no equipment alarms related to the DCM,
SFD44, SFD44B, or ITLB shelves. ()

2. CLI procedure :
Type show shelf * and <Enter>.
Sample output.
Shelf 1 Information
Name
: Master Shelf
Description
: Master Shelf
ExpectedAmps
: 30
Programmed Type
Shelf

: Universal Shelf

Present Type

: Universal

Verify there are no shelves number 25 or greater.


Refer to the site documentation to determine the shelf numbering of the DCM, SFD44,
SFD44B, and ITLB units. List them in order starting with 25.
Does the shelf numbering contain non contiguous numbers (numbers are skipped)?
If yes, skip to steps between two ().
If no, continue.
Determine the next sequential DCM, SFD44, SFD44B, or ITLB unit that has not been
discovered and connect the inventory cable to that unit.
Wait 2 minutes and type show shelf * and <Enter>.
The new shelf should be listed in the output with the appropriate shelf number. If not, repeat
show shelf. If the shelf still does not appear, check the cable connection or replace the inventory
cable.
Are there additional DCM, SFD44, SFD44B, or ITLB units to be discovered?
If yes, repeat the last 3 steps.
If no, end of steps.

20

()Type config shelf <shelf> type <type> and <Enter>.


Where <shelf> is the shelf number of the next shelf to be created and <type> is either dcm,
sfd44, sfd44b, or itlb.

Repeat this step until all the DCM, SFD44, SFD44B, and ITLB shelves have been created.
Type show shelf * and <Enter>.
Verify all the shelves that were created are now listed correctly.
Connect the inventory cables to all the DCM, SFD44, SFD44B, and ITLB units.
Type alm and <Enter>.
Verify there are no equipment alarms related to the DCM, SFD44, SFD44B, or ITLB shelves. ()

VII. Insert duplicate equipment controller


Purpose

In this procedure, the duplicate Equipment Controller (EC), if equipped, in slot 18 will be
installed. The EC from the factory will have the factory software and firmware already
installed on the pack. After seating the pack, the EC will synchronize with the existing EC
in slot 1.
Note: If the shelf is equipped with only one EC, skip this procedure.

Once again verify that both EC circuit packs in the shelf have Part Number (APN) 8DB59241AB.
Fully seat the EC circuit pack in slot 18. If the NE is equipped with multiple shelves, insert the slot
18 EC on each shelf.
Note: software mismatch and database unsynchronized alarms will appear.
These alarms will clear after the ECs are synchronized.
Wait at least 15 minutes and verify the software mismatch and database unsynchronized alarms
have cleared.

21

VIII. Set the network element date and time


Purpose

The network element date and time should be initially set manually using the network
elements internal clock. The network element can later be synchronized with a network
time protocol (NTP) server. This procedure performs the initial setting manually.

1. WebUI procedure :
Select the Date/Time menu item under Administration.

The Date/Time provisioning window appears.

Enter the current date and time and time zone settings and click the Apply button.
Note: All current WebUI users will be logged off.
22

2. CLI procedure :
Type config general date <date> and <Enter>.
Where date is of the format yyyy mm dd.
Type config general time <time> and <Enter>.
Where time is of the format hh mm ss, and hh is between 0 and 23.

IX. Disable ES port monitoring


Purpose

By default, the ES (Extension Shelf) ports on the EC packs are monitored. This will generate an alarm for
each port that does not have a lan cable connected. Therefore, if the NE does not have any extension
shelves, the EC port monitoring should be disabled.
Note: If the NE has extension shelves installed, this procedure should not be completed.

There is no need to disable the port monitoring.

1. WebUI procedure :
Expand Shelf 1 in the equipment tree and then expand each of the EC packs.
Select an ES port (ES1 or ES2) that is currently in alarm. The ES port provisioning window
will appear.

Uncheck the Port Enabled checkbox and click Submit.


Repeat the last two steps until all the ES port alarms have cleared.
23

2. CLI procedure :
Type config interface ec <sh/sl/pt> state down and <Enter>.
Where <sh/sl/pt> is the shelf, slot (1 or 18), and port (ES1 or ES2) of the ES port that is in
alarm.
Repeat the last step until all the ES alarms have cleared.

X. Update firmware on all circuit packs


Purpose

This procedure will ensure that the latest firmware is uploaded to all the installed circuit packs. This is
done by performing a cold reboot on the NE.

1. WebUI procedure :
Select the reboot tab from the system view.

Select the Cold Reboot radio button and click the Submit button.
The following warning message will appear. Click OK.

24

The NE will reboot. The reboot will take several minutes depending on the number of circuit
packs requiring a firmware upgrade.

2. CLI procedure :
Type config admin resetNE cold and <Enter>.
The following warning message will appear. Type yes and <Enter>.

WARNING:

You are about to perform a cold system restart.


This is a service affecting command.

Enter 'yes' to confirm, 'no' to cancel:

The NE will reboot. The reboot will take several minutes depending on the number of circuit
packs requiring a firmware upgrade.

XI. Configure additional system properties


Purpose

This procedure allows changes to system properties including temperature units and AINS
timer. The AINS timer value is system-wide and will become the default for all ports; the
value can be overridden on each individual port. See the Alcatel-Lucent 1830 Photonic
Service Switch 32/16 (1830 PSS-32/PSS-16) User Provisioning Guide, Equipment
Provisioning for more information on the AINS timer.

25

1. WebUI procedure :
Select System from the tree and the Details tab.

Select or type in the AINS Timer value to use as the system-wide default.
Select the desired value for the Temperature Units to be used in the system.
Click the Submit button.

2. CLI procedure
To change the AINS timer value, type config general ainstimer <hours> and <Enter>.
Where <hours> is of the format <hh> [<mm>]. You can also type config general ainstimer
help for the default value and range.
The temperature unit defaults to Celsius. To change the temperature units to Fahrenheit, type
config admin tempUnits fahrenheit and <Enter>.

26

27