EDF (Elite Data Force) Network

7. Layer 3 Interface: In addition to Layer 2 (L2) interfaces (switchports), Cisco Catalyst also supports Layer 3 (L3) interfaces to route IP traffic.
7.1. Layer 3 interfaces come in two flavors:
7.1.1. Layer 3 routed interfaces
7.1.2. SVI (Switch Virtual Interfaces)
7.2. To disable “default” L2 switching and enable L3 routing on the interface issue “no switchport” from the interface level.
7.3. Once the port/interface is configured for L3 traffic, IP addresses can be configured on that interface by issuing “ip address ” command.

!
SW1(config-if)#no switchport ?
access     Set access mode characteristics of the interface
backup     Set backup for the interface
block     Disable forwarding of unknown uni/multi cast addresses
host     Set port host
mode     Set trunking mode of the interface
nonegotiate     Device will not engage in negotiation protocol on this interface
port-security     Security related command
priority      Set appliance 802.1p priority
protected     Configure an interface to be a protected port
trunk     Set trunking characteristics of the interface
voice     Voice appliance attributes
!
SW1(config-if)#do sh run interface fastethernet0/1
!
interface FastEthernet0/1
no switchport
no ip address
!
SW1(config-if)#ip address ?
A.B.C.D IP address
dhcp IP Address negotiated via DHCP

SW1(config-if)#ip address 10.10.10.10 255.255.255.0 ?
secondary Make this IP address a secondary address

SW1(config-if)#ip address 10.10.10.10 255.255.255.0
SW1(config-if)#do sh run
!
interface FastEthernet0/1
no switchport
ip address 10.10.10.10 255.255.255.0
!
SW1(config-if)#
!

7.4. L3 routed interface has the same characteristics as Ethernet interfaces on a router.
7.5. To verify if an interface is in L3 mode issue the “show interface status” in privilege mode.
7.5.1. In the VLAN field of the output L3 is listed as “routed”.

!
SW1#sh interfaces status

Port     Name     Status     Vlan     Duplex     Speed     Type
Fa0/1          notconnect     routed      auto      auto      10/100BaseTX
Fa0/2          notconnect      1          auto     auto     10/100BaseTX
!
Output suppressed
!

7.6. SVI is used to route traffic between VLAN. For example lets say various hosts are connected two different VLAN (VLAN 1 and VLAN 2). Each VLAN is a separate broadcast domain, and traffic must be processed by a L3 device before each domain (subnet) can communicate with each other. In this case two SVI needs to be configured for each VLAN (interface VLAN 1 and interface VLAN 2).
7.7. Hosts of this VLAN will be configured with appropriate VLAN. SVI interface IP will be configured as the hosts default gateway.
7.8. When switch receives traffic from one VLAN destined for another VLAN, the packets are re-encapsulated with new L2 header and forwarded out to the appropriate L2 interface.
7.9. This setup is similar to legacy router on a stick configuration.
7.9.1. In router in a stick scenario, a trunk link attaches a router and a switch to carry multiple L3 VLAN traffic to the router. In the router each VLAN is configured with sub-interfaces to route L3 traffic. The router routes traffic between sub-interfaces and back down in the switch to the appropriate VLAN.
7.10. Creating/configuring SVI:
7.10.1. First verify the VLAN exists in the VLAN database by issuing “show vlan” in the privilege mode. *Note: In the VLAN does not exist it should be configured before configuring the SVI.
7.10.2. If the VLAN exist, then issue “interface VLAN command in the global configuration mode. This will create the SVI interface, which can be accessed via “interface vlan ”.
7.10.3. After the SVI interface is created, IP address can be configured for this interface.
7.10.4. To verify the SVI issue the “show interface status” or “show interface brief” command in the privilege mode.

!
SW1#sh vlan brief

VLAN Name Status Ports
—- ——————————– ——— ——————————-
1     default     active     Fa0/2, Fa0/3, Fa0/4, Fa0/5
10    VLAN0010      active
SW1#
SW1#sh run interface vlan 10
^
% Invalid input detected at ‘^’ marker.

SW1#
SW1#config t
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#
SW1(config)#interface vlan ?
<1-4094> Vlan interface number

