Welcome to the module 7362 Mini OLT Turn up procedure.

Before we start, please take a quick look at the controls of this web based training. The
side panel allows you to see the menu and view the voice over script. The control bar along
the bottom allows you to play or pause, adjust the volume or go to the next or previous
page. At the top right, you can view the glossary of this module and the resources allow
you to download the PDF or podcast version. When you are ready select the Next button to
continue.

2
Here, you see the overview of how this module is setup.
You can take a short quiz at the end to test your newly acquired knowledge.
After you finish this module, you will be able to:
• Perform the 7362 DF-16GW Mini OLT turn-up
Let’s get started, we shall first have an overview about the mini OLT turn up procedure.
Before starting with the turn-up procedure, let us understand the internal and external
communication management in ISAM.
For internal communication between the controller and the IACM (The management
instance of the NT and the LTs) and IHUB (The management instance of the Router on the
NT), ISAM defines a default internal communication VLAN with the VLAN ID 4094. This VLAN
ID 4094 is fixed in the software and cannot be used externally.
The external VLANs can be configured and these are used for all layer 2 communications
outside of ISAM. The range available for external VLANs is 1 to 4093.
One of them is used as the management VLAN of the ISAM to reach the controller
The management IP interface gives the ISAM the management IP address and is freely
configurable
The turn-up procedure for 7362 DF-16GW Mini OLT requires configuring ISAM to be
reachable for management.
For layer 1, configure the network port (or ports) on the NT and configure LAG if
required.
For layer 2, configure the external management VLAN.
For layer 3, configure the management IP address and default gateway.
For layer 4, configure the SNMP settings for IACM in order to manage the ISAM
from EMS systems like the 5520 AMS. In some cases SNMP V3 and SFTP are required
and should be provisioned accordingly.
Next are the additional system settings like system ID.
This slide provides an overview of the Physical ports on 7362DF-16GW Stand-alone Mini
OLT
This node acts as a stand-alone mini OLT.
The controller card provides eight SFP+ uplink ports.
The LT card is fixed and has 8 XFP ports for 4 NGPON2 ports or 16 GPON ports, depending
on the XFP type that is used.
It can be deployed in the Central Office or in a remote location.
Several input power variants exist.

Please note that the GE port is not usable in CLI or AMS.

In order to perform a turn up procedure you have to connect to the CRAFT port of
the network element.
Depending on the type of NE the cable needed to connect to the CRAFT port is
different.

7362DF-16GW is the one only one which needs a standard USB cable 2.0 A male to
micro-B cable. In the PDF file “736x_CRAFT_over_USB” which comes with the course
material you can find additional information regarding the various USB cable types
needed, direction to do download and install the drivers needed.

The craft port for the 7362 is shown on the slide.

Once connected to the CRAFT port hit the Enter key once to trigger the port.
Type C to get into the CLI.
Login into the CLI as shown.
When you log in the first time via CLI, log in as “isadmin” with the password as
shown in the slide. The system will prompt you to change the password and then
you may change it, preferably to “ANS#150”.
The new password shown here is the most common one used. However, it does not
mean that this is must. The “isadmin” user password can be freely chosen but the
one shown here is typically set up in all ISAMs.

This first-time login password is also the password after a reset to default
database or to factory settings.
The NT card (control slot) of the 7362 DF-16GW Mini OLT has ___ SFP port(s).

1. 1
2. 8
3. 16

Answer: 2
Chapter 2 - Layer 1 – Physical port configuration. Here in this chapter you will understand
about the Layer 1 Physical port configuration.
Network ports on the NT have to be administratively turned on and few additional
parameters might be set.

The port configuration on NT is performed through the "configure ethernet line"

command. Bring up the admin state of the port with the command “configure ethernet line
port admin-up”.
Depending on the configuration at the other end of the NT port, auto-negotiation can
make the NT port’s operational status down.
The “autonegotiate” parameter enables speed and duplex auto negotiation on such Fast
Ethernet ports. When auto-negotiation is enabled on a port, the link attempts to
automatically negotiate the link speed and duplex parameters, ignoring the configured
duplex and speed parameters.
To avoid depending on the other end, disable or enable auto-negotiate at the port.
To disable auto-negotiate, use the command “configure ethernet line nt:xfp:1 mau 1 no
autonegotiate ” and to enable it, use the command “configure ethernet line nt:xfp:1 mau 1
autonegotiate ”.

To check the media attachment unit, use the command “show ethernet mau”.
If you see, for example, that an electrical SFP is inserted of type 1000 base tfd, configure
this type as the new mau type and power up the administrative status of the
sfp.
The “show interface port” displays the admin state and the operational state
of the port. This should be “up” now.

13
This example shows the “show ethernet mau” command, which displays the media
attachment unit table.

As per the example, the port nt:xfp:1 advertises 1G electrical capability and the media are
available for operation, but the auto-negotiate is disabled.

The show interface port command provides the administration and operational status of
the port.

In this example, the ethernet line at nt:xfp:1 is up for administration and operation.
Operators can also check if there is SFP mismatch through the alarm current table. The
“show alarm current table” displays the alarm in the NT port.

To view the details on the “uplink etherent sfp” alarm, use the command “show alarm
current uplink-ether sfp”, followed by the alarm index number. In addition to other details,
operators can also see if there is an sfp mismatch in the output.

In the example, we see that there is an “uplink etherent sfp” current alarm.
The basic concept of the LAG is that multiple physical ports are combined into one
logical bundle. This provides benefits including:
• Increased capacity - traffic may be balanced across the member ports to provide
increased aggregate throughput.
• Link redundancy - the LAG bundle can survive the loss of one or more member
links.
The characteristics of a LAG are:
In most implementations all the ports consist of the same physical type.
(10/100/1000BASE-T), depending on the switch implementation different types of
physical ports are supported.
Speed and Duplex - Since traffic is distributed by a simple hash, it is not possible to
combine links of different speeds in the same bundle.
Ports can be added and removed on the group without the need to bring the group
down, that means services are not interrupted, only the capacity of the group is
increased or decreased.
Data should be sent to group and not to the physical ports anymore. The group will
take care of the distribution of the data over the physical links.
Link Aggregation Control Protocol (LACP) is the control protocol used for Link
Aggregation Groups.
All ports in a LAG must share the same characteristics.
LAG changes can be done only to the primary port configuration and these changes
are automatically made to the non-primary ports.
The LACP provides a standardized means for exchanging information between
Partner Systems on a link to allow their Link Aggregation Control instances to reach
agreement on the identity of the Link Aggregation Group to which the link belongs,
move the link to that Link Aggregation Group, and enable its transmission and
reception functions in an orderly manner.

Also the use of LACP requires some operator control. Especially important is the
configuration of actor-keys per physical link. This parameter identifies the Link
Aggregation Group and is exchanged within the protocol to the peer side to assure
that the links of one link aggregate really connect to the same node.

If a link fails, this is detected by LACP. It removes the link from the active set of the
link aggregate. When the link comes up again, LACP puts the link back in the active
set of the link aggregate

If a network link in a load-sharing group is lost, the traffic is redistributed across

the remaining links of the load-sharing group. The failure can be detected by
means of detection of link loss on the physical link.
The link aggregation of the uplink ports in 7362 ISAM DF/SF increases the capacity
of the resulting ISAM single network interface, and also provides link protection. In
7362 LAG is possible on the eight ethernet ports.

Link Aggregation Groups are defined by configuring individual physical links with
identical link aggregation parameters.

Load balancing across links is supported. Depending on the type of traffic (L2, IP,
MPLS) the load balancing is based on the combination of traffic parameters like
SrcMAC, DstMAC,SrcIP, DstIP, Tunnel/Service Label, Physical Port and/or TCP/UDP
Port numbers.
The LAG is configured in ISAM by first configuring the physical ports. As ports in a
LAG share the same characteristics, auto negotiation is turned-off through the "no
autonegotiate" parameter.

The LACP parameters are set next, where the lacp system priority can be set.

The LAG port parameters are set next. Especially important is the configuration of
actor-keys per physical link. This parameter identifies the Link Aggregation Group
and is exchanged within the protocol to the peer side to assure that the links of
one link aggregate really connect to the same node.

The next step is to configure the link aggregation group parameters. The max
active port number in a LAG in Mini OLT is 8.

The configured ports are added with the LAG through the configure link-agg group
(group name ) port (port id ) command.

You can check the status of the link-aggregation port, group and member port
details using the ‘’ show link-agg port-info ‘’ command

It might be a good idea to put even a single network port used for management in
a LAG from the beginning, since this prevents a service interrupt which will be
caused by reconfiguring a single port configuration into a LAG configuration.
Which of the following is a prerequisite to perform the ISAM turn-up procedure?

1. Connection to ISAM through AMS

2. Connection to ISAM through the craft port
3. Configuration of the ISAM uplinks
4. Defining ISAM system ID

