Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 29 subscribers
  • Views 1130 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VLANs and HP ProCurve 2810-48g running N.11.78

SyPhEn

I am struggling with getting my interfaces fully functional. I am currently configured on the Sophos as follows:

Port 1:

VLAN 10 - 10.10.10.1

DHCP Pool for that subnet

VLAN 100 - 172.16.20.1

No DHCP (MGMT)

Port 3:

VLAN 20 - 10.10.20.1

DHCP Pool for that subnet

VLAN 30 - 10.10.30.1

DHCP Pool for that subnet

Port 1 is connected to Port 14 of my switch and Port 3 is connected to Port 16 on the same switch. The following is the current configuration for those VLANs on the ProCurve:

; J9022A Configuration Editor; Created on release #N.11.78

vlan 10
name "HOMENET"
untagged 25-30
no ip address
tagged 14
exit
vlan 20
name "VLAN20"
untagged 31-33
tagged 16
exit
vlan 30
name "VLAN30"
untagged 34-36
tagged 16
exit
vlan 100
name "MGMT"
untagged 21-24
tagged 14
exit

I currently do not have it configured using the trunk command, but if my understanding is correct, tagged traffic only passes on a trunk. However, in both this configuration and when configuring with the trunk command:

trunk 14 trk1
trunk 16 trk2

I have been unsuccessful in bringing up the connections. My Sophos VLAN Interfaces still read N/A under status. If there is anyone more familiar with this switch and OS the has any input, it would be greatly appreciated. 



This thread was automatically locked due to age.
  • 0

    Hi,

    which version go XG software are you running?

    Ian

    XG115W - v19.5.1 mr-1 - Home

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Hello again rfcat_vk! I am the one who built a homebrew Sophos. Specs below. BTW, after I successfully installed the OS with the intel server nic, I was able to add back the D-Link, giving me a 4th interface.

    OS: SW-18.5.2_MR-2-380
    Mainboard: ASUS H81M-C
    Processor: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz 3.20GHz
    Onboard: Realtek GB Ethernet
    RAM: 8 GB
    Storage: 160 GB SSD
    Added Adapter 1: Intel EXPI9402PTBLK 10/100/1000Mbps PCI-Express Two Gigabit Copper Server Connections
    Added Adapter 2: D-Link DGE-530T V.D2

  • 0 in reply to SyPhEn

    Hi,

    why I asked the version is that earlier versions eg v17 did not support L2 type VLANs while v18 does.

    Ian

    Update:- Reading the handbook, trunks would not be suitable for your setup, they are for groups of connections between similar switches.

    I was not able to determine whether the switches L2 or L3, suspect L3 which means you need to enable the L1 configuration on the XG port. Though HP building a L3 switch would be a bit unusual.

    XG115W - v19.5.1 mr-1 - Home

    If a post solves your question please use the 'Verify Answer' button.

  • +1

    There is a good overview about HP and VLAN naming conventions at this site: https://www.petenetlive.com/KB/Article/0000741

    Good luck!

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • +1

    Hi,

    HP Procure 2xxx switches use a different view on vlan and trunks.

    Trunks on a procurve are basicly LAG (Link Aggregation groups) interfaces and have nothing to do with vlan's. 

    Cisco vlan ports have three configuration modes, trunks, access and hybrid ports. Basicly procurve's have only hybrid ports.

    Hybrid ports have one access vlan (untagged) and can have multiple tagged ports at the same time.

    The XG acts the same: Use one interface and make that untagged on the switch. Then add vlan interfaces on top of the physical one, and ad teh tagges to the interface in the switch.

    When on the switch cli use command menu -> 2, Configure switch, and i beleive 8 Vlan menu to configure those ports. It's easier.

    A lot of info on vlan's is available on procurves from HP since it has been in use for a long time, they use a different approach to vlans and trunking than lets say Cisco.

    Al is compatible but just the way to configure is different. 

    So in HP trunk is a different thing than in Cisco and have nothing to do with each other.

    Succes.

       

    Bart van der Horst

    Sophos XG v18(.5) / v19 Certified Architect
    https://www.bpaz.nl

  • 0 in reply to rfcat_vk

    This is strictly a L2 switch, but I suspected that all trunks were seen as LAG when I read through the documentation on HP's site.When I connect to my Ubiquiti 8 Port EdgeSwitch, I also have issues with passing VLANs.

  • 0 in reply to Bart van der Horst

    Because I came from a Cisco background and was primarily routing, I was mixing up tagged and untagged traffic. I was successful in getting my Sophos implemented by tagging my vlans on each interface and leaving my static vlan untagged. After that it was just a matter of untagging the ports on those vlans and everything was beautiful! I believe I made the same mistake when attempting to uplink to my Ubiquiti Edgeswitch, plan to test that after I get home tonight. Thank you all for the input, it was valuable!

Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?