SW1(config)#interface vlan 10
SW1(config-if)#
00:33:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
SW1(config-if)#ip address 10.11.11.11 255.255.255.0
SW1(config-if)#^Z
SW1#
SW1#sh running-config interface vlan 10
Building configuration…

Current configuration : 62 bytes
!
interface Vlan10
ip address 10.11.11.11 255.255.255.0
end
SW1#
SW1#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES NVRAM up up
Vlan10 10.11.11.11 YES manual up up
FastEthernet0/1 10.10.10.10 YES manual down down
!
Output suppressed
!

7.11. Although L3 interface is configured, IP routing will still need to be enabled. To enable IP routing issue “ip routing” from the global mode.

!
SW1#config t
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#ip routing ?
protocol IP routing protocol

SW1(config)#ip routing
SW1(config)#
!

6. Additional VTP features:
6.1. Authentication: is to prevent rouge network devices to inject wrong information in a VTP domain.
6.1.1. To configure VTP authentication issue the “vtp password <password>” command from the global mode.

Switch#
Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#vtp ?
  domain     Set the name of the VTP administrative domain.
  file       Configure IFS filesystem file where VTP configuration is stored.
  interface  Configure interface as the preferred source for the VTP IP updater
             address.
  mode       Configure VTP device mode
  password   Set the password for the VTP administrative domain
  pruning    Set the adminstrative domain to permit pruning
  version    Set the adminstrative domain to VTP version

Switch(config)#vtp password ccielab
Password already set to ccielab
Switch(config)#

6.1.2. To verify authentication issue the “show vtp status” command from the privilege mode.

Switch#
Switch#sh vtp status
VTP Version                     : 2
Configuration Revision          : 3
Maximum VLANs supported locally : 255
Number of existing VLANs        : 13
VTP Operating Mode              : Server
VTP Domain Name                 : ccielab
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0×23 0xA4 0xA1 0xC3 0×76 0×9F 0×7D 0×3B
Configuration last modified by 0.0.0.0 at 3-1-93 00:27:02
Local updater ID is 0.0.0.0 (no valid interface found)
Switch#

*Note: The MD5 digest field shows the encrypted password. If the hash password is consistent throughout the VTP domain member switches the password is the same.

6.1.3. Anther way to verify the password is to issue the “show vtp password” command from the privilege mode.

Switch#sh vtp pass
Switch#sh vtp password
VTP Password: ccielab
Switch#

6.2. Pruning: is used to minimize unnecessary broadcast and unknown traffic sent over a trunk link throughout the VTP domain.
6.2.1. Broadcast frames: When an Ethernet switch receives a broadcast frame, the frame is replicated out on all member interfaces in a VLAN except the port it was received from.
6.2.2. Unicast/Multicast frames: When a switch receives a unicast or multicast frame with unknown destination, the frame is treated like a broadcast. So if a VLAN does not have a member port in a switch then the broadcast or the unknown frame belong to that VLAN does need to transmit the frame in that switch. It is unnecessary waste of bandwidth.
6.2.3. To resolve that issue we need to enable VTP pruning. When VTP pruning is enabled the switch that does not have the particular VLAN will not receive any broadcast or unknown frames on its trunk port from that VLAN.
6.2.4. To enable VTP pruning issue the “vtp pruning” command from the global mode. VTP pruning is advertised by VTP updates.

Switch(config)#
Switch(config)#vtp pruning ?
  <cr>

Switch(config)#vtp pruning
Pruning switched on
Switch(config)#
Switch(config)#exit
Switch#

6.2.5. To verify if VTP pruning is enable issue the “show vtp status” command from the privilege mode.

Switch#sh vtp status
VTP Version                     : 2
Configuration Revision          : 4
Maximum VLANs supported locally : 255
Number of existing VLANs        : 13
VTP Operating Mode              : Server
VTP Domain Name                 : ccielab
VTP Pruning Mode                : Enabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xFF 0×6D 0xA9 0×58 0×53 0xC7 0×80 0xC9
Configuration last modified by 0.0.0.0 at 3-2-93 03:18:52
Local updater ID is 0.0.0.0 (no valid interface found)
Switch#

5. Managing VLAN with VTP
5.1. To configure VTP, you must create VLANs to be used in the L2 network.
5.1.1. VLAN ranging from 2 to 1001 are standard VLANs.
5.1.2. VLAN 1 and VLAN 1002 to VLAN 1005 are default VLANS for Ethernet, Token Ring and FDDI.
5.1.3. VLAN ranging from 1006 to 4094 are extended VLAN, which can only be used under transparent mode.

