Trabajo 2 Spanning Tree Alcatel

CONECTIVIDAD DE
REDES I
CONFIGURACIN DE SPANNING
TREE
INTEGRANTES:
Palacios Mendizbal, Ricardo

Sandoval Oviedo, Marco
Mendoza Paredes, Hans
Vargas Vieira, Juwer
Cavero Leyva, Edson
Len Sabuco, Jackeline
DOCENTE:
Umezawa Yokoyama, Julio
Martes, 06 de junio de 2014
LIMA - PER
CONFIGURACIN DE SPANNING TREE PACKET TRACER
DEDICATORIA:
A nuestra familia por tu apoyo
incondicional que nos brindan en todo
este camino de desarrollo profesional.
A Dios, por iluminar y bendecir nuestros
hogares, llenarnos de vida, voluntad y
sabidura para lograr nuestras metas.
Al profesor Alfredo, Rodrguez Gutirrez,
por su gran apoyo, exigencia y
constante motivacin para la
culminacin de este trabajo, ayudarnos
as a impulsar el desarrollo de nuestra
formacin profesional.
R62A | UNIVERSIDAD PERUANA DE CIENCIAS APLICADAS
CONFIGURACIN DE SPANNING TREE - PACKET TRACER

OBJETIVO:
Empleando los switches del fabricante seleccionado, implementar spanning
tree, sabiendo que el switch de core es un Switch Cisco en el cual se ha
configurado los siguientes VLAN:
Vlan
Vlan
Vlan
Vlan
99
10
20
30
:
:
:
:
Management.
Administracin.
Ventas.
Ingeniera.
(172.16.10.0/24) vlan nativa

(172.16.20.0/24)
(172.16.30.0/24)
(172.16.40.0/24)
El trabajo consiste en configurar el switch Cisco, pueden emplear el Switch L3

del packet tracer , adems configurar los switches que han seleccionado para la
primera parte y configurar la parte de spanning tree y el enlace con el Switch
Cisco empleando Link Aggregation del grfico mostrado.
DIAGRAMA INICIAL Y ESTADO INICIAL DE LOS PUERTOS:

Adems de un alto rendimiento y fcil manejo, los OmniSwitch 6860 ofrecen
calidad de servicio mejorada (QoS), autenticacin de usuarios, deep packet
inspection (DPI) y caractersticas seguridad integradas para asegurar el
permetro de la red, mientras que brinda alta movilidad de usuarios y otros
dispositivos con un alto grado de integracin entre la LAN cableada e
inalmbrica. Los modelos de la familia OmniSwitch 6860 tambin son
compatibles con los servicios emergentes como toma de huellas dactilares,
solicitud de anlisis de red y hasta 60 vatios de potencia a travs de Ethernet
(PoE) por puerto; por lo que es un producto preparado para las necesidades en
la evolucin de las redes empresariales.
Estos conmutadores LAN son muy verstiles y pueden posicionarse:
En redes empresariales convergentes de mediano a gran tamao.

En la capa de agregacin.
En pequeas redes empresariales como switch de core.
En el centro de datos para conectividad de servidores GigE y aplicaciones
SDN
R62A | CONECTIVIDAD DE REDES I
La familia OmniSwitch 6860 se compone de estos modelos:
OS6860E-P24
OS6860E-P48
OS6860E-24
OS6860E-48
OS6860E-U28
OS6860-P24
OS6860-P48
OS6860-24
OS6860-48
CARACTERSTICAS:
Caractersticas verstiles y modelos que ofrecen una alta densidad de

interfaces Gigabit y 10 Gigabit.
Hasta ocho switches apilables usando tecnologa de chasis virtual para
simular un solo equipo con 32 enlaces ascendentes 10 Gigabit y 384
puertos Gigabit.
IEEE 802.3af y 802.3at compatible con PoE de 30 W en todos los puertos.
Los modelos mejorados de la familia OmniSwitch 6860 soporta hasta 60 W
de PoE por cada cuatro puertos.
Hardware acelerado para DPI (deep packet inspection) disponible en todos
los modelos.
Monitorizacin de aplicaciones y las huellas digitales disponibles en los
modelos mejorados.
Funciones de Acceso Unificado avanzadas para soluciones de redes de
campus convergentes en aplicaciones para fluidez de red.
Poltica Integrada con perfiles de red dinmica de usuario.
Funciones integrales de seguridad para el control de acceso a la red (NAC),
aplicacin de polticas y contencin de ataques.
Fluidez SIP para la provisin y monitoreo de QoS a travs de flujos SIP.
Servicios de red Airgroup .
Permite el despliegue exhautivo y seguro de servicios BYOD en redes

empresariales:
Capacidades de gestin avanzada de invitados.
Dispositivo de on-boarding y automatizado IEEE 802.1x aprovisionamiento.
Postura Device / comprobacin de estado y las huellas dactilares.
Gestin de aplicaciones.
El OmniSwitch 6860 es SDN listo.
Apoyar programables AOS APIs REST, OpenFlow y OpenStack permite la
creacin de especializada servicios.
BENEFICIOS:
Con la variedad de interfaces y modelos, la familia OmniSwitch 6860

