Switching Tshoot Ticket 4

ISSUE -  

RAJU COME TO OFFICE  AFTER 2 WEEKS AND CONNECTED HIS NEW LAPTOP IN THE LAN PORT BUT NOT ABLE TO ACCESS THE NETWORK 

SW4#sh int status

Port      Name               Status       Vlan       Duplex  Speed Type

Fa0/1                        connected    1          auto    auto  10/100BaseTX

Fa0/2                        err-disabled 10         auto    auto  10/100BaseTX

Fa0/3                        notconnect   1          auto    auto  10/100BaseTX

Fa0/4                        notconnect   1          auto    auto  10/100BaseTX

Fa0/5                        notconnect   1          auto    auto  10/100BaseTX

SW4#  sh mac address-table interfaces fa0/2

          Mac Address Table

-------------------------------------------

Vlan    Mac Address       Type        Ports

----    -----------       --------    -----

SW4#sh port-security interface fa0/2

Port Security              : Enabled

Port Status                : Secure-shutdown

Violation Mode             : Shutdown

Aging Time                 : 0 mins

Aging Type                 : Absolute

SecureStatic Address Aging : Disabled

Maximum MAC Addresses      : 1

Total MAC Addresses        : 1

Configured MAC Addresses   : 1

Sticky MAC Addresses       : 0

Last Source Address:Vlan   : 0060.47A9.C1E7:10

Security Violation Count   : 1

interface FastEthernet0/2

 switchport access vlan 10

 switchport mode access

 switchport port-security

 switchport port-security mac-address 0060.47A9.C1E4

SW4(config)#int fa0/2

SW4(config-if)#no switchport port-security mac-address 0060.47A9.C1E4

SW4(config-if)#switchport port-security mac-address 0060.4745.D5DE

SW4(config-if)#

SW4(config-if)#^Z

SW4#sh int fa0/2

FastEthernet0/2 is down, line protocol is down (err-disabled)

  Hardware is Lance, address is 0000.0c7c.0502 (bia 0000.0c7c.0502)

 BW 100000 Kbit, DLY 1000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

SW4#config

Configuring from terminal, memory, or network [terminal]? 

Enter configuration commands, one per line.  End with CNTL/Z.

SW4(config)#int fa0/2

SW4(config-if)#shut

%LINK-5-CHANGED: Interface FastEthernet0/2, changed state to administratively down

SW4(config-if)#

SW4(config-if)#

SW4(config-if)#

SW4(config-if)#no shut

SW4(config-if)#

%LINK-5-CHANGED: Interface FastEthernet0/2, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2, changed state to up

^Z

SW4#

%SYS-5-CONFIG_I: Configured from console by console

SW4#

SW4#

SW4#sh int fa0/2

FastEthernet0/2 is up, line protocol is up (connected)

  Hardware is Lance, address is 0000.0c7c.0502 (bia 0000.0c7c.0502)

 BW 100000 Kbit, DLY 1000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s

  input flow-control is off, output flow-control is off

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:08, output 00:00:05, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue :0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     956 packets input, 193351 bytes, 0 no buffer

     Received 956 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     0 watchdog, 0 multicast, 0 pause input

     0 input packets with dribble condition detected

     2357 packets output, 263570 bytes, 0 underruns

     0 output errors, 0 collisions, 10 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

SW4#  sh port-security int fa0/2

Port Security              : Enabled

Port Status                : Secure-up

Violation Mode             : Shutdown

Aging Time                 : 0 mins

Aging Type                 : Absolute

SecureStatic Address Aging : Disabled

Maximum MAC Addresses      : 1

Total MAC Addresses        : 1

Configured MAC Addresses   : 1

Sticky MAC Addresses       : 0

Last Source Address:Vlan   : 0060.47A9.C1E7:10

Security Violation Count   : 0

SW4#sh mac address-table interfaces fa0/2

          Mac Address Table

-------------------------------------------

Vlan    Mac Address       Type        Ports

----    -----------       --------    -----

  10    0060.4745.d5de    STATIC      Fa0/2

SW4#  

Switching Tshoot - Ticket 3

PC AND LAPTOP BOTH ARE IN THE SAME VLAN 10 (10.1.1.0/24)

WHEREAS SERVER IS IN THE ANOTHER VLAN 20 (10.1.2.0/24)

SW1 is a Layer 3 Switch

SW2 , SW3 AND SW4 are Layer 2 Switches

Issue :-

=================

Intervlan Communication is not happening

Lets check from PC

!!!! Able to ping laptop which is in the same vlan but not able to ping server which is in different vlan

C:\>ping 10.1.1.3

Pinging 10.1.1.3 with 32 bytes of data:

Reply from 10.1.1.3: bytes=32 time=1ms TTL=128
Reply from 10.1.1.3: bytes=32 time<1ms TTL=128
Reply from 10.1.1.3: bytes=32 time<1ms TTL=128
Reply from 10.1.1.3: bytes=32 time=1ms TTL=128

Ping statistics for 10.1.1.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>ping 10.1.2.2

Pinging 10.1.2.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.1.2.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


C:\>

Also let check pinging PC from Server

C:\>ping 10.1.1.2

Pinging 10.1.1.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.1.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


C:\>

!!!! Lets check whether we are able to ping the default gateway from PC and Server

PC
=====
C:\>ping 10.1.1.1

Pinging 10.1.1.1 with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time<1ms TTL=255
Reply from 10.1.1.1: bytes=32 time<1ms TTL=255
Reply from 10.1.1.1: bytes=32 time<1ms TTL=255
Reply from 10.1.1.1: bytes=32 time=2ms TTL=255

Ping statistics for 10.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms

Server
======

C:\>ping 10.1.2.1

Pinging 10.1.2.1 with 32 bytes of data:

Reply from 10.1.2.1: bytes=32 time=1ms TTL=255
Reply from 10.1.2.1: bytes=32 time<1ms TTL=255
Reply from 10.1.2.1: bytes=32 time<1ms TTL=255
Reply from 10.1.2.1: bytes=32 time=1ms TTL=255

Ping statistics for 10.1.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 1ms, Average = 0ms

Checking from SW1 which is the gateway

SW1#ping 10.1.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/3 ms

SW1#ping 10.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.2, timeout is 2 seconds:
!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/3 ms

Both SVIs are also up

SW1#sh int vlan 10
Vlan10 is up, line protocol is up
Hardware is CPU Interface, address is 00d0.ba25.3301 (bia 00d0.ba25.3301)
Internet address is 10.1.1.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 21:40:21, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1682 packets input, 530955 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
563859 packets output, 0 bytes, 0 underruns
0 output errors, 23 interface resets
0 output buffer failures, 0 output buffers swapped out

SW1#sh int vlan 20
Vlan20 is up, line protocol is up
Hardware is CPU Interface, address is 00d0.ba25.3302 (bia 00d0.ba25.3302)
Internet address is 10.1.2.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 21:40:21, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1682 packets input, 530955 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
563859 packets output, 0 bytes, 0 underruns
0 output errors, 23 interface resets
0 output buffer failures, 0 output buffers swapped out


SW1#


Intravlan Communication needs Routing

& Routing is not happening on Gateway SW1

SW1#sh ip route
Default gateway is not set

Host Gateway Last Use Total Uses Interface
ICMP redirect cache is empty

SW1#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.

SW1(config)#ip routing

SW1(config)#^Z
SW1#
%SYS-5-CONFIG_I: Configured from console by console

SW1#
SW1#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, Vlan10
C 10.1.2.0 is directly connected, Vlan20


By default Routing is disabled on Layer 3 Switches and hence we have enabled the routing on same.


PC

C:\>ping 10.1.2.2

Pinging 10.1.2.2 with 32 bytes of data:

Reply from 10.1.2.2: bytes=32 time<1ms TTL=127
Reply from 10.1.2.2: bytes=32 time<1ms TTL=127
Reply from 10.1.2.2: bytes=32 time=10ms TTL=127
Reply from 10.1.2.2: bytes=32 time=12ms TTL=127

Ping statistics for 10.1.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 12ms, Average = 5ms


Server

C:\>ping 10.1.1.2

Pinging 10.1.1.2 with 32 bytes of data:

Reply from 10.1.1.2: bytes=32 time=1ms TTL=127
Reply from 10.1.1.2: bytes=32 time<1ms TTL=127
Reply from 10.1.1.2: bytes=32 time<1ms TTL=127
Reply from 10.1.1.2: bytes=32 time<1ms TTL=127

Ping statistics for 10.1.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms



Now we are able to ping!!!!

Issue resolved

Thanks for Reading !!!!

Switching Tshoot Ticket - 2

PC AND LAPTOP BOTH ARE IN THE SAME VLAN 10 (10.1.1.0/24)

WHEREAS SERVER IS IN THE ANOTHER VLAN 20 (10.1.2.0/24)

SW1 is a Layer 3 Switch

SW2 , SW3 AND SW4 are Layer 2 Switches

Issue :-

=================

Not able to ping Server from PC 

From PC we are not able to ping server


C:\>ping 10.1.2.2

Pinging 10.1.2.2 with 32 bytes of data:

Reply from 10.1.1.1: Destination host unreachable.
Reply from 10.1.1.1: Destination host unreachable.
Reply from 10.1.1.1: Destination host unreachable.
Request timed out.

Ping statistics for 10.1.2.2:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

But able to ping the Gateway i.e SW1

C:\>ping 10.1.1.1

Pinging 10.1.1.1 with 32 bytes of data:

Reply from 10.1.1.1: bytes=32 time=1ms TTL=255
Reply from 10.1.1.1: bytes=32 time<1ms TTL=255
Reply from 10.1.1.1: bytes=32 time<1ms TTL=255
Reply from 10.1.1.1: bytes=32 time<1ms TTL=255

Ping statistics for 10.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms


Let's check on the Gateway

SW1#ping 10.1.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/3 ms

SW1#ping 10.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.2, timeout is 2 seconds:
.....

Success rate is 0 percent (0/5)

Able to PC but not server

Lets check the SVI status for vlan 20

SW1#sh int vlan 20
Vlan20 is down, line protocol is down
Hardware is CPU Interface, address is 00d0.ba25.3302 (bia 00d0.ba25.3302)
Internet address is 10.1.2.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 21:40:21, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1682 packets input, 530955 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
563859 packets output, 0 bytes, 0 underruns
0 output errors, 23 interface resets

0 output buffer failures, 0 output buffers swapped out


VLAN 20 IS DOWN

SW1#sh vlan brief

VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/4, Fa0/5, Fa0/6, Fa0/7
Fa0/8, Fa0/9, Fa0/10, Fa0/11
Fa0/12, Fa0/13, Fa0/14, Fa0/15
Fa0/16, Fa0/17, Fa0/18, Fa0/19
Fa0/20, Fa0/21, Fa0/22, Fa0/23
Fa0/24, Gig0/1, Gig0/2
10 VLAN0010 active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

SW1#


You can see L2 VLAN 20 IS NOT CREATED

Lets create it

SW1#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#
SW1(config)#vlan 20
SW1(config-vlan)#
%LINK-5-CHANGED: Interface Vlan20, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to up

SW1(config-vlan)#^Z
SW1#
%SYS-5-CONFIG_I: Configured from console by console
sh int vlan 20
Vlan20 is up, line protocol is up
Hardware is CPU Interface, address is 00d0.ba25.3302 (bia 00d0.ba25.3302)
Internet address is 10.1.2.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 21:40:21, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1682 packets input, 530955 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
563859 packets output, 0 bytes, 0 underruns
0 output errors, 23 interface resets
0 output buffer failures, 0 output buffers swapped out


SW1#


!!!!! Now we can see that Vlan 20 is UP

SW1#ping 10.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/2/8 ms


SW1#

Able to ping from SW1

Lets check from PC

C:\>ping 10.1.2.2

Pinging 10.1.2.2 with 32 bytes of data:

Reply from 10.1.2.2: bytes=32 time=13ms TTL=127
Reply from 10.1.2.2: bytes=32 time<1ms TTL=127
Reply from 10.1.2.2: bytes=32 time<1ms TTL=127
Reply from 10.1.2.2: bytes=32 time<1ms TTL=127

Ping statistics for 10.1.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 13ms, Average = 3ms


Able to ping

Issue resolved


Thanks for Reading !!!!

Switching Tshoot - Ticket 1

PC AND LAPTOP BOTH ARE IN THE SAME VLAN 10 (10.1.1.0/24)

WHEREAS SERVER IS IN THE ANOTHER VLAN 20 (10.1.2.0/24)

SW1 is a Layer 3 Switch

SW2 , SW3 AND SW4 are Layer 2 Switches

Issue :-

=================

PC not able to ping laptop and vice versa

SW2#sh int status
Port      Name               Status       Vlan       Duplex  Speed Type
Fa0/1                        connected    1          auto    auto  10/100BaseTX
Fa0/2                        connected    1          auto    auto  10/100BaseTX

From PC

FastEthernet0 Connection:(default port)

   Link-local IPv6 Address.........: FE80::201:64FF:FE0C:9609
   IP Address......................: 10.1.1.2
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: 10.1.1.1
 
 
Let try to ping the laptop

C:\>ping 10.1.1.3

Pinging 10.1.1.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.1.1.3:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

interface FastEthernet0/2
 switchport access vlan 10
 switchport mode access

SW2#sh vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/3, Fa0/4, Fa0/5, Fa0/6
                                                Fa0/7, Fa0/8, Fa0/9, Fa0/10
                                                Fa0/11, Fa0/12, Fa0/13, Fa0/14
                                                Fa0/15, Fa0/16, Fa0/17, Fa0/18
                                                Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                Fa0/23, Fa0/24, Gig0/1, Gig0/2
1002 fddi-default                     active 
1003 token-ring-default               active 
1004 fddinet-default                  active 
1005 trnet-default                    active 
SW2#

NO L2 VLAN 10 IS CREATED

LETS CREATE VLAN 10

SW2#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line.  End with CNTL/Z.
SW2(config)#vlan 10
SW2(config-vlan)#^Z
SW2#
%SYS-5-CONFIG_I: Configured from console by console

SW2#
SW2#sh vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/3, Fa0/4, Fa0/5, Fa0/6
                                                Fa0/7, Fa0/8, Fa0/9, Fa0/10
                                                Fa0/11, Fa0/12, Fa0/13, Fa0/14
                                                Fa0/15, Fa0/16, Fa0/17, Fa0/18
                                                Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                Fa0/23, Fa0/24, Gig0/1, Gig0/2
10   VLAN0010                         active    Fa0/2
1002 fddi-default                     active 
1003 token-ring-default               active 
1004 fddinet-default                  active 
1005 trnet-default                    active 
SW2#


But still not able to ping Laptop

C:\>ping 10.1.1.3

Pinging 10.1.1.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.1.1.3:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Lets check on switch 4

SW4#sh int status
Port      Name               Status       Vlan       Duplex  Speed Type
Fa0/1                        err-disabled 1          auto    auto  10/100BaseTX
Fa0/2                        connected    10         auto    auto  10/100BaseTX

We can see the trunk interface Fa0/1 is in err-disabled

SW4(config)#int fa0/1
SW4(config-if)#sh

%LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
SW4(config-if)#no sh

SW4(config-if)#
%LINK-5-CHANGED: Interface FastEthernet0/1, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
%SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port FastEthernet0/1 with BPDU Guard enabled. Disabling port.

%PM-4-ERR_DISABLE: bpduguard error detected on 0/1, putting 0/1 in err-disable state


%LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down

On interface Fa0/1 which is a trunk port BPDU guard is enable which makes it disabled

SW4#sh spanning-tree interface fa0/1
no spanning tree info available for FastEthernet0/1

interface FastEthernet0/1
 switchport mode trunk
 spanning-tree bpduguard enable

SW4(config)#int fa0/1
SW4(config-if)#spanning-tree bpduguard ?
  disable  Disable BPDU guard for this interface
  enable   Enable BPDU guard for this interface
SW4(config-if)#spanning-tree bpduguard disable
SW4(config-if)#^Z
SW4#

SW4(config)#int fa0/1
SW4(config-if)#shut

%LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
SW4(config-if)#no shut

SW4(config-if)#
%LINK-5-CHANGED: Interface FastEthernet0/1, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up

SW4(config-if)#^Z
SW4#
%SYS-5-CONFIG_I: Configured from console by console

SW4#sh spanning-tree interface fa0/1
Vlan             Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
VLAN0001         Altn LSN 19        128.1     P2p
VLAN0010         Altn LSN 19        128.1     P2p

NOW LETS PING PC TO Laptop
C:\>ping 10.1.1.3

Pinging 10.1.1.3 with 32 bytes of data:

Reply from 10.1.1.3: bytes=32 time=11ms TTL=128
Reply from 10.1.1.3: bytes=32 time<1ms TTL=128
Reply from 10.1.1.3: bytes=32 time=1ms TTL=128
Reply from 10.1.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 11ms, Average = 3ms


Thanks For Reading !!!!

Difference between L2 SWITCH ,L3 SWITCH & ROUTER

Difference between LAYER 2 AND LAYER 3 SWITCH

Let's first talk about the major similarity between Layer 2 i.e L2 & Layer 3 i.e L3 Switch is that both of them work on Ethernet Technology.

A L2 switch does switching only.

Basically a L2 Switch  maintains a Layer 2 address table i.e MAC address table which includes list of mac addresses and there respective ports of the switch.

L2 Switch refers this MAC address table to switch the packets from a port to the destination port.

L2 SWITCH - 2960

Whereas ,

A L3 switch also does switching exactly like a L2 switch.

& addition to that a L3 switch is also capable of doing routing by refering L3 address table i.e IP Routing table.

For intra-VLAN communication, it uses the MAC address table. For inter-VLAN communication, it uses the IP routing table.

L3 SWITCH - CISCO 4500 SERIES SWITCH

Difference between LAYER 3 SWITCH & ROUTER

Let's first talk about similarity between L3 Switch and a Router - Both are capable of doing Routing .

Fast Switching is possible in L3 Switches and not for Routers.

In Layer3 Switches forwarding is hardware based - routing decisions are made by specialized ASIC.

Application-specific integrated circuit (ASIC) is a kind of integrated circuit that is specially built for only for one purpose of forwading Hence provides "fast switching"

whereas on Routers forwarding decision is centralized software based and hence fast switching is not possible.

Port density is more in L3 Switch as compared to Router.

ROUTER - CISCO ASR 1002 ROUTER

Routers are more expensive as compared to L3 Switches .The reason behind this would be that Router can perform routing on Multitechnology ports .

L3 Switches can perform routing only on Ethernet ports whereas a Router can perform routing on Ethernet , ISDN , Serial port.

Routers supports Edge technologies like NAT , IPSec , Tunneling , Firewall feature etc. which L3 Switch can't.

Routers provides MPLS and VPN services which L3 Switches can't.

Routers can handle relatively larger Routing Table as compared to L3 Switches.

Thanks For Reading !!!!

CISCO 3 TIER ARCHITECTURE

When we have a big Campus Network then the Campus Network Architecture should be
" 3- Tier Architecture "

These Architecture will be having 3 layers -

1) Access Layer

2) Distribution  / Aggregation Layer

3) Core Layer

Each Building in the Campus will be having Access & Distribution layer components which will be connected to the Core Layer.

CISCO 3 TIER ARCHITECTURE

1) Access Layer :-

Provides Access to the Network.

This layer will have Components / Equipment through which a user can access the network .

If the Campus have 50,000 employee then these 50,000 employees will be connected to the access -layer devices .

L2 Switches are required in this layer

VLAN are created on the switches - Some ports of the access switch may be in vlan 100 , some ports may be in vlan 200 etc. depending upon the services required by the users.

These Access layer switches should have Trunk Capabilities - Multiple vlans are created on access switches hence there up-links connecting to the Distribution switch must be capable of  carrying multiple vlan traffic hence they should have trunking capabilities .

The uplink should be according to the port capacity of the downlinks where the users will be connected .

The access layer switches ports should have properly configured port level security so exclude any chance of the misuse of the network.

Access Layer Device -

L2 Devices

Cisco Switches - 2960 , 3560 , 3750 , Modular switches like 4500 Series etc.

Cisco Nexus Switches - N9K Switches , N5K Switches .

2) Distribution Layer :-

In Distribution Layer L3 /Multilayer Switches (MLS ) are used .

They should be capable of handling Intra building communication .

Vlan Aggregation - All the vlans are terminated on  Distribution Layer

Intervlan Routing is preformed on this layer devices.

This Layer devices breaks the broadcast domain.

QoS is provided in this  layer.

L2 / L3 Security is provided on this layer

Maximum Traffic Manipulation.

Devices used :-

4500 / 6500 series Switches

Cisco Nexus 7K Series Switches .

3) Core Layer :-

Simple L2 function only .

Just Forwards the traffic which comes from one building to the desired destination Building.

These switches should have very high port density.

No Traffic Manipulation - There should be no delay in the communication .

Devices Used:-

Cisco 4500 . 6500 (Layer 2 function only)

Cisco Nexus 9k switches .

Thanks for Reading !!!!!

BASICS OF SWITCH

1) Switch is an Intelligent Device

If a switch receives a frame on a port it reads the destination MAC address and forward to appropriate port only and not to other ports.

2) When Switch receives a frame on a port it will open Layer 2 Information read source MAC   of and make the entry of the mac address in its MAC table against the port on which it was received.

Switch takes forwarding decision on basis of MAC address and MAC address is Layer 2 address.
Hence Switch is a "Layer 2" device.

For Quick reference and fast forwarding the MAC address table should be precise and updated with the correct MAC address entries.

So the MAC address table should be controlled and Stale entries have to be deleted.

Any entry not referred / used for a stipulated time is consider as Stale.

Switch would remove stale entry from MAC table and the stipulated time can be from 5 to 30 mins depending upon the switch.

Cisco Switch

3) Switch is also called as "Multiport Bridge"

Normally Bridge would have only 16 ports where as switch have multiple ports.

Switch & Bridge are similar devices but use to different mediums.

Bridge -----> Thick , thin wire
Switch -----> Twisted Pair / Fiber.

4) If a switch receives a " Broadcast Frame " on a port it will create multiple copies of the frame and forwards it to all other ports.

Switch don't broadcast but forwards the broadcast received on a port to all other ports.

If a sender and receiver are on the same ports switch blocks / discards the frame.

If sender and receiver are on the different ports , Switch will bridge the information to relevant port only.

Switch segments the network whereas HUB extends the  network.

If a receiver is not known switch forwards the information to all the ports.

5) Switch allows simultaneous communication between  multiple communicating pairs connected on different ports.

Every port of a switch has its own dedicated Bandwidth .

6) Every port of a switch is member of a separate collision domain.

Switch is a multiple collision domain.

Every port of a switch is member of same broadcast domain.

Switch is a single broadcast domain device .

Thanks for Reading !!!!

UNDERSTANDING MAC ADDRESS

MAC (Media Access Control) Address -

6 bytes (48 bits)  Hexadecimal  Hardware Unique Address that Identifies  each device on the network.

Also known as - 

BIA  (Burned in Address)

Layer 2  or L2 Address 

Machine Address

Hardware Address 


00 -1A -2B- 3C-4D-5E
     24 bits                 24 bits

Manufacture         Vendor 
    Code                 Assigned

Manufacture Code is also know as OUI - Organization Unique Identifer

Each Manufacture Vendor have unique OUI 

For eg - Intel have OUI as 00:19:D1

There are plenty of website which helps to get the Manufacture Vendors name from MAC address.

Some of them are :-

https://macvendors.com

https://aruljohn.com/mac.pl

https://www.macvendorlookup.com

http://www.coffer.com/mac_find/

Finding the mac address for your Windows PC or Laptop 

C:\Users\AMAR>ipconfig/all

Now lets try to find the Manufacture Vendor for my Windows Machine LAN Card 

Hopefully you all found the post useful.

Thanks for Reading !!!!!