Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0

Section 1 · Module 3 · Page 1
 This page is left blank intentionally

Document History

Edition Date Author Remarks

01 Jan/2013 ALU-University R4.4-AMS R9.1.10

01P01 Abr/2013 ALU-University R4.4-AMS R9.1.10

02 July/2013 ALU-University Madrid R4.5/R4.6 - AMS R9.2.30

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 2
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 3
 This page is left blank intentionally

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 4
 Page

1 Introduction 7
1.1 Management communication 8
1.2 Turn up procedure: User/Pswd, Itf Configuration 9
1.2 Turn up procedure: NTs CT port, Ntwk ports 10
2 Standard procedure 11
2.1 Turn up procedure using an access port: L1/L2 configuration 12
2.2 Basic concepts: Virtual Port 13
2.3 Turn up procedure using an access port: L3 configuration 14
2.4 Turn up procedure: SNMPv1-2 15
2.5 Turn up procedure: SNMPv3 16
2.6 Saving the management configuration 17
2.7 Manage NE in AMS 5520 18
2.8 The system interface (1) 19
2.9 The system interface (2) 20
3 Alternative scenarios 21
3.1 Alternative 1: LAG – Link Aggregation Group 22
3.2 Alternative 1: using an access port: L1/L2 configuration with LAG 23
3.3 Alternative 1: using an access port: L1/L2 configuration with LAG 24
3.4 Alternative 2: Turn up procedure using a network port 25
4 “7302/5520” Hands-on 26
4.1 Hands-on 27
4.2 Hands-on 28
4.2 Hands-on 29

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 5
 This page is left blank intentionally

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 6
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 7
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 8
 CT Cable Pin-out
NANT-D/E, FANT-F

PIN-OUT

DB-9S (RS232) RS232 RJ45

FEMALE 1 2 RJ45
2 5
PC SIDE
3 6
ISAM SIDE
Soldering view Connection view 4 3
5 4
6 1
7 8
8 7
9 X

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 9
pos:isadmin># configure port ?
- no port {<port-id>}
- port {<port-id>}
<port-id> : <nwport-id | ltport-id>
nwport-id - <slot-address>:<port-type>:<port-num>
slot-address - nt|nt-a|nt-b|ntio-1
port-type - sfp|xfp|vp|eth|ieee1588|AI
port-num - port-number
ltport-id - lt:<rack>/<shelf>/<slot>
lt - keyword
rack - number identifying the rack
shelf - number identifying the shelf
slot - number identifying the slot
[no] description - Add/remove a text description for the port
ethernet + Configure attributes for an ethernet port
[no] shutdown - Administratively enable/disable the port

Example
configure port nt-a:sfp:1 …
configure port nt-a:eth:1 …
configure port nt-a:xfp:1 …

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 10
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 11
Traditionally the management VLAN was 4093, which was the factory default. The NANT-D/E amd FANT-
F have no default management VLAN. In fact the VPLS created is simply a regular VPLS like any other
VPLS carrying customer traffic!

For untagged outband management use 0 as vlan tag in the sap, e.g.: sap nt-a:sfp:3:0

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 12
The virtual port is visible on the VPRN, but not on the v-VPLS.
Here the SAP on the V-VPLS, representing VLAN 4080 is linked to the L3 interface of the IES (i.e. the base router)
with the management IP address of the ISAM.

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 13
Be aware that the management interface is created in the base router and has no special status. If it is
reachable from somewhere (depending on the VPLS SAPs) you can log-in to the ISAM, even if the log-in
attempt comes through an LT SAP! If you want to avoid this, you will have to install an IP filter on the
interface. It is, by the way, perfectly possible to create multiple management interfaces with different
IP addresses (linked to different VPLSs).

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 14
Before you enter the command “configure system security snmp community NETMAN ip-addr <ip-addr of
AMS>” context ihub, you’ll see that there’s SNMP connectivity towards the ASAM-CORE but not towards
the IHUB (Reachability test).

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 15
Within the SNMP group, you set the security level:
-Without Authentication and Without Privacy
-With Authentication but Without Privacy
-With Authentication and With Privacy

As Authentication protocol there are two options:

MD5
SHA
As Privacy setting (Encryption protocol) you have the following options:
DES
AES-128
AES-196
AES-256
DES: Digital Encryption Standard
AES : Advanced Encryption Standard (number refers to the length of the symmetrical key used, in bits)

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 16
The IHUB database is automatically saved in the overall database every so many minutes. Therefore it is not
needed to save it explicitly as it will automatically be done. However if you’re performing configuration changes to
the IHUB and reboot immediately it’s mandatory to save else you’ll loose some configuration changes.

After re-activation with clear-db, the IHUB config is completely empty as is the protected storage.
CLI command: admin software-mngt oswp [1…2] activate clear-db
When no action is taken to save a protected config (e.g. with management config), a subsequent re-activiation
with-default-db will also remove management config!
CLI command for re-activating with-default-db: admin software-mngt oswp [1…2] activate with-default-db

Although the intention of protected storage is to store the management configuration, the operator is free to store
any configuration he sees fit.
The only requirement is that the configuration is first saved in the normal way (admin save).
The save-protected command actually stores a copy of the regularly saved configuration in protected storage (not
the running configuration)!

Therefore:
•When re-activation with default db, the management config is restored
admin software-mngt oswp [1…2] activate with-default-db

•When re-activation with clear db, no management config is restored

admin software-mngt oswp [1…2] activate clear-db

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 17
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 18
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 19
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 20
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 21
LAG – Link Aggregation Group: group of physical ports that are put together in a group to function as 1 logical link.
Once created, the LAG can be used everywhere in the configuration where we can use individual physical ports.
E.g. with the definition of a SAP:
Sap nt-a:sfp:1:300
Sap lag-10:300
Where lag-10 is the name of a LAG that contains the port nt-a:sfp:1
But, once a port is used in configuration, the only way to get it in a LAG afterwards is to tear down all
configuration using that port. So if there is even the slightest chance of using LAG at one point in time, it is better
to put it in a LAG from the beginning (even if that means it will stay alone in that LAG).

All ports in a LAG must share the same characteristics (speed, duplex, hold-timer, etc.). Therefore, auto-
negotiation must be switched off.
Once a LAG is created and ports assigned, changes can only be made to the primary port configuration, and
changes to the primary port configuration are automatically made to the non-primary ports.
When a non-primary port is removed from a LAG, it retains the same characteristics it had while it was a part of
the LAG (it does not revert to the default settings)

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 22
Traditionally the management VLAN was 4093, which was the factory default. The NANT-D has no
default management VLAN. In fact the VPLS created is simply a regular V-VPLS like any other VPLS
carrying customer traffic!
It might be a good idea to put the network port, used for management in a LAG from the beginning

For untagged out-of-band management use ‘0’ as VLAN tag in the sap, e.g.: sap lag-11:0

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 23
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 24
From R4.1 onwards!!!
Traditionally the management VLAN was 4093, which was the factory default. The NANT-D/E has no
default management VLAN.

For untagged management use 0 as vlan tag in the port, e.g.: port nt-a:sfp:1:0

Be aware that if you configure nt-a:sfp:1 as a network port, you will not be able to run v-VPLS services
with SAPs (VLAN emulation) over it.
The port can only be used for normal routed traffic and MPLS traffic (which can be bound to VPLS
services via SDPs).
If you need both SAPs and SDPs to the same router/switch, you will need two different ports (one in
access mode and one in network mode).

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 25
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 26
Perform the exercises with CLI and AMS where possible
Resetting the 7302 ISAM retrieval exercises

What is the IP address of the ASAM-CORE ?

What is the external management VLAN that we use for the management of the ISAM? Are we using inband or
outband management?

Delete the ISAM in 5520 AMS equipment perspective and check your connections. Does the setup of the PPP
session still work ?

Create the ISAM again in AMS with the same parameters and bring it to the supervised state. Browse through
the different views and check if something has changed. Why (not) ?

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 27
Resetting the 7302 ISAM Configuration exercises

The MIB database(s) of the ISAM will be cleared (by the teacher). In addition, the ISAM will be deleted in 5520
AMS.
Bring the ISAM back up with all parameters required to make sure that you can supervise the ISAM again with
the AMS. Create the ISAM again and bring it to the supervised status. Follow these requirements:

>We want to work in a way that our ISAMs are grouped per region. Use the NE groups “North" and “South".

>Do you see a difference in the 5520AMS concerning the configuration of the ISAM compared to the situation
that you had before the MIB was cleared? Why (not)?

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

TAC42047-HO02 Edition I2.0
>Delete the AMS as SNMP manager. ExplainSection
what 1happens.
· Module 3 · Page 28
Copyright © 2013 Alcatel-Lucent. All Rights Reserved.
TAC42047-HO02 Edition I2.0
Section 1 · Module 3 · Page 29