Alcatel Hands On Exerc7302/5523 Operator Hands-Onises Answers

2005 ALCATEL BELL N.V.
ALL RIGHTS RESERVED
Broadband Access
7302/5523 Operator
Hands-on
Exercises Answers
University
Exercises - Answers
7302-7330/5523 operator part 1
Alcatel-Lucent University Antwerp
Alcatel-Lucent University Antwerp

1
3FL 00324 AAAA WHAAA Ed 01
Alcatel 5523 & 7302 Hands-on Exercises
2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED
Table of contents
Getting started with the CDE & Alcatel 5523 AWS
p. 3
ANEL features of AWS
p. 5
License Key of 5523 AWS
p. 7
Basic equipment setup with AWS/CLI
p. 8
Cross-connect. : VLAN setup and end-user setup
p. 25
IP-aware bridge : VLAN set-up and end-user setup
p. 35
Resetting the Alcatel 7302 ISAM
p. 39
Backup / restore of ASAM-CORE and service hub
p. 43
Fault management
p. 46
3FL 00324 AAAA WHAAA Ed01
Alcatel-Lucent University
Getting started with the CDE & Alcatel 5523 AWS
Objectives
After completing the assignments in this chapter, the trainee will be able to:
Log on to the Alcatel 5523 via the Common Desktop Environment (CDE)
Start and stop the AWS processes
Monitor and interpret the AWS status (including process status)
Use the CDE to navigate between different USMs
References
Alcatel 5523/7302 Hands-on (3FL 00324_A AAAA WBZZA ED02)

Customer Documentation: Alcatel 5523 AWS Administration User Guide
Logon
1. Log on to the AWS. The trainer will provide you with logon-ids and
passwords.
Fill in your logon-id and press enter. Next, give the corresponding
password and press enter again. The Solaris desktop should open.
2. What is the version of the AWS?
In the right bottom corner of the desktop you should see the AWS icon.
Open the AWS menu by clicking on the triangle. Clicking on the
adminstration icon , opens a new window .Dobble click on the versionicon shows the different versions of all the processes that make up the
AWS.
3. Set up the CDE so that you have the network elements view (ANEL) in one
"workspace" and the NE you will be working on (EML) in another.
Move the applications in the different workspaces, e.g. One, Two.
Note: you should open ANEL and EML before you can move them.
Moving is done by right clicking on the application, choose Occupy
Workspace and select the correct workspace.
Start / Stop the

AWS
1. Is the AWS currently running? How is this indicated? What is the status? How
did you check the status?
Via the Administration Maintenance menu, start the Status
application (marked with a big yellow ?). The color represents the
status. You can also check the status via the minimized Process
Monitoring window
2. Is it a stand-alone or distributed set-up that you are working on? How can you
see this? Give 2 possibilities.
Via the Status Window. Workstation and type of Workstation are
specified
Via Process monitoring, in the tree view all the processes are visibly
divided per workstation. The first visible workstation is always the
master.
3. Make sure that you can see the AWS status, without keeping the processingmonitoring window open.
See previous answer. Minimize the Status window (or the Process
Monitoring window). The minimized window shows the color. If one
process is failing or acknowledged, the minimized status window will be
red. The process-monitoring window makes the distinction (red for
failing process, blue for acknowledged process).
4. Start the AWS processes (guided by the teacher, because this assignment is the
same for all the groups), and make sure that you can see the different processes
starting up one by one.
Via the DPC Process Monitoring (Administration Maintenance
Process Monitoring). Expand all the processes (clicking on the + in front
of the AWS process) and right click on the top-level process. From here
you can start/stop all sub-processes, and you can monitor them.
Review
Questions
1. What is the application to start when you want to see the network elements?
ANEL or Network Elements
2. How can we be notified in a very simple way that something goes wrong with
a process?
When the minimized Status window or the minimized Process Monitoring
window turns from green to red. See previous questions.
3. What is the application to open when you want to see the different boards of
the NE?
The EML-USM window. Open Network Elements, double click on an
NE, and double click on a subrack.
4. How can you have more details on the running processes?
In the DPC process list (Process Monitoring), simply select a process and
right click - Show info. You can also select a process and go to the Actions
menu - Show info.
ANEL features of AWS
Objectives
Modify the list of network elements.
Apply a filter to the ANEL view.
Perform a search on specific NEs, boards, etc.
Check the load of IM-processes.
Check the reachability of the NE (IP and SNMP connectivity).
Retrieve a list of VLANs defined on the AWS (per mode).
Search which VLAN-ids are still available.
ANEL
1. You have a very large network. The NEs are organized in a lot of different
folders/locations. You had to go away for a while. You want to have a fast
view on all the supervised NEs in the network, which have critical and major
alarms.
ANEL view: First make a flat view via Views Layout - Flat. This way
all the NEs are visible on the screen.
Then create the appropriate filter via Views Filter: Add condition select Alarm Status - Is at least - major. (If you select "Alarm Status is
equal to major", you have to select a similar condition for critical alarms
and you have to select "match any of the following".)
2. At a certain moment, the decision has been made to replace all EBLT-C/J
boards. As an operator, you need to know which NEs need to be visited by a
field engineer. Retrieve all the NEs containing EBLT-C/J boards.
Select all the supervised NEs and go to Views Find Boards.
Select the correct type (in the column installed boards) and the result will
be shown in a new window.
3. Customer "Smith" calls the helpdesk (you). He has some problems with his
connection. You don't know to which ASAM he is connected. How can you
quickly find the port of that customer?
ANEL view (select one or more NEs): Views Go to port by customer
When the ASAM is not supervised or isolated, the option "go to port by
customer" is grayed out.
Remark: the administrator can disable this option. (Administration Customization - System Tuning). See Advanced AWS Operator course.
4. Check the IM load of EML-IM process 100.
ANEL view: Views IM load
5. Check the IP connectivity between the AWS and your NE.

ANEL view, select NE: NE Reachability test
6. Stop the supervision on the NE and try again. What happens and why?
ANEL view, select NE: NE Supervision Stop. The NE is still
reachable! Stopping the supervision only stops the management and no
alarms are reported but the connection is not lost!
7. How many Residential Bridge VLANs are created on the AWS?
ANEL view
Service
Definition
Show (Select: RB VLAN)
8. Is VID 101 still free? Is there no VLAN with VID 101 on the AWS? (How do
you find a list of all free VLAN IDs?)
Service
Utilities
Get Free VLANs
ANEL view
License Key of 5523 AWS
Objectives
License key
After completing these assignments, you will be able to:

-
Identify the place where to adapt the license keys
Retrieve license rights and actual usage
1. Until what date is your license for AWS-CORE valid?

What is the host ID of the AWS?
Go to Administration Maintenance - License and select AWS-Core to
see more details (a.o. validation period and host id).
2. How many ADSL2+ lines does the license allow to be configured? And
how many ADSL2+ lines are currently in use?

Go to Administration Maintenance - License and select ADSL2+ to
see more details (a.o. number of lines allowing ADSL2+).
3. Is the number of used ports affected when you stop supervising an NE
that has configured EBLT boards?

Go to Administration Maintenance - License and select AWS-Core to
check the number of used ports. Then go to the ANEL view and stop
supervising an NE with configured EBLT boards. After that you check
the license usage again. The number of used ports will have decreased.
4. Try to find the number of users that are currently logged on. Which user-id are
they using?
Go to Administration Maintenance - License List logged in users
Go to Administration Session List logged in users
Basic equipment setup

With the Alcatel 5523 AWS
And with the full CLI
Objectives
After completing the assignments in this chapter, the trainee will be able to
configure and retrieve information on:
References
Profiles
Ports and connections
STP
LACP
Alcatel 5523 AWS (3FL 00324_C AAAA WBAAA Ed 02)

Alcatel 5523/7302 Hands-on (3FL 00324 AAAA WBAAA)
Alcatel 5523 AWS: customer documentation
Perform these exercises with CLI and AWS unless specified differently
Retrieval of
equipment
information
Using the AWS, how can you navigate from ANEL to the rack view of your
ISAM (2 possibilities)?
Double-click on ISAM
Via ANEL: select ISAM Views Equipment
There is no way that you can physically go to the ISAM. How do you know
the HW version of the shelf that you are working on? (ASPS-X, ALTS-X, )
AWS:
1) Go to EML-USM of the ISAM. Click on Subrack sub-menu.Goto
Show.The HW version of the shelf is displayed next to Detected Type.
Via Full CLI: The command show equipment shelf gives you errorstatus: no error. This means that the configured shelf and the installed
shelf match.
To see the configured shelf enter the command show equipment shelf
detail or show equipment shelf 1/1 detail or configure equipment shelf
1/1 info detail or info configure equipment shelf 1/1.
Without going physically to the shelf, how can you see if there is an NT I/O
inserted in the ISAM?
Via AWS: Go to EML-USM shelf view, on the GUI you can
immediately see whether an NT I/O is present or not.
Via Full CLI: Enter the command Show equipment applique 1/1/2.
Then you can only see the actual type, not the planned type. You can
verify the planned-type with the command configure equipment applique
1/1/2 info detail.
The command Show equipment applique 1/1/2 detail gives you some
more information. Here you can see the actual type (plugged) and the
planned type.
How many boards are configured on the ISAM?

Via AWS: Go to EML-USM shelf view. On the GUI you can see which
boards are configured. Configured boards appear in white
Via Full CLI: The command configure equipment <enter> info detail
gives you not only the information on slots, but also information on
appliques, shelf, rack and system.
Which boards are actually inserted in the ISAM?

Via AWS: Go to EML-USM shelf view. On the GUI you can see which
boards are configured. If a board is configured but not installed, the
board will come up with a missing board-tag. You can also recognize
slot positions with plugged boards that havent been configured.
Via Full CLI: The command show equipment slot gives you
information on all slots. The slots where the Type field indicates
EMPTY, are the slots where physically no board is installed.
Find the inventory/FPBA code of one of the boards physically inserted in the
shelf. How do you find this information?
Via AWS: Go to EML-USM shelf view, select the board. Go to board
show remote inventory.
Via Full CLI: The command show equipment slot Rack/shelf/slot
detail gives you the requested information.
The inventory/FPBA code is e.g.: 3FE21641AAAA.
Retrieving port
/connection
information
Ask the teacher which board and ports to use for the retrieval
exercises!
1. Which xDSL line profiles are present on the ISAM?
Both xdsl spectrum profile as xdsl service profile exist.
Via AWS: Go to EML-USM view. Go to configuration
show.
profiles
Via Full CLI: the command show xdsl profiles gives you the next
available index that you can use to configure a new profile. But you do not
see how many profiles are actually created. When the next available index
is e.g. 3, it doesnt mean that index 8 is not yet created.
If you want to see the profiles created, you need to go via the command
configure xdsl info . This command gives you all the profiles created on
the ISAM but also all the xdsl-ports configurable at this stage.
Index 0 for service profile and spectrum profile indicates that the xdsl-line
is not configured.
2. Which ports are configured on your board?

Via AWS: Go to EML-USM board view. Make sure you are in
expanded view. (++ sign)
Via Full CLI: Use the match (filter) command . Configure>xdsl> info
| match after exact:1/1/x . The output will then also give all the info of the
ports on slots x + 1,2, . You can stop the output by typing <control> c
3. Which xdsl line profiles are installed on your user port Training-a?
On port level xdsl line profiles are configured.
Via AWS: Go to the EML-USM board view. Go to Port Show and
activate the General tab. This will display the used profiles. Clicking on
the show button opens the profile details.
Via Full CLI: via the command configure>xdsl>line
rack/shelf/slot/port# info detail. You retrieve the indexes of the profiles.
For more details on the used profiles, use the configure xdsl service/
spectrum-profile x info detail command
4. Which line rates are configured on your port?
activate the General tab . Click on the show button next to the xdsl service
profile. .
Via Full CLI: first you need to know the profiles configured on your
port. These can be retrieved by the command configure>xdsl>line
rack/shelf/slot/port# info detail
The physical line parameters are configured via the service-profile .
configure>xdsl>service-profile>x# info detail gives you the requested
information.
5. What is the minimum alarm severity reported on your port?
activate the General tab and check the alarm configuration window pane.
In this window you find the minimum severity reported on your port.
Via Full CLI: The alarm severity reporting mode is configured on xdslinterface level.
configure>interface> port >xdsl-line: rack/shelf/slot/port# info detail
gives you the alarm severity reported on the port.
10
6. How many ATM-connections are configured on the xDSL-port Training-a?

Display a list of all VP/VCs used on your port. How did you find this
information?
| Via AWS:
Double click on a customer port. This way the port-view
window appears. Here you can count the number of ATM connections.
The connection tag ( ) on the board view window doesnt give you an
indication on the number of connections.
Via Full CLI: show > atm > interface 1/1/slot/port (to see the number)
configure >atm> info | match exact rack/shelf/slot/port (to get the list)
7. Which Ethernet ports are configured on the ISAM?

Via AWS: Go to the EML-USM board view of the NT-board. The 24
Ethernet ports available on the ISAM are shown. The ports in the unused
state are not configured. ASAM ports and the control port are not
configurable. You can only perform show commands on these ports
Via Full CLI: Ethernet port is an interface on the SHUB.
configure>interface> shub> info | match after exact port (otherwise you
also get IP interfaces and vlan interfaces). Port type unused, or port type
not mentioned means that the Ethernet port is not configured.
Via the command show interface shub port you can see the status of
these ports.
8. What is the configuration of network port 1?
Via AWS: Go to the EML-USM board view of the NT-board. Network
port 1 is Ethernet port 18. Click on the port, go to Port Show
Via Full CLI: Ethernet port is an interface on the SHUB .
configure>interface> shub>port>1# info detail.
Or you can enter the command: info configure interface shub port 1
detail
Port-Type is e.g. out-band management or network.
9. You are not able to physically access the ISAM. How can you verify if your
Ethernet ports are up?
Via AWS: Go to the port view of the NT board. Active ports are
indicated via a green v-sign ( ).
Via Full CLI: Ethernet port is an interface on the SHUB. show
interface shub port 1 (oper-status: up)
11
Basic
configuration
of ISAM
Ask the teacher which board and ports to use for the configuration
exercises!
1. Create an EBLT-C board in one of the free slots via the AWS/CLI. What are
the default settings? Verify your configuration on CLI/AWS.
Via AWS: Go to the EML USM shelf view
Board
Accept (in case
the board is plugged in).
Use Board
Create when the board is not plugged in yet.
Via Full CLI: The command configure equipment slot 1/1/x plannedtype eblt-c.
Default settings are unlocked and no power down.
2. Configure 2 ports, port x and port x+10, on the board assigned to you by the
teacher, so that they will operate in the following conditions.
- Operational mode: ADSL
- Upstream synchronizing at 350 kbps
- Downstream synchronizing at 7 Mbps
- Provide customer id to your liking
- For other parameters keep default profile settings. Use your own profiles!
Configure port x with AWS
configure port x + 10 with CLI
Only port x has a modem physically connected. Make sure that on that port the
modem synchronizes!
Note: x=ADSLx
To configure the xdsl port, first the service and spectrum profile need to
be created on the ISAM. Once they are present on the ISAM they can be
applied to an xdsl port
Via AWS: Create Profile Templates on the AWS (In the ANEL
window). Download them to ISAM. ISAM considers them as profiles. To
apply the profiles on the port, go to the EML-USM board view, select the
port, go to port port configure
Via Full CLI: Configuration of service and spectrum profile with CLI
is done via the command configure xdsl service-profile/spectrum profile
<index> name <xxxx>.
Now the profile is created with default parameters. Now you can modify
the parameters you want.
Make sure that you activate your profile, otherwise you will not be able to
apply it to an xdsl port.
Note: via the show xdsl profiles you are able to retrieve the next available
index id that you can use.
Once the profiles are created, apply them to your port via the command
configure xdsl line <port id> service-profile <x> spectrum profile <y>
Note: When configuring the xdsl line for the first time, you need to specify
service and spectrum profile together. Afterwards you can modify one of
the two profiles independent of the other.
The last step is the configuration of the xdsl interface via configure
interface port xdsl-line <port id>. Here you configure the user id and
default alarm setting of the port.
12
From now on perform the exercises on the port where the

modem is connected. (= port x )
3. How do you know if the modem is synchronized?
Via AWS: Go to the port view of the LT board. Synchronized (active)
modems are indicated via a green v-sign ( ). Otherwise, a red cross ( ) is
shown.
Via Full CLI: The command show interface port xdslline:rack/shelf/slot/port gives you Operational status of the interface.
Note: It is necessary to check this, because the ISAM remembers the rate
at which the modem synched the last time, even though the modem is not
synched anymore.
4. What is the physical bit rate at which the modem is synchronized?

