Show Arp Command Not Showing Everything It should be

[chueymtz]

I'm trying to figure out why my show arp isn't showing all my of addresses for Vlan 2. Vlan 1 shows the correct addresses which would be 74.x.x.233-238. Vlan 2 should show 70.x.x.65 - 70 

3560-CX_HQ_ASA_GATEWAY#show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 65.x.x.85 17 54e0.xxxx.xxxx ARPA GigabitEthernet0/1
Internet 65.x.x.86 - 3c41.xxxx.xxxx ARPA GigabitEthernet0/1
Internet 70.x.x.67 - 3c41.xxxx.xxxx ARPA Vlan2
Internet 73.x.x.76 - 3c41.xxxx.xxxx ARPA GigabitEthernet0/2
Internet 74.x.x.233 - 3c41.xxxx.xxxx ARPA Vlan1
Internet 74.x.x.234 0 001c.xxxx.xxxx ARPA Vlan1
Internet 74.x.x.235 109 001c.xxxx.xxxx ARPA Vlan1
Internet 74.x.x.236 0 Incomplete ARPA
Internet 74.x.x.237 0 001c.7f84.xxxx ARPA Vlan1
Internet 74.x.x.238 0 001c.7f84.xxxx ARPA Vlan1

[Richard Burts]

try undebug all

Was this debug running with devices connected to the vlan 2 ports? If so post some of the output. Also please provide the information from the computers that I requested.

[chueymtz]

that didn't work, still scanning. Heres the output though

eSqe pf i l6t e1r6e:d3 7s:r5c8 .7700.39:1 . 2A0R8P. 7r0e q6 0i3sd .d2e6q7u1e.u6e5d5 1s,r cd s7t0 .7901..9210.82.0688./6080 10c0.070f.8040.0700.d050,0 0d swtr o7n0g. 9c1a.b2l0e8,. 7i0n/t0e0r0f0a.c0e0 0G0i.g0a0b0i0t Eotnh eVrlnaent20/2
eep 6 16:37:58.580: ARP req is dequ
.uSeedp s r6c 1764:.357.:25381..720337:/ 0I0P1 cA.R7Pf:8 4a.r7p0_dp3r,o cdessts _7r4e.q5u.e2s3t1:. 27304./9010.0200.80.06080,. 0h0w0:0 0o0n1 cV.l7afn814
77S0edp5 ; 6r c1:6 :33
:S5e8p. 5 860 :1 6I:P3 7A:R5P8:. 7a0r3p:_ pIrPo cAeRsPs _rreeqq ufeisltt:e r7e4d. 5s.r2c3 17.02.3971,. 2h0w8:. 6080 10c0.17cf.874f.8740.d730;d 5r,c :d s3t
07S0e.p9 1 .62 0186.:7307 :05080.05.8000:0 0I.P0 0A0R0P :w rrocnvgd craebql es,r ci n7t4e.r5f.a2c3e1 .V2l3a7n 20
1Sce.p7 6 16:37:59.374: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:37:59.374: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:37:59.374: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
1ep 6 16:37:59.388: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.68/0000.P0 0A0R0P.:0 0a0r0p _opnr oGciegsasb_irteEqtuheesrtn:e t700/.29
.S2e0p8 . 668 ,1 6h:w3:7 :05091.c3.878f:8 4I.P7 0AdR5P;: racr:p _3process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:37:59.388: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.68 0000.0000.0000 wrong cable, interface GigabitEthernet0/2
Sep 6 16:38:00.083: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
8ep 6 16:3
:S0e0p. 0 863 :1 6I:38:00.083: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:00.856: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlan1
Sep 6 16:38:00.856: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:00.856: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
Sep 6 16:38:00.866: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.68/0000.0000.0000 on GigabitEthernet0/2
Sep 6 16:38:00.866: IP ARP: arp_process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:38:00.866: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.68 0000.0000.0000 wrong cable, interface GigabitEthernet0/2
0ep 6 16:38:00.866: ARP req 3i2s7 :d e qAuRePu erde qs rics 7d0e.q9u1e.u2e0d8 .s6r8c/ 07041.c5..72f3814..27307d/50,0 1dcs.t7 f7804..9710.d230,8 .d7s0t/ 07040.05..0203010..203040/00 0o0n0 .V0l0a0n02.
0S0e0p o n6 V1l6a:n318:00.866: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:00.866: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:01.
Sep 6 16:38:01.327: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
tep 6 16:38:01.327: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 .00000000. 0w0r0o0n.g0 0c0a0b lVel,a ni1n
:eSrefpa c e6 V1l6a:n328
00S2e.p4 8 46: 1 6A:R3P8 :r0e2q. 4i9s5 :d e qAuRePu erde qs rics 7d0e.q9u1e.u2e0d8 .s6r8c/ 07001.c9.17.f28048..7608d/50,0 1dcs.t7 f7804..9710.d250,8 .d6s5t/ 07000.09.10.020008..07000/00 0o0n0 .V0l0a0n02.
e0S0e0p o n6 V1l6a:n328:02.484: IP ARP: arp_proc
2sSse_pr e q6u e1s6t::3 87:00.29.17.5270:8 . 6A8R,P hrwe:q 0i0s1 cd.e7qfu8e4u.e7d0 ds5r;c r7c4:. 53.
73S1e.p2 3 76/ 01061:c3.87:f0824..47804d:3 ,I Pd sAtR P7 4r.e5q. 2f3i1l.t2e3r8e/d0 0s0r0c. 07000.09.10.020008 .o6n8 V0l0a1nc1.
fS8e4p. 7 06d 51,6 :d3s8t: 0720..79517.:2 0I8P. 6A5R P0:0 0a0r.p0_0p0r0ocess_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:02.757: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.238 0000.0000.0000 Vlan1
Sep 6 16:38:02.768: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:38:02.768: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:02.768: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
1ep 6 16:38:02.897: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/00:0 07.40.050.02.3010.0203 7o,n hVwl:a n020
7cS.e7pf 8 46. 7106d:33;8 :r0c2:. 839
:S eIpP A6R P1:6 :a3r8p:_0p3r.o8c7e2s:s _IrPe qAuRePs:t :r c7v0d. 9r1e.q2 0s8r.c6 87,4 .h5w.:2 3010.12c3.77 f08041.c7.07df58;4 .r7c0:d 33,
adSsetp 7 46. 51.62:3318.:20328. 809070:0 .I0P0 0A0R.P0 0r0e0q Vflialnt1ered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interf
6cSee pV l a6n 21
:S3e8p: 0 36. 81863::3 8 :A0R3P. 8r7e2q: i sA RdPe qrueequ eids sdrecq u7e0u.e9d1 .s2r0c8 .7648./50.0213c1..72f3874/.07001dc5.,7 fd8s4t. 7700d.39,1 .d2s0t8 .7645./50.020301..0203080/.00000000. 0o0n0 0V.l0a0n020
6oSne pV l a6n 11
:S3e8p: 0 36. 81866::3 8I:P0 3A.R8P7:2 :a rIpP_ pArRoPc:e sasr_pr_epqruoecsets:s _7r0e.q9u1e.s2t08.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:03.886: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:05.025: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
Sep 6 16:38:05.025: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:05.025: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:05.808: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlan1
Sep 6 16:38:05.808: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:05.808: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
Sep 6 16:38:05.903: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:38:05.903: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:05.903: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:06.305: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
Sep 6 16:38:06.305: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:06.305: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:07.077: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:38:07.077: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:07.077: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:07.088: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.65/0000.0000.0000 on GigabitEthernet0/2
Sep 6 16:38:07.088: IP ARP: arp_process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:38:07.088: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.65 0000.0000.0000 wrong cable, interface GigabitEthernet0/2
Sep 6 16:38:07.465: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.68/0000.0000.0000 on GigabitEthernet0/2
Sep 6 16:38:07.465: IP ARP: arp_process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:38:07.476: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlan1
Sep 6 16:38:07.476: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:07.476: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
Sep 6 16:38:07.476: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.238/0000.0000.0000 on Vlan1
Sep 6 16:38:07.476: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:07.476: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.238 0000.0000.0000 Vlan1
Sep 6 16:38:08.821: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
.ep 6 16:38:08.821: IP ARP: rcvd req src 0704 .V5l.a2n311
02S3e7p 0 061 c1.67:f3884:.0790.d435,0 :d s tA R7P4 .r5e.q2 3i1s. 2d3e4q u0e0u0e0d. 0s0r0c0 .7000.0901 .V2l0a8n.17
/S6e0p3 d .62 61761:.3685:5018,. 8d2s1t: 7 0A.R9P1 .r2e0q8 .i6s5 /d0e0q0u0e.u0e0d0 0s.r0c0 0704 .o5n. 2G3i1g.a2b3i7t/E0t0h1ecr.n7eft804/.270d3, dst 74.5.231.238/0000.0000.0000 on Vlan1
rep 6 16:38:08.821: IP ARP: a
cpS_eppr o c6e s1s6_:r3e8q:u0e9s.t4:6 47:4 .I5P. 2A3R1P.:2 3r7c,v dh wr:e q0 0s1rcc. 77f48.45..7203d13.;2 3r7c :0 031
1.S7efp8 4 .67 01d63:,3 8d:s0t8 .7842.55:. 2I3P1 .A2R3P4: 0r0c0v0d. 0r0e0q0 .s0r0c0 07 4V.l5a.n213
.S2e3p7 060 11c6.:73f88:40.97.04d634,: d sAtR P7 4r.e5q. 2i3s1 .d2e3q8u e0u0e0d0 .s0r0c0 07.40.05.231.237/001c.7f84.70d3, dst 74.5.231.238/0000.0000.0000 on Vlan1
Sep 6 16:38:09.464: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:09.464: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.238 0000.0000.0000 Vlan1
Sep 6 16:38:10.576: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:38:10.576: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:10.583: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:10.583: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:11.429: IP ARP: sent req src 74.5.231.233 3c41.0eef.47c0,
dst 74.5.231.236 0000.0000.0000 Vlan1
_ep 6 16:38:11.436: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlaens1s
rSeeqpu e s6t :1 67:43.85:.1213.14.3263:7 ,I Ph wA:R P0:0 1acr.p7_fp8r4o.c70d3; rc: 3
Sep 6 16:38:11.436: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
Sep 6 16:38:11.436: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.66/0000.0000.0000 on GigabitEthernet0/2
Sep 6 16:38:11.436: IP ARP: arp_process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:38:11.436: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.66 0000.0000.0000 wrong cable, interface GigabitEthernet0/2
sep 6 16:38:12.142: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.00P0 0A.R0P0:0 0a ropn_ pVrloacne1s
_Sreepq u e6s t1:6 :7348.:51.22.3114.22:3 7I, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:12.142: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
7ep 6 16:38:12.946: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlfa8n41.
30Sde3p; r6c :1 63:
58S:e1p2 . 964 91:6 :I3P8 :A1R2P.:9 5a3r:p _IpPr oAcRePs:s _rrcevqdu ersetq: s7r4c. 57.42.351..223317.,2 3h7w :0 0010c1.c7.f78f48.47.07d03d,3 ;d srtc :7 43.
.S2e3p1 . 263 81 60:03080:.1020.0904.90:0 0I0P VAlRaPn:1 rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.234 0000.0000.0000 Vlan1
Sep 6 16:38:12.953: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.238/0000.0000.0000 on Vlan1
7ep 6 16:38:12.953: IP ARP: arp_process_request: 74.5.231.23
,S ehpw : 60 0116c:.378:13.582: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
Sep 6 16:38:13.582: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:13.582: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:14.204: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.238/0000.0000.0000 on Vlan1
Sep 6 16:38:14.204: IP ARP: arp_process_request: 74.5.231.237, hw: 001c.7f84.70d3; rc: 3
Sep 6 16:38:14.204: IP ARP: rcvd req src 74.5.231.237 001c.7f84.70d3, dst 74.5.231.238 0000.0000.0000 Vlan1
.ep 6 16:38:14.990: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.20:8 .7740./50.020301..0203070,. 0h0w0:0 0o0n1 cV.l7afn824
87S0edp3 ; 6r c1:6 :33
.:S1e4p. 9 960 :1 6I:P3 8A:R1P4:. 9a9r7p:_ pIrPo cAeRsPs:_ rrecqvude srte:q 7s0r.c9 17.42.058..26381,. 2h3w7: 000011cc..77ff8844..7700dd35,; drsct: 734
5S.e2p3 1 .62 3186 :03080:01.40.090900.:0 0I0P0 AVRlPa nr1eq filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
2ep 6 16:38:14.997: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.
r3S8e/p0 0 060 .1060:0308.:01050.05 8o8n: V lAaRnP1
eSqe pi s 6d e1q6u:e3u8e:d1 4s.r9c9 77:0 .I9P1 .A2R0P8:. 6a8r/p0_0p1rco.c7efs8s4_.r7e0qdu5e,s tdst 70.91.208.70/0000.0000.0000 on Vlan2
Sep 6 16:38:15.588: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:15.588: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:17.402: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.65/0000.0000.0000 on Vlan2
Sep 6 16:38:17.402: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:38:17.402: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.65 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:38:17.409: ARP req is dequeued src 74.5.231.237/001c.7f84.70d3, dst 74.5.231.234/0000.0000.0000 on Vlan1
Sep 6 16:38:17.409: IP ARP: arp_pro:c e7s4s._5r.e2q3u1e.s2t37, hw: 001c.7f84.70d3; rc: 3
0ep 6 16:38:17.409: IP ARP: rcvd req src 70P. 9r1e.q2 0i8s. 6d8e/q0u0e1uce.d7 fs8r4c. 7700d.59,1 .d2s0t8 .7608./9010.12c0.87.f6854/.07000d05.,0 0d0s0t. 07000.09 1o.n2 0V8l.a7n02/
P0S0e0p. 0 060 01.60:04000: 5o2n. 0V1l1a:n 2I
SAeRpP : 6a r1p6_:p4r0o:c5e1s.s9_9r7e:q uIePs tA:R P7:0 .a9r1p._2p0r8o.c6e8s,s _hrwe:q u0e0s1tc:. 77f08.49.17.02d058;. 6r8c,: h3w: 001c.7f84.70d5; rc: 3
2ep 6 16:40:51.997: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan
S
eSpe p 6 61 61:64:04:05:25.24.3011:1 : A RAPR Pr erqe qis dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
Sep 6 16:40:52.431: IP ARP: arp_process_request: 70.91.208.68, hw: 001c.7f84.70d5; rc: 3
Sep 6 16:40:52.431: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2
Sep 6 16:40:52.815: ARP req is dequeued src 70.91.208.70/603d.2671.6551, dst 70.91.208.65/0000.0000.0000 on GigabitEthernet0/2
Sep 6 16:40:52.819: IP ARP: arp_process_request: 70.91.208.70, hw: 603d.2671.6551; rc: 3
Sep 6 16:40:52.819: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.65 0000.0000.0000 wrong cable, interface GigabitEthernet0/2
Sep 6 16:40:53.490: ARP req is dequeued src 70.91.208.68/001c.7f84.70d5, dst 70.91.208.70/0000.0000.0000 on Vlan2
1S9e7p: I6P 1A6R:P4:0 :s5e3n.t4 9r0e:q IsPr cA R7P4:. 5a.r2p3_1p.r2o3c3e s3sc_4r1e.q0ueeesft.:4 77c00.,9
0. 2 0 8 . 6 8 , h w : 0 0 1 c .d7sft8 47.47.05d.52;3 1r.c2:3 63
0S0e0p. 0

[Richard Burts]

Thank you for the debug output. Some of the messages clearly show that there is a mismatch between the source address of the arp request and the address of the interface on which it was received. For example

Sep 6 16:37:59.388: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.68 0000.0000.0000 wrong cable, interface GigabitEthernet0/2

the source address of 70.91.208.70 appears to be received on G0/2 whose address is 73.x.x.76 which clearly do not match up. When this type of mismatch occurs IOS rejects the request. Understanding why this source address is received on this interface requires knowledge of the environment that we do not have.

There are other messages which are puzzling such as this

Sep 6 16:38:06.305: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2

The posted partial config shows this for vlan 2

interface Vlan2
ip address 70.x.x.67 255.255.255.248

Is this a mismatch?

[chueymtz]

So the g0/2 73.x.x.76 address is the WAN ip for the comcast router based on the settings inside of the modem and the 70.91.208.70 is the gateway for the 5 static ip's comcast gave us. Am i putting the wrong ip on interface g0/2? I tried using 70.91.208.67 but then i can't add 70.91.208.69 to vlan2 because it says it's overlapping.

[MHM Cisco World]

sorry I was Busy 
I will deep analysis your info. update you today 

[Richard Burts]

Thanks for the additional information. If you have been assigned a Public IP by comcast for the connection to them and assigned an additional block of Public IPs then what you have described is reasonable. The Public IP for connection on G0/2 and the other Public IPs on a vlan.

The issue here is that some device connected to G0/2 is sending arp requests which have a source address of 70.91.208.70. This does not match the subnet of the interface and the arp request is rejected. You should figure out what device this is and why it appears to be configured with that address.

[MHM Cisco World]

interface GigabitEthernet0/1
description connection to Internet
no switchport
ip address 65.x.x.86 255.255.255.252
!
interface GigabitEthernet0/2
description to Comcast Router
no switchport
ip address 73.x.x.76 255.255.255.248
!
interface Vlan1
ip address 74.x.x.233 255.255.255.248
!
interface Vlan2
ip address 70.x.x.67 255.255.255.248

Sep 6 16:40:52.819: IP ARP req filtered src 70.91.208.70 603d.2671.6551, dst 70.91.208.65 0000.0000.0000 wrong cable, interface GigabitEthernet0/2

Sep 6 16:38:15.588: IP ARP req filtered src 70.91.208.68 001c.7f84.70d5, dst 70.91.208.70 0000.0000.0000 wrong cable, interface Vlan2

sure this is IP conflict but where ?
VLAN 2 have subnet from to 
70.91.208.65 - 70.91.208.70
so this range include the VLAN 2 range, i.e. one host connect to this subnet ask the mac address of other host connect to same subnet.
that great no issue 
BUT the issue the packet receive on G0/2 !!!!WHAT!!!!

the G0/2 is L3 (L2 but with no switchport command) and config with subnet totally different?

the Q here is there any L2 device connect this L3SW to Router?

[chueymtz]

Thanks, Ok so i got the arp working now, the issue was that I didn't have my comcast modem in bridgemode once i did that I was able to see all arp and everything on vlans. And yes we go from a cisco switch with isps and vlans to a firewall to an L3 cisco switch that does dhcp etc. My question now that when I pull the plug on port 1 65.x.x.x port 2 isn't taking over and we lost internet, not sure if my static route is incorrect for the 73.x.x.x network, here is my current config

!
interface GigabitEthernet0/1
description connection to Internet 25.KXGS.467980
no switchport
ip address 65.144.247.86 255.255.255.252
!
interface GigabitEthernet0/2
description to Comcast Router
no switchport
ip address 73.23.193.76 255.255.255.0
!
interface GigabitEthernet0/3
!
interface GigabitEthernet0/4
!
interface GigabitEthernet0/5
switchport mode access
!
interface GigabitEthernet0/6
switchport mode access
!
interface GigabitEthernet0/7
switchport access vlan 2
switchport mode access
!
interface GigabitEthernet0/8
switchport access vlan 2
switchport mode access
!
interface GigabitEthernet0/9
!
interface GigabitEthernet0/10
!
interface GigabitEthernet0/11
!
interface GigabitEthernet0/12
!
interface Vlan1
ip address 74.5.231.233 255.255.255.248
ip policy route-map ISP-A
!
interface Vlan2
ip address 70.91.208.67 255.255.255.248
ip policy route-map ISP-B
!
ip forward-protocol nd
!
!
ip http server
ip http secure-server
ip route 0.0.0.0 0.0.0.0 65.144.247.85
ip route 0.0.0.0 0.0.0.0 70.91.208.70
!
!
access-list 46 permit 185.189.149.184
access-list 46 permit 185.189.151.235
access-list 46 permit 89.248.173.131
access-list 46 permit 185.158.251.126
access-list 46 permit 185.212.47.166
access-list 100 permit ip 0.0.0.1 255.255.255.248 any
access-list 110 permit ip 0.0.0.3 255.255.255.248 any
!
!
route-map ISP-B permit 10
match ip address 110
set ip next-hop 73.23.193.76
!
route-map ISP-A permit 10
match ip address 100
set ip next-hop 65.144.247.86
!
!
!
line con 0
line vty 0 4
access-class 46 in
privilege level 15
login local
transport input telnet ssh
line vty 5 14
access-class 46 in
login
line vty 15
login
!
!
end