5.2. Creating a single VLAN
5.2.1. From the global configuration mode issue “vlan <vlan#>”.
5.2.2. “name” option can used to define a name for a particular VLAN.

Switch#
Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#vlan ?
  WORD      ISL VLAN IDs 1-4094
  internal  internal VLAN

Switch(config)#vlan 2 ?
  <cr>

Switch(config)#vlan 2
Switch(config-vlan)#?
VLAN configuration commands:
  are          Maximum number of All Route Explorer hops for this VLAN (or zero if none specified)
  backupcrf    Backup CRF mode of the VLAN
  bridge       Bridging characteristics of the VLAN
  exit         Apply changes, bump revision number, and exit mode
  media        Media type of the VLAN
  mtu          VLAN Maximum Transmission Unit
  name         Ascii name of the VLAN
  no           Negate a command or set its defaults
  parent       ID number of the Parent VLAN of FDDI or Token Ring type VLANs
  remote-span  Configure as Remote SPAN VLAN
  ring         Ring number of FDDI or Token Ring type VLANs
  said         IEEE 802.10 SAID
  shutdown     Shutdown VLAN switching
  state        Operational state of the VLAN
  ste          Maximum number of Spanning Tree Explorer hops for this VLAN (or zero if none specified)
  stp          Spanning tree characteristics of the VLAN
  tb-vlan1     ID number of the first translational VLAN for this VLAN (or zero if none)
  tb-vlan2     ID number of the second translational VLAN for this VLAN (or zero if none)

Switch(config-vlan)#
Switch(config-vlan)#name ?
  WORD  The ascii name for the VLAN

Switch(config-vlan)#name management ?
  <cr>

Switch(config-vlan)#name management
Switch(config-vlan)#
Switch(config-vlan)#^Z
Switch#

5.2.3. A single VLAN can also be created at the time they are being applied to the interface by issuing “switchport access VLAN#> at the interface level.

Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#interface gigabitEthernet 0/1
Switch(config-if)#switchport access vlan 9
% Access VLAN does not exist. Creating vlan 9
Switch(config-if)#^Z
Switch#
Switch#sh run interface gigabitEthernet 0/1
Building configuration…
Current configuration : 62 bytes
!
interface GigabitEthernet0/1
 switchport access vlan 9
end
Switch#

5.3. Creating multiple VLAN simultaneously
5.3.1. To create non-consecutive multiple VLAN use “vlan <vlan list separated by comma> from the global mode.

Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#vlan 2,3,4 ?
  <cr>

Switch(config)#vlan 2,3,4
Switch(config-vlan)#
Switch(config-vlan)#name ccie
%Can’t modify name for multiple VLANs
Switch(config-vlan)#
Switch#

5.3.2. To create consecutive list use “vlan <vlan range separated by (-)>”

Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#vlan 5-8 ?
  <cr>

Switch(config)#vlan 5-8
Switch(config-vlan)#
Switch(config-vlan)#name ccie
%Can’t modify name for multiple VLANs
Switch(config-vlan)#
Switch#

5.4. All VLAN must be created in the server or transparent mode. If the VLAN is created in a client, then the VLAN will be applied to the interface but no VLAN will be created. Traffic will not pass through the interface, which has the same effect as port being in disable state.

5.5. It is best practice to create the VLANs before in the VLAN database or from global config mode.

5.6. To verify VLAN status issue “show vlan” command.

Switch#
Switch#sh vlan

VLAN Name                             Status    Ports
—- ——————————– ——— ——————————-
1    default                          active    Gi0/2, Gi0/3, Gi0/4, Gi0/5
                                                Gi0/6, Gi0/7, Gi0/8, Gi0/9
                                                Gi0/10, Gi0/11, Gi0/12, Gi0/13
                                                Gi0/14, Gi0/15, Gi0/16, Gi0/17
                                                Gi0/18, Gi0/19, Gi0/20, Gi0/21
                                                Gi0/22, Gi0/23, Gi0/24