satisface cualquier necesidad de configuracin del cliente y ofrece una
excelente inversin proteccin y flexibilidad.
El OmniSwitch 6860 de chasis virtual aumenta la redundancia del sistema,
capacidad de recuperacin y alta disponibilidad al tiempo que simplifica la
implementacin, operaciones y gestin de la red.
Con sus avanzadas capacidades de PoE y alta densidad de puertos PoE, la
OmniSwitch 6860 es ideal para despliegues de campus convergentes
ofreciendo flexibilidad de despliegue, lo que simplifica el cableado y
reduciendo el tiempo a implementar los dispositivos de ltima generacin
como telfonos VoIP, cmaras de vigilancia, 802.11ac los puntos de acceso
y dispositivos emergentes que requieren mayor que 30 W, tales como
pantallas de vdeo o incluso un conmutador de red pequea o un escritorio
virtual delgada infraestructura (VDI) cliente.
La tecnologa DPI permite para la clasificacin en tiempo real de los flujos en
la aplicacin nivel, el seguimiento y el tratamiento de QoS para asignar una
mayor prioridad y ms ancho de banda para las aplicaciones crticas de
negocio.
Al activar la funcin de supervisin de aplicaciones en el OmniSwitch 6860,
los administradores de red pueden obtener una visin global de hasta 1.000
aplicaciones que se ejecutan en la red.
Este tipo de visibilidad puede ser utilizado para optimizar el rendimiento de
la red, as como aplicar adecuada de control.
Acceso Unificado y de aplicaciones de redes fluidas proporcionan
simplificada de la red arquitectura con controles automatizados y la mayor
seguridad tanto para el cable y usuarios inalmbricos. Ofrece una mejor
gestin y seguridad para reducir el costos de la complejidad operativa.
Perfiles de red de los usuarios agregan inteligencia a la red adaptarse
automticamente ya que los usuarios se mueven en torno a la empresa sin
comprometer la seguridad.
Con sus funciones avanzadas, el OmniSwitch 6860 muestra excepcional

rendimiento al apoyo de voz en tiempo real, datos y vdeo.
Mejora de la experiencia del usuario con la integracin de los servicios que
permiten a empleados para acceder a las mismas aplicaciones y servicios, y
tienen constante experiencia a travs de cable e inalmbricas.
El OmniSwitch 6860 ofrece opciones flexibles de implementacin y permite
al red para despliegues BYOD y de gestin de clientes zero-touch.
Soporta el cambio dinmico de autenticacin (CoA) y hace cumplir el trfico
remediacin o restriccin para los dispositivos que no cumplen.
Proporciona un control y una mayor seguridad sobre datos corporativos /
aplicaciones para el entorno personal y empresarial mixto para mejorar la
visibilidad y controlar las TI.
Abre la puerta para el despliegue rpido de nuevos servicios de red que
cumplen necesidades de los empleados a adoptar continuamente nuevas
aplicaciones que soportan el negocio.
El apoyo de SDN tranquiliza a los clientes que su inversin est listo para el
futuro y permite la interoperabilidad con soluciones de terceros.
ESTUDIO DE LAS FUNCIONES DEL SWITCH:

Flow Control and Autonegotiation
PAUSE frames are used to pause the flow of traffic between two connected
devices when traffic congestion occurs. Flow control provides the ability to
configure whether or not the switch will transmit and/or honor PAUSE frames on
an active interface. This feature is supported on standalone OmniSwitch 6400,
OmniSwitch 6850, and OmniSwitch 6855 switch interfaces configured to run in
full-duplex mode. An OmniSwitch chassis-based switch or a stack of switches
will honor and process receive PAUSE frames but do not transmit any such
frames.
In addition to configuring flow control settings, this feature also works in
conjunction with autonegotiation to determine operational transmit/receive
settings for PAUSE frames between two switches. Note that the operational
settings, as shown in the following table, override the configured settings as
long as autonegotiation and flow control are both enabled for the interface:
If autonegotiation is disabled, the configured flow control settings are applied to

the local interface.
Configuring Flow Control on Non-Combo Ports

The interfaces pause command is used to configure end-to-end (E2E) flow
control (pause) settings for non-combo ports that run in full duplex mode.
Configuring flow control is done to specify whether or not an interface will
transmit, honor, or both transmit and honor PAUSE frames. PAUSE frames are
used to temporarily pause the flow of traffic between two connected devices to
help prevent packet loss when traffic congestion occurs between switches.
Using the interfaces pause command alone is sufficient to configure E2E flow
control on a 24-port OmniSwitch 6400, a 24-port OmniSwitch 6850 and an
OmniSwitch 6855 running in standalone mode.
However, if a switch is a 48-port switch running in standalone mode, then a flow
control VLAN is required in addition to enabling flow control. This type of VLAN is
configured using the interfaces e2eflow-vlan command.
Although E2E flow control is only supported on standalone OmniSwitch 6400,

OmniSwitch 6850, and OmniSwitch 6855 switches, it is possible to configure a
stack of switches or a chassis-based switch to honor PAUSE frames only. This is
also done with the interfaces pause command.
Note that if autonegotiation and flow control are both enabled for an interface,
then autonegotiation determines how the interface will process PAUSE frames.
See Flow Control and Autonegotiation on page 1-9 for more information. If
autonegotiation is disabled but flow control is enabled, then the configured flow
control settings apply.
By default, flow control is disabled. To configure flow control for one or more
ports, use the interfaces pause command with one of the following parameters
to specify how PAUSE frames are processed:
txTransmit PAUSE frames to peer switches when traffic congestion occurs
on the local interface. Do not honor PAUSE frames from peer switches.
rxAllow the interface to honor PAUSE frames from peer switches and
temporarily stop sending traffic to the peer. Do not transmit PAUSE frames
to peer switches.
tx-and-rxTransmit and honor PAUSE frames when traffic congestion
occurs between peer switches.
For example, the following command configures ports 1/1 through 1/10 to
transmit and honor PAUSE frames:
-> interfaces 1/1-10 pause tx-and-rx
To disable flow control for one or more ports, specify the disable parameter
with the interfaces pause command. For example:
-> interfaces 1/10 pause disable
If the interfaces pause command is used to configure E2E flow control on a
48-port standalone OmniSwitch 6400 or OmniSwitch 6850, then configuring a
flow control VLAN is also required. For example, the following command
configures VLAN 700 as a flow control VLAN:
-> interfaces e2e-flow-vlan 700
Note that the VLAN specified with the above command must already exist in the
switch configuration. In addition, flow control VLANs are not configurable using
standard VLAN management commands.
There is only one flow control VLAN configured per switch. To remove this type
of VLAN, use the no form of the interfaces e2e-flow-vlan command. Note
that specifying a VLAN ID is not necessary. For example, the following command
removes the flow control VLAN from the switch configuration:
-> interfaced no e2e-flow-vlan
Configuring Flow Control on Non-Combo Ports

