Thanks, ill go and give it a try now...
Main Topics
Browse All TopicsOk first thing is im in a real hurry! these are important links! Please help!!!
I seem to be having issues with these configs, can somebody just tell me if i have gone wrong somewhere... I have the feeling its due to the VLAN configurations, im used to HP and they are a hell of a lot easier! :)
All I really want to do is Tag both vlans over the trunk link and have the ports as untagged on each switch. It works perfectly on the HP kit but it isnt as straight forward on the Cisco Gear.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Looking at your diagrams, I see a few problems (unless it wasnt noted)
You need to run a trunk link from the HP to the Cisco switches (either cascade or a link to each). if anything is critical on that HP switch, i advise you dont cascade as everything below the beak point will lose connectivity.
That said...
on each Cisco trunk port,
conf t
switchport
switchport trunk enc dot1q
switchport mode trunk
switch trunk allowed vlan x,y,z (only if you have more VLANS you dont need to allow)
on the access (non-tagged) port
conf t
sw
sw mode access
sw acc vlan x (or Y or Z)
spanning-tree portfast (only if you are sure they will nto be connected to another switch!!!!!) ~ removes the spanning tree process from the port.
make sure the Trunk port on the HP is configured the same way (Dot1q etc).
You will be ready to go from that point.
>You need to run a trunk link from the HP to the Cisco switches
If there are only two VLAN's and you're willing to run two separate links, there's no "need" to run a trunk.
>switchport trunk enc dot1q
This is an invalid command on 2950 switches as 802.1q is the only encapsulation they support.
>switch trunk allowed vlan x,y,z (only if you have more VLANS you dont need to allow)
Not required. Optional... but recommended.
>removes the spanning tree process from the port.
Portfast does not remove spanning tree from a port. It simply bypasses the Listening/Learning stage.
I was also under the impression that because I was running 2 separate links from the HP that I would not need to use Tagging or a trunk link...
and I take it the more i restrict the allowed VLAN;s the quicker it would be?
I have just been out to each switch and put the new commands up, I will post the new configs up now...
If you are not doing trunks, you will need a separate link for each VLAN. So you can have as many VLANs as you want. But without additional access links or trunks between the switches, traffic from that VLAN will never leave the switch.
It's not unusual for the first ping packet to fail. I can timeout while ARP entries are created.
Im testing by logging into the top cisco switch and pinging the gateway (192.168.5.1 - HP6108 port 5)
the cisco switch has 192.168.5.252 255.255.255.0 assigned to the VLAN5 Interface.
it drops the first packet and then pings <1ms forever after that... bloody weird!
the problem is, my tills that are sitting on that VLAN 5 are having problems with the chip and pin failing on the first few attempts... when pinging off the till the first couple of pings fail and then it seems alright after that.
If i put a static arp entry in, it seems to work fine...
from the 6108 i get 10 succesful pings to each switch... but from switch to switch it drops out!
Are the tills communicating to another VLAN5 host or to something on VLAN1?
As a side note, configure the top switch in the diagram (the one that has the HP plugged into it) as the STP root:
conf t
spanning-tree vlan 1-4094 root primary
Then connect the bottom switch (Gig0/2) in the diagram to the top switch (Gig0/2) in the diagram. This will provide some redundancy.
C:\Documents and Settings\epos>ping 192.168.5.51 -n 10
Pinging 192.168.5.51 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.5.51: bytes=32 time<1ms TTL=128
Reply from 192.168.5.51: bytes=32 time<1ms TTL=128
Reply from 192.168.5.51: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.5.51:
Packets: Sent = 10, Received = 3, Lost = 7 (70% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This was on a till that sits in the same VLAN and on the same Switch as the server...
C:\Documents and Settings\groves>ping 192.168.5.51 -n 10
Pinging 192.168.5.51 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.5.51: bytes=32 time=285ms TTL=128
Reply from 192.168.5.51: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.5.51:
Packets: Sent = 10, Received = 2, Lost = 8 (80% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 285ms, Average = 142ms
Im also going to attach a new visio drawing which shows the bits you might need!
So I was just pinging from EPOS31 to EPOS Server. All on Cisco3.
Thanks
right well I feel stupid now...
so I went to each switch and cleared the arp tables and then it turns out they all had a arp entry to the same little router, so i logged onto the router, and somebody had configured it as a bridge.
So all of the broadcast traffic was being being pushed through this little bridge when the other end of it was disconnected!
Needless to say thanks for everybodies hard work on this because without it I never would have found the culprit!
Thanks
Martin
Business Accounts
Answer for Membership
by: JFrederick29Posted on 2009-02-23 at 06:28:33ID: 23711428
First off, don't use VTP.
conf t
vtp mode transparent <--do this on all 3 cisco switches
Then create the VLAN's on each switch:
conf t
vlan 6
exit
Make sure you "no shut" the interfaces.
If that doesn't fix it, post a "show vlan" and a "show int trunk" from each Cisco switch.