For a modem connected to an ADSL board
via AWS In the Port Show window on the Channel/RI tab you find
the upstream bit rates in the XTU-C column and downstream bit rates in
the XTU-R colunmn (bit rate and Max. Attainable Bit Rate).
Via Full CLI: via command
show>xdsl>operational-data> line rack/shelf/slot/port
5. On the port where the modem is attached to, create an ATM termination point
using VPI/VCI value 8/35, encapsulation type LLC/SNAP for IPoE/PPPoE,
with AWS.
Via AWS: Go to the EML-USM port view. Select connection Create
ATM termination. Provide VPI/VCI value and leave AAL parameters
to default
6. Create an ATM termination point using VPI/VCI value 8/36, encapsulation
type LLC/SNAP for IPoE/PPPoE, with CLI.
Via Full CLI: This requires two separate steps
Step 1: Configure atm pvc <Rack/Shelf/board/port:VPI:VCI> <enter>.
From now on you can also configure/modify the AAL parameters by going
to the configure>atm>pvc> Rack/Shelf/Board/Port:VPI:VCI$ prompt.
Step 2: configure the bridge port no vlan id, tag, qos parameters defined
at this stage. These parameters need to be filled in when the bridge port is
associated to a VLAN. Use the command:
configure bridge port <Rack/Shelf/board/port:VPI:VCI>.
Retrieving STP
info
1. What are the STP (or RSTP) parameters on the system (bridge parameters, e.g.
hello time, forwarding delay)?
Via AWS: Go to EML-USM view. Go to configuration STP show
config.
Via Full CLI: show rstp port-info
2. Which Ethernet ports on the SHUB are in the forwarding state?
Via AWS: Go to EML-USM board view. Select a network port on the
13
NT. Go to port show.Select the Operational tab

Via Full CLI: show rstp port-info.
3. Is LACP enabled?
Via AWS: Go to EML-USM view. Go to configuration LACP
show
Via Full CLI: configure la > info detail (no disable-lacp means that
LACP is enabled)
4. Create a link aggregation group with 2 network links only via AWS. Keep the
default settings for the LACP related parameters (actor admin key etc.)
More details on the meaning of the LACP parameters will be given in the
advanced course.
Via AWS: Go to the EML-USM view. Go to the NT. Select one
configured network port and one unconfigured port. Go to port
link
aggregation
aggregate
5. Retrieve link aggregation information from the LAG you created. What value
do the LACP parameters have?
Via AWS: select the logical group on the NT. Go to port
link
aggregation
configure
Via Full CLI: configure la > info detail
6. Deaggregate a link from the LAG you created only via AWS.
Via AWS: Go to the EML-USM view. Go to the NT. Select one of the
contributing links of the LAG. Go to configuration LACP
deaggregate.
Review Questions 1. In which window can you find the profiles present at the AWS?
AWS
ANEL view: Templates Profile Show
2. How do you know that your modem is synchronized? In which window can
you see it?
EML view (port view): green v-sign or red cross.
3. Where can you find the profiles available on the ISAM? Is this list the same
for all ISAMs?
EML view: Configuration Profiles Show. This list can be different
for other ISAMs.
14
Residential Bridge
VLAN setup and end-user setup
Objectives
After completing the assignments in this chapter, you will be able to:
Retrieve vlan info
Create Residential Bridge vlan and deploy on bridge port
References
Alcatel 5523/7302 Basic Operator (3FL 00324_D_WB_Ed02)

Perform these exercises with CLI and AWS unless specified

differently
Retrieval of
global
Service/VLAN
information
1. Which Services are created on the AWS?

Via AWS: In the ANEL window go to Service Definition show.
Select the service type: RB VLAN first, then L2 Terminated VLAN.
2. Find all the VLANs (Services) that are configured on the ISAM.
Via AWS: On the EML-USM go to views find VLANs do not
apply any filter (you want to see all configured VLANs), then click on the
filter button.
Via Full CLI: To be sure that the VLAN is created in the entire system
you need to check if the VLAN is created on the SHUB and on the LTs.
Via configure vlan <enter> info and configure vlan shub <enter> info
Note: this gives you a list with configured VLANs and ports added to this
VLAN, which can make the output cluttered. The command show vlan
name and show vlan shub-vlan-name gives you a more compact list. Be
aware that in that case the management VLANs are not shown.
Residential
bridge retrieval
exercises
Perform these exercises on the board and ports assigned to you to do

the retrieval exercises.
1. What is the forwarding mode of VLAN 200 (cross-connect, bridged, )?
Via AWS: On the EML-USM go to views find VLANs apply filter
on VLAN id, then click on the filter button
Via Full CLI: You need to check the configuration on ASAM-CORE
and SHUB (configuration needs to be consistent). The commands are
Configure vlan id 200 <enter> info and configure vlan shub id 200
15
<enter> info
2. What are the ports belonging to vlan 200 on the SHUB? Explain what you
see.
All ASAM ports belong to vlan 200
on VLAN id, then click on the filter button. Clicking on the show config
button gives you a list of all configured ports associated to this VLAN. The
Show Actual button gives you a list of all the ports associated to this
VLAN which are operational.
Via Full CLI: configure vlan shub id 200 gives you all configured
ports belonging to vlan 200.
Show vlan shub-port-vlan-map | match exact:200 gives you the same
list. To see if the ports are operational see one of the previous exercises.
3. Which logical ports are associated to VLAN 200?
VLAN of which the board is operational.
Via Full CLI: Via Show vlan residential bridge 200 gives you the
bridge ports associated to VLAN 200 configured on boards that are
operational (plugged in).
If you want to see all the ports associated with that VLAN (so also the
ports on boards extracted, use configure bridge <enter> info --> you get
a lot of information but theres no possibility to get output per VLAN via
filter.
(You can configure ports on a planned board that isnt plugged yet.)
4. Explain the total configuration of the user logical port PVC 8/35 on port
TRAINING-a.
Note: For the downstream forwarding, we assume that the SHUB knows the
MAC@ of the end user within the respective VLANs.
Via AWS: Go to the EML-USM port view, select the ATM connection
and go to connection. The logical user port is associated to only 1 VLAN,
VLAN 200 and this is also the default VLAN. Frames accepted from user
side are untagged!
16
Via Full CLI: VLAN association is defined in the configure bridge port
command. Via configure bridge port <port id> <enter> info detail
the bridged port is associated to VLAN 200 (VID 200) and there you see
frame type is untagged. PVID is also VLAN 200 so the VLAN 200 is also
the default VLAN
What happens when the end-user sends a frame with VLAN tag 200?
Frames are sent to the network with VLAN tag 200. MAC-address of end
user is learned on user logical port.
Frames are deleted in RB.
What happens when the end-user sends an untagged frame?

Frames are sent to the network with VLAN tag 200. MAC-address of end
user is learned on user logical port.
What happens with a frame with VLAN tag 200 coming from the network?
If destination MAC-address is learned on user logical port, the frame is
sent towards end-user untagged.
What happens with a frame with VLAN tag 300 coming from the network?
Logical port is not member of VLAN 300 so frames are deleted.
5. How many MAC-addresses can be learned in VLAN 200 on the logical user
port VP/VC 8/35 of port TRAINING-a
Number of MAC-addresses learned is configured at VLAN association of
the logical port (ATM PVC). So only when there is already one (or more)
VLAN associated to the connection, this question is relevant. Logical user
port VP/VC 8/35 is associated to VLAN 200. The max number of MAC
addresses that can be learned you can find is 4
and go to connection
VLAN association
Residential Bridge
VLAN
Show configuration. In the Bridge Port window pane there is a
field Max Number of MAC Addresses.
command. Via configure bridge port <port id> <enter> info detail you
can see max-unicast-mac.
6. Explain the total configuration of the user logical port PVC 8/35 on port
TRAINING-b.
Note: For the downstream forwarding, we assume that the SHUB knows the
MAC-address of the end user within the respective VLANs.
Egress
Ingress
DSL port
DSL port
150
150
8/ 35
160
160
210
210
50
50
17
The logical user port is associated to 3 different VLANs. Frames accepted

from user side are untagged since we use Residential bridge VLAN
services. In this case port and protocol based VLAN are used. We have a
VLAN for IPoE traffic, PPPoE traffic and a default VLAN
and go to the relevant connection. You see 3 different VLAN associations.
command. Via configure bridge port <port id> <enter> info detail.
The bridged port is associated to 3 different VLANs, VLAN 50, 160
and 210. The PVID is VLAN 50
Frames are deleted
Frames are sent to the network with VLAN tag 50.
This is in function of the protocol on top of Ethernet: In case of IPoE it
will be forwarded with tag 160, in case of PPPoE it will be forwarded with
tag 210, all others are forwarded with tag 50.
What happens when a frame with VLAN tag 150 is sent towards the end user?
Logical port is not member of VLAN 150 so frames are deleted.
Only in case of IPoE frame is forwarded to end-user (untagged)
Only in case of PPPoE frame is forwarded to end-user (untagged)
What happens when a frame with VLAN tag 50 is send towards the end user?
Frame is forwarded to end-user (untagged)
What happens when an untagged frame is sent towards the end user?
Frame is not forwarded
7. How many MAC-addresses can be learned on the user logical port PVC 8/35
on port TRAINING-b within VLAN 50?
The max number of MAC addresses that can be learned on a port is not
configured per VLAN. The total nr of MAC addresses learned on the port
is 4. But this can be in whatever VLAN!
configuration
Residential
Bridge Mode
For these exercises go back to the board and ports assigned to you
18
to do the configuration exercises.

1. Go to the port that you configured before and where the modem is connected.
Use CLI to apply the service with VLAN id as default VLAN 150 to PVC
8/36. Frames coming from the end user are untagged. You should be able to
connect with 2 PCs. DHCP server is available on the other side.
setup
VLAN ID 150 is already present on the ISAM. This is a VLAN in

Residential bridge mode.
Via Full CLI: When creating the ATM PVC we already configured the
bridge port (see above).
At this stage we will associate a VLAN to it and configure the parameters
needed by the IWF for it to know how to process the ethernet frames.
Use the command Configure bridge port Rack/Shelf/board/port:VPI:VCI
vlan-id 150 to associate port to VLAN 150
Then go to the Configure > bridge>port> Rack/Shelf/board/port:VPI:VCI
$ prompt to configure parameters like : pvid, max-unicast-mac, maclearning
2. Check if you are able to get an IP address from the DHCP server.
Note: in function of the modem setup you need to disconnect your PC from the
AUA LAN and connect the PC to the modem (or connect your own PC to
the modem) or DHCP request can be triggered from the modem onwards.
Ask the teacher what to do!
Force your PC to ask for a new IP-address (DHCP release/renew)
What is the IP-address you received? What is the IP-address of the DHCP
server?
You can verify this via the ipconfig command in a command window.
3. Check the MAC-address learned on your bridged port using AWS and CLI.
Via AWS: Go to the EML-USM port view, click on the bridged port,
go to connection --> Mac Addresses --> Show
Via Full CLI: show vlan bridge-port <pvc id>
4. Are you able to ping the PC of one of your colleagues connected to the same
ISAM? Explain.
This is only possible when the edge-router has proxy-arp enabled. The
19
ISAM itself will block user-to-user communication.

5. Use the AWS to associate logical port 8/35 with VLAN 200 as the default
VLAN. Frames coming from the end user are untagged. You should be able to
connect with 3 PCs to this connection.
VLAN 200 terminates on a BRAS so use PPPoE to set up a connection. Check
if you can surf the web.
Note: in function of the modem setup PPPoE session needs to be initiated from
modem or PC. Ask the trainer what to do!
Setup
VLAN ID 200 is already present on the ISAM. This is a VLAN in

Residential bridge mode
Via AWS: First create ATM connection via the create ATM TP
command. Then go to Connection VLAN Association Residential
Bridge VLAN Configure.
6. Check the MAC-addresses learned on the VP/VC 8/35 and VP/VC 8/36 with
the AWS. What do you notice ? Explain what you see.
Dependent of the setup of the modem there is the possibility that we learn
the MAC-address of the PC/modem on both VP/VCs but they are learned
on different VLANs, so no issues.
Via AWS: Go to the EML-USM port view, click on the bridged port,
go to connection --> Mac Addresses --> Show
7. Use the AWS to remove the RB vlan with id 200 from the 8/35 ATM
termination point on your port.
Via AWS: in the EML-USM port view go to Connection VLAN
association Residential Bridge VLAN Unconfigure all
8. Use the CLI to remove the RB vlan with id 150 from the 8/36 ATM
termination point on your port.
Via CLI: Go to the configure bridge port <pvc id># prompt and
delete PVID and VLAN-ID. This is done with the command no pvid 150
and no vlan-id 150
to unlock the connection via CLI use the command configure interface
port xdsl-line:R/S/LT/port admin-up
9. Create RB VLAN with VLAN ID=20x (x = adsl-x) via CLI. All traffic types
are possible within the VLAN. The VLAN is default VLAN on logical port
8/35. 4 user sessions possible on the logical port. No user line id is required
for DHCP or BRAS. No MC service is deployed within the VLAN.
20
Try to initiate a PPPoE session towards the network. Verify if your

configuration works.
Note: BRAS will not provide you with an IP-address (Setup of the network
currently not ready )
Setup
Creating a VLAN via CLI implies creation of the VLAN in the ASAMCORE and in the SHUB. Check if you can surf the web. VLAN 20x
terminates on a BRAS so use PPPoE to set up a connection.
It is a RB VLAN so you need to make sure that on the SHUB all the
ASAM-links are associated to this VLAN
Via CLI: Step 1: creation of VLAN on ASAM core.
Use command configure vlan id xxx name <service name> mode
residential-bridge. Once the VLAN is created you can modify the
parameters.
Step 2: creation of VLAN on SHUB
Use command configure vlan shub id xxx name <service name> mode
residential-bridge.
Step 3: Associate appropriate ports to the VLAN
For a RB this means all the ASAM-ports and 1 or more network ports.
Use command configure>vlan>shub>id>xxx# egress-port lt:1/1/x and
configure>vlan>shub>id>xxx# egress-port network:x
10. Create a Service for RB VLAN on the AWS. All traffic types are possible
within the VLAN. 4 user sessions possible on the logical port. No user line id
is required for DHCP or BRAS. No MC service is deployed within the VLAN.
Leave status under construction.
Note: unique VLAN-ID per [IP-edge ISAM] pair to prohibit user-to-user
communication.
Via AWS: in the ANEL window:
go to Service Definition Create Residential Bridge VLAN
11. You want to have line identification information on the DHCP server. Try to
apply the change and explain.
Line ID for DHCP is option 82. We can change parameters in the service
since the state of Service is still under construction
Via AWS: in the ANEL window: go to Service Definition modify.
In the Modify Service Template window select Service type = RB (default)
and Action field set it to Edit Template Under Construction
21
12. Use the AWS to associate the service you just created on VP/VC 8/36 of the
port assigned to you. VLAN id to be used is VLAN 16x (x=adslx). Frames
coming from the end user are untagged. VLAN 16x is the default VLAN.
Check if your configuration works by setting up a DHCP session and see if
you are able to receive an IP-address.
Setup
Via AWS: VLAN Service is still under construction so the first step
is to change the status to Ready to use you can do in the ANEL window
by e.g. do a Service Definition modify or do Service Definition
Change State.
Now deploy the Service to the ISAM. Click on the ISAM via Service
Deployment Deploy. Then associate the VLAN to the VP/VC by
clicking on the relevant connection and go to connection VLAN
association.
13. Release your IP address. (ipconfig /release)
14. Your management changed mind and the VLAN 16x can only be used for
PPPoE traffic. Apply the change with CLI. Check if you are still able to
retrieve an IP-address via DHCP. Does it work? Why? Why not?
DHCP traffic is IPoE traffic. The VLAN is created as such that IPoE
traffic will not be forwarded within that VLAN (pass PPPoE only). So we
will not be able to retrieve an IP-address via DHCP on that particular
logical port.
15. In normal operation would you normally apply such change with CLI?
NO since it only impacts that specific ISAM
16. Your management changed mind again, and now only wants IPoE traffic in
VLAN 16x and disable option 82. Apply the change with AWS. Check if you
are still able to retrieve an IP-address via DHCP. Does it work ? Why? Why
not??
When a Service is in Ready to use state you cannot modify it anymore.
Solution is to create a new version of this Service Template and then to
upgrade this service.
Via AWS: New version of Service can be created by going to the
ANEL window via Service Definition Modify. In the Modify Service
Template window select Service type = RB (default) and set the Action
field to create new version Then deploy the Service to the ISAM by
clicking on the ISAM in the ANEL window and go to Service
Deployment Upgrade.
22
17. Can you ping the client PC from the server side on VLAN 16x?
Ask the trainer to assist you since access to DHCP server is secured.
First check the ARP table of DHCP server and make sure the MAC-address of
your PC is no longer in the self-learning table of VLAN 16x, then issue the
ping command.
What do you notice? Explain.
By default, the IWF on the LT does not allow BC frames to pass
through in the downstream direction.
The broadcast control flag of the RB can be checked via
Via AWS: Find VLAN information. In the EML-USM window go to
Views Find VLANS and query for vlan id 16x. When checking
configuration via the Show Config button you find Broadcast control
Disabled in the VLAN Settings window pane.
Broadcast control Disabled means that broadcast frames are blocked.
Via CLI: use the configure vlan id 150 <enter> info detail command.
No broadcast-frames means that broadcast frames are blocked.
18. Force the system to allow broadcast frames to pass through in the downstream
direction. Use a CLI command to achieve this goal. Verify, and explain what
you notice.
Via CLI: configure vlan id 16x broadcast-frames
Pinging from the server to the client now succeeds.
19. Delete the association with VLAN 20x from VP/VC 8/35 on your port and
associate VP/VC 8/35 with VLAN 21x.
VLAN 21x is a RB service and parameters are such that only PPPoE traffic is
allowed on this VLAN.
Perform this exercise with the AWS.
Check if your setup works.
What is the IP-address you get from the BRAS?
What is the IP-address you got from the DHCP server?
Note: BRAS will not provide you with an IP-address (Setup of the network
currently not ready)
Setup
VLAN 21x has not been created yet. You need to create the service as a
RB with PPPoE filter.
23
20. Try to delete VLAN 16x from the ISAM via the AWS. What happens?
Explain.
Note: If not possible just proceed to the next exercise after explanation
Via AWS: in ANEL, execute the Service Deployment Remove
command after selecting one or more ISAMs. Select service type RB
VLAN, then pick the appropriate service and click on OK. Click OK and
YES to confirm, but then you get an error message because the service is
still in use.
Via CLI: configure vlan no id 16x
You get the error message when vlan is associated with port, this vlan cant
be deleted.
21. Version 2 of service with VLAN-ID 16x has been deployed in the entire
network. Delete version 1 from the AWS.
Via AWS: These actions need to be done in the ANEL window.
You can only delete a Service Template when its status is modified to
obsolete.
Once this is done you can delete the Service Template via Service
Definition Delete
22. MC Teaser .
Set-up a MC control-channel on VP/VC 8/36 and allow your user to see
package 1. Ask the teacher for assistance and see if you can watch some video.
24
Cross-connect.
VLAN setup and end-user setup
Objectives
Distinguish between the different cross-connect models
Understand the ingress/forwarding/egress mechanisme
Create cross-connect vlans and associations via CLI and AWS
References
Alcatel 5523/7302 Operator ( 3FL 00324_E AAAA WBZZA ED02 )

Cross-connect
Mode retrieval
exercises

Check with AWS and CLI.
Configure vlan id 333 <enter> info and configure vlan shub id 333
<enter> info
2. What are the ports assigned to VLAN 333 on the ASAM-CORE and on the
service hub . Explain what you see.
VLAN 333 is C-VLAN Cross connect mode (VLAN association: Crossconnect, Stack type: unstacked C-VLAN).
This means that only one user is associated to one VLAN. On the ASAMcore this means that only one logical port is bridged towards this VLAN.
On the Service hub it means that maximum one ASAM-link or one
directly connected end user (Ethernet user) is connected to this VLAN.
Multiple Network ports can be assigned to this VLAN.
Via Full CLI: configure vlan shub id 333 gives you all configured
ports belonging to vlan 333.
Show vlan shub-port-vlan-map | match exact:333 gives you the same
list. To see if the ports are operational see one of the previous exercises.
25
3. Is there a service defined on the AWS for any of the cross-connect modes?
Explain for which cross-connect mode this is useful and why.
Via AWS: The only service defined on the AWS for cross-connect
forwarding mode is the service stacked VLAN. Service defined to ease
configuration of the S-VLAN/C-VLAN cross-connect mode.
This is logical since in the single tag cross connect and S-VLAN
transparency the S-VLAN and C-VLAN is unique per logical port.
In case of S-VLAN/C-VLAN cross-connect the S-VLAN defines a service
and can be mapped on multiple logical ports. So in that case having a
service defined on the ISAM makes sence.
4. Explain the configuration on port TRAINING c on VP/VC 8/35 with AWS

and CLI. In the upstream? In the downstream?
According to the ingress rule ( see AWS : show VLAN association on
bridgeport
accept Frames From Subscriber = All) the frame will
be accepted .According to the fdb, the frame will be forwarded to the
network with VID=333
bridgeport
be accepted . According to the fdb, the frame will be forwarded to the
network with VID=444
The frame will not be forwarded, since there is no C-tag with vid = 555
defined on the bridge port.( bridgeport-vlan associations )
26
bridgeport
be accepted.
The frame will get the default vlan value, C-Tag vid = 333 as defined in
the pvid, and will be forwarded to the network.
According to the vlan associations on the bridge port the frame is
accepted and forwarded to the appropriate bridge port.
According to the egress rule ( see VLAN association parameter : Send
frames back to the subscriber as = untagged ) the Ethernet frame will
be send untagged to the user .
accepted and forwarded to the appropriate bridge port.
frames back to the subscriber as = single tagged ) the Ethernet frame
will be send single tagged to the user .
discarded since vlan 555 is not defined on the bridge port
5. What is the forwarding mode of VLAN 400 (cross-connect, bridged)?

