This document shows how to configure AXXXEdge(9200) for ip over dcc interface.

There are 2 major steps to be carried out for login Step 1.Initial configuration thru CLI login. Step 2.Configuration thru Craft terminal session. A fresh node configuration should always be carried out starting with initial configuration thru CLI login.

STEP 1. CLI Login

1. Initial configuration through CLI is used to assign community-handler, management-node and IP address to the node. 2. Connect craft craft cable to VT100 port of the node. 3. Doule click on the computer icon on the bottom right corner of the craft terminal window.

4. 5. 6. 7. 8.

Give port name COM1 and press OK. Press ENTER to get the > sign on the window. Type axxcli and password axxcli. The prompt axxcli will appear. Type com to enter to Community-handler command prompt.

9. Type add manager=0.0.0.0 community=public access=super t=d and press enter. 10. Press dot . twice and enter to come back to axxcli prompt. 11. Type management to enter to management node command prompt. 12. Type sys sys=ipunnumbered and yes to confirm. 13. Press . Twice and enter to come back to axxcli prompt. 14. type ip ip=X.X.X.X subnet=Y.Y.Y.Y and press enter (X.X.X.X stands for the ip address of the node and Y.Y.Y.Y for subnet mask 15. type exit and press enter 16. The node is ready to have craft login session through cross cable. 17. The CLI.txt file shows the commands run on the system. N.B: The command axxcli>erase will erase the complete configuration database and the node has to be configured again starting from CLI login.

STEP 2: Craft Session

To get into the node thru craft terminal connect the cross cable to the mngt port on the AXX. 1. In the TCP/IP properties of the LAN port give ip of the node as laptop Gateway ip ,Subnet mask same as that of the AXX node and IP of the laptop different from the IP of the node. 2. In the craft terminal give ip of the node which was assigned thru the CLI login. 3. User name admin and password public and press logon.

4. The main window appears on the screen.

5. Click on slot1- unequipped and scroll down on the expected module to choose the type of card used in that slot .Save. Refresh the screen. Enable alarm reporting 6. The install state will change from installed and unexpected to installed and expected and the service state should be in service. 7. The s-shot below shows the final state.

7. Repeat the steps 5 and 6 for slot number 2 and the installed and expected card should be 63*E1 tributary card. Enable the Alarm reporting. 8. Open the slot-1 tree and Right-click on the SDH-1.1 and click structure. A SDH structuring wizard will appear. Keep clicking next till it asks for structure type. 9. ChooseTU-12 to cross-connect and click next and finish. 10. Repeat the step 8 and 9 for SDH 1.2 also and structure it to TU-12 level.

11. Click on the management interfaces in the management tree. 12. Click management Dcc on the right. 13. Change the mode on both the Dcc-M to Ip over DCC and save 13 Refer below for the screen shot

14. Click on the managementinterfaces on in the management tree. 15. Click the DCN router, enable IPunnumbered gateway and save.

16. Click on OSPF and set administrative status to Enable. 17. Click areaOSPF ,click Add on top and give the required area ID and save.Imp:The area ID once set cannot be changed unless we erase the whole node completely and reconfigure.

This completes the basic configuration in Ipunnumbered mode. Cross-connections can be made only after the SDH ports are structured. To make cross-connections. 1. Go to Equipment on top of main window and select cross-connect. 2. Press search now. 3. Under the available Tps will show all the KLMs from Port 1 and 2 and all the 63 E1 ports. 4. 1/1/1.1.1.1.1 means slot/port/C.B.K.L.M 5. Hence 1/2/1.1.3.7.3 means slot1, SDH port 2 the KLM is 3-7-3.C.B is constant 1.1 6. But 2/51/1.1.1.1.1 means slot 2 which is tributary card and port no 51 on the patch panel or E1 number 51. 1.1.1.1.1 is constant for tributary card. 7 To pass thru the KLM select slot1 port 1 KLM, Right click and select ADD.

8 9 10 11

select slot 1 port 2 KLM ,right click and select Set B and save. The connection will be shown in the right window and the graphical view can also be seen. To drop any particular KLM onto tributary port, select the tributary port first, right click and select ADD. Then select the KLM for the particular SDH port, right click and select Set B. Save the connection. To provide protection to the tributary port in step 9, complete step 9 and select the KLM of left SDH port, right click and select Set Prot and save. Below S-shot provide you with all the 3 examples.

Cross-connect window 1. 1/1/1.1.1.1.1(A) pass thru to (1/2/1.1.1.1.1) 2. KLM 1.1.2 from slot 1 Sdh port 1( B ) is dropped onto tributary port 1 of slot 2. 3. Tributary port 2 of slot 2 (A) is attached with KLM 1.1.3 from slot1 sdh port 1(B) and is protected by KLM 1.1.3 of slot 1 sdh port 2.(Protection).

12.It is recommended to make all the KLMs collectively pass thru. Then delete the required KLMs on the right window which are supposed to dropped locally. It makes the task easier. Click save after deleting and the deleted Tps will appear in the column of available Tps.

To set system time. 1. Go to equipment and select commissioning wizard. 2. click next till basic set-up. Fill information for the node in network element information 3. click next

3 In Expected service module check for any left out unequipped slots. if none click next until you find alarm reporting.

4 .In alarm reporting select the power modules which are used Click next.

5. In date and time , select synchronize to work station.

6. Click next and save.

To enable alarm status of the tributary port and giving the loops. 1. In the management tree open the slot -2 63XE1 card tree. 2. Click the particular pdh port being used. Change administrative status to Enable.

3. Open the PDH port further to find E1.Select the E1 and change administrative loop mode from no loop to the required loop and save. Two loops can be given network or ll2 loop and customer or ll3 loop

To define synchronization. 1. Go to devices in the management tree. Click synchronization on the right . 2. Click T0synchsource.Click ADD on top. 3. If clock source is E1 level which is dropped onto any tributary port 3.1 Click the E1 port of the selected PDH from where we have to give the clock. 3.2 Define the E1 mode as PRA . Default mode is TRA 3.3 Now in the T0syncsource frame select slot 2 and the port to the corresponding E1, disable SSM, administrative quality as PRC , give priority and save. 4. If providing SDH clock select slot1 1 port of the particular SDH, give priority and SSM is by enabled by default. 5. Save the changes. 6. Check for the operational quality of the clock. 7. Defining synchronization is necessary otherwise minor epj (excessive pointer justification) alarm will be there in the network.

This screen shows how to put the selected E1 mode to PRA.

This screen shows clock is defined at E1 and SDH level with different priority. This is only for explanation.

To upgrade software in the node.

1. The below screen shows the older running software version R2.0 ICS09.

2.Go to Equipment and select NE Maintenance. 3. Wait for 5 seconds. The window will expand automatically.

4. click on the Device and highlight the bank on the right screen. 5.click download on the top left of screen.

6. The new window may not contain the patch file for up gradation. Click on Add file to repository and fetch the file on the system. The file is attached.

7. Highlight the fetched patch and press next. 8. Select restart NE time immediately. 9 Select auto switch bank. 10 press next and finish. The screen below the process of downloading the file to the node.

After the download is complete the screen will appear showing the new software version successfully downloaded.

The version has been upgraded from ICS 2.0.9 to the latest version I.C.S 2.1.04. N.B: There is a change in the procedure for software up gradation in the node. The above mention procedure is carried out in Device in NE maintenance. Before doing this step on the device, the same above mentioned steps from step 4 till step 10 has to be carried for the System controller. By the time I have framed the document the up gradation has already been done, hence I am unable to provide the screen-shots but will mail you soon the procedure when I get to work on the fresh node.

POWER CONNECTION