Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
added 38 characters in body
Source Link
Zac67
  • 88.1k
  • 4
  • 73
  • 137

We have recently switched from HP Procurve series to HP Comware based switches. A configuration which has been working on Procurve doesn't seem to work on Comware. Here are the details:

The provider interface is Cisco based, network connectivity is delivered using a specific vlan (provider side), lets say vlan 600.

We have defined access ports on HP switches for internet access, using vlan 2. Port mode is access port. So I would expect the switch to discard the incoming vlan tag 600 and forward packets internally to all ports assigned to vlan 2. A 2nd access port on the switch with vlan 2 connects to the firewall wan port.

Configuration is as simple as it can get, first for HP Procurve, 2nd for Comware Switch:

Procurve: vlan 2 name "Wan" untagged 1-4 tagged 15,43-44 no ip address

vlan 2
   name "Wan"
   untagged 1-4
   tagged 15,43-44
   no ip address

Port 1 is connected to provider uplink, port 2 to Firewall WAN IF. WORKING!

Comware: interface Ten-GigabitEthernet1/0/3 port access vlan 2 interface Ten-GigabitEthernet1/0/4 port access vlan 2

interface Ten-GigabitEthernet1/0/3
 port access vlan 2
interface Ten-GigabitEthernet1/0/4
 port access vlan 2

Port 3 is connected to provider uplink, port 4 to Firewall WAN IF. NOT working.

So where is the difference between Procurve and Comware Switch? Is there anything I'm missing? I would expect to see port 3 & 4 communicate, as they are forced to the same vlan 2. But I do only see a MAC address entry on port 3 (Firewall MAC), no MAC from provider uplink on port 4.

We have recently switched from HP Procurve series to HP Comware based switches. A configuration which has been working on Procurve doesn't seem to work on Comware. Here are the details:

The provider interface is Cisco based, network connectivity is delivered using a specific vlan (provider side), lets say vlan 600.

We have defined access ports on HP switches for internet access, using vlan 2. Port mode is access port. So I would expect the switch to discard the incoming vlan tag 600 and forward packets internally to all ports assigned to vlan 2. A 2nd access port on the switch with vlan 2 connects to the firewall wan port.

Configuration is as simple as it can get, first for HP Procurve, 2nd for Comware Switch:

Procurve: vlan 2 name "Wan" untagged 1-4 tagged 15,43-44 no ip address

Port 1 is connected to provider uplink, port 2 to Firewall WAN IF. WORKING!

Comware: interface Ten-GigabitEthernet1/0/3 port access vlan 2 interface Ten-GigabitEthernet1/0/4 port access vlan 2

Port 3 is connected to provider uplink, port 4 to Firewall WAN IF. NOT working.

So where is the difference between Procurve and Comware Switch? Is there anything I'm missing? I would expect to see port 3 & 4 communicate, as they are forced to the same vlan 2. But I do only see a MAC address entry on port 3 (Firewall MAC), no MAC from provider uplink on port 4.

We have recently switched from HP Procurve series to HP Comware based switches. A configuration which has been working on Procurve doesn't seem to work on Comware. Here are the details:

The provider interface is Cisco based, network connectivity is delivered using a specific vlan (provider side), lets say vlan 600.

We have defined access ports on HP switches for internet access, using vlan 2. Port mode is access port. So I would expect the switch to discard the incoming vlan tag 600 and forward packets internally to all ports assigned to vlan 2. A 2nd access port on the switch with vlan 2 connects to the firewall wan port.

Configuration is as simple as it can get, first for HP Procurve, 2nd for Comware Switch:

Procurve:

vlan 2
   name "Wan"
   untagged 1-4
   tagged 15,43-44
   no ip address

Port 1 is connected to provider uplink, port 2 to Firewall WAN IF. WORKING!

Comware:

interface Ten-GigabitEthernet1/0/3
 port access vlan 2
interface Ten-GigabitEthernet1/0/4
 port access vlan 2

Port 3 is connected to provider uplink, port 4 to Firewall WAN IF. NOT working.

So where is the difference between Procurve and Comware Switch? Is there anything I'm missing? I would expect to see port 3 & 4 communicate, as they are forced to the same vlan 2. But I do only see a MAC address entry on port 3 (Firewall MAC), no MAC from provider uplink on port 4.

Source Link

Correct vlan/interface config for connection to upstream provider network

We have recently switched from HP Procurve series to HP Comware based switches. A configuration which has been working on Procurve doesn't seem to work on Comware. Here are the details:

The provider interface is Cisco based, network connectivity is delivered using a specific vlan (provider side), lets say vlan 600.

We have defined access ports on HP switches for internet access, using vlan 2. Port mode is access port. So I would expect the switch to discard the incoming vlan tag 600 and forward packets internally to all ports assigned to vlan 2. A 2nd access port on the switch with vlan 2 connects to the firewall wan port.

Configuration is as simple as it can get, first for HP Procurve, 2nd for Comware Switch:

Procurve: vlan 2 name "Wan" untagged 1-4 tagged 15,43-44 no ip address

Port 1 is connected to provider uplink, port 2 to Firewall WAN IF. WORKING!

Comware: interface Ten-GigabitEthernet1/0/3 port access vlan 2 interface Ten-GigabitEthernet1/0/4 port access vlan 2

Port 3 is connected to provider uplink, port 4 to Firewall WAN IF. NOT working.

So where is the difference between Procurve and Comware Switch? Is there anything I'm missing? I would expect to see port 3 & 4 communicate, as they are forced to the same vlan 2. But I do only see a MAC address entry on port 3 (Firewall MAC), no MAC from provider uplink on port 4.