Latency question - warning long 2

[unclerico]

Hey all, I am studying for my CCNA right now. Since this is a lab area and not a production network I chose to stick my issue here as opposed to the Router/Switch forums.

I currenly have the following equipment:
3 switches
- C2950C-24 (c2950-i6k2l2q4-mz.121-22.EA11.bin)
- 2 x C2924-XL (c2900xl-c3h2s-mz.120-5.WC17.bin)

3 routers
- 3640 (c3640-jk9o3s-mz.124-7a.bin)
- 2620XM (c2600-ipbasek9-mz.124-19.bin)
- 2610XM (c2600-advsecurityk9-mz.124-15.T4.bin)

Here's my issue
Using the 3640, 2950, one 2924, and two PC's I have configured a Router on a Stick. My setup is like so:
3640
| (trunk f0/0 to f0/24)
2950 - PC1 on f0/10
| (trunk f0/1 to f0/1)
2924 - PC2 on f0/21

When I have f0/21 configured as a member of VLAN 10 I am experiencing severe latency when pinging any other device on the network from PC2.

C:\>ping 172.20.20.5

Pinging 172.20.20.5 with 32 bytes of data:

Reply from 172.20.20.5: bytes=32 time=642ms TTL=127
Reply from 172.20.20.5: bytes=32 time=141ms TTL=127
Reply from 172.20.20.5: bytes=32 time=249ms TTL=127
Reply from 172.20.20.5: bytes=32 time=10ms TTL=127

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

f0/10 is configured as a member of VLAN 20 and response times are <1ms when pinging from PC1. The wierd thing is if I configure f0/21 as a member of VLAN 20 ping times go to <1ms. Here are the config's from the devices
3640

Current configuration : 1662 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3640
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
!
!
ip cef
!
!
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/0.1
 encapsulation dot1Q 1
 ip address 192.168.10.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.10
 encapsulation dot1Q 10
 ip address 172.20.10.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.20
 encapsulation dot1Q 20
 ip address 172.20.20.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.920
 encapsulation dot1Q 920 native
 no snmp trap link-status
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial1/0
 no ip address
 shutdown
 no dce-terminal-timing-enable
 no fair-queue
!
interface Serial1/1
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/2
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/3
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/4
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/5
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/6
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/7
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
ip http server
no ip http secure-server
!
!
control-plane
!
!
line con 0
 logging synchronous
line aux 0
line vty 0 4
!
!

2950

Current configuration : 1615 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname SW2950
!
!
ip subnet-zero
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
!
!
!
!
interface FastEthernet0/1
 description SW2950 to SW2924 trunk
 switchport trunk native vlan 910
 switchport trunk allowed vlan 1,10,20
 switchport mode trunk
 switchport nonegotiate
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
 switchport access vlan 20
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
 description SW2950 to R3640 trunk
 switchport trunk native vlan 920
 switchport trunk allowed vlan 1,10,20
 switchport mode trunk
 switchport nonegotiate
!
interface FastEthernet0/25
!
interface FastEthernet0/26
!
interface Vlan1
 ip address 192.168.10.29 255.255.255.0
 no ip route-cache
!
ip http server
!
line con 0
 logging synchronous
line vty 0 4
 login
line vty 5 15
 login
!
!

2924

version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname SW2924
!
!
ip subnet-zero
!
!
!
interface FastEthernet0/1
 description SW2924 to SW2950 trunk
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 910
 switchport trunk allowed vlan 1,10,20,1002-1005
 switchport mode trunk
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
 switchport access vlan 10
 spanning-tree portfast
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface VLAN1
 ip address 192.168.10.30 255.255.255.0
 no ip directed-broadcast
 no ip route-cache
!
!
line con 0
 logging synchronous
 transport input none
 stopbits 1
line vty 0 4
 login
line vty 5 15
 login
!

Like I said above, this is only a lab environment so it's not a big deal, but I'm still wondering nevertheless. Thanks.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[lerdalt]

Just giving a quick glance, I question why you set vlan 920 as your native and not vlan1. I don't think it's related, but just seemed a little odd to me.

I would try moving your workstations both into the same switch on separate vlans, and make certain it's not an issue with your trunk interface, or even cabling.

Also, double check your vlan database, make certain both switches are seeing the same vlans correctly.

Another test..on the router, ping one interface to another. Verify your routing.

 

[unclerico]

thanks for the reply lerdalt...The native VLAN configuration was suggested by ADB100 and verified as best practice by the following document:

http://www.cisco.com/en/US/products...cts_white_paper09186a008013159f.shtml#wp39054

As a matter of fact, the proper configuration that should always be used is to clear the native VLAN from all 802.1Q trunks (alternatively, setting them to 802.1q-all-tagged mode achieves the exact same result). In cases where the native VLAN cannot be cleared, then always pick an unused VLAN as native VLAN of all the trunks; don't use this VLAN for any other purpose.

As for layer 1/2 issues, I have tried multiple cables, I've tried plugging both PC's directly into the same switch, and making ports on both switches members of the same VLAN. The only thing that made a difference was making ports on each switch members of VLAN 20, once I did that then the latency issue went away. I've checked the interface stats all the way around and there no errors. Pinging from the router to the PC on VLAN 10 results in severe latency also. The VLAN databases are consistent.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[lerdalt]

Did you try an extended ping from the router sourcing from both the local vlan the workstations are on as well as the other?

 

[maczen]

You seem to be missing a "switchport mode access" on 0/21 as well as a no-negotiate.. Could be that you have some attempted DTP negotiation occurring when you cross VLANs.. Not sure.. I would try those first...

Is there a reason that you have BPDUGuard turned off on that port?? If it is shutting the port down then that tells us that there is a loop somewhere...

I do recall reading somewhere that you can change the native vlan but it's not adviseable to use VLAN1 for anything else if you do... Will try to locate that... Can not recall why.. Sorry..

 

[burtsbees]

Uh oh, look out...maczen's learning fast!
Lerdalt---many people I have seen change the management from vlan 1 for security reasons. I have also seen people use multiple switches when they are not necessarily needed (4 nodes, 2 vlans) to prevent vlan hopping attacks.

Burt

 

[maczen]

LoL.. Thanks Burt.. Let's hope fast enough to pass this CCNA ICND2 on the first attempt.. LoL...

UncleRico: Please let us know what this was when you find it.. Peeked my curiosity!! LoL

 

[unclerico]

absolutely...I actually redid the setup last night but changed it around a bit (including IP Addressing). I set it up to use the 2924 as the "core" switch as opposed to the 2950 like I had before and now latency is a problem all the way around. The topology looks like this:

3640
|(trunk to 2924xl)
2924XL - PC1
|(trunk to 2950)
2950 - PC2

From PC2 I pinged PC1 and here are the response times:

C:\>ping 192.168.60.11

Pinging 192.168.60.11 with 32 bytes of data:

Reply from 192.168.60.11: bytes=32 time=75ms TTL=127
Reply from 192.168.60.11: bytes=32 time=98ms TTL=127
Reply from 192.168.60.11: bytes=32 time=92ms TTL=127
Reply from 192.168.60.11: bytes=32 time=116ms TTL=127

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

From PC1 I pinged PC2:

C:\>ping 192.168.50.12

Pinging 192.168.50.12 with 32 bytes of data:

Reply from 192.168.50.12: bytes=32 time=138ms TTL=127
Reply from 192.168.50.12: bytes=32 time=127ms TTL=127
Reply from 192.168.50.12: bytes=32 time=183ms TTL=127
Reply from 192.168.50.12: bytes=32 time=2ms TTL=127

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

The 2924 has got to be the bottleneck. What say you? If you want me to post my new configs I will.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[burtsbees]

I say try both pc's in the 2924---fa0/1 the trunk, fa0/2 as pc1, vlan 10, and fa0/3 pc2 vlan 20. Post the results of pings from pc1 to pc2, and pc2 to pc1---only one switch and one router. Then make both pc's members of vlan 10, post the ping results. The make them members of vlan 20, post the results. Then do the exact same with the 2950--leave the 2924 out this time. Post results of pc2 to pc1 and pc1 to pc1.
When all is said and done, you will have posted results for 6 pings in each switch, for a total of 12 pings. This will really help narrow it down. After that (ha ha ha), try both switches, but make vlan 10 in the 2924 and vlan 20 int the 2950, with the 2924 trunked to the router.

Burt

 

[maczen]

Please post the configs as well..

 

[burtsbees]

You are using a straight-thru cable between the router and switch, and a crossover between the 2 switches...right?
If you use a straight thru between the cables, you will have created an uplink, instead of a trunk. This will confuse the poor switch, and after a little time, it will burst into flames, which will mark the beginning of the Apocalypse. You don't want that on your conscience...

Burt

 

[unclerico]

Ok bert, here are all of the ping tests

2924 -> 3640
VLAN10 and VLAN20
From PC1 to PC2:

C:\>ping 192.168.20.11

Pinging 192.168.20.11 with 32 bytes of data:

Reply from 192.168.20.11: bytes=32 time=9ms TTL=127
Reply from 192.168.20.11: bytes=32 time=39ms TTL=127
Reply from 192.168.20.11: bytes=32 time=43ms TTL=127
Reply from 192.168.20.11: bytes=32 time=87ms TTL=127

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

From PC2 to PC1:

C:\>ping 192.168.10.11

Pinging 192.168.10.11 with 32 bytes of data:

Reply from 192.168.10.11: bytes=32 time=55ms TTL=127
Reply from 192.168.10.11: bytes=32 time=31ms TTL=127
Reply from 192.168.10.11: bytes=32 time=77ms TTL=127
Reply from 192.168.10.11: bytes=32 time=92ms TTL=127

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

VLAN10 and VLAN10
From PC1 to PC2:

C:\>ping 192.168.10.12

Pinging 192.168.10.12 with 32 bytes of data:

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

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

From PC2 to PC1:

C:\>ping 192.168.10.11

Pinging 192.168.10.11 with 32 bytes of data:

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

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

VLAN 20 and VLAN 20
From PC1 to PC2:

C:\>ping 192.168.20.13

Pinging 192.168.20.13 with 32 bytes of data:

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

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

From PC2 to PC1:

C:\>ping 192.168.20.12

Pinging 192.168.20.12 with 32 bytes of data:

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

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

2950 -> 3540
VLAN 10 and VLAN 20
From PC1 to PC2:

C:\>ping 192.168.20.13

Pinging 192.168.20.13 with 32 bytes of data:

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

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

From PC2 to PC1:

C:\>ping 192.168.10.13

Pinging 192.168.10.13 with 32 bytes of data:

Reply from 192.168.10.13: bytes=32 time=1ms TTL=127
Reply from 192.168.10.13: bytes=32 time=1ms TTL=127
Reply from 192.168.10.13: bytes=32 time=1ms TTL=127
Reply from 192.168.10.13: bytes=32 time=1ms TTL=127

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

VLAN 10 and VLAN 10
From PC1 to PC2:

C:\>ping 192.168.10.12

Pinging 192.168.10.12 with 32 bytes of data:

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

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

From PC2 to PC1:

C:\>ping 192.168.10.13

Pinging 192.168.10.13 with 32 bytes of data:

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

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

VLAN 20 and VLAN 20
From PC1 to PC2:

C:\>ping 192.168.20.14

Pinging 192.168.20.14 with 32 bytes of data:

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

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

From PC2 to PC1:

C:\>ping 192.168.20.12

Pinging 192.168.20.12 with 32 bytes of data:

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

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

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[burtsbees]

OK---you are correct in assuming that the 2924 is indeed a bottleneck. Did you plug the pc's into ports fa0/1 and 0/2? And you only had one switch at a time plugged into the router during these tests? I'd say that there was something wrong with that 2924...I have VLAN 1, 10 and 20 in a 2924...vlan 1 is the management, 10 is my computer, and 20 is my printer...from pc to printer...

C:\Documents and Settings\Administrator>ping -n 10 10.67.67.3
Pinging 10.67.67.3 with 32 bytes of data:

Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254
Reply from 10.67.67.3: bytes=32 time=2ms TTL=254

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

I wonder why your time to live value is 1/2 of what mine is...

Try an extended ping from the router...no sweep ranges, but set the df bit (answer yes to extended commands). Datagram size, make 500, repeat count make 25.

Burt

 

[unclerico]

Wierd stuff I'm tellin' ya...Yes, there was only one switch plugged in at a time. I plugged f0/10 into PC1, f0/20 into PC2, and f0/24 as the trunk to the 3640. As for the TTL values, I'm not 100% sure why they are different, but for some reason they fluctuate between 127, 128, and 254 all on their own.

After I posted my ping results I recabled my lab as it was originally with the exception of now the 2950 is trunking to the 2924 via a two port etherchannel. The results of the recabling took my ping times to 2ms and below all the way around.

3640
| (trunk from f0/0 to f0/24 on 2950)
2950 - PC1 (VLAN 10)
| (etherchannel trunk from f0/1,f0/2 to f0/1,f0/2 on 2924)
2924 - PC2 (VLAN 20)

Here are the new configs. They should be essentially the same as in my original post with the exception of the etherchannel config and the IP addresses.

3640

Current configuration : 2008 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3640
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
!
!
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp excluded-address 192.168.20.1 192.168.20.10
ip dhcp excluded-address 192.168.10.254
ip dhcp excluded-address 192.168.20.254
!
ip dhcp pool PC1
   network 192.168.10.0 255.255.255.0
   default-router 192.168.10.254 
!
ip dhcp pool PC2
   network 192.168.20.0 255.255.255.0
   default-router 192.168.20.254 
!
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/0.10
 encapsulation dot1Q 10
 ip address 192.168.10.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.20
 encapsulation dot1Q 20
 ip address 192.168.20.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.30
 description Management
 encapsulation dot1Q 30
 ip address 192.168.30.254 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.900
 encapsulation dot1Q 900 native
 no snmp trap link-status
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial1/0
 no ip address
 shutdown
!
interface Serial1/1
 no ip address
 shutdown
!
interface Serial1/2
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/3
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/4
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/5
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/6
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
interface Serial1/7
 no ip address
 shutdown
 no dce-terminal-timing-enable
!
ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
line con 0
 logging synchronous
line aux 0
line vty 0 4

2950

Current configuration : 2117 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname SW2950
!
!
ip subnet-zero
!
ip ssh time-out 120
ip ssh authentication-retries 3
vtp interface VLAN30 only
!
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 10,20,30 priority 24576
!
!
!
!
interface Port-channel1
 description Trunk to SW2924
 switchport trunk native vlan 900
 switchport trunk allowed vlan 10,20,30
 switchport mode trunk
 switchport nonegotiate
 flowcontrol send off
!
interface FastEthernet0/1
 switchport trunk native vlan 900
 switchport trunk allowed vlan 10,20,30
 switchport mode trunk
 switchport nonegotiate
 channel-group 1 mode on
!
interface FastEthernet0/2
 switchport trunk native vlan 900
 switchport trunk allowed vlan 10,20,30
 switchport mode trunk
 switchport nonegotiate
 channel-group 1 mode on
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
 switchport access vlan 10
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
 description Trunk to 3640
 switchport trunk native vlan 900
 switchport trunk allowed vlan 10,20,30
 switchport mode trunk
 switchport nonegotiate
!
interface FastEthernet0/25
!
interface FastEthernet0/26
!
interface Vlan1
 no ip address
 no ip route-cache
 shutdown
!
interface Vlan30
 ip address 192.168.30.1 255.255.255.0
 no ip route-cache
!
ip http server
!
line con 0
 logging synchronous
line vty 0 4
 login
line vty 5 15
 login

2924

Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname SW2924
!
!
ip subnet-zero
!
!
!
interface FastEthernet0/1
 port group 1 distribution destination
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 900
 switchport trunk allowed vlan 1,10,20,30,1002-1005
 switchport mode trunk
!
interface FastEthernet0/2
 port group 1 distribution destination
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 900
 switchport trunk allowed vlan 1,10,20,30,1002-1005
 switchport mode trunk
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
 switchport access vlan 20
 spanning-tree portfast
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface VLAN1
 no ip address
 no ip directed-broadcast
 no ip route-cache
 shutdown
!
interface VLAN30
 ip address 192.168.30.2 255.255.255.0
 no ip directed-broadcast
 no ip route-cache
!
!
line con 0
 logging synchronous
 transport input none
 stopbits 1
line vty 0 4
 login
line vty 5 15
 login

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[burtsbees]

Well, I wanted you to put the pc's on fa0/2 and fa0/3, with the trunk to fa0/1---this would rule out those individual ports. Anyway, looks like you have a solution. By the way, you don't need stp with 2 switches---that would slow things down (not ping times).

Burt

 

[unclerico]

Sorry bout that, I was trying to match interfaces to the VLAN that they would be in. Regarding STP, as I said I'm practicing for my CCNA so I want to practice the commands as often as possible and also make sure I understand the operation 100% so that is why the config is in there. Thanks for spending the time on this. Until next time...

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[burtsbees]

Oh, that's right---CCNA. Sorry, man. I myself would still be curious as to whether or not the individual ports are causing the problem. If you recently got the 2924 off of Ebay, then perhaps you can report that it's not a very good switch, unless you picked it up for cheap. Good luck with the CCNA!

Burt