VLAN 400 is S-VLAN Cross connect mode (VLAN association: Crossconnect, Stack type: S-VLAN).
Via AWS: On the EML-USM go to views find VLANs: search for SVLANs then click on the filter button. You see that the S-VLAN is in
cross-connect mode so the mode is S-VLAN cross connect mode or CVLAN transparency mode
and SHUB (configuration needs to be consistent). The global command is
Configure vlan info detail
service hub? Explain what you see.
VLAN 400 is S-VLAN Cross connect mode (VLAN association: Crossconnect, Stack type: S-VLAN).
This means that only one user is associated to one S-VLAN.
The end user can send frames with C-VLAN tag already attached in
case settings on acceptable frame types from subscriber allow it but the
ISAM will function as if no tag is present (transparent) and will add SVLAN to the frame.
On the ASAM-core this means that only one logical port is bridged
towards the respective S-VLAN.
On the Service hub it means that maximum one ASAM-link or one
directly connected end user (Ethernet user) is connected to this VLAN.
27


Configure vlan id stacked:400:0 <enter> info and configure vlan shub
id 400 <enter> info or very simply Configure>vlan# info detail
28
7. Explain the configuration on port TRAINING -c on VP/VC 8/36 with AWS

and CLI. What happens in the upstream ? What happens in the downstream ?
Remark: the outer labels should be the S-TAGs. In the egress scenario, VID
400 is given to an untagged frame, so it is supposed to be an S-TAG (S-VLAN
tagging; C-VLAN transparency). But in the ingress VID 400 is a C-TAG. This
is rather confusing. For the egress scenario, you notice that VID 400 is an STAG in the first case and a C-TAG in the second. This is very well possible,
but may cause confusion.
Since all incoming frames are treated as payload ( C-vlan transparent ),
the frame is accepted and forwarded with S-TAG 400.
the frame is accepted and forwarded with S-TAG 400.
the frame is accepted and forwarded with pvid S-TAG 400.
What happens when a frame with S-VLAN tag 400 and C-VLAN tag 444 is
sent towards the end user?
The LT will accept the frame (only check the first TAG) , remove the Stag and forward the frame towards the appropriate bridge port.
What happens when a frame with S-VLAN tag 500 and C-VLAN tag 400 is
sent towards the end user?
The LT will not accept the frame since the S-TAG is not define on the
bridge port.(S-Tag is first tag )
The LT will accept the frame (only check the first TAG) , remove the tag
and forward the frame towards the appropriate bridge port.
29

VLAN 500 is S-VLAN/C-VLAN Cross connect mode (VLAN association:
Cross-connect, Stack type: stacked C-VLANs).
Via AWS: On the EML-USM go to views find VLANs: search for SVLANs--> then click on the filter button. You see that the S-VLAN is in
layer 2 terminated mode so the mode is S-VLAN/C-VLAN cross connect
mode.

and SHUB (configuration needs to be consistent). The global command is
Configure vlan info detail
service hub? Explain what you see.
VLAN 500 is S-VLAN/C-VLAN Cross connect mode (VLAN association:
Cross-connect, Stack type: stacked C-VLANs).
This means that more than one user is associated to the same S-VLAN.
On the ASAM-core this means that more than one logical port can be
bridged towards the respective S-VLAN.
On the Service hub it means that all ASAM-links are member of this
VLAN.
Via AWS: On the EML-USM go to views find VLANs: search for SVLANs then click on the filter button. Clicking on the show config
Configure vlan id stacked:500:0 <enter> info and configure vlan shub
id 500 <enter> info or very simply Configure>vlan# info detail
10.
AWS
Explain the configuration on port TRAINING c on VP/VC 8/37 with

and CLI. In the upstream ? In the downstream?
30
accept Frames From Subscriber = All) the frame will be
bridgeport
accepted .
According to the defined bridgeport-vlan associations, the frame will get an
additional tag ( S-tag with VID= 500 )
The frame will be forwarded as stacked VLAN 500:123 to the network
The frame will not be forwarded, since there is no C-tag with vid = 500
defined on the bridge port.( bridgeport-vlan associations )
bridgeport
accepted.
The frame will get an additional tag ( S-tag = 500)
The frame will be forwarded as stacked VLAN 500:234 to the network
bridgeport
accepted.
The frame will get the default vlan values, S-Tag vid = 500 and C-Tag vid =
123 as defined in the stacked pvid, and will be forwarded stacked to the
network.
What happens when a frame with S-VLAN tag 500 and C-VLAN tag 123 is sent
towards the end user?
According to the vlan associations on the bridge port the frame is accepted
and forwarded to the appropriate bridge port.
frames back to the subscriber as = untagged ) the Ethernet frame will be
send untagged to the user .
According to the vlan associations on the bridge port the frame is discarded
since vlan-stack 500:128 is not defined on the bridge port
31
According to the vlan associations on the bridge port the frame is accepted
and forwarded to the appropriate bridge port.
frames back to the subscriber as = single tagged ) the S-TAG will be
removed and theEthernet frame will be send single tagged to the user.(CVLAN=234 )
What happens when an untagged frame is sent towards the end user?The frame
will be discarded as no SVLAN vid = 123 is defined on the bridge port.
VLAN-set up
configuration
Cross-connect
Mode
to do the configuration exercises.
1. Go to the port that you configured before and where the modem is connected.
Delete all previously configured VLAN associations from the different logical
ports.
2. Use the AWS to cross-connect PVC 8/35 with VLAN id 20x as default VLAN.
Frames coming from the end user are untagged. The BRAS is available on the
other side. Do all what is necessary to be able to configure this setup.
Verify if you receive an IP address.
Setup
Via AWS: VLAN 20x was already used for a residential bridge service
(is a VLAN created with CLI before). You cannot use the same VLAN for
different forwarding modes. Therefore the first step is to remove RB
VLAN 20x from the ISAM.
Now we can configure the VLAN association in C-VLAN cross-connect
mode. In that case no service is defined on the ISAM.
One unique VLAN per end user.
32
Go to the EML-USM port view. Click on the PVC, go to connection

VLAN association
cross-connect vlan
configure
3. Use the CLI to cross-connect PVC 8/36 with VLAN id 15x as default VLAN
15X to PVC 8/36. Frames coming from the end user are untagged. DHCP
server is available on the other side. Verify if you receive an IP address.
Setup
Creating a VLAN via CLI implies creation of the VLAN in the ASAMCORE and in the SHUB.
It is a CC VLAN so on the SHUB only one ASAM-link is associated to this
VLAN
Via CLI: Step 1: creation of VLAN on ASAM core.
Use command configure vlan id xxx name <service name> mode crossconnect. Once the VLAN is created you can modify the parameters.
Step 2: creation of VLAN on SHUB
Use command configure vlan shub id xxx name <service name> mode
residential-bridge.
Step 3: Associate appropriate ports to the VLAN
For a C-VLAN cross-connect this means only one ASAM-port and 1 or
more network ports.
Use command configure>vlan>shub>id>xxx# egress-port lt:1/1/x and
configure>vlan>shub>id>xxx# egress-port network:x
4. Delete all previously configured VLAN associations from the different logical
ports.
5. A business user has different sites, connected to different ISAMs.

In their respective LAN, they use VLAN-tags.
We want to connect the different sites with VLAN-id 15x in the EMAN.
How do you proceed? Do all what is necessary to be able to configure this
setup. Proceed with AWS and check your configuration with CLI.
Verify if you have IP connectivity to end user(s) on the other sites
setup
33
6. Delete all previously configured VLAN associations from the different logical
ports.
7. Multiple end-users are connected towards the IPedge with VLAN 15x.
End-users send their frames untagged. We use a VLAN tag to identify the enduser within the ISAM.
Associate port 8/35 with the service going towards this IP-edge.
Do all what is necessary to be able to configure this setup. Proceed with AWS
and check your configuration with CLI.
Setup
34
IP-aware bridge.
VLAN set-up and end-user setup
Objectives
retrieve information about VRFs
Setup and configure vrf via AWS
Create user-network connectivity
References
Alcatel 5523/7302 Operator (3FL 00324_F AAAA WBZZA ED02 )
IP aware bridge
retrieval
exercises

1. What is the forwarding mode of VLAN170 (cross-connect, bridged, )?

and SHUB (configuration needs to be consistent). . The commands are
Configure vlan id 170 <enter> info and configure vlan shub id 170.
Both vlan-modes are layer2 terminated which means that forwarding
model is IP aware bridge
2. What are the ports belonging to vlan 170 on the SHUB? Explain what you
see.
All ASAM ports belong to vlan 170 because forwarding mode is IP aware
bridge (Layer2 terminated)
on VLAN id, click on the filter button
click on the show config
clicking on associations tab gives you a list of all configured
button
ports associated to this VLAN on the SHUB.
You will not find any information on the associations of the end-user ports
since IP interfaces are mapped to a VRF and then the mapping towards a
VLAN depends on the destination address of the IP packet.
Via Full CLI: configure vlan shub id 170 <enter> info gives you all
configured ports belonging to vlan 170.
35
3. Which logical ports (end-users) are associated to VLAN 170?

You will not find any information on the associations of the end-user ports
since IP interfaces are mapped to a VRF and then the mapping towards a
VLAN depends on the destination address of the IP packet.
4. Explain the total configuration of the user logical ports on port TRAINING-d.
How is the forwarding done? To which VRF(s) are the logical ports mapped.
What is the difference between the configuration on logical port VP/VC 8/35
and VP/VC 8/36
Both VP/VC 8/35 and VP/VC 8/36 are IP interfaces.
To VP/VC 8/35 an IPoE interface is attached, where on VP/VC 8/36 we
have configured an IPoA interface.
On this level you are unable to see if routed mode or IP aware bridged
mode is used. The creation or configuration of the IP interface and the
mapping on a VRF is in both cases done in the same way.
Checking to which VRF the IP interface is mapped can be done in the
following way:
Via AWS: Go to the EML-USM port view, select the relevant IP
interface and double click on it. The EML-USM interface view appears.
Select the IP interface and go to service
Ethernet/IP
IP interface
show.
Via Full CLI: IP interfaces are defined in the configure ip interface
command. Via configure ip interface user port <port id> <enter> info
detail for IPoA interfaces and configure ip interface user bridgeport
<port id> <enter> info detail for IPoE interfaces
5. How many MAC-addresses can be learned on the connection 8/36?

Limiting the number of MAC-addresses that can be learned is a L2
feature. It is not configurable on a layer 3 / IP interface.
Forwarding is done based on IP addresses. On the LT you have ARPProxy functionality and the ARP table will give IP-address /MAC-address
table
36
User setup for

IP aware bridge to do the configuration exercises.
Note: Full configuration of VRF setup and IP aware bridge setup is not discussed
in this course. This is subject of the advanced course
1
Go to the port that you configured before and where the modem is connected
to. Delete all previous configured VLAN associations from the different
logical ports.
The forwarding on logical port VP/VC 8/36 needs to be done based on IP

addresses. The ISAM is not next hop. Packages received on the interface are
IPoE. And the forwarding table configured in VRF 17 has to be used. The enduser will receive his IP-address with DHCP.
Set up the configuration with AWS and verify with CLI.
Setup
Via AWS: Go to the EML-USM port view, select the ATM PVC and go
to service
Ethernet/IP
IP interface
create.
Make sure that you select the correct VRF. The configuration of the
routing table on the network side and DHCP related configuration is not
focus of this course.
Via Full CLI: IP interfaces are defined in the configure ip interface
command. Via configure ip interface user port <port id> <enter> info
detail you will see to which VRF the interface is mapped.
37
Initiate DHCP. Which IP address did your modem/PC receive?

What is the default GW of the end-user? Is this the same as the default GW of
the ISAM (Check setup of network drawing)? Explain what you see.
The default gateway of the ISAM and the default GW of the end-user is
not necessarily the same. In our setup it is.
You are a business user and your IP address is statically allocated. What are
the additional thinks that need to be configured on the IP interface configured
on VP/VC 36?
You need to configure a static route towards end-user site and configure
the Gateway of the end-user so that the ISAM can perform correct ARPProxy functionality
The ISAM is set up so that static end-users with default GW 10.10.170.1.are

supported (user gateway is configured)
Give your modem/PC a static IP address 10.10.170.10x and a gateway
10.10.170.1. Make the necessary configuration on the ISAM towards the enduser to make the setup work.
Check your configuration by pinging the ISAM gateway.
As stated in the exercise, the user gateway is already configured for you,
the only thing that still needs to be set up, is the static route towards the
end user.
Via AWS: go to the EML-USM ip interface view. Select the IP
interface and go to service
Ethernet/IP
IP route
create
Via Full CLI: Routes are defined in the VRF. Via configure ip vrf 17
route-dest 10.10.170.10x/32 next-hop direct:user-bridgeport:<portid:VP/VC>
Give your modem/PC a static IP address 10.10.170.11x. Will you still be able
to ping the gateway? Check it? Why (not)?
This will not work since there is no route configured back to IP address
10.10.170.11x.
38
Resetting the Alcatel 7302 ISAM.

Objectives
The AWS can only access the ISAM once IP connectivity has been established
between the AWS and the ISAM.
Retrieve IP and other management related information
configure the ASAMs IP settings via the CLI
delete/create an ISAM in the ANEL view of the AWS
configure the ISAM layout in the EML view of the AWS
(un)supervise an ISAM
References
Alcatel 5523/7302 Basic Operator (3FL 00324 _B AAAA WBZZA ED02

)
Resetting the
7302 ISAM /
retrieval
exercises
Perform the exercises with CLI and AWS where possible
1. What is the IP-address of the ISAM?

Via AWS: Go to the ANEL window, select the ISAM and go the NE
show info. In this window you find the IP-address of the ISAM.
Via
Full CLI: IP address of the ISAM can be retrieved via the command
configure system management <enter> info .
2. What is the external management VLAN that we use to for the management of
the ISAM? Are we using in-band or out-band management?
Via AWS: Go to the EML-USM view. Go to Service
VLAN
System parameters
show config. Here you see the OAM settings. You
can also go to the board view of the NT card. One of the external
Ethernet ports is configured as out-band management ports (Icon). Click
on the port and go to port
show. To know the VLAN id of the
management VLAN, right-click on the port used for management and go
to show VLAN associations
Via Full CLI: The OAM mode can be retrieved via the command
configure system shub entry <enter> info detail.
Once you know the vlan id for external management you can retrieve the
ports mapped to this VLAN with the command configure vlan shub id
xxx <enter> info.
If you want to know if management is done tagged or untagged and
39
whether the external management vlan id is PVID or not, you can enter
the command configure bridge shub <enter> info detail
3. Delete the ISAM from the ANEL view and check your connections. Does the
setup of the PPP session still work?
Before you can delete the ISAM, you have to bring it to the nonsupervised state.
Via AWS: Go to the ANEL window, Select the ISAM NE
Supervision Stop. Now you can delete the ISAM. Select the ISAM NE
Delete (+ confirm)
You can still initiate a PPP session, because the MIB database on the
ISAM is not affected.
4. Recreate the ISAM with the same parameters and bring it to the supervised
state. Browse through the different views and check if something has changed.
Why (not)?
ANEL view: NE Create. Fill in the correct values (see first question)
again and start supervision (immediately from the creation window, or via
NE Supervision Start).
Nothing has changed. Once the AWS has established IP connectivity with
the ISAM, it seems as if nothing happened.
If you dont touch the MIB database on the ISAM, everything is still OK.
The AWS is only a management system.
5.
6. Which machines are able to perform full SNMP management on the ISAM?
Via the CLI: Within the ISAM you need to define the SNMP
managers allowed. You can check the configuration via the command
configure system security snmp <enter> info Youll see the
ipaddress(es) or subnet(s) associated with the SNMP communities
public and NETMAN that have SNMP connectivity to the ISAM
Resetting the
7302 ISAM /
Configuration
exercises
1. The MIB database(s) of the ISAM will be cleared (by the teacher). In addition,
the ISAM will be deleted from the ANEL view. Check your connections. Can
you still surf the web? Why (not)?
No. The complete configuration is deleted. Resetting the ISAM will
clean up the system, and consequently remove all profiles, customers and
other configuration from the ISAM.
2. Bring the ISAM back up with all parameters required to make sure that you
can supervise the ISAM again with the AWS. Recreate the ISAM and bring it
to the supervised state. Follow these requirements:
40
We represent an operator with equipment installed in Belgium. We want to

work in a way that our ISAMs are grouped per province. We divide each
province in a logical "north" and "south" region.
Use the locations "north of Antwerp" and "south of Luxembourg". Ask the
teacher which location to use.
Reconfiguration of IP parameters
1) Setup Management IP Address (here: ISAM IP = 172.31.79.15X )
configure system single-public-ip
configure system management host-ip-address manual: 172.31.79.15X/24
configure system management default-route 172.31.79.129

configure system security snmp community public host-address 172.31.79.15X /24
(context nt ) privilege read-write
configure system security snmp community NETMAN host-address
172.31.79.15X /24 context shub privilege read-write
2) Set Out-band management on port 1 / vlan 4093
configure interface shub port 1 port-type outband-mngt
configure interface shub port 1 admin-status auto-up
configure system shub entry vlan ext-vlan-id 4093
configure vlan shub id 4093 egress-port network:1
configure vlan shub id 4093 untag-port network:1
configure bridge shub port 1 pvid 4093
configure vlan shub id 1 no egress-port network:1
3) save the IP configuration of the SHUB and reboot to make it active
admin software-mngt shub database save
admin equipment reboot-shub system reset
recreating the ISAM on the AWS
ANEL view NE Create.
3. Open the EML-USM. Do you see a difference in the configuration of the
ISAM compared with the situation that you had before the MIB was cleared ?
Why (not)?
The creation of the shelf and the NT board is done automatically. The
other entire configuration is lost.
4. Delete the AWS as SNMP manager. Explain what happens.

Perform a reachability test on the ASAM-CORE and on the SHUB. Explain
what you see.
Defining the AWS as SNMP manager as security feature is only
possible on the SHUB. The command to use is configure system security
snmp no community <x>.
In that case you will see that the SHUB is still pingable but you have lost
SNMP reachability.
41
5. Restore the situation

Via the CLI with command configure system security snmp shub
community <x> name NETMAN privilege read-write ip-addr <IP-address
AWS>
6. Make sure that the ISAM is configured such that your modem synchronizes
using Service profile and spectrum profile TRAINING
42
Backup / restore of ASAM-CORE and service hub
Objectives
References
After completing the assignments of this chapter, the trainee will be able to:
perform a manual backup of an ISAM, including the service hub
locate the backup files on the AWS
retrieve the list of all backup files of a single ISAM
restore a specific backup from the A5523 AWS to the ISAM: via the AWS for
the ASAM-CORE and via CLI for the service hub.
Backup
Alcatel 5523/7302 Operator, ISAM backup & restore (3FL 00324_J AAAA
WBZZA ED02 )
1. Take a manual backup of your ISAM (both ASAM-CORE and service hub!)
using the AWS. How do you proceed? (2 possibilities). What is the file name
given by the AWS?
ANEL view: Configuration Backup/Restore Backup.Specify a file
name and click OK.
EML view: Supervision Backup/Restore Backup.. Specify a file
name and click OK.
The system will take the name given by the operator but it will also
include the SW version running on the NT and time&date of the backup
in the name.
2. Show a list of all backups of the ISAM you have been working on (2
possibilities).
ANEL view: Supervision Backup/Restore List Backup Files
EML view: Supervision Backup/Restore List Backup Files
3. Can I take a backup of multiple ISAMs at the same time? Y/N
If it possible, how? Do it. How are the different backups differentiated?
Via ANEL view. Make sure you select multiple ISAMs.
The backup files will have the same name, but they are all kept in their
own specific directory (per ISAM).
4. Display a list of all backup files at Unix level. In which directory do you need
to look?
open a terminal window.
1)AWS versie 7.1 :
Go to
/var/opt/aws/isam/_7.1.0.17.3/isamim_710Mt_WAL_102.3/data/backup/IS
AMx of the ISAM>. Enter the command ls l to list all files in that
directory.
43
2) AWS versie 6.5

Go to /var/opt/aws/equipment/backup/<name of the ISAM> Enter the
command ls l to list all files in that directory.
5. Restore the ASAM-CORE backup taken in (1). (Notify the other trainees
working on the same ISAM!) What happens?
EML view: Supervision Backup/Restore Restore (select the correct
file). The ISAM will reset.
6. Can I restore ASAM-CORE backups on multiple ISAMs at the same time?
Not possible!
7. Restore the service hub backup taken in (1) via CLI. (Notify the other trainees
working on the same ISAM!)
show > software-mngt > shub (to see which partition is active: e.g.
config -1)
admin software-mngt shub copy from 138.203.21.209:backup/<ISAM>
to shub:/config2/iss.conf
admin software-mngt shub select-config config-2
admin equipment reboot-shub
8. Try to find out if the automatic backup feature is active and at what time the
backup is taken.
ANEL
Configuration
Backup/Restore
Show config (to see if
a periodic backup will be taken. It doesnt say how often and at what
time.)
EML-USM
Supervision
Backup/Restore
Show config (same
info)
Via the Administration menu Customization Backup tuning (to see
the periodicity and the time the backup is to be taken).
9. Delete the backup files you created on the AWS.
ANEL
Configuration
Backup/Restore
Delete backup files
EML-USM
Supervision
Backup/Restore
Delete backup files
Review
Questions
1. What is the meaning of "backing-up the ISAM?

Saving the current configuration of the ASAM, i.e. the profiles,
connections, customer-ids, configuration data. It saves/copies the MIB
settings in flash memory on to the hard disk of the AWS.
2. How can you see a list of all the backups of the ISAM available in the ISAM?
(2 possibilities)
ANEL window configuration backup/restore list backup files
EML view supervision backup/restore list backup files
44
3. In which window can you perform a manual backup?

ANEL & EML window.
4. What are the differences between a manual and an automatic backup parameter
wise?
Filename, frequency, scheduling,
45
Fault management
Objectives
References
After completing the assignments of this chapter, you will be able to:
describe how alarms are handled in the 5523 AWS.
analyse the different alarm indications
retrieve a list of all the current alarms (NE or object level)
create and use alarm sublists
describe the different actions that can be performed on an alarm
retrieve detailed information of a specific alarm
overrule the alarm reporting mode on the ISAM for a specific port
3FL00324 Alcatel 5523/7302 Hands-on, Alarms

Alarms
Before you start the assignments on fault management, close all the AWS windows
except for the ANEL window.
1. Make sure you have an additional workspace in your CDE environment to put
in the CAL-USM.
See first chapter on how to move a specific window to another
workspace.
2. Focus on the ANEL window while you remove your LT board (inform your
colleagues!). What do you see?
The status of the ISAM changes (the alarm is always propagated to the
highest level, even to the hierarchical structure on the left side in the
ANEL window).
3. Navigate to the specific object on which the alarm occurred. While doing so,
try to analyze the tags and messages on the different screens. When you are on
board level, do you still see the alarm? Why (not)?
Double click on the ISAM and subrack. Single click on the alarm tag
to see the list of possible alarms. Occurring alarms are blue, yellow,
orange or red. Moving the mouse pointer over the alarm tags will display
the alarm description.
Once you click on the alarm status tag of the board you see at the
bottom the CFG tag changing color, indicating a board-removed error
When you reach the board view you do not see the alarm anymore, also
the indicators on the screen do not show correlated errors.
4. Analyze the alarm counters on the EML-USM window. Explain them.
The counters on the top of the screen indicate the number of alarms of
a particular kind: at the left there are 5 counters per severity level and at
46
the right you have counters per domain: e.g. IP related alarms, SubNE
alarms, LT Port Alarms, NT Port Alarms, Equipment Alarms.
5. What is the system proposed solution for the generated alarm in exercise 2?
How did you find this information?
Proposed solution is re-plug board, check configuration. This text
can be found by going to the More Info window:
double click on the alarm
select the alarm, right click with your mouse and select 'More Info'
select the alarm, go to the Display menu and select 'More Info'.
6. Re-insert the board and watch the status of the alarm

The alarm is automatically cleared (CLR)

7. Acknowledge the alarm and see what happens
Select the alarm in the sublist: Action Acknowledge or go to the
relevant alarm, right click with the mouse and select Acknowledge. The
alarm will be removed from the CAL (current alarm list) and moved to
the HAL (historical alarm list).
8. Make sure that the system only generates a list of alarms for your NE only (in
the CAL). How do you proceed? (2 possibilities)
ANEL window: Select 1 NE, go to View Show Alarms
Go to the EML view. Via Views Show Alarms On NE
In both cases a sublist for that NE is created on the fly.
In fact theres also a third possibility: go to the CAL USM Sublist
Create - <enter a name>. In that way you can clone an existing sublist
and give it a name of your choosing. Next you need to modify the filter
criteria to make sure the right alarms are added to this sublist. See
Advanced AWS Operator course.
9. Is it possible to see the alarms of multiple ISAMs at the same time? If yes,
how?
By opening the Alarm Application from the AWS main menu.
By creating a new sublist and modifying the filter (see Advanced AWS
Operator course).
10. Can you see the current alarms of an ISAM that is not supervised?
If you stop supervising your NE, can you still see the alarms you saw before in
the CAL?
When supervision is stopped, the alarms of the relevant ISAM are
removed from the CAL and sent to the HAL (with insertion cause:
invalidation). See Advanced AWS Operator course for more information.
11. Switch off the power of your CPE modem. Will the ISAM generate an alarm?
Do you see this event at the AWS? Why (not)?|
No alarm at the AWS is generated because the severity (Minor) doesnt
exceed the threshold (Major and higher).
47
12. Imagine a customer has problems with his ADSL line and calls the helpdesk (=
you) already for the second time. You want to monitor all events on his line.
Other ports cannot be touched. Is this possible (and how)?
On port level you can change the minimum alarm severity for
reporting. In the menu Port Configure you can change the Alarm
Severity threshold. Change it to Minor and you will see the alarm
related to exercise 10. If you want to see a list of only the alarms on that
port, go to port level: Views Show Alarms On selected object.
Review
Questions
1. How do you start the CAL window (3 possible answers)?

From the AWS main menu
From the ANEL view: View Show Alarms
From the EML-USM window: View Show Alarms - On
2. When you don't see an alarm in the CAL, does it mean that there is no alarm?
Explain.
No! It depends on the alarm severity assignment template (ASAT) that
is used by the ISAM and if the ISAM is in the supervised state or not.
(And if the sublists in the CAL Summary Window are active or not,
For more information on alarms: see Advanced AWS Operator course.)
48

Alcatel Hands On Exerc7302/5523 Operator Hands-Onises Answers

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Alcatel Hands On Exerc7302/5523 Operator Hands-Onises Answers

Загружено:

Авторское право:

Доступные форматы

2005 ALCATEL BELL N.V.

ALL RIGHTS RESERVED

7302-7330/5523 operator part 1

Alcatel-Lucent University Antwerp

Alcatel-Lucent University Antwerp

3FL 00324 AAAA WHAAA Ed 01

Alcatel 5523 & 7302 Hands-on Exercises

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

Getting started with the CDE & Alcatel 5523 AWS

ANEL features of AWS

License Key of 5523 AWS

Basic equipment setup with AWS/CLI

Cross-connect. : VLAN setup and end-user setup

IP-aware bridge : VLAN set-up and end-user setup

Resetting the Alcatel 7302 ISAM

Backup / restore of ASAM-CORE and service hub

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

Getting started with the CDE & Alcatel 5523 AWS

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

Use the CDE to navigate between different USMs

Alcatel 5523/7302 Hands-on (3FL 00324_A AAAA WBZZA ED02)

Start / Stop the

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

ANEL features of AWS

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

Search which VLAN-ids are still available.

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

5. Check the IP connectivity between the AWS and your NE.

Get Free VLANs

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

License Key of 5523 AWS

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

After completing these assignments, you will be able to:

Identify the place where to adapt the license keys

Retrieve license rights and actual usage

1. Until what date is your license for AWS-CORE valid?

how many ADSL2+ lines are currently in use?

that has configured EBLT boards?

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

Basic equipment setup

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

Ports and connections

Alcatel 5523 AWS (3FL 00324_C AAAA WBAAA Ed 02)

Alcatel 5523 AWS: customer documentation

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

How many boards are configured on the ISAM?

Which boards are actually inserted in the ISAM?

3FL 00324 AAAA WHAAA Ed01

Alcatel 5523 & 7302 Hands-on Exercises

2007 ALCATEL BELL N.V. ALL RIGHTS RESERVED

2. Which ports are configured on your board?

3FL 00324 AAAA WHAAA Ed01