The interfaces hybrid pause command is used to configure flow control
(pause) settings for combo ports that run in full duplex mode. Configuring flow
control is done to specify whether or not an interface will transmit, honor, or
both transmit and honor PAUSE frames. PAUSE frames are used to temporarily
pause the flow of traffic between two connected devices to help prevent packet
loss when traffic congestion occurs between switches.
Using the interfaces hybrid pause command alone is sufficient to configure
E2E flow control on a 24-port OmniSwitch 6400, a 24-port OmniSwitch 6850 and
an OmniSwitch 6855 running in standalone mode. However, if a switch is a 48port switch running in standalone mode, then a flow control VLAN is required in
addition to enabling flow control. This type of VLAN is configured using the
interfaces e2eflow-vlan command.
Although E2E flow control is only supported on standalone OmniSwitch 6400,
OmniSwitch 6850, and OmniSwitch 6855 switches, it is possible to configure a
stack of switches or a chassis-based switch to honor PAUSE frames only. This is
also done with the interfaces pause command.
Note that if autonegotiation and flow control are both enabled for an interface,
then autonegotiation determines how the interface will process PAUSE frames.
See Flow Control and Autonegotiation on page 1-9 for more information. If
autonegotiation is disabled but flow control is enabled, then the configured flow
control settings apply.
By default, flow control is disabled. To configure flow control for one or more
ports, use the interfaces hybrid pause command with one of the following
parameters to specify how PAUSE frames are processed:
txTransmit PAUSE frames to peer switches when traffic congestion occurs
on the local interface. Do not honor PAUSE frames from peer switches.
rxAllow the interface to honor PAUSE frames from peer switches and
temporarily stop sending traffic to the peer. Do not transmit PAUSE frames
to peer switches.
tx-and-rxTransmit and honor PAUSE frames when traffic congestion

occurs between peer switches. For example, the following command
configures port 1/23 to transmit and honor PAUSE frames:
-> interfaces 1/23 hybrid fiber pause tx-and-rx
To disable flow control, use the disable parameter with the interfaces hybrid
pause command.
For example:
-> interfaces 1/23 hybrid fiber pause disable
If the interfaces hybrid pause command is used to configure E2E flow control
on a 48-port standalone OmniSwitch 6400 or OmniSwitch 6850, then
configuring a flow control VLAN is also required. For example, the following
command configures VLAN 700 as a flow control VLAN:
-> interfaces e2e-flow-vlan 700
Note that the VLAN specified with the above command must already exist in the
switch configuration. In addition, flow control VLANs are not configurable using
standard VLAN management commands.
There is only one flow control VLAN configured per switch. To remove this type
of VLAN, use the no form of the interfaces e2e-flow-vlan command. Note
that specifying a VLAN ID is not necessary. For example, the following command
removes the flow control VLAN from the switch configuration:
-> interfaced no e2e-flow-vlan
Port Mirroring
On chassis-based or standalone switches, you can set up port mirroring sessions
between Ethernet ports within the same switch, while on stackable switches,
you can set up port mirroring sessions across switches within the same stack.
Ethernet
ports
supporting
port
mirroring
include
10BaseT/100BaseTX/1000BaseT (RJ-45), 1000BaseSX/LX/LH, and 10GBaseS/L
(LC) connectors. When port mirroring is enabled, the active mirrored port
transmits and receives network traffic normally, and the mirroring port
receives a copy of all transmit and receive traffic to the active port. You can
connect an RMON probe or network analysis device to the mirroring port to see
an exact duplication of traffic on the mirrored port without disrupting network
traffic to and from the mirrored port.
Port mirroring runs in the Chassis Management software and is supported for
Ethernet (10 Mbps), FastEthernet (100 Mbps), Gigabit Ethernet (1000 Mpbs), and
10 Gigabit Ethernet (10000 Mbps) ports. In addition, the switch supports N-to1 port mirroring, where up to 24 (OmniSwitch 6800) or 128 (OmniSwitch 6400,
6850, 6855, and 9000) source ports can be mirrored to a single destination port.
Note the following restriction when configuring a port mirroring session:
Two (2) port mirroring sessions are supported per standalone chassis-based
switch or in a stack consisting of two or more switches.
You cannot configure a port mirroring and a port monitoring session on the
same NI module in an OmniSwitch chassis-based switch.
You cannot configure port mirroring and monitoring on the same switching
ASIC on OmniSwitch 6400, 6850, and 6855 switches. Each switching ASIC
controls 24 ports (e.g., ports 124, 2548, etc.). For example, if a port
mirroring session is configured for ports 1/12 and 1/22, then configuring a
port monitoring session for any of the ports between 1 and 24 is not
allowed.
You cannot configure port mirroring and monitoring on the same switching
ASIC on OmniSwitch 6800 Series switches. Each switching ASIC controls 12
ports (e.g., ports 112, 1324, etc.). For example, if a port mirroring session
is configured for ports 1/6 and 1/10, then configuring a port monitoring
session for any of the ports between 1 and 12 is not allowed.
If a port mirroring session is configured across two switching ASICs, then
configuring a monitoring session is not allowed on any of the ports
controlled by each of the ASICs involved. For example, if a port mirroring
session is configured for ports 1/8 and 1/30 on a 48-port switch, then
configuring a port monitoring session involving any of the ports between 1
and 48 is not allowed.
What Ports Can Be Mirrored?