Answer: 2
Chapter 3 – Layer 2- Management VLAN & Layer 3 Management IP. This chapter sheds light
on the Layer 2 and Layer 3 configuration.
Layer 1 is configured. Now we have to understand, how Layer 2 and Layer 3 are
implemented on a Mini OLT.
To create Layer 2, for our management VLAN, use “configure system mgnt-vlan-id”
command.

The management VLAN, in the example VLAN 4080, is created through the command
"configure system mgnt-vlan-id“, followed by the VLAN ID number.
The creation of the management VLAN establishes a connection between the ISAM and the
default gateway.
To set up a Layer 3, we need to assign an IP address and configure the default
route.

The host ip address is assigned via the "configure system management host-ip-
address manual" command for IPV4 and “configure system management ipv6 “ for
IPV6.

After configuring the host IP address, the default gateway has to be configured,
which will be used as the next hop for the traffic.

The default route is configured via the command "configure system management
default-route“ for IPV4 and “Configure system management ipv6 default-route” for
IPV6.

In these examples, we can see commands when the management IP

address/subnet mask of the ISAM is 192.168.1.81/22, the management VLAN ID of
the ISAM is 4080 and the default gateway IP is 192.168.0.1

For IPV6, the host is configured as 2017::21 with mask 64 and the default-route is
configured as 2018::1

A host IP address can only be changed if the default gateway is removed.

The VLAN ID 4094 in ISAM:

1. Is used for communications between the NT and ASAM interface

2. Is used for NT communications outside ISAM
3. Can be used as management VLAN
4. Is fixed internal communication VLAN
Answers: 1 and 4
Which of the following are required to establish a connection between the ISAM and the
default gateway?

1. Configuration of the ISAM IP address

2. Configuration of the default route
3. Configuration of the management VLAN
4. Configuration of the SNMP settings

Answers: 1, 2, and 3
Now lets move on to the next chapter - Layer 4 SNMP and SFTP
If the ISAM would be managed by the 5520 AMS, SNMP has to be setup. The SNMP
community is configured through the “configure system security” command.

The security functions provided by the SNMP protocols v1 and v2 follow the Community-
based Security Model, where the data protected by a password is referred to as the
community name. The community name defined for the ISAM is public. The “Community
Name” is a case sensitive character string of up to 32 characters and should match the
SNMP setting of the AMS.

The “host-address” can be used to define from which IP addresses you accept SNMP
command. The source IP in the IP header for incoming SNMP frames are checked if they
match within the host-address range, if not they will be dropped. If set all to zeros
(0.0.0.0/0) you accept from everyone. Operators can also restrict the SNMP managers by
specifying an IP address with a subnet mask instead of 0.0.0.0/0.The context is used to
assign the SNMP setting to the management instance in the ISAM.
If you want to use SNMP V3, the configuration is done as follows:
First the SNMP V3 user is created with the authentication and privacy setting as required.
Next the SNMP V3 groups is created with the security level settings. The group is linked to
either a single context or to all.
Last the SNMP V3 user is mapped into a SNMP V3 group.
Remember that authentication method values and privacy values should match with the
settings defined in the AMS.
In the example you see the creation of a user, a group and the mapping of the user into
the group.
In case SNMPv3 is used, then first configure the sftp protocol via the "configure system
security filetransfer protocol" command. The SFTP user name and password are configured
through the sftp-user option.

In this example, the sftp protocol is configured with the sftp-user "amssftp.“

Remember that authentication method values and privacy values should match with the
settings defined in the AMS.
The command "configure system security snmp community public host-address
10.15.10.206/24 context nt" configures ________.

1. SNMP v1/v2 security and allows any SNMP manager to manage ISAM
2. SNMP v1/v2 security and allows SNMP manager 10.15.10.206 to manage ISAM
3. SNMP v3 security and allows any SNMP manager to manage ISAM

Answer: 2
Chapter 5 – Additional Settings. After Layer 4 configurations there are few additional
settings that can be carried out, this chapter will illustrate the same.
An ISAM system ID identifies an NE, and this is unique for each NE.

The name that the ISAM gets in the AMS, must be provisioned and should be exactly same
as in the AMS, otherwise an alarm will be raised. To prevent it, set the parameter “system
id”.

This is configured through the “configure system ID” command.

The NE System ID prevents any LABEL mismatch alarm in the AMS.

Chapter 6 – Example. This chapter provides you with an example scenario for the turn up
procedure and the corresponding CLI commands.
Here is an example for the complete Turn-up procedure for a Mini OLT - 7362DF-
16GW
Now that you have completed this module, you should be able to:
• Perform the 7362 DF-16GW Mini OLT turn-up.
This completes the learning. Thank You.