7342GPON

University
System turn up
7342 FTTU operator
Alcatel-Lucent University Antwerp

1
During class please switch off your mobile, pager or other that may interrupt.
Entry level requirements:
3FL 00458_G AAAA WBZZA ED 01
2007 Alcatel-Lucent., All rights reserved
Objectives
At the end of this session, you will be able to
set up the 7342 FTTU from scratch,
get the 7342 node managed from the AMS,
and put the ONT software on the node
Table of contents
GPON node management
p.4
GPON management VLANs
p.8
System turnup
p.10
Management from AMS .
p.17
Get rid of alarms .
p.20
MAC address aging .
p.26
ONT software download .
p.28
Hands-on
p.33
University
GPON node management
7342/5523 operator
Management entities
a 7342 node is two separate entities
from management point of view
service hub
y set-up of VLAN (e.g. new ISP)
y service specific functions performed
on service hub
LT shelf
y rest of the FTTU
y set-up of VLAN
y service specific functions performed
on ASAM-CORE
y configure end users
CLI agent
service hub and LT shelf do

contain
SNMP
a separate SNMP agent

a separate MIB
TL1
CLI
SNMP
MIB
MIB
LT shelf
SHUB
> The 7342 FTTU node actually is two management entities

the service hub: SHUB
the ASAM-core LT-shelf
> Logical access to these entities is either through SNMP or through a man machine interface.
Management access
7342
FTTU
Remote NMS
or CLI
NMS
LT
Remote NMS
or CLI
NT
service
E-MAN
hub
.
.
.
LT
Remote NMS
or CLI
ACU
TL1 & CLI

RS232/Ethernet
> Logical access to the 7342 FTTU node uses

CLI Command Line Interface
management of service hub
TL1 Transaction Language number 1
management of ASAM-core
management via AMS
management of ASAM-CORE and service hub
> Physical access to the node can be local or remote.
> --> Remote CLI = telnet or ssh
> NMS = Network Management Station
Management strategy
inband management
use the same interface as the user data path
a network link of the service hub is used for OAM data and for user data
outband management
use a different interface as the user data path
a dedicated link of the shub is exclusively used for OAM data
University
GPON management VLANs
> This chapter describes the steps to take for getting your node under supervision of the
manager.
> Basically this comes down to configuring an IP-address and a default router in the node.
VLANs used for management

Internal Communication VLAN
a.k.a. IC-VLAN
internal communication between
controller (NT) and ASAM I/F
E-MAN
controller
ASAM link
94
40
typical vlan-id(s):
network
links
AN
VL
internal Eth ports of the ASAM
control
link
ASAM link
4091, 4092 and 4094
External VLAN
network
links
E-MAN
EXT. VLAN***
a.k.a. the management VLAN

used for AMS to node
communication
typical vlan-id:
control
link
L
T
L
T
controller
ASAM link
ASAM link
L
T
L
T
4093
> The drawing looks similar to but is different from the ISAM: the ISAM does support subtending
access nodes and direct user links, where the GPON node does not!
University
System turn up
10
manager.
10
Prerequisite
RS232:
9600
8/1
no parity
no flow control
FTTU
Login: isadmin
Password: i$@mad- (first time)
New password: xxxxx
Confirm new password : xxxxx
initial setup serial link terminated on the ACU
11
Connect via RS232 port on AACU

DCE DB9 interface
ASCII coding
9600 bps
8 bits / 1 stop bit
no parity
no flow control
11
Configure date and time

set-dat:::::5-30-08,14-22-11;
sets the date and time
m-d-y, h-m-s
LT
NT
LT
12
> set-dat is needed before you define the cli-password!

> Default date and time for the system is 01/01/1970, 00:00 (also point zero in time for UNIX)
> Assume you forget to set the date and time. Then log in to the system with cli for the very first
time: you are forced to define a password, e.g. ANS#150.
> Then you define the date and time (TL1): there will be a big time jump. Next time you login to
the system using cli, it detects your login was used more than 37 years ago ;-)) and forces you
to change your password again (e.g. to ANS##150)
12
Configure IP settings
ent-ipport::ntenet:::manual:
ipaddr=172.31.79.193,
netmask=255.255.255.128;
set-ne-all::com::::
IP
memalm=,
shutprep=,
sntp=,
defrouter=172.31.79.129,
authsuper=local,
lanxmac=00-0c-86-10-a8-34;
LT
NT
LT
MAC address used by LANX

must be unique
13
> Although the 7342 FTTU is two entities from management point of view, they share the same
IP-address ( single ip-address mode for ISAM).
> The commands to define the IP-address, netmask, default gateway, are TL1 commands.
> You can get access to the system via one of the optical ports of the NT, or via the ethernet
interface available on the ACU:
ntenet -> optical access via NT
acuenet -> electrical access via ACU
> The system can receive an IP address either statically (by manual configuration) or
dynamically (by bootp).
> If you do plan to use ACUENET as the OAM network, the default IP must be removed with
DLT-IPPORT before creating the OAM network with your own OAM subnet.
> --> The MAC address of the NT can be found
on the label present on the stiffener of the EHNT,
or with the rtrv-ipport command.
> To make the MAC address of the lanx/shub unique, one can e.g. use the MAC address of the
NT+1.
> --> If the NT Ethernet interface (NTENET) and the ACU Ethernet interface (ACUENET) need to
be provisioned, they must be on different subnets.
13
Configure system VLANs(1/2)

set-ponvlansys::com::::
ageing=,
arptblrefresh=,
tndvlan=,
brcmvlan=,
mgmtvlan=4080;
LT
IP
NT
LT
14
> Next thing to do is defining the system VLANs. They are:

trace and debug vlan (4091)
broadcom vlan (broadcom stacking) (4092)
management vlan (4093)
> Default values are shown between brackets.
> Both the ASAM-core as the service hub needs to know the management VLAN-id, which by
default is 4093.
> If you plan to use the default management vlan id (=4093) you can skip this step.
> If you plan to use a different value (999 in the example above), you also need to define the
management VLAN on the service hub.
14
Configure system VLANs (2/2)

configure interface shub port 1
port-type network/outband-mngt
LT
admin-status auto-up
NT
configure vlan shub id 4080

mode reserved
LT
egress-port network:1
untag-port 1 (optional)
configure bridge-shub port 1
for untagged management traffic
pvid 4080 (optional)
[admin software-mngt shub database save]
15
> Before you can configure the management VLAN at the service shub, the management port
has to be up, and thats exactly the function of the first command on this slide!
> If you didnt forget to configure your (management) network accordingly, you should be
capable to ping the 7342 FTTU node.
> From now on you can telnet/ssh into the node, but you cannot manage it from the
management platform yet!
15
Configure SNMP community strings

configure system security snmp
community NETMAN host-address 172.31.79.148/25
context shub
configure system security snmp

community public host-address 172.31.79.148/25
public
NETMAN
CLI agent
SNMP
TL1
CLI
SNMP
MIB
MIB
ASAM core
SHUB
16
> From now on the node is also accessible/manageable from the management platform.
16
University
Management from AMS R8
17
17
Create NE
18
18
Bring node(s) under supervision
LT
NT
LT
supervision start
the node registers the AMS as a trap destination
19
This can be verified using the following cli- command:

# info configure system security snmp
You then should find a notify profile which originally was not there!
19
University
Get rid of alarms
20
20
Getting rid of alarms using TL1

set-sid:::::gpon193;
sets the system identity
LT
ed-syncn::clksrcnt::::srcselsch=loc;
NT
sets the synchronisation channel to local
if you prefer synch to use the BITS interface,

use extloc
LT
set-ne-all:: ontswact=auto ;
the ont will automatically activate a freshly downloaded swimage
otherwise: force a reset of a single ont (init-sys)
set-sntp-all:
set-attr-eqpt::eqpt:::nr,lanxlinkfail,,;
21
> These commands are not needed for getting the management channel operational, but are
very typically executed when a node is brought online for the very first time.
> BITS = Building Integrated Timing Service
> This clears the 2 alarms regarding timing reference (see rtrv-alm-all)
21
Configure the synchronisation channel
22
22
Configure the SNTP server
23
23
Configure ONT software activation
24
24
Configure the alarm severity template
25
25
University
MAC address aging
26
26
Configure aging timers

(1)
network
interface
NW
(3) access
interface
OLT
SHUB
OLT
(2) control
interface
# configure bridge-shub ageing-time 300
< set-ponvlansys::com::::ageing=300;
27
27
University
ONT software download
28
manager.
28
Copy ONT software from CD to AMS

Prerequisite step
ONT software files must be present on AMS
directory:
/opt/ni/ne/software
FTP
29
29
ONT software file preparation
30
> First you might have to add some hardware related info in the upper window pane.
> But you definitely need to add an ONT load: click on the add-button, select the ONT file
name, the release, load type and default. Optionally you can provide a description.
> This will copy the file named FE50854AFNA12
from /opt/ni/ne/software
to /opt/ni/ne/ONT/I-221E-A
30
Download ONT software to NE

copy the ONT software to the node
triggered from the AMS GUI:
select NE(s)
select ONT type
select SW load
using ftp under the hood
FTP
N
T
L
T
L
T
31
> Getting ONT software on the ONT itself typically happens at ONT provisioning time!
31
Download status
software download status can be viewed from
the S/W Status view:
32
32
University
Hands-on
33
33
Startup from scratch

For doing the next set of exercises, a couple of teams have to join together as not every team
has its own GPON node.
1. Get the GPON node back to the factory defaults state. But before doing so check the current
management channel related settings like the IP-address, netmask, default gateway,
management VLAN and so on!
2.
Make sure the node is reachable ip-wise using the settings retrieved in exercise 1.
3.
What do you need to do to get the node reachable and manageable from the AMS too?
4. Get rid of the alarms using AMS!
5.
Make sure the ONT-software is present on the node to simplify ONT provisioning.
34
www.alcatel-lucent.com
35
35

7342GPON

Uploaded by

Copyright:

Available Formats

7342GPON

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7342GPON

Uploaded by

Copyright:

Available Formats

What are the objectives of the training session?

What are the objectives of the training session?

What are the different management entities of the 7342 FTTU node?

What are the different management entities of the 7342 FTTU node?

University

7342 FTTU operator

Alcatel-Lucent University Antwerp

Alcatel-Lucent University Antwerp

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

GPON management VLANs

Management from AMS .

Get rid of alarms .

MAC address aging .

ONT software download .

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

Alcatel-Lucent University Antwerp

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

service hub and LT shelf do

a separate SNMP agent

> The 7342 FTTU node actually is two management entities

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

TL1 & CLI

> Logical access to the 7342 FTTU node uses

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

Alcatel-Lucent University Antwerp

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

VLANs used for management

internal Eth ports of the ASAM

4091, 4092 and 4094

a.k.a. the management VLAN

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

Alcatel-Lucent University Antwerp

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

initial setup serial link terminated on the ACU

Connect via RS232 port on AACU

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

Configure date and time

> set-dat is needed before you define the cli-password!

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

MAC address used by LANX

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved

Configure system VLANs(1/2)

> Next thing to do is defining the system VLANs. They are:

3FL 00458_G AAAA WBZZA ED 01

2007 Alcatel-Lucent., All rights reserved