+ Post New Thread
Results 1 to 9 of 9
Wired Networks Thread, VLAN Issue in Technical; Evening... now bear with me while I try and explain the problem! We have 2 HP ProCurve 2910al-48G switches (Sender ...
  1. #1
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    VLAN Issue

    Evening... now bear with me while I try and explain the problem!

    We have 2 HP ProCurve 2910al-48G switches (Sender for ease), connected via CX4 cable at the back. We are trying to connect the Sender switches to 2x HP ProCurve 2910al-24G switches (receiver) via a fibre cable.

    The fibre cable from the sender terminates in the comms rack.
    The receiver is connected to a fibre connection that terminates in the same comms rack.
    The 2 connections are connected with an ST to ST fibre patch cable.

    The idea is that we have one part of a SAN connected to the sender switches and one SAN on the receiver switches and create an iSCSI network over the fibre.

    I have created a vlan on the sender switches, vlan 10 and have ports 1-30 & 48 untagged. I have A1 (CX4) tagged and jumbo frames switched on. Port 48 has the SFP connected. This vlan is replicated to the second of the sender switches.

    I have also created a vlan on the receiver switches, again vlan 10 and have ports 1-22 & 24 untagged. I have A1 (CX4) tagged and jumbo frames switched on. Port 24 has the SFP connected. This vlan is also replicated to the second switch.

    It looks like the vlan is configured correctly but when we try and ping the SAN at the receiver end we get no reply.

    We have broken into the network at the comms cab with a PowerConnect 2824 and we can ping the SANs at both the sender and receiver ends but with the ST Patch connecting the 2 connections nothing seems to get through. The ST Patch cable is brand new (62.5/125). I have also tried another brand new patch cable (again 62.5/125) and nothing seems to be talking.

    Can anyone think of anything else we are missing here?

  2. #2

    Join Date
    Apr 2012
    Location
    Leeds
    Posts
    343
    Thank Post
    3
    Thanked 72 Times in 57 Posts
    Rep Power
    38
    Ummm this may seem way too simple but are both devices at each end in the same subnet mask?

    Dave

  3. #3
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi Dave

    Nope not a simple question at all! We have an ip of 192.168.130.230:255.255.255.0 on the sender and 192.168.130.231:255.255.255.0 on the receiver.
    I have attached the config of the switches below:

    Running configuration - Sender Switches

    ; J9147A Configuration Editor; Created on release #W.14.70

    hostname "ProCurve 2910al-48G Switch"
    module 1 type J9147A
    module 2 type J9165A
    no stack
    ip default-gateway 10.107.71.254
    vlan 1
    name "DEFAULT_VLAN"
    untagged 47,A1
    ip address 10.107.64.88 255.255.248.0
    no untagged 1-46,48
    exit
    vlan 10
    name "iSCSI"
    untagged 1-30,48
    ip address 192.168.130.231 255.255.255.0
    tagged A1
    jumbo
    exit
    vlan 50
    name "vMotion"
    untagged 31-46
    tagged A1
    no ip address
    exit
    snmp-server community "public" unrestricted
    spanning-tree
    no autorun
    password manager


    Running configuration - Receiver Switches

    ; J9145A Configuration Editor; Created on release #W.14.49

    hostname "SVS HP2910-24 iSCSI 2"
    module 1 type J9145A
    module 2 type J9165A
    ip default-gateway 10.107.71.254
    vlan 1
    name "DEFAULT_VLAN"
    untagged 23,A1
    ip address 10.107.64.86 255.255.248.0
    no untagged 1-22,24
    exit
    vlan 10
    name "iSCSI"
    untagged 1-22,24
    ip address 192.168.130.230 255.255.255.0
    tagged A1
    jumbo
    exit
    snmp-server community "public" unrestricted
    snmp-server contact "Wayne Tuckwell" location "Science Prep"
    spanning-tree
    no autorun
    password manager


    Wayne

  4. #4

    twin--turbo's Avatar
    Join Date
    Jun 2012
    Location
    Carlisle
    Posts
    2,334
    Thank Post
    1
    Thanked 381 Times in 340 Posts
    Rep Power
    151
    what device is "10.107.71.254" and does it have knowledge of the vlan10 and it's ip range.

    You should not need IP's on anything other than your router with the exception of the management address for the switch although I doubt it is the cause of the probelm.

    As always a diagram paints a thousand words.

    Also is Spanning treee enabled and is the bridge priority correctly set?

    Rob

  5. #5
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi Rob

    10.107.71.254 is the default gateway of the entire network. Spanning Tree is enabled on all switches and Jumbo Frames is on all ports on the vlans. Bridge Priority? I don't know what this is?

    Wayne

  6. #6
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    --UPDATE--

    By removing the management cable from Port 47 on the sender, we now have the switches talking????

    Considering Port 47 is in the default Vlan why would this be the case? We have also tried with the port connected and spanning tree off on both the sender and receiver and this also works?

    Confused now thought that vlans were meant to be apart?

  7. #7

    twin--turbo's Avatar
    Join Date
    Jun 2012
    Location
    Carlisle
    Posts
    2,334
    Thank Post
    1
    Thanked 381 Times in 340 Posts
    Rep Power
    151
    As I say a diagram would be very helpful, I am also not familiar with the term "Sendre/Reciver" Switch?

    Rob

  8. #8
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Sorry Rob, Sender is server room a, receiver is server room b.

    Looks like a leaky vlan and spanning tree causing the issue.

  9. #9
    cmpwat's Avatar
    Join Date
    Dec 2011
    Location
    Gloucester
    Posts
    42
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Issue has been resolved



SHARE:
+ Post New Thread

Similar Threads

  1. 1 Vlan out of 8 having issues
    By mrbios in forum Wired Networks
    Replies: 5
    Last Post: 20th October 2011, 03:26 PM
  2. Intresting issue - WDS / Multicasting /PXE and Vlans
    By craigg in forum Enterprise Software
    Replies: 0
    Last Post: 17th August 2011, 09:23 AM
  3. vlan design issue on HP procurve 5406zl
    By puliramesh in forum Wireless Networks
    Replies: 4
    Last Post: 10th August 2010, 07:23 AM
  4. 3Com VLAN Issues
    By boogster in forum Hardware
    Replies: 2
    Last Post: 8th February 2010, 08:22 AM
  5. Vlan issue on Procurve
    By sassine in forum Wireless Networks
    Replies: 7
    Last Post: 16th November 2009, 02:39 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •