03-27-2012 10:04 AM - edited 03-07-2019 05:49 AM
Hello Experts,
Can someone please tell me what I'm missing here. I have switches connected via eth 1/0, and an SVI's for vlan 200. I have configured svi's 200.1.1.1 255.255.255.252 and 200.1.1.2 255.255.255.252 for DLS2 and ALS2 respectively, however I can't ping from als2 to dls2 and vica versa.
Can someone shed some light on the issue.
Attached are the configs
Cheers
Carlton
03-27-2012 10:27 AM
Hi Carlton
I see from the config that eth 1/0 on both the switches are shutdown . can you bring up that interface and try?
-Vijay
03-27-2012 11:01 AM
Vijay,
Thanks for responding, but are we looking at the configs?
The attached show that eth 1/0 is up up?????
03-27-2012 11:01 AM
Vijay
Ethernet1/0 unassigned YES unset up up
03-27-2012 11:11 AM
Experts,
Here is the show cdp nei details:
ALS2#sh cdp nei detail
-------------------------
Device ID: DLS2
Entry address(es):
IP address: 200.1.1.1
Platform: Linu, Capabilities: Router Switch
Interface: Ethernet1/0, Port ID (outgoing port): Ethernet1/0
Holdtime : 147 sec
Version :
Cisco IOS Software, Linux Software (LINUXL2-UPK9-M), Experimental Version 12.2(20100802:165548) [mtimm-mtrosel2iol 102]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Mon 02-Aug-10 10:05 by mtim
advertisement version: 2
VTP Management Domain: 'switch'
Native VLAN: 200
Management address(es):
IP address: 200.1.1.1
ALS2#
DLS2#sh cdp nei deta
-------------------------
Device ID: DLS1
Entry address(es):
IP address: 100.1.1.1
Platform: Linu, Capabilities: Router Switch
Interface: Ethernet2/1, Port ID (outgoing port): Ethernet2/1
Holdtime : 145 sec
Version :
Cisco IOS Software, Linux Software (LINUXL2-UPK9-M), Experimental Version 12.2(20100802:165548) [mtimm-mtrosel2iol 102]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Mon 02-Aug-10 10:05 by mtim
advertisement version: 2
VTP Management Domain: 'switch'
Native VLAN: 1
Management address(es):
IP address: 100.1.1.1
-------------------------
Device ID: DLS1
Entry address(es):
IP address: 100.1.1.1
Platform: Linu, Capabilities: Router Switch
Interface: Ethernet2/0, Port ID (outgoing port): Ethernet2/0
Holdtime : 155 sec
Version :
Cisco IOS Software, Linux Software (LINUXL2-UPK9-M), Experimental Version 12.2(20100802:165548) [mtimm-mtrosel2iol 102]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Mon 02-Aug-10 10:05 by mtim
advertisement version: 2
VTP Management Domain: 'switch'
Management address(es):
IP address: 100.1.1.1
-------------------------
Device ID: ALS2
Entry address(es):
IP address: 200.1.1.2
Platform: Linu, Capabilities: Router Switch
Interface: Ethernet1/0, Port ID (outgoing port): Ethernet1/0
Holdtime : 169 sec
Version :
Cisco IOS Software, Linux Software (LINUXL2-UPK9-M), Experimental Version 12.2(20100802:165548) [mtimm-mtrosel2iol 102]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Mon 02-Aug-10 10:05 by mtim
advertisement version: 2
VTP Management Domain: 'switch'
Management address(es):
IP address: 200.1.1.2
DLS2#
Cheers
03-27-2012 11:12 AM
As you can see both routers can see each other via cdp....
Don't understand why als2 can't ping 200.1.1.2 and dls2 can't ping 200.1.1.1
03-27-2012 11:14 AM
oh..sorry my bad .. I was referring to eth 0/1 instead of eth 1/0.
I have labbed this up and it works for me
Can you check if your arp tables are proper ??
-Vijay
03-27-2012 11:18 AM
How do I check if the arp tables are proper?
03-27-2012 11:22 AM
To add what Vijay said...
clear arp or clear mac-address-table
Are you doing this on PT or GNS3?
Your ints look like the ints on howtonetwork.net....they use simulators. But I could be wrong about the ints.
When you ping what does the debug arp and debup ip icmp show?
03-27-2012 11:31 AM
Jimmy,
Very good deduction.
Its howtonetwork.net
03-27-2012 11:34 AM
Jimmy
DLS2#ping 200.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.1.1.2, timeout is 2 seconds:
*Mar 27 18:33:22.122: IP ARP: sent req src 200.1.1.1 aabb.cc00.c400,
dst 200.1.1.2 0000.0000.0000 Vlan200.
*Mar 27 18:33:24.122: IP ARP: sent req src 200.1.1.1 aabb.cc00.c400,
dst 200.1.1.2 0000.0000.0000 Vlan200.
*Mar 27 18:33:26.122: IP ARP: sent req src 200.1.1.1 aabb.cc00.c400,
dst 200.1.1.2 0000.0000.0000 Vlan200.
*Mar 27 18:33:28.122: IP ARP: sent req src 200.1.1.1 aabb.cc00.c400,
dst 200.1.1.2 0000.0000.0000 Vlan200.
*Mar 27 18:33:30.122: IP ARP: sent req src 200.1.1.1 aabb.cc00.c400,
dst 200.1.1.2 0000.0000.0000 Vlan200.
Success rate is 0 percent (0/5)
DLS2#
03-27-2012 11:52 AM
Hi guys
I cleared the arp and mac tables
03-27-2012 01:09 PM
Carlton,
I use them also....we use to have live equipment, then about 3-4 weeks ago they started running Linux emulators for their equipment....and when you have emulators (like Packet Tracer)...there have been times where I take the same exact config on PT (that wont work) and put it on live racks, works no issues.
I will take your configs tonight and see I have any luck....Vijay already proofed them (you did too probably 48 times , so they are probably correct.
03-27-2012 01:54 PM
Jimmy,
We're on the same page.
I have proofed them on GNS and the configs work fine. The problem is with the emulators:
For your information, I have sent the following to Customer Services and the Rack Team at HowToNetwork:
RackTeam,
I recently started a thread on the topic of Rack Limitations. You provided me with an comment which quite frankly is totally incorrect and quite ludicrous. Your statement was "Etherchannel is not supported on switches. Cisco imposed limitation (there are some)"
I think Paul would disagree with you as he wrote a whole lab on Etherchannels between switches, and to be honest you can't truly be a Cisco Engineer to ever say such a thing...
So when I asked what are the limitations of IOU (IOS on Unix) its best to just be straight with your members.
There are two limitations that I found after spending many many hours trying to figure out why I couldn't get the devices to work.
1st limitation; It is not possible to configure routed Etherchannels on the switches.
2nd limitation; it is not possible to pass traffic between switches that have their interfaces configured for static access rather than trunk mode.
These two limitations have cost me two days of troubleshooting. The reason it has taken me so long to figure this out is because this is networking 101 and I couldn't believe that it wouldn't work.
Some of the credit goes to the clever engineers at cisco forum for help figuring this out.
So, RackTeam, whether these limitations are fixed doesn't bother me but what would be most helpful if you would kindly same me and your members hours, and days of troubleshooting by letting us know what commands aren't supported.
I'm sure there will be new engineers following Paul's brilliant 101 lab book with the new rack solution only to find that they can't perform simple commands on the new rack.
Please help us......
Regards
03-27-2012 02:20 PM
The racks were awesome before, but due to space limitations/time slots, I think they went with the other emulators.
BTW....port security does not work either.
Thanks for the update!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide