Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

catalyst switch - encapsulation failed problem!!!

[es] :: Enterprise Networking :: catalyst switch - encapsulation failed problem!!!

[ Pregleda: 2261 | Odgovora: 12 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon catalyst switch - encapsulation failed problem!!!27.03.2011. u 07:28 - pre 144 meseci
Pozdrav svima ...

Ovako, imam jedan cudan problem na poslu sa jednostavnim povezivanjem dva Catalyst switcha i to:
1. swirch - Catalyst 3550, konfigurisan kao VTP server, sa tri VLAN-a
2. switch - Catalyst 2950, konfigurisan kao VTP client

Topologija izgleda otprilike ovako:

Cat3550(f0/1) -> transparent_wireless_AP1 ->transparent_wireless-AP2 -> Cat2950(f0/24)

I interfejs f0/1 na Cat3550 i interfejs f0/24 na Cat2950 su konfigurisani kao trunk portovi sa dot1q enkapsulacijom i dozvoljeni su svi VLAN-ovi.

Na Cat3550 postoje tri IP adrese za pomenuta tri VLAN-a (172.16.1.1, 172.16.2.1 i 172.16.3.1), dok na Cat2950 ima jedna adresa za VLAN 1 (172.16.1.2)

Stanje je sledece:
1. oba switcha se vide po CDP protokolu (show cdp neigbor detail)
2. razmjena VTP baze sa VTP servera na VTP client radi (na Cat2950 show vlan prikazuje sva tri VLANa)
3. ping ne prolazi ni sa jedne strane

Evo kako ja na to gledam:
1. paketi koji ne zahtjevaju VLAN tag i koji se salju multicast-om salju se bez problema (CDP, VTP)
2. paketi koji su tagovani sa VLAN-om ne prolaze (ping ..). Nema ni ARP zapisa u ARP keshu.

Sve mi upucuje na to da wireless AP-ovi ne proslijedjuju broadcast nego samo multicast, te zbgog toga radi CDP i VTP koji se prenose broadcast-om a ne radi ARP (a kao posledica toga ni pinganje) jer se ARP Request prenosi broadcastom.

U debug listingu na CAT2950 se javlja stavka ''enacpsulation failed''. 100% sam siguran da su trunk portovi dobro konfigursani (switchport trunk encapsulation dot1q, switchport mode trunk, s tim sto CAT2950 ne trazi eksplicitno navodjenje moda enkapsulacije jer podrzava samo dot1q).


Listin sa debug komandama pri slanju ping paketa sa oba switcha je ispod:

*************************************************
Cat2950 listing:

CAT2950#debug ip packet de
CAT2950#debug ip packet detail
IP packet debugging is on (detailed)
CAT2950#
CAT2950#pin
CAT2950#ping 172.16.1.1

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

00:07:42: datagramsize=100, IP 35: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, sending
00:07:42: ICMP type=8, code=0.
00:07:45: datagramsize=100, IP 35: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, encapsulation failed
00:07:45: ICMP type=8, code=0
00:07:45: datagramsize=100, IP 36: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, sending
00:07:45: ICMP type=8, code=0.
00:07:48: datagramsize=100, IP 36: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, encapsulation failed
00:07:48: ICMP type=8, code=0
00:07:48: datagramsize=100, IP 37: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, sending
00:07:48: ICMP type=8, code=0.
00:07:51: datagramsize=100, IP 37: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, encapsulation failed
00:07:51: ICMP type=8, code=0
00:07:51: datagramsize=100, IP 38: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, sending
00:07:51: ICMP type=8, code=0.
00:07:54: datagramsize=100, IP 38: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, encapsulation failed
00:07:54: ICMP type=8, code=0
00:07:54: datagramsize=100, IP 39: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, sending
00:07:54: ICMP type=8, code=0.
Success rate is 0 percent (0/5)
CAT2950#
00:07:57: datagramsize=100, IP 39: s=172.16.1.2 (local), d=172.16.1.1 (Vlan1), t
otlen 100, fragment 0, fo 0, encapsulation failed
00:07:57: ICMP type=8, code=0
Cat2950#
***********************************************************************

CAT3550 listing:
**********************************************************************
CAT3550#deb
CAT3550#debug ip pa
CAT3550#debug ip packet
IP packet debugging is on
CAT3550#PIN
CAT3550#ping 172.16.1.2

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

01:02:50: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:02:50: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet.
01:02:52: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:02:52: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet.
01:02:54: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:02:54: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet.
01:02:56: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:02:56: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet.
01:02:58: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:02:58: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet.
Success rate is 0 percent (0/5)
CAT3550#ping 172.16.1.2 det
CAT3550#ping 172.16.1.2 deta
CAT3550#deb
CAT3550#debug ip pa
CAT3550#unde
CAT3550#undebug all
All possible debugging has been turned off
CAT3550#deb
CAT3550#debug ip pa
CAT3550#debug ip packet de
CAT3550#debug ip packet detail
IP packet debugging is on (detailed)
CAT3550#pin
CAT3550#ping 172.16.1.2

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

01:03:34: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:03:34: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:03:34: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:03:34: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:03:34: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:03:34: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:03:34: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:03:34: FIBipv4-packet-proc: packet routing succeeded
01:03:34: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:03:34: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:03:34: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:03:34: ICMP type=8, code=0
01:03:34: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
pac.ket
01:03:34: ICMP type=8, code=0
01:03:36: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:03:36: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:03:36: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:03:36: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:03:36: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:03:36: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:03:36: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:03:36: FIBipv4-packet-proc: packet routing succeeded
01:03:36: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:03:36: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:03:36: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:03:36: ICMP type=8, code=0
01:03:36: IP: s=172.16.1.1 (local), d=172.16..1.2 (Vlan1), len 100, sending full
packet
01:03:36: ICMP type=8, code=0
01:03:37: FIBipv4-packet-proc: route packet from Vlan1 src 172.16.1.100 dst 172.
16.1.255
01:03:37: FIBfwd-proc: Default:172.16.1.255/32 receive entry
01:03:37: FIBipv4-packet-proc: packet routing failed
01:03:37: IP: s=172.16.1.100 (Vlan1), d=172.16.1.255 (Vlan1), len 229, rcvd 3
01:03:37: UDP src=138, dst=138
01:03:37: IP: s=172.16.1.100 (Vlan1), d=172.16.1.255, len 229, stop process pak
for forus packet
01:03:37: UDP src=138, dst=138
01:03:38: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:03:38: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:03:38: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:03:38: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:03:38: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:03:38: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:03:3.8: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:03:38: FIBipv4-packet-proc: packet routing succeeded
01:03:38: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:03:38: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:03:38: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:03:38: ICMP type=8, code=0
01:03:38: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:03:38: ICMP type=8, code=0
01:03:40: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:03:40: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:03:40: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:03:40: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:03:40: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:03:40: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib. 0 path type adjacency prefix
01:03:40: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:03:40: FIBipv4-packet-proc: packet routing succeeded
01:03:40: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:03:40: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:03:40: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:03:40: ICMP type=8, code=0
01:03:40: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:03:40: ICMP type=8, code=0
01:03:42: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:03:42: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:03:42: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:03:42: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:03:42: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:03:42: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535.
Success rate is 0 percent (0/5)
CAT3550# if Vlan1 nh 172.16.1.2 deag 0 via fib 0 path type adjacency prefix
01:03:42: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:03:42: FIBipv4-packet-proc: packet routing succeeded
01:03:42: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:03:42: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:03:42: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:03:42: ICMP type=8, code=0
01:03:42: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:03:42: ICMP type=8, code=0
CAT3550#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 172.16.1.1 - 001f.6d53.6fc0 ARPA Vlan1
Internet 172.16.3.1 - 001f.6d53.6fc2 ARPA Vlan3
Internet 172.16.1.2 22 0012.00ec.2480 ARPA Vlan1
Internet 172.16.2.1 - 001f.6d53.6fc1 ARPA Vlan2
Internet 172.16.1.100 18 0006.1bcb.bb63 ARPA Vlan1
CAT3550#ping 172.16.1.2

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

01:04:23: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:04:23: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:04:23: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:04:23: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:04:23: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:04:23: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:04:23: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:04:23: FIBipv4-packet-proc: packet routing succeeded
01:04:23: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:04:23: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:04:23: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:04:23: ICMP type=8, code=0
01:04:23: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
pac.ket
01:04:23: ICMP type=8, code=0
01:04:25: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:04:25: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:04:25: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:04:25: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:04:25: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:04:25: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:04:25: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:04:25: FIBipv4-packet-proc: packet routing succeeded
01:04:25: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:04:25: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:04:25: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:04:25: ICMP type=8, code=0
01:04:25: IP: s=172.16.1.1 (local), d=172.16..1.2 (Vlan1), len 100, sending full
packet
01:04:25: ICMP type=8, code=0
01:04:27: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:04:27: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:04:27: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:04:27: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:04:27: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:04:27: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:04:27: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:04:27: FIBipv4-packet-proc: packet routing succeeded
01:04:27: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:04:27: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:04:27: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:04:27: ICMP type=8, code=0
01:04:2.7: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:04:27: ICMP type=8, code=0
01:04:29: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:04:29: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:04:29: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:04:29: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
01:04:29: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
01:04:29: FIBfwd-proc: ip_pak_table 0. ip_nh_table 65535 if Vlan1 nh 172.16.1.2
deag 0 via fib 0 path type adjacency prefix
01:04:29: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:04:29: FIBipv4-packet-proc: packet routing succeeded
01:04:29: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:04:29: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:04:29: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:04:29: ICMP type=8, code=0
01:04:29: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:04:29: ICMP type=8, code=0
01:04:31: FIBipv4-packet-proc: route packet from (local) src 172.16.1.1 dst 172.
16.1.2
01:04:31: FIBfwd-proc: Default:172.16.1.2/32 proces level forwarding
01:04:31: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
01:04:31: FIBfwd-proc: try path 0 (of 1) v4-adp-172.16.1.2-Vl1 first short ext 0
(-1)
.1:04:31: FIBfwd-proc: v4-adp-172.16.1.2-Vl1 valid
Success rate is 0 percent (0/5)
CAT3550#
01:04:31: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 d
eag 0 via fib 0 path type adjacency prefix
01:04:31: FIBfwd-proc: packet routed to Vlan1 172.16.1.2(0)
01:04:31: FIBipv4-packet-proc: packet routing succeeded
01:04:31: FIBfwd-proc: ip_pak_table 0 ip_nh_table 65535 if Vlan1 nh 172.16.1.2 u
hp 1 deag 0 ttlexp 0
01:04:31: FIBfwd-proc: sending link IP ip_pak_table 0 ip_nh_table 65535 if Vlan1
nh 172.16.1.2 uhp 1 deag 0 ttlexp 0 rec 0
01:04:31: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending
01:04:31: ICMP type=8, code=0
01:04:31: IP: s=172.16.1.1 (local), d=172.16.1.2 (Vlan1), len 100, sending full
packet
01:04:31: ICMP type=8, code=0
CAT3550#
CAT3550#
CAT3550#
CAT3550#und
CAT3550#undebug all
All possible debugging has been turned off
CAT3550#
CAT3550#
CAT3550#pi
CAT3550#ping 172.16.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
CAT3550#
**************************************************************************

Da li osim problema sa ARP broadcastingom postoje i neki drugi problemi koje ne uocavam?
Da li je problem mozda u tome sto je izmedju dva switcha wireless mreza, da li wireless mreza mozda ''skida'' VLAN tagove pa enkapsulacije ne prolazi??

Sutra cu pokusati sa ISL enkapsulacijom dok nabavim jos jedan 3550 switch jer 2950 ne podrzava ISL.

Sta je uostalom uzrok da se desi ''encapsulation failed''???

Hvala unaprijed!!!


[Ovu poruku je menjao gogo82 dana 27.03.2011. u 12:59 GMT+1]

[Ovu poruku je menjao gogo82 dana 28.03.2011. u 20:50 GMT+1]
Pozdrav!
Gogo82
 
Odgovor na temu

mckrsta
Nenad Krstic
System Engineer
AT&T Slovakia
Bratislava

Član broj: 44532
Poruke: 219
*.dynamic.isp.telekom.rs.

Sajt: www.bor030.net


+6 Profil

icon Re: catalyst switch - encapsulation failed problem!!!28.03.2011. u 16:50 - pre 144 meseci
pokusacu da malo pomognem, mada ni sam nisam siguran,

encapsulation failed ti kaze da SW zna na koj port treba da pusti frame, ali jednostavno nezna kako, tj. neki problem oko enkapsulacije, bar bi tako trebalo da bude... pitanje je kako AP prosledjuje frame-ove...

najlakse je, da spojih, ako mozes, direktno ta dva sw i vidis sta se desava.... eventualno pustis running....

Code:


Evo kako ja na to gledam:
1. paketi koji ne zahtjevaju VLAN tag i koji se salju broadcast-om salju se bez problema (CDP, VTP)
2. paketi koji su tagovani sa VLAN-om ne prolaze (ping ..). Nema ni ARP zapisa u ARP keshu.



ako ti je native vlan 1 i ti pingujes iz vlan-a 1 ni one nece biti tagovan... tako da bi trebalo da prodje....
 
Odgovor na temu

yellow pinky
Niš

Član broj: 28354
Poruke: 193
*.dynamic.isp.telekom.rs.



+13 Profil

icon Re: catalyst switch - encapsulation failed problem!!!28.03.2011. u 17:10 - pre 144 meseci
Encapsulation problem se ovde najverovatnije javlja zato što Catalyst 2950 ne zna kako da stigne do adrese koja se pinguje, tj. da ARP sa te strane ne radi.
Prvo što bih pogledao (pod uslovom da je sve povezano i konfigurisano kako treba)je da nije možda uključen neki firewall na APovima (ako postoji).
Ako postoji komanda , proveri na 2950 show arp ili show ip arp (da li postoji unos za 172.16.1.1).
Da li postoji možda i neka Access lista koja blokira icmp echo ili icmp echo-reply ?
Proveri i da li je spanning-tree u forwarding stanju.

p.s.

ARP je broadcast dok su CDP i VTP multicast .

p.s.s

mogao bi i okačiti running conf (ako nisu tajna) čisto da se pogledaju.

[Ovu poruku je menjao yellow pinky dana 28.03.2011. u 18:23 GMT+1]
 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!28.03.2011. u 19:40 - pre 144 meseci
@mckrsta ''ako ti je native vlan 1 i ti pingujes iz vlan-a 1 ni one nece biti tagovan... tako da bi trebalo da prodje....''

nisam bas 100% siguran za ovo da nece biti tagovani, native vlan sluzi samo ako dodje paket koji nije tagovan da ga proslijedi na native vlan ... Ne kazem da nije ni da jeste nego nisam bas siguran oko ovoga ...


@ yellow pinki ''ARP je broadcast dok su CDP i VTP multicast .''
naravno moja greska, multicast je u pitanju, a broadcast ne radi pa samim tim ni ARP


Inace switcheve sam prije postavljanja tetsirao preko UTP kabla, sve radi OK.

sh arp pokazuje gresku ARP INCOMPLETE tj ne moze da razrijesi mac adresu, da li zato sto ne radi broadcast ili zbog neceg drugog ne znam ... ali ne radi.

ACL na AP-ovima ne postoji, a sto se tice drugih smetnji nisam 100% siguran jer nisam ja postavljao AP-ove.

Znaci da sumiram
1. VTP i CDP koji se salju multicastom rade
2. ARP prijavljuje gresku ARP INCOMPLETE
3. STP je iskljucen, ne radi



Konfiguracija je uglavnom ovakva:

=========================================
VTP server Catalyst 3550
=========================================
vtp mode server
vtp domain test

vlan 1

vlan 2
name test_2

vlan 3
name test_3

interface f0/1
switchport trunk encapsulation dot1q
switchport mode trunk

interface vlan 1
ip address 172.16.1.1 255.255.255.0

interface vlan 2
ip address 172.16.2.1 255.255.255.0

interface vlan 3
ip address 172.16.3.1 255.255.255.0

ip routing

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


===================================================
VTP client Catalyst 2950
====================================================

vtp mode client
vtp domain test

interface f0/24
switchport mode trunk

interface vlan 1
ip address 172.16.1.2 255.255.255.0

ip default-gateway 172.16.1.1

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

Ima li jos neko neki prijedlog kako da resim ovo? Ponavljam sve dobro radi ako sw switchevi povezu UTP-om.
Mislim da ako resim zbog cega ne radi ARP da cu resiti i ceo problem.
Pozdrav!
Gogo82
 
Odgovor na temu

yellow pinky
Niš

Član broj: 28354
Poruke: 193
*.dynamic.isp.telekom.rs.



+13 Profil

icon Re: catalyst switch - encapsulation failed problem!!!28.03.2011. u 20:35 - pre 144 meseci
Parcijalna konfiguracija deluje dobro.

Multicast je vrlo sličan broadcastu tako da i tu sigurno nije problem.

Za ovakve probleme najčešći razlog su loši kablovi. Probaj da zameniš kabl od switcha 2950 do APa pa probaj tada.



[Ovu poruku je menjao yellow pinky dana 28.03.2011. u 21:53 GMT+1]
 
Odgovor na temu

mckrsta
Nenad Krstic
System Engineer
AT&T Slovakia
Bratislava

Član broj: 44532
Poruke: 219
*.dynamic.isp.telekom.rs.

Sajt: www.bor030.net


+6 Profil

icon Re: catalyst switch - encapsulation failed problem!!!28.03.2011. u 23:22 - pre 144 meseci
generalno vrlo cudna stvar, jeste da su CDP i VTP multicast, ako na samom Sw nije podesen, ove poruke ce biti broadcast, a isto tako je i ARP, iz nekog razloga se ne vraca response na ARP request... sto se tice vlan1, ili bilo kog drugog koji je native, frame se ne taguje...

koncentrisi se na layer 3, tu je negde problem, L1/L2 bi trebalo da je ok, s obzirom da ima razmene CDP, VTP... probaj da na AP, stavis AP/Client kombinaciju, eventualno neke staticke rute...pa da vidis

ajde bas javi sta je bio problem, kad budes resio...

 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!29.03.2011. u 01:03 - pre 144 meseci
Citat:
yellow pinky: Parcijalna konfiguracija deluje dobro.

Multicast je vrlo sličan broadcastu tako da i tu sigurno nije problem.

Za ovakve probleme najčešći razlog su loši kablovi. Probaj da zameniš kabl od switcha 2950 do APa pa probaj tada.


[Ovu poruku je menjao yellow pinky dana 28.03.2011. u 21:53 GMT+1]


Pokusavao sam da racunar stavim preko tog kabla u AP i sa racunara radi i ARP i ping i sve ostalo. Stvarno cudno. Ali ako nista drugo ne rijesi priblem, pokusat cu i sa zamjenom konektora na tom kablu.


Citat:
mckrsta: generalno vrlo cudna stvar, jeste da su CDP i VTP multicast, ako na samom Sw nije podesen, ove poruke ce biti broadcast, a isto tako je i ARP, iz nekog razloga se ne vraca response na ARP request... sto se tice vlan1, ili bilo kog drugog koji je native, frame se ne taguje...

koncentrisi se na layer 3, tu je negde problem, L1/L2 bi trebalo da je ok, s obzirom da ima razmene CDP, VTP... probaj da na AP, stavis AP/Client kombinaciju, eventualno neke staticke rute...pa da vidis

ajde bas javi sta je bio problem, kad budes resio...


OK, i jas sam nasao u dokumentaciji da se ne taguju frame-ovi. Ne znam vise ni sam sta da radim. Ta dva switcha sam konfigurisao u kancelariji i povezao UTP kablom radi testa, 100% sve radi OK. Ne vjerujem da je greska uopste na Cisco uredjajima, najvjerovatnije je na tim AP-ovima i njihovom ARP lookup-u, ili u krajnjem slucaju, sto kaze yellow pinky mozda neki banalan problem sa kablovima i sl.) Prije bih rekao da su AP-ovi.

Sto se tice layer-a 3, ne vidim sta bi tu mogao biti problem, CAT2950 pinga interfejs na CAT3550 koji je na istom subnetu. Nema rutiranja. Jedino smo u pocetku sumnjali da wireless ima razlicit MTU od switcheva .... te da to mozda pravi probleme, ali je MTU na Motoroli 1522 znaci ne bi trebali da je to u pitanju.

Sto se tice samih AP-ova u pitanju je Motorola sistem, jedan uredjaj je AP (Access Point) a drugi SM (Subsriber Module). AP je povezan na CAT3550 switch a SM je povezan na CAT2950 switch.

Nego, na koji nacin se moze menjati da switchevi koriste broadcast ili multicast za CDP, VTP ili ARP? Koja komanda (ili komande)?

U svakom slucaju mnogo hvala na pomoci, svakako javljam sta je bio problem kad resim.

Naravno, ako se jos necega setite sta bi mogao biti problem, molim javite!!!




[Ovu poruku je menjao gogo82 dana 29.03.2011. u 02:32 GMT+1]
Pozdrav!
Gogo82
 
Odgovor na temu

mckrsta
Nenad Krstic
System Engineer
AT&T Slovakia
Bratislava

Član broj: 44532
Poruke: 219
*.dynamic.isp.telekom.rs.

Sajt: www.bor030.net


+6 Profil

icon Re: catalyst switch - encapsulation failed problem!!!29.03.2011. u 09:01 - pre 144 meseci
gledam nesto ove debug-ove, iskljuci CEF pa odradi debug-ove, i pingaj....ako nista drugo bice preglednije....
p.s. nemoj da zaboravis da vratis cef....
 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!29.03.2011. u 19:10 - pre 144 meseci
Pozdrav,

danas sam kontaktirao ove sto su postavljali wireless uredjaje, to je nesto do njih problem, vjerovatno ne mogu da rade sa VLAN-ovima ili sta vec.
Cisco switchevi su potpuno ispravno konfigurisani, detaljno smo testiswitcheve ako se povezu UTP-om.
Mislim da je problem mozda u nacinu na koji wireless uredjaji proslijedjuju broatcast i multicast, ili sa ARP forwardingom. Stalno se iznova pojavljuje problem ARP incomplete.


Pozdrav!
Gogo82
 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!30.03.2011. u 19:41 - pre 144 meseci
pozdrav,

danas sam opet radio ''svu silu'' testova, i konacno otkrio sta pravi problem, tj. potvrdio svoju pocetnu pretpostavku.

Naime, ako i samo ako se kao native vlan na switchevima postavi vlan 1, ona radi ARP i to samo za taj VLAN. Znaci AP-ovi ili nemaju podrsku za VLAN-ove ili imaju samo VLAN 1. Ako se kao native vlan na switchevima postavi bilo koji drugo vlan ne radi ARP, tj. javlja se poruka encapsulation failed i ARP incomplete.

Sutra cu pokusati sa ISL enkapsulacijom, nesto razmisljam ako AP-ovi ne prepoznaju ISL mozda ce pretpostaviti da frejmovi nisu tagovani proslijediti ih do odredisnog switcha pa sve to mozda i proradi.

Javljam se sutra sa novim vijestima poslije testa.
Pozdrav!
Gogo82
 
Odgovor na temu

yellow pinky
Niš

Član broj: 28354
Poruke: 193
*.dynamic.isp.telekom.rs.



+13 Profil

icon Re: catalyst switch - encapsulation failed problem!!!30.03.2011. u 20:03 - pre 144 meseci
ISL enkapsulacija funkcioniše drugačije no dot1q.

Dok dot1q u originalni ethernet frejm umeće 4voro bajtni vlan tag, ISL enkapsulira celokupan originalni ethernet frejm i dodaje svoj header i trailer.
Takođe, ISL je Cisco proprietary protokol koji razumeju samo cisco uređaji , tako da postoji mogućnost da ga APovi uopšte ne prepoznaju kao validan frejm i odbace ga.

Btw, da li na switchu 2950 planiraš da računare ubacuješ samo u VLAN 1 ili planiraš više VLANova na njemu?

[Ovu poruku je menjao yellow pinky dana 30.03.2011. u 21:39 GMT+1]
 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!31.03.2011. u 04:49 - pre 144 meseci
Citat:
yellow pinky: ISL enkapsulacija funkcioniše drugačije no dot1q.

Dok dot1q u originalni ethernet frejm umeće 4voro bajtni vlan tag, ISL enkapsulira celokupan originalni ethernet frejm i dodaje svoj header i trailer.
Takođe, ISL je Cisco proprietary protokol koji razumeju samo cisco uređaji , tako da postoji mogućnost da ga APovi uopšte ne prepoznaju kao validan frejm i odbace ga.

Btw, da li na switchu 2950 planiraš da računare ubacuješ samo u VLAN 1 ili planiraš više VLANova na njemu?

[Ovu poruku je menjao yellow pinky dana 30.03.2011. u 21:39 GMT+1]


Planiram umjesto 2950 da postavim cat3560 koji ima podrsku za ISL. Nadam se da bi to moglo uspjeti, jer AP ovi ne poznaju ISL te bi mogli smatrati da je frejm netagovan i proslijediti ga dalje kao i sve druge netagovane frejmove, vredi pokusati pa sta bude ....

Inace, na obe strane planiram koristiti sve vlanove tzv end-to-end VLAN.
Pozdrav!
Gogo82
 
Odgovor na temu

gogo82

Član broj: 228454
Poruke: 118



+8 Profil

icon Re: catalyst switch - encapsulation failed problem!!!31.03.2011. u 19:00 - pre 144 meseci
Problem (bar zasad) resen!!!

ISL je resio problem!!! Wireless nema podrsku za VLANove, tj ima samo za vlan1 ali sam konfigurisao enkapsulaciju i sad sve radi OK!!!

Hvala svima na pomoci!!!
Pozdrav!
Gogo82
 
Odgovor na temu

[es] :: Enterprise Networking :: catalyst switch - encapsulation failed problem!!!

[ Pregleda: 2261 | Odgovora: 12 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.