To configure a Private VLAN:
1
Set VTP mode to transparent
2
Create the secondary Private VLANs
3
Create the primary Private VLAN
4
Associate the secondary with the primary. Only 1
isolated private VLAN can be mapped to a primary VLAN but more than one
community Private VLAN can be mapped to a primary Private VLAN
5
Configure an interface as an isolated or community port
6
Associate the isolated port or community port with the
primary-secondary Private VLAN pair
7
Configure an interface as a promiscuous port
8
Map the promiscuous port to the primary-secondary
Private VLAN pair
To configure Private VLANs in Cisco IOS:
1
Global config to configure Private VLANs: vlan pvlan-id
2
Configure the type of Private VLAN: private-vlan {community | isolated |
primary}
3
Exit config mode
4
Global config: vlan
primary-vlan-id
5
If it’s a primary VLAN, make sure to associate the
Layer 2 secondary VLAN to the primary VLAN: private-vlan association {secondary-vlan-list
| add secondary-vlan-list | remove
secondary-vlan-list}
6
Select the interface configuration mode for the primary
VLAN from the global config: interface
vlan primary-vlan-id
7
Map secondary VLAN to the Layer 3 VLAN interface of a
primary VLAN to allow Layer 3 switching of Private VLAN ingress traffic: private-vlan mapping {secondary-vlan-list | add secondary-vlan-list
| remove secondary-vlan-list}
8
Select the LAN port interface to configure as the
Private VLAN host or promiscuous port: interface
type slot/port
9
Configure the LAN port for Layer 2 operation if the
default behaviour is a Layer 3 operation: switchport
10
Configure the Layer 2 port as a Private VLAN port
either as host or promiscious: switchport
mode private-vlan {host | promiscious}
11
To access Private VLAN ports, associate the community
or isolated Private VLAN to the Private VLAN: switchport private-vlan host-association primary-vlan-id secondary-vlan-id
12
For promiscuous ports, configure the interface by
mapping the port to the private VLAN: switchport
private-vlan mapping primary-vlan-id
{secondary-vlan-list | add secondary-vlan-list | remove secondary-vlan-list}
13
Exit the config mode
Verify the configuration:
1
show interface type slot/port switchport
2
show vlan
private-vlan
●
Private VLANs can span multiple switches. A trunk port
carries the primary and secondary VLAN just like any other VLAN. Configure
Private VLANs on all switches on the path which includes devices that have no
Private VLAN ports to maintain the security of your Private VLAN configuration
and to avoid using other VLANs configured as Private VLANs
●
VTP does not support Private VLANs - so they have to be
configured manually across all the switches
●
To trunk Private VLANs on a host port or a port that is
supposed to carry multiple secondary VLANs, the Private VLAN trunk feature is
also available which can carry multiple secondary and non-Private VLANs.
Packets are received and transmitted with secondary or regular VLAN tags on the
Private VLAN trunk ports.
●
Private VLAN host trunk feature is supported only with
801.1Q encapsulation. Isolated trunk ports enable you to combine traffic for
all secondary ports over a trunk. Promiscuous trunk ports enable you to combine
the multiple promiscuous ports required in this topology in a single trunk port
that carries multiple primary VLANs
●
Private VLAN promiscuous trunks are used in situations
where a Private VLAN promiscuous host port is normally used but where it is
necessary to carry multiple VLANs either normal VLANs or multiple Private VLAN
domains. This makes it useful for connecting an upstream router that does not
support Private VLANs
●
Command to configure the Private VLAN trunk feaure: switchport private-vlan association trunk primary_vlan_ID secondary_vlan_ID
●
If the port is set to promiscuous, use the mapping
command: switchport private-vlan mapping
[trunk] primary_vlan_ID
secondary_vlan_ID
●
Once trunk configured, allow VLANs: switchport private-vlan trunk allowed vlan vlan_list
●
Configure native VLAN: switchport private-vlan trunk native vlan vlan_ID
●
Protected ports on older or simpler switches are simple
versions of private VLANs. Traffic can flow only between a protected and
unprotected port and between an unprotected and unprotected port. Traffic
between protected ports are blocked.
●
A protected port only has local significance and
doesn’t affect different switches. Can still traverse Layer 3
●
Etherchannel allows up to eight physical links to be
bundled together in a single logical Etherchannel
●
Etherchannel uses one of two management protocols to
create Port-Channel.
○
Port Aggregation Protocol (PAgP) - Cisco proprietary.
PAgP packets are sent to negotiate the forming of the channel. Identifies
matched Ethernet links and groups the links into EtherChannel. Spanning tree
adds the Etherchannel as a single bridge port. PAgP packets sent every 30
seconds. Checks for config consistency and manages link additions and failures
between switches.
○
LACP - IEEE standard that allows several links to be
bundled together into etherchannel. Enables a switch to negotiate an automatic
bundle by sending LACP packets to the peer. This is better for a mixed-switch
environment
Different setting options for PAgP:
|
Mode
|
Purpose
|
|
Auto
|
Places an interface in a
passive negotiating state in which the interface responds to the PAgP packets
that it receives but does not initiate (default)
|
|
Desirable
|
Places an interface in an
active negotiating state in which the interface initiates negotiations with
other interfaces by sending PAgP packets
|
|
On
|
Forces the interface to channel
without PAgP. Does not exchange PAgP packets
|
|
Non-silent
|
If switch is connected to a
PAgP-capable partner, configure the switch interface for non-silent
operation. Keyword is always used with the auto or desirable mode. If you
don’t specify, it is assumed silent. Silent setting is for connections to
file servers or packet analyzers
|
●
Modes need to be compatible on each side
●
If one deconfigures all modes by using the no command or if no mode is configured,
the interface is placed in an Off mode and Etherchannel is disabled
●
LACP provides same negotiation benefits as PAgP
●
Must be compatible on both sides as well
LACP Mode Options:
|
Mode
|
Purpose
|
|
Passive
|
Places port in a passive
negotiating state. Port responds to LACP packets but doesn’t initiate
negiotiation
|
|
Active
|
Places port in an active
negotiating state
|
|
On
|
Forces the interface to the
channel without PAgP or LACP
|
●
Additional parameters that can be configured with LACP:
○
System priority
- Each switch running LACP must have a system priority. Can be specified
automatically or through the CLI. Switch uses MAC address and system priority
to form the system ID
○
Port priority - Each
port in the switch must have a port priority. Can be automatic or through CLI.
Port priority and port number form the port identifier. Switch uses port
priority to decide which ports to put in standby mode when a hardware
limitation prevents all compatible ports from aggregating
○
Administrative
key - Each port in the switch must have an administrative key value which
can be specified automatically or through CLI. Administrative key defines the
capability of the port to aggregate with other ports which is determine by the
ports physical characteristics (such as data rate, duplex capability, and
point-to-point or shared medium) and the configuration constraints that you
establish
●
If the ports cannot be actively included in the channel
due to hardware limitations on either side, LACP puts the ports in hot standby
state and will be used if one of the channeled ports fail
●
Guidelines and restrictions for configuring
EtherChannel:
○
EtherChannel support - All Ethernet interfaces on all
modules support EtherChannel with no requirement that interfaces must be
physically contiguous or on the same module
○
Speed and duplex - Configure all interfaces to operate
at the same speed and duplex. Make sure all interfaces are not shutdown
○
Switched port analyzer (SPAN) and etherchannel -
EtherChannel does not form if one of the interfaces is a SPAN destination port
○
Layer 3 EtherChannels - Assign Layer 3 addresses to the
port-channel logical interface, not to the physical interfaces in the channel
○
VLAN match - All interfaces much be assigned to the
same VLAN or be configured as a trunk. Native VLANs much match
○
Range of VLANs - Supports the same allowed range of
VLANs on all the interfaces in a trunking Layer 2 EtherChannel. If the ranges
aren’t the same, Etherchannel will not form.
○
STP path cost - Interfaces with different STP port path
costs can form Etherchannel as long as they are otherwise compatibly
configured.
○
Port channel versus interface configuration - After the
Etherchannel is configured, any config applied to the port-channel interface
affect the Etherchannel. Any config you apply to the physical interfaces
affects only the specific interface you configure
To configure Etherchannel
1
Specify the interface range. Usually good to shut them
down as well: interface range interface_type [interface_range]
2
Specify the channeling protocol: channel-protocol {pagp | lacp}
3
Create port-channel interface: channel-group number mode {active | on | {auto [non-silent]} |
{desirable [non-silent]} | passive
4
Specify the port-channel interface. You can configure
additional parameters from there: interface
port-channel number
●
Verifying EtherChannel:
○
show interfaces type port_number etherchannel - shows if the
interface is part of an etherchannel and the protocol for it
○
show
etherchannel number port-channel - Shows all the ports part
of the etherchannel, whether active, and what protocol is being used
○
show
etherchannel summary - Useful for simply displaying one-line information
per port-channel
●
On Etherchannel,
traffic is load balanced across multiple links.
●
User a load-balancing option that provides the greatest
variety in your configuration
●
Load-balancing is applied globally for all EtherChannel
bundles in a switch. To configure Etherchannel load balancing, use the port-channel load-balance command. Load
balancing keywords are as follows:
|
src-mac
|
Source MAC Addresses
|
|
dst-mac
|
Destination MAC addresses
|
|
src-dst-mac
|
Source and destination MAC
addresses
|
|
src-ip
|
Source IP addresses
|
|
dst-ip
|
Destination IP addresses
|
|
src-dst-ip
|
Source and destination IP
addresses (default)
|
|
src-port
|
Source TCP/UDP port
|
|
dst-port
|
Destination TCP/UDP port
|
|
src-dst-port
|
Source and destination TCP/UDP
port
|
●
Checking load balancing: show etherchannel load-balance
No comments:
Post a Comment