Mirroring between any 10/100/1000 port to any other 10/100/1000 port and
between any SFP to any other SFP port is supported.
How Port Mirroring Works

When a frame is received on a mirrored port, it is copied and sent to the
mirroring port. The received frame is actually transmitted twice across the
switch backplaneonce for normal bridging and then again to the mirroring port.
When a frame is transmitted by the mirrored port, a copy of the frame is made,
tagged with the mirroring port as the destination, and sent back over the switch
backplane to the mirroring port. The diagram below illustrates the data flow
between the mirrored and mirroring ports. Diagnosing Switch Problems Port
Mirroring OmniSwitch AOS Release 6 Network Configuration Guide September
2009 page 45-15 Note that when port mirroring is enabled, there may be some
performance degradation, since all frames received and transmitted by the
mirrored port need to be copied and sent to the mirroring port.
What Happens to the Mirroring Port

When you set up port mirroring and attach cables to the mirrored and mirroring
ports, the mirroring port remains enabled and is a part of the Bridging Spanning
Tree until you protect it from Spanning Tree updates by specifying an unblocked
VLAN as part of the configuration command line. The mirroring port does not
transmit or receive any traffic on its own.
Mirroring on Multiple Ports

If mirroring is enabled on multiple ports and the same traffic is passing through
these ports, then only one copy of each packet is sent to the mirroring
destination.
When the packet is mirrored for the first time, the switching ASIC flags the
packet as already mirrored If the packet goes through one more port where
mirroring is enabled, that packet will not be mirrored again. If both mirroring and
monitoring are enabled then the packet will be either mirrored or monitored
(i.e., sent to CPU), whichever comes first.
Using Port Mirroring with External RMON Probes

Port mirroring is a helpful monitoring tool when used in conjunction with an
external RMON probe. Once you set up port mirroring, the probe can collect all
relevant RMON statistics for traffic on the mirrored port. You can also move the
mirrored port so that the mirroring port receives data from different ports. In this
way, you can roam the switch and monitor traffic at various ports.
The diagram on the following page illustrates how port mirroring can be used
with an external RMON probe to copy RMON probe frames and Management
frames to and from the mirroring and mirrored ports.
Frames received from an RMON probe attached to the mirroring port can be
seen as being received by the mirrored port. These frames from the mirroring
port are marked as if they are received on the mirrored port before being sent
over the switch backplane to an NMS station. Therefore, management frames
destined for the RMON probe are first forwarded out of the mirrored port.
After being received on the mirrored port, copies of the frames are mirrored out
of the mirroring portthe probe attached to the mirroring port receives the
management frames.
Remote Port Mirroring

Remote Port Mirroring expands the port mirroring functionality by allowing
mirrored traffic to be carried over the network to a remote switch. With Remote
Port Mirroring the traffic is carried over the network using a dedicated Remote
Port Mirroring VLAN, no other traffic is allowed on this VLAN.
The mirrored traffic from the source switch is tagged with the VLAN ID of the
Remote Port Mirroring VLAN and forwarded over the intermediate switch ports to
the destination switch where an analyzer is attached. Since Remote Port
Mirroring requires traffic to be carried over the network, the following exceptions
to regular port mirroring exist:
Spanning Tree must be disabled for the Remote Port Mirroring VLAN on all
switches.
There must not be any physical loop present in the Remote Port Mirroring
VLAN.
On the intermediate and destination switches, source learning must be
disabled or overridden on the ports belonging to the Remote Port Mirroring
VLAN.
The QoS redirect feature can be used to override source learning on an
OmniSwitch. The following types of traffic will not be mirrored:
Link Aggregation Control Packets (LACP)
802.1AB (LLDP)
802.1x port authentication
802.3ag (OAM)
Layer 3 control packets
Generic Attribute Registration Protocol (GARP)
BPDUs will not be mirrored on OmniSwitch 6400, 6850, and 6855 switchess
but will be mirrored on OmniSwitch 9000 switches.
Ring Rapid Spanning Tree Protocol (RRSTP)
RRSTP is only supported on VLAN Stacking NNI ports; UNI ports are not
supported.
An RRSTP ring must consist of either all VLAN Stacking NNI ports or all
standard switch ports; a mixture of the two port types in the same ring is
not supported.
If an RRSTP ring contains NNI ports, the VLAN tag configured for the ring
must match the SVLAN tag that VLAN Stacking appends to packets before
they are received or forwarded on NNI ports.
Spanning Tree
Spanning Tree is enabled by default for VLAN Stacking SVLANs. The

Spanning Tree status for an SVLAN is configurable through VLAN Stacking
commands. Note that the SVLAN Spanning Tree status applies only to the
service provider network topology.
BPDU frames are tunneled by default. See Configuring a UNI Profile on

page 9-19 for information about configuring VLAN Stacking to tunnel or
discard Spanning Tree BPDU.
See Configuring VLAN Stacking Network Ports on page 9-14 for
information about configuring VLAN Stacking interoperability with legacy
Spanning Tree BPDU systems.
A back door link configuration is not supported. This occurs when there is a
link between two customer sites that are both connected to a VLAN Stacking
provider edge switch.
A dual home configuration is not supported. This type of configuration
consists of a single customer site connected to two different VLAN Stacking
switches or two switches at a customer site connect to two different VLAN
Stacking switches.
USING 802.1Q 2005

Multiple Spanning Tree
The Alcatel-Lucent Multiple Spanning Tree (MST) implementation provides
support for the Multiple Spanning Tree Protocol (MSTP) as defined in the IEEE
802.1Q 2005 standard. In addition to the 802.1D Spanning Tree Algorithm and
Protocol (STP) and the 802.1w Rapid Spanning Tree Algorithm and Protocol
(RSTP), MSTP also ensures that there is always only one data path between any
two switches for a given Spanning Tree instance to prevent network loops.
MSTP is an enhancement to the 802.1Q Common Spanning Tree (CST), which is
provided when an Alcatel-Lucent switch is running in the flat Spanning Tree
operating mode. The flat mode applies a single spanning tree instance across all
VLAN port connections on a switch. MSTP allows the configuration of Multiple
Spanning Tree Instances (MSTIs) in addition to the CST instance. Each MSTI is
mapped to a set of VLANs. As a result, flat mode can support the forwarding of
VLAN traffic over separate data paths. In addition to MSTP support, the STP and
RSTP are still available in either the flat or 1x1 mode.
However, if using STP or RSTP in the flat mode, the single Spanning Tree
instance per switch algorithm applies.
Spanning Tree Specifications
Spanning Tree Bridge Parameter Defaults
Spanning Tree Port parameter Defaults
Multiple Spanning Tree Region Defaults
CONFIGURING STATIC LINK AGGREGATION

Alcatel-Lucents static link aggregation software allows you to combine several
physical links into one large virtual link known as a link aggregation group.
Using link aggregation provides the following benefits:
Scalability. It is possible to configure up to 32 link aggregation groups that

consist of 2, 4, or 8 10 Mbps, 100-Mbps, 1-Gbps, or 10-Gbps Ethernet links.
Reliability. If one of the physical links in a link aggregate group goes down
(unless it is the last one) the link aggregate group can still operate.
Ease of Migration. Link aggregation can ease the transition from 100Mbps Ethernet backbones to Gigabit Ethernet backbones.
Static Link Aggregation Specifications
Static Link Aggregation Default Values
QUICK STEPS FOR CONFIGURING STATIC LINK AGGREGATION

Follow the steps below for a quick tutorial on configuring a static aggregate link
between two switches. Additional information on how to configure each
command is given in the subsections that follow.
1. Create the static aggregate link on the local switch with the static linkagg
size command. For example:
-> static linkagg 1 size 4
2. Assign all the necessary ports with the static agg agg num command. For
example:
-> static agg 1/1 agg num 1
3. Create a VLAN for this static link aggregate group with the vlan command.
For example:
-> vlan 10 port default 1
4. Create the equivalent static aggregate link on the remote switch with the
static linkagg size command. For example:
5. Assign all the necessary ports with the static agg agg num command. For
example:
6. Create a VLAN for this static link aggregate group with the vlan command.
For example:
Note. Optional. You can verify your static link aggregation settings with the
show linkagg command. For example:
-> show linkagg 1
Static Aggregate
SNMP Id : 40000001,
Aggregate Number : 1,
SNMP Descriptor : Omnichannel Aggregate Number 1 ref 40000001 size 4,
Name : ,
Admin State : ENABLED,
Operational State : UP,
Aggregate Size : 4,
Number of Selected Ports : 4,
Number of Reserved Ports : 4,
Number of Attached Ports : 4,
Primary Port : 1/1
An example of what these commands look like entered sequentially on the

command line on the local switch:
And an example of what these commands look like entered sequentially on the
command line on the remote switch:
Static Link Aggregation Overview

Link aggregation allows you to combine 2, 4, or 8 physical connections into
large virtual connections
known as link aggregation groups. You can configure up to 32 link aggregation
groups per a standalone switch or a stack of switches. Each group can consist of
2, 4, or 8 10-Mbps, 100-Mbps, 1-Gbps, or 10-Gbps Ethernet links.
You can create Virtual LANs (VLANs), 802.1Q framing, configure Quality of
Service (QoS) conditions,
and other networking features on link aggregation groups because the switchs
software treats these virtual links just like physical links. (See Relationship to
Other Features on page 22-6 for more information on how link aggregation
interacts with other software features.)
Load balancing for Layer 2 non-IP packets is on a MAC address basis and for IP
packets the balancing algorithm uses IP address as well. Ports must be of the
same speed within the same link aggregate group.
Alcatel-Lucents link aggregation software allows you to configure the following
two different types of link aggregation groups:
Static link aggregate groups

Dynamic link aggregate groups
Static Link Aggregation Operation

Static link aggregate groups are virtual links between two nodes consisting of 2,
4, or 8 10-Mbps, 100-Mbps, or 1-or 10-Gbps fixed physical links. You can
configure up to 32 link aggregation groups per astandalone switch or a stack of
switches. Static aggregate groups can be created between each of the following
OmniSwitch products:
two OmniSwitch 6400, 6800, 6850, 6855, or 9000 switches.

an OmniSwitch 6400, 6800, 6850, 6855, or 9000 switch and an OmniSwitch
7700/7800, OmniSwitch 8800, or OmniSwitch 6600 Series switch.
an OmniSwitch 6400, 6800, 6850, 6855, or 9000 switch and an earlygeneration Alcatel-Lucent switch, such as an Omni Switch/Router.
The figure below shows a static aggregate group that has been configured
between Switch A and Switch B. The static aggregate group links four ports on a
single OS9-GNI-C24 on Switch A to two ports on one OS9-GNI-C24 and two ports
on another OS9-GNI-C24 on Switch B. The network administrator has created a
separate VLAN for this group so users can use this high speed link.
CONFIGURING DYNAMIC LINK AGGREGATION

Alcatel-Lucents dynamic link aggregation software allows you to combine
several physical links into one large virtual link known as a link aggregation
group. Using link aggregation provides the following benefits:
Scalability. It is possible to configure up to 32 link aggregation groups that

consist of 2, 4, or 8 10-Mbps, 100-Mbps, 1-Gbps, or 10-Gbps Ethernet links.
Reliability. If one of the physical links in a link aggregate group goes down
(unless it is the last one) the link aggregate group can still operate.
Ease of Migration. Link aggregation can ease the transition from 100Mbps Ethernet backbones to Gigabit Ethernet backbones.
Dynamic Link Aggregation Specifications
Dynamic Link Aggregation Default Values
Quick Steps for Configuring Dynamic Link Aggregation

Follow the steps below for a quick tutorial on configuring a dynamic aggregate
link between two switches. Additional information on how to configure each
command is given in the subsections that follow.
1. Create the dynamic aggregate group on the local (actor) switch with the
lacp linkagg size command as shown below:
-> lacp linkagg 2 size 8 actor admin key 5
2. Configure ports (the number of ports should be less than or equal to the size
value set in step 1) with the same actor administrative key (which allows
them to be aggregated) with the lacp agg actor admin key command. For
example:
-> lacp agg 1/1 actor admin key 5
3. Create a VLAN for this dynamic link aggregate group with the vlan
command. For example:
4. Create the equivalent dynamic aggregate group on the remote (partner)

switch with the lacp linkagg size command as shown below:
5. Configure ports (the number of ports should be less than or equal to the size
value set in step 4) with the same actor administrative key (which allows
them to be aggregated) with the lacp agg actor admin key command. For
example:
6. Create a VLAN for this dynamic link aggregate group with the vlan
Note. As an option, you can verify your dynamic aggregation group settings
with the show linkagg
command on either the actor or the partner switch. For example:
-> show linkagg 2
Dynamic Aggregate
SNMP Id : 40000002,
Aggregate Number : 2,
SNMP Descriptor : Dynamic Aggregate Number 2 ref 40000002 size 8,
Name : ,
Admin State : ENABLED,
Operational State : UP,
Aggregate Size : 8,
Number of Selected Ports : 8,
Number of Reserved Ports : 8,
Number of Attached Ports : 8,
Primary Port : 1/1,
LACP
MACAddress : [00:1f:cc:00:00:00],
Actor System Id : [00:20:da:81:d5:b0],
Actor System Priority : 0,
Actor Admin Key : 5,
Actor Oper Key : 0,
Partner System Id : [00:20:da:81:d5:b1],
Partner System Priority : 0,
Partner Admin Key : 5,
Partner Oper Key : 0

command line on the actor switch:

command line on the partner switch:
Dynamic Link Aggregation Overview

Link aggregation allows you to combine 2, 4, or 8 physical connections into
large virtual connections
known as link aggregation groups. You can configure up to 32 link aggregation
groups per a standalone switch or a stack of switches. Each group can consist of
2, 4, or 8 10-Mbps, 100-Mbps, 1-Gbps, or 10-Gbps Ethernet links.
You can create Virtual LANs (VLANs), 802.1Q framing, configure Quality of
Service (QoS) conditions,
and other networking features on link aggregation groups because switch
software treats these virtual links just like physical links. (See Relationship to
Other Features on page 23-9 for more information on how link aggregation
interacts with other software features.)
Link aggregation groups are identified by unique MAC addresses, which are
created by the switch but can be modified by the user at any time. Load
balancing for Layer 2 non-IP packets is on a MAC address basis and for IP
packets the balancing algorithm uses the IP address as well. Ports must be of
the same speed within the same aggregate group.
Alcatel-Lucents link aggregation software allows you to configure the following
two different types of link aggregation groups:
Static link aggregate groups

Dynamic link aggregate groups
Dynamic Link Aggregation Operation

Dynamic aggregate groups are virtual links between two nodes consisting of 2,
4, or 8 10-Mbps, 100-Mbps, or 1-or 10-Gbps fixed physical links. Dynamic
aggregate groups use the standard IEEE 802.3ad Link Aggregation Control
Protocol (LACP) to dynamically establish the best possible configuration for the
group. This task is accomplished by special Link Aggregation Control Protocol
Data Unit (LACPDU) frames that are sent and received by switches on both sides
of the link to monitor and maintain the dynamic aggregate group. The figure on
the following page shows a dynamic aggregate group that has been configured
between Switch A and Switch B. The dynamic aggregate group links four ports
on Switch A to four ports on Switch B.
Dynamic aggregate groups can be created between each of the following

OmniSwitch products:
two OmniSwitch 6400, 6800, 6850, 6855, or 9000 switches.

an OmniSwitch 6400, 6800, 6850, 6855, or 9000 switch and an OmniSwitch
7700/7800, OmniSwitch 8800, or OmniSwitch 6600 Series switch.
an OmniSwitch 6400, 6800, 6850, 6855, or 9000 switch and an earlygeneration Alcatel-Lucent switch, such as an Omni Switch/Router.
an OmniSwitch 6400, 6800, 6850, 6855, or 9000 switch and another
vendors switch if that vendor supports IEEE 802.3ad LACP.
CONFIGURING LEARNED PORT SECURITY

Learned Port Security (LPS) provides a mechanism for authorizing source

learning of MAC addresses on Ethernet and Gigabit Ethernet ports. The only
types of Ethernet ports that LPS does not support are link aggregate and tagged
(trunked) link aggregate ports. Using LPS to control source MAC address learning
provides the following benefits:
A configurable source learning time limit that applies to all LPS ports.
A configurable limit on the number of MAC addresses allowed on an LPS
port.
Dynamic configuration of a list of authorized source MAC addresses.
Static configuration of a list of authorized source MAC addresses.
Two methods for handling unauthorized traffic: stopping all traffic on the
port or only blocking traffic that violates LPS criteria.
Learned Port Security Specifications
Learned Port Security Defaults

Sample Learned Port Security Configuration

This section provides a quick tutorial that demonstrates the following tasks:
Enabling LPS on a set of switch ports.

Defining the maximum number of learned MAC addresses allowed on an LPS
port.
Defining the time limit in which source learning is allowed on all LPS ports.
Selecting a method for handling unauthorized traffic received on an LPS
port.
Note that LPS is supported on Ethernet and gigabit Ethernet fixed, mobile,
tagged and authenticated ports.
Link aggregate and tagged (trunked) link aggregate ports are not eligible for LPS
monitoring and control.
1. Enable LPS on ports 6 through 12 on slot 3, 4, and 5 using the following

command:
-> port-security 3/6-12 4/6-12 5/6-12 enable
2. Set the total number of learned MAC addresses allowed on the same ports
to 25 using the following command:
-> port-security 3/6-12 4/6-12 5/6-12 maximum 25
3. Configure the amount of time in which source learning is allowed on all LPS
ports to 30 minutes using the following command:
-> port-security shutdown 30
4. Select shutdown for the LPS violation mode using the following command:
-> port-security 3/6-12 4/6-12 5/6-12 violation shutdown
Note. Optional. To verify LPS port configurations, use the port-security learntrap-threshold command. For example:
-> show port-security
Port: 1/30
Operation Mode : DISABLED,
Max Bridged MAC allowed : 1,
Max Filtered MAC allowed : 5,
Low End of MAC Range : 00:00:00:00:00:00,
High End of MAC Range : ff:ff:ff:ff:ff:ff,
Violation Setting : RESTRICT,
MAC VLAN MAC TYPE
-------------------+------+-------------------
00:20:95:00:fa:5c 1 STATIC
To verify the new source learning time limit value, use the show port-security
shutdown command. For example:
-> show port-security shutdown
LPS Shutdown Config = 2 min
Convert-to-static = DISABLE
Remaining Learning Window = 110 sec
Learned Port Security Overview

Learned Port Security (LPS) provides a mechanism for controlling network device
access on one or more switch ports. Configurable LPS parameters allow the user
to restrict the source learning of host MAC addresses to:
A specific amount of time in which the switch allows source learning to occur
on all LPS ports.
A maximum number of learned MAC addresses allowed on the port.
A list of configured authorized source MAC addresses allowed on the port.
Additional LPS functionality allows the user to specify how the LPS port handles
unauthorized traffic. The following two options are available for this purpose:
Block only traffic that violates LPS port restrictions; authorized traffic is
forwarded on the port.
Disable the LPS port when unauthorized traffic is received; all traffic is
stopped and a port reset is required to return the port to normal operation.
LPS functionality is supported on the following Ethernet and Gigabit Ethernet

port types:
Fixed (non-mobile)
Mobile
802.1Q tagged
Authenticated
802.1x
The following port types are not supported:
Link aggregate
Tagged (trunked) link aggregate
CONFIGURIN VLANs
In a flat bridged network, a broadcast domain is confined to a single LAN
segment or even a specific physical location, such as a department or building
floor. In a switch-based network, such as one comprised of Alcatel-Lucent
switching systems, a broadcast domainor VLAN can span multiple physical
switches and can include ports from a variety of media types. For example, a
single VLAN could span three different switches located in different buildings
and include 10/100 Ethernet, Gigabit Ethernet, 802.1q tagged ports and/or a
link aggregate of ports.
VLAN Specifications
Note that the maximum limit values provided in the following Specifications
table are subject to available system resources:
VLAN Defaults
Sample VLAN Configuration

The following steps provide a quick tutorial that will create VLAN 255. Also
included are steps to define a VLAN description, IP router interface, and static
switch port assignments.
Note. Optional. Creating a new VLAN involves specifying a VLAN ID that is not
already assigned to an existing VLAN. To determine if a VLAN already exists in
the switch configuration, enter show vlan. If VLAN 255 does not appear in the
show vlan output, then it does not exist on the switch. For example:
1. Create VLAN 255 with a description (e.g., Finance IP Network) using the
following command:
-> vlan 255 name Finance IP Network
2. Define an IP router interface using the following command to assign an IP

host address of 21.0.0.10 to VLAN 255 that will enable routing of VLAN
traffic to other subnets:
-> ip interface vlan-255 address 21.0.0.10 vlan 255
3. Assign switch ports 2 through 4 on slot 3 to VLAN 255 using the following
command:
-> vlan 255 port default 3/2-4
Note. Optional. To verify the VLAN 255 configuration, use the show vlan
-> show vlan 255
Name : Finance IP Network,
Administrative State: enabled,
Operational State : disabled,
1x1 Spanning Tree State : enabled,
Flat Spanning Tree State : enabled,
Authentication : disabled,
IP Router Port : 21.0.0.10 255.0.0.0 forward e2,
IPX Router Port : none
Mobile Tag : off
To verify that ports 3/2-4 were assigned to VLAN 255, use the show vlan port
-> show vlan 255 port
port type status
--------+---------+--------------
3/2 default inactive
VLAN Management Overview
One of the main benefits of using VLANs to segment network traffic, is that
VLAN configuration and port assignment is handled through switch software.
This eliminates the need to physically change a network device connection or
location when adding or removing devices from the VLAN broadcast domain.
The VLAN management software handles the following VLAN configuration tasks
performed on an Alcatel-Lucent switch:
Creating or modifying VLANs.

Assigning or changing default VLAN port associations (VPAs).
Enabling or disabling VLAN participation in the current Spanning Tree
algorithm.
Enabling or disabling classification of mobile port traffic by 802.1Q tagged
VLAN ID.
Enabling or disabling VLAN authentication.
Defining VLAN IPX router interfaces to enable routing of VLAN IPX traffic.
Enabling or disabling unique MAC address assignments for each router VLAN
defined.
Displaying VLAN configuration information. In addition to the above tasks,
VLAN management software tracks and reports the following information to
other switch software applications:
VLAN configuration changes, such as adding or deleting VLANs, modifying
the status of VLAN properties (e.g., administrative, Spanning Tree, and
authentication status), changing the VLAN description, or configuring VLAN
router interfaces.
VLAN port associations triggered by VLAN management and other switch
software applications, such as 802.1Q VLAN tagging and dynamic mobile
port assignment.
The VLAN operational state, which is inactive until at least one active switch
port is associated with the VLAN.
BIBLIOGRAFIA
OmniSwitch AOS Release 6.4.5 CLI Reference Guide.

Noviembre 06, 2013.
OmniSwitch AOS Release 6.4.5 Network Configuration Guide.

Julio 03, 2013.
OmniSwitch AOS Release 6.4.3.R01 Feature Guidelines.

Abril 08, 2011.
Folleto comercial Alcatel-LucentOmniSwitch 6860
Julio 12, 2013.

Trabajo 2 Spanning Tree Alcatel

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Trabajo 2 Spanning Tree Alcatel

Diunggah oleh

Hak Cipta:

Format Tersedia

CONECTIVIDAD DE

Palacios Mendizbal, Ricardo

Martes, 06 de junio de 2014

CONFIGURACIN DE SPANNING TREE PACKET TRACER

R62A | UNIVERSIDAD PERUANA DE CIENCIAS APLICADAS

CONFIGURACIN DE SPANNING TREE - PACKET TRACER

(172.16.10.0/24) vlan nativa

El trabajo consiste en configurar el switch Cisco, pueden emplear el Switch L3

DIAGRAMA INICIAL Y ESTADO INICIAL DE LOS PUERTOS:

En redes empresariales convergentes de mediano a gran tamao.

R62A | CONECTIVIDAD DE REDES I

La familia OmniSwitch 6860 se compone de estos modelos:

Caractersticas verstiles y modelos que ofrecen una alta densidad de

R62A | CONECTIVIDAD DE REDES I

Permite el despliegue exhautivo y seguro de servicios BYOD en redes

Con la variedad de interfaces y modelos, la familia OmniSwitch 6860

R62A | CONECTIVIDAD DE REDES I

Con sus funciones avanzadas, el OmniSwitch 6860 muestra excepcional

ESTUDIO DE LAS FUNCIONES DEL SWITCH:

R62A | CONECTIVIDAD DE REDES I

If autonegotiation is disabled, the configured flow control settings are applied to

Configuring Flow Control on Non-Combo Ports

R62A | CONECTIVIDAD DE REDES I

Although E2E flow control is only supported on standalone OmniSwitch 6400,

-> interfaced no e2e-flow-vlan

Configuring Flow Control on Non-Combo Ports

R62A | CONECTIVIDAD DE REDES I

tx-and-rxTransmit and honor PAUSE frames when traffic congestion

What Ports Can Be Mirrored?

How Port Mirroring Works

What Happens to the Mirroring Port

Mirroring on Multiple Ports

Using Port Mirroring with External RMON Probes

R62A | CONECTIVIDAD DE REDES I

Remote Port Mirroring

Ring Rapid Spanning Tree Protocol (RRSTP)

Spanning Tree is enabled by default for VLAN Stacking SVLANs. The

R62A | CONECTIVIDAD DE REDES I

BPDU frames are tunneled by default. See Configuring a UNI Profile on

USING 802.1Q 2005

Spanning Tree Specifications

R62A | CONECTIVIDAD DE REDES I

Spanning Tree Bridge Parameter Defaults

R62A | CONECTIVIDAD DE REDES I

Spanning Tree Port parameter Defaults

R62A | CONECTIVIDAD DE REDES I

Multiple Spanning Tree Region Defaults

CONFIGURING STATIC LINK AGGREGATION

Scalability. It is possible to configure up to 32 link aggregation groups that

R62A | CONECTIVIDAD DE REDES I

Static Link Aggregation Specifications

Static Link Aggregation Default Values

QUICK STEPS FOR CONFIGURING STATIC LINK AGGREGATION

R62A | CONECTIVIDAD DE REDES I

R62A | CONECTIVIDAD DE REDES I

-> static agg 1/12 agg num 1

-> show linkagg 1

SNMP Descriptor : Omnichannel Aggregate Number 1 ref 40000001 size 4,

Admin State : ENABLED,

Operational State : UP,

Number of Selected Ports : 4,

Number of Reserved Ports : 4,

Number of Attached Ports : 4,

R62A | CONECTIVIDAD DE REDES I