2    VLAN0002                         active   
3    VLAN0003                         active   
4    VLAN0004                         active   
5    VLAN0005                         active   
6    VLAN0006                         active   
7    VLAN0007                         active   
8    VLAN0008                         active   
9    VLAN0009                         active    Gi0/1
1002 fddi-default                     act/unsup
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup

VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
—- —– ———- —– —— —— ——– —- ——– —— ——
1    enet  100001     1500  -      -      -        -    -        0      0  
2    enet  100002     1500  -      -      -        -    -        0      0  
3    enet  100003     1500  -      -      -        -    -        0      0  
4    enet  100004     1500  -      -      -        -    -        0      0  
5    enet  100005     1500  -      -      -        -    -        0      0  
6    enet  100006     1500  -      -      -        -    -        0      0  
7    enet  100007     1500  -      -      -        -    -        0      0  
8    enet  100008     1500  -      -      -        -    -        0      0  
9    enet  100009     1500  -      -      -        -    -        0      0  
1002 fddi  101002     1500  -      -      -        -    -        0      0  
1003 tr    101003     1500  -      -      -        -    -        0      0  
1004 fdnet 101004     1500  -      -      -        ieee -        0      0  
1005 trnet 101005     1500  -      -      -        ibm  -        0      0  

Remote SPAN VLANs
——————————————————————————
Primary Secondary Type              Ports
——- ——— —————– ——————————————

Switch#

4. VTP (VLAN Trunking Protocol)
4.1. VTP is a management protocol used to advertise VLANs between switches connected together with L2 trunk links.
4.1.1. VTP is NOT required for operations of Ethernet network.
4.1.2. VTP is an optional feature to ease management of VLAN throughout the layer 2 network.
4.2. VTP operation can be configured from VLAN database mode and global configuration mode. There are minor differences between applying VTP from VLAN database vs. Global configuration.
4.3. Default VTP configuration
4.3.1. Default is “NULL” or “Not configured”.
4.3.2. “show vtp status” will verify VTP status.

Switch#sh vtp status
VTP Version                     : 2
Configuration Revision          : 0
Maximum VLANs supported locally : 255
Number of existing VLANs        : 5
VTP Operating Mode              : Server
VTP Domain Name                 :
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0×57 0xCD 0×40 0×65 0×63 0×59 0×47 0xBD
Configuration last modified by 0.0.0.0 at 0-0-00 00:00:00
Local updater ID is 0.0.0.0 (no valid interface found)
Switch#

4.4. In 3550, if domain name is not configured it will accept any domain name it receives from VTP updates.
4.5. There are three VTP mode
4.5.1. Server: has the authority to create, modify and delete VLANs in VTP domain.
4.5.2. Clients: listens for VTP updates from other clients and servers, and then installs the advertised information. VTP clients can not create or modify VLAN parameters.
4.5.3. Transparent: device in the transparent mode will pass information with out modification but does not install the information learned from other devices.
4.5.3.1. In transparent mode devices can create and modify VLANs. Any changes to VTP are only locally significant.
4.5.4. To setup VTP mode use “VTP mode <server/client/transparent>

Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#
Switch(config)#vtp ? 
  domain     Set the name of the VTP administrative domain.
  file       Configure IFS filesystem file where VTP configuration is stored.
  interface  Configure interface as the preferred source for the VTP IP updater
             address.
  mode       Configure VTP device mode
  password   Set the password for the VTP administrative domain
  pruning    Set the adminstrative domain to permit pruning
  version    Set the adminstrative domain to VTP version

Switch(config)#vtp mode ?
  client       Set the device to client mode.
  server       Set the device to server mode.
  transparent  Set the device to transparent mode.

Switch(config)#
Switch(config)#exit
Switch#

4.5.5. Verification “show vtp status”

Switch#sh vtp status
VTP Version                     : 2
Configuration Revision          : 1
Maximum VLANs supported locally : 255
Number of existing VLANs        : 5
VTP Operating Mode              : Server
VTP Domain Name                 :
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Enabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0×8E 0×38 0×09 0xF3 0×55 0xF3 0xE9 0×78
Configuration last modified by 0.0.0.0 at 3-3-93 21:31:50
Local updater ID is 0.0.0.0 (no valid interface found)
Switch#

