Web and Unmanaged
cancel
Showing results for 
Search instead for 
Did you mean: 

HP VLAN tagging on SFP

ag-wetter
Visitor

HP VLAN tagging on SFP

I am experiencing a few ssues with  our 1920-24G and 1910 switches. First the VLAN tagging is not working on the SFP port. Secondly when I want to save a configuration the system never comes back to say save succesfully this works perfectly on other switches though.  This however isn't critical as it seems to save it although it never confirms that it does. I did try different browsers as well.

The VLAN tagging however is an issue and it was tested on the Gigabit port 24 as an uplink and is working perfectly fine. As soon as we use the GBICS module with exact same vlan tagging on it, the end devices don't get an IP assigned. The GBICs modules used are both HP compatible and branded (J4858D and J4858C) Also the link is up between the 2 switches when using the SFP ports and data flow as expected except for tagging of the VLANs. When we switch to the copper on port 24 the Tagging works again. Both switches have been upgraded to latest firmware available.  I have  changed the link type from trunk to hybrid with no difference at all. Currently it is set as a trunk.

Below is the interface status of the SFP port 25 with Gigabit interface 24 Disabled

GigabitEthernet1/0/25 current state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: d894-0353-13f9
Description: GigabitEthernet1/0/25 Interface
Loopback is not set
Media type is optical fiber, Port hardware type is 1000_BASE_SX_SFP
1000Mbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
The Maximum Frame Length is 9600
Broadcast MAX-ratio: 100%
Unicast MAX-ratio: 100%
Multicast MAX-ratio: 100%
PVID: 1
Port link-type: trunk
VLAN passing : 1(default vlan), 10, 20, 100
VLAN permitted: 1(default vlan), 10, 20, 100
Trunk port encapsulation: IEEE 802.1q
Port priority: 0
Last clearing of counters: Never
Peak value of input: 1056 bytes/sec, at 2000-04-26 12:34:02
Peak value of output: 2358 bytes/sec, at 2000-04-26 12:34:02
Last 300 seconds input: 15 packets/sec 1056 bytes/sec 0%
Last 300 seconds output: 15 packets/sec 2358 bytes/sec 0%
Input (total): 4544 packets, 311837 bytes
309 unicasts, 4165 broadcasts, 70 multicasts, 0 pauses
Input (normal): 4544 packets, 311837 bytes
309 unicasts, 4165 broadcasts, 70 multicasts, 0 pauses
Input: 0 input errors, 0 runts, - giants, - throttles
0 CRC, - frame, 0 overruns, 0 aborts
- ignored, - parity errors
Output (total): 4596 packets, 696046 bytes
440 unicasts, 4134 broadcasts, 22 multicasts, 0 pauses
Output (normal): 4596 packets, 696046 bytes
440 unicasts, 4134 broadcasts, 22 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, - late collisions
- lost carrier, - no carrier

Below is the status of Interface Gigabit 24 with SFP 25 disabled

GigabitEthernet1/0/24 current state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: d894-0353-13f8
Description: GigabitEthernet1/0/24 Interface
Loopback is not set
Media type is twisted pair, Port hardware type is 1000_BASE_T
1000Mbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
The Maximum Frame Length is 9600
Broadcast MAX-ratio: 100%
Unicast MAX-ratio: 100%
Multicast MAX-ratio: 100%
PVID: 1
Mdi type: auto
Port link-type: trunk
VLAN passing : 1(default vlan), 10, 20, 100
VLAN permitted: 1(default vlan), 10, 20, 100
Trunk port encapsulation: IEEE 802.1q
Port priority: 0
Last clearing of counters: Never
Peak value of input: 24948 bytes/sec, at 2000-04-26 12:17:31
Peak value of output: 92209 bytes/sec, at 2000-04-26 12:06:00
Last 300 seconds input: 126 packets/sec 20427 bytes/sec 0%
Last 300 seconds output: 130 packets/sec 31553 bytes/sec 0%
Input (total): 65084 packets, 16473380 bytes
26518 unicasts, 5348 broadcasts, 33218 multicasts, 0 pauses
Input (normal): 65084 packets, 16473380 bytes
26518 unicasts, 5348 broadcasts, 33218 multicasts, 0 pauses
Input: 0 input errors, 0 runts, - giants, - throttles
0 CRC, - frame, 0 overruns, 0 aborts
- ignored, - parity errors
Output (total): 87064 packets, 58310632 bytes
50866 unicasts, 5307 broadcasts, 30891 multicasts, 0 pauses
Output (normal): 87064 packets, 58310632 bytes
50866 unicasts, 5307 broadcasts, 30891 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, - late collisions
- lost carrier, - no carrier

3 REPLIES
parnassus
Honored Contributor

Re: HP VLAN tagging on SFP

Note that SFP port:

GigabitEthernet1/0/25 current state: UP
PVID: 1
Port link-type: trunk
VLAN passing : 1(default vlan), 10, 20, 100
VLAN permitted: 1(default vlan), 10, 20, 100

and copper port: 

GigabitEthernet1/0/24 current state: UP
PVID: 1
Mdi type: auto
Port link-type: trunk
VLAN passing : 1(default vlan), 10, 20, 100
VLAN permitted: 1(default vlan), 10, 20, 100

share the same PVID, VLAN passing and VLAN permitted settings (PVID is 1, permitted VLANs are 10, 20 and 100)...so it's quite difficult to understand what is going on.

Which software release your 1920-24G is currently running on? can you share (sanitized) configuration file?

ag-wetter
Visitor

Re: HP VLAN tagging on SFP

Thanks for the response. 

I have in the meantime found out what has caused the issue. After some investigation it turns out someone enabled DHCP snooping but never trust the SFP port. So all is working now as expected after correctly configure it. 

Yes you are correct and Sorry for the confusion regarding the same PVID etc. I meant to make it clear that I disable the Ethernet port when I enable the SFP and vice versa.

 

parnassus
Honored Contributor

Re: HP VLAN tagging on SFP


@ag-wetter wrote: Yes you are correct and Sorry for the confusion regarding the same PVID etc. I meant to make it clear that I disable the Ethernet port when I enable the SFP and vice versa.

That was not an issue, I understood that you offered a comparison between 1/0/24 and 1/0/25 and both can't be active (Up) concurrently...indeed I wrote that, maybe, a sanitized configuration file would have helped to understand what else was going on...great you solved.