[MHM Cisco World]

try this instead 
ip route 0.0.0.0 0.0.0.0 <egress interface> <next-hop>

[chueymtz]

and do i remove the other 2 ip routes ip route 0.0.0.0 0.0.0.0 65.144.247.85, ip route 0.0.0.0 0.0.0.0 70.91.208.70 and replace with the one you recommended? and which would be my egress interface?

[MHM Cisco World]

usually the egress interface will be VLAN but in your case I dont think the VLAN is transit VLAN so, this option not suitable for you. 
you need to config IP SLA to detect the next-hop reachability. 

[Richard Burts]

Thanks for the update. Glad to know that the arp issue is now resolved.

You certainly do not want to remove both of the existing static default routes (though you probably may want to change some things about them). If you remove both and configure a single default route then you will have a single path outbound - and no possibility of failover if a problem develops with one ISP.

I am puzzled why you have PBR in this configuration. And I am puzzled about how PBR is configured. The access lists used in both route maps are very odd and come very close to being permit ip any any. The result of this PBR is that vlan 1 will always be forwarded to ISP A and vlan 2 will always be forwarded to ISP B. No opportunity  to failover is either ISP is having a problem. Unless you can explain some reason why you need the PBR I suggest that you remove it.

[chueymtz]

Thank you for the response. I actually got that recommendation from this forum for the PBR, I've never done anything failover and that config that i used was based on what they asked me to put in.

[Richard Burts]

Thank you for the additional information. It is interesting that the PBR is in the config because it was suggested in some post in the forum. Am I correct in understanding that in that post you described a situation where you have a Public IP from some ISP, a small block of addresses from that ISP (used in vlan 1), a Public IP from comcast, and a small block of addresses from Comcast (used in vlan 2). And that you were asking how to forward traffic originated from vlan 1 to that ISP and forward traffic from vlan 2 to comcast? I believe that there was some misunderstanding about how to configure access lists 100 and 110 used in the route maps but basically this is what the PBR is doing in your config.

Now you have a different question: " when I pull the plug on port 1 65.x.x.x port 2 isn't taking over". The thing to understand about the PBR that you are using is that it is saying that ALL traffic originated in vlan 1 should always be sent to the first ISP. There is not anything there to allow for port 2 to take over if port 1 has a problem. If you want port 2 to be able to take over then there are 2 things that you need to do in your config.

1) You need to configure PBR to check to see if the ISP on port 1 is working and only forward traffic to it while it is working. If your code supports it the verify-availability parameter in the set statement could do this. And you probably want to do this for the PBR for comcast as well.

2) In the current config you have 2 static default routes (one to each ISP). And they are both active all of the time. You need to add tracking for those static default routes so that if there is a problem with one of the ISP then the static default route pointing to that ISP is withdrawn from the routing table and all traffic would be forwarded to the ISP that is working.

[paul driver]

Hello
Ping an missing ip address from the L3  switch/rtr and see then the arp gets populated?