Beginning of this week on Monday Mike Down from IPExpert was feeling very generous. So he decided to match purchase of vRack sessions. Read all about it at his blog “http://mdownipexpert.blogspot.com/2008/08/so-you-want-deal-do-you.html”. I am not quite ready to jump in the lab as of yet but soon I will be. I decided to take his super deal and purchased 10 vRack sessions today. Hopefully in the near future Mike Down will feel generous again. Thanks Mike for your help today.

3. Trunk Ports (Layer 2)
3.1. Layer 2 trunk ports are used to carry multiple VLANs simultaneously. They are used to connect multiple layer 2 devices together to expand layer 2 broadcast domain across multiple devices.

3.2. Trunking is achieved by adding an additional header to Ethernet packet that is used to identify which VLAN the packet belongs to.

3.3. There are two method used for Trunk encapsulation (header)
3.3.1. ISL (Inter Switch link) which is Cisco proprietary
3.3.2. 802.1q which is open standard

3.4. Main functional difference between ISL & 802.1q is 802.1q definition of native VLAN
3.4.1.1.  With ISL all VLAN is encapsulated, if a packet is received on ISL trunk with out ISL header, it is discarded.
3.4.1.2.  With 802.1q all traffic with the exception of native VLAN is encapsulated with 802.1q header. If a frame arrives on 802.1q trunk with out a header, it is assumed to be in native VLAN.
3.4.1.3.  By default VLAN 1 is the native VLAN, therefore if a frame does not have 802.1q header it is assumed to be on VLAN 1. Since native VLAN header info is not propagated over the trunk link, it is essential both end of the trunk belongs on the same native VLAN. If there is Native VLAN mismatch traffic can leak between VLAN boundaries.
3.4.1.4.  To manually change native VLAN use “switchport trunk native vlan #” command at the interface level mode.

!
Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#interface gigabitEthernet 0/1
Switch(config-if)#switchport trunk native vlan ?
  <1-4094>  VLAN ID of the native VLAN when this port is in trunking mode

Switch(config-if)#switchport trunk native vlan 3 ?
  <cr>

Switch(config-if)#switchport trunk native vlan 3
Switch(config-if)#
!
Switch#show run
interface GigabitEthernet0/1
 description <<< Trunk Port >>>
 switchport trunk native vlan 2
 switchport mode trunk
!

3.5.  Trunking can be automatically configured by dynamic mode. The dynamic negotiation is controlled by DTP (Dynamic Trunking Protocol).

3.6. DTP can negotiate if a port is to be access or trunk mode.
3.6.1. If DTP negotiates the port to be in trunk mode, it also negotiates the encapsulation method (802.1q or ISL)

3.7. DTP is on by default and can be turned off at the interface level by “switchport no negotiation”

!
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface gigabitEthernet 0/1
Switch(config-if)#switchport nonegotiate ?
  <cr>

Switch(config-if)#switchport nonegotiate
Switch(config-if)#
!
interface GigabitEthernet0/1
 switchport mode trunk
 switchport nonegotiate
!

3.8. Trunking can also be manually configured by “switch mode trunk” command at the interface level.

Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface gigabitEthernet 0/1
Switch(config-if)#switchport mode ?           
  access   Set trunking mode to ACCESS unconditionally
  dynamic  Set trunking mode to dynamically negotiate access or trunk mode
  trunk    Set trunking mode to TRUNK unconditionally

Switch(config-if)#switchport mode trunk
Switch(config-if)#
!
interface GigabitEthernet0/1
 switchport trunk native vlan 2
 switchport mode trunk
 switchport nonegotiate
!

*Note: This command does not disable DTP but prevents the interface to be in access mode.

3.9. To configure 802.1q trunking manually issue “switchport trunk encapsulation dot1q” and then switchport mode trunk command.

* Note: Order is important, interface set to negotiate encapsulation mode can not be set to static mode if “switport mode trunk” command issued before the “switchport trunk encapsulation” command. The switches will generate an error.

Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#interface gigabitEthernet 0/1
Switch(config-if)#switchport trunk encapsulation ?
dot1q Interface uses only 802.1q trunking encapsulation when trunking
isl Interface uses only ISL trunking encapsulation when trunking
negotiate Device will negotiate trunking encapsulation with peer on
interface

!
Switch#
interface GigabitEthernet0/1
description <<< Trunk port >>>
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 2
switchport trunk allowed vlan 2,205
switchport mode trunk
!

3.10. Trunking status can be verified by “sh interface trunk” command. This command details encapsulation, negotiation and which vlan is allowed to transit the trunk link.

Switch#sh interfaces trunk ?
  module  Limit display to interfaces on module
  |       Output modifiers
  <cr>

Switch#sh interfaces trunk

Port          Mode         Encapsulation  Status        Native vlan
Po1           on           802.1q         trunking      2
Po2           on           802.1q         trunking      2
Po3           on           802.1q         trunking      2

Port          Vlans allowed on trunk
Po1           2,203-205
Po2           2,6,203-205
Po3           2,203-205

Port          Vlans allowed and active in management domain
Po1           2,203-205
Po2           2,6,203-205
Po3           2,203-205

Port          Vlans in spanning tree forwarding state and not pruned
Po1           2,203-205
Po2           2,6,203-205
Po3           2,203-205
Switch#

I want to write briefly about my experience of buying both the IP Expert BLS and Internetwork Expert End to End study materials.  If you have read my earlier blogs, my intention was to purchase both products.  After continuous deliberations, in terms of cost and which product was going to be the best aid in my success, I purchased both.  I was able to obtain funding through my job for the Internetwork Expert, and was extended a great deal from IP Expert, which I will explain:

Mike Down from IP Expert contacted me and asked me if I would put an IP Expert advertisement on my blog. I agreed and in the sprit of full disclouser he offered to give me 50% off from the BLS sticker price. It seemed like a great offer, and since I was planning to get both study material I took up his offer.

Sales Team:
Internetwork Expert sales team was helpful and answered all my questions. Upon request they sent me an email outlining the steps to studying their material. Other then the initial login issue , the transaction was smooth.

IP Expert sales team, particularly Mike Down (his role has changed recently within IPExpert), was very helpful.  He went out of his way to get me a deal.  We exchanged several emails and spoke over the phone as well. Since I was paying out of my own pocket, he gave me an offer I could not refuse.
Although IP Expert gave me 50% off the cost of their study material, I do not think it affected my opinion. After speaking with Mike Down he seems like a genuine person. We continued to exchange emails even after I purchased their product. I look forward to use both of the vendors for lab practices.

Note: BLS does not come with printed version of the workbook or the labs. All is in electronic version.  The printer version will cost extra.

I received my IP Expert Blended Learning Solution (BLS) package earlier today, and I could not wait till to open it and start studying.

*NOTE: The BLS Learning solution does not come with printer version of the workbook or lab. If you wanted printed version you have pay extra.

2. Layer 2 Switchports
2.1. Layer 2 switchports can be
2.1.1. Access ports (used to carry traffic for single VLAN)
2.1.2. Trunk ports (used to carry traffic for multiple VLANs). Trunkports connects switches together to span a logical broadcast domain (VLAN) between multiple physical devices. It can be used to connect routers or servers to connect VLANs.
2.1.3. Trunnel ports (used to carry traffic for multiple 802.1q VLAN in a single 802.1q VLAN)
2.2. By default all switch interfaces are set to L2 switchports in dynamic desirable mode (detects automatically if the port should be in access or trunk mode).
2.3. The mode in the interface can be set manually by issuing
2.3.1. “switchport mode (access/trunk/tunnel)
2.4. If a switch port fails to negotiate a mode it will default to access mode.
2.5. Access ports by default resides in VLAN 1
2.5.1. To manually configure interface (ports) VLAN associate issue “switchport access vlan (vlan #)” command.
2.5.2. To verify interface status issue “show interface status” command.
2.5.2.1. It lists all the interfaces in the switch
2.5.2.2. The port number
2.5.2.3. The name (description) if configured
2.5.2.4. The status (connect/disable/Errdisable)
2.5.2.5. VLAN mode (trunk/routed)
2.5.2.6. Duplex/Speed
2.5.2.7. Media Type
2.6. To verify VLAN status use “show vlan” command

1. Introduction to 3550
1.1. Switch 3550 is a layer 2 Ethernet sw/ also functions as L3 device
1.2. Supports three different interface type
1.2.1. Switchport (L2 switching)
1.2.2. Routed interface (L3 routing)
1.2.3. Switch virtual interface (SVI) – (VLAN L3 routing)