HP 1810G-8 vlan tagged port

Hello, friends!
I have some issue on HP ProCurve 1810G. My HP switch is uplinked to Netgear GSM7248 6 port. Some machine1 is connected to Netgear untagged port with PVID 11. I needed machine2 connected to HP to get reachable from machine1. So, on HP I've created vlan 11, tagged uplink port and set untagged port which is connected to machine2.
On Netgear I just tagged 6 port.
It works, no problem.
But later I needed another 2 machines to see each other in same manner. So, I have done same steps, but for vlan 32.
After this HP switch and all connected to it stuff became unreachable.No suspicious entries found in log.
I tried to replace HP with old as hell cisco switch and it works.
Tried also to upgrade HP to p2.12, but it didn't help.
Please, help.

Hi:
You may also want to post your question on the HP Business Support Forum -- Procurve Switches section.
http://h30499.www3.hp.com/t5/ProCurve-ProVision-Based/bd-p/switching-e-series-forum#.VCgRxHl0y9I

Similar Messages

VLAN assistance, tagged port lost internet

I'm working on getting a new building set up that will be connected directly to our current building but we need it separated with its own VLAN. I've created the VLAN in all our switches and untagged all the ports to the new VLAN for the switches that will be in the new building and created a sub-interface on our sonicwall for the VLAN. Our main site will continue using the default vlan. I tried tagging port 1 on our LAN switch which goes to our sonicwall but we immediately lost internet connectivity for our main site. Could I be missing something here? Do I need to create sub-interfaces for the default vlan now that we have more than one traversing the sonicwall?
This topic first appeared in the Spiceworks Community

I'm working on getting a new building set up that will be connected directly to our current building but we need it separated with its own VLAN. I've created the VLAN in all our switches and untagged all the ports to the new VLAN for the switches that will be in the new building and created a sub-interface on our sonicwall for the VLAN. Our main site will continue using the default vlan. I tried tagging port 1 on our LAN switch which goes to our sonicwall but we immediately lost internet connectivity for our main site. Could I be missing something here? Do I need to create sub-interfaces for the default vlan now that we have more than one traversing the sonicwall?
This topic first appeared in the Spiceworks Community

RV Support VLAN Tagging on WAN Port?

Hi,
I'd like to know if RV Series Router can support VLAN tagging on the WAN port itself? I need this cause my ISP using such method to connect to end user modem/router.
Thank you.
Regards,
Danny

Anything available other than this RV315W? That model is only 10/100 on the LAN. VLAN on the WAN is fairly standard for fibre installs and should be a feature across all SMB routers.

Is it better to use router port versus vlan member port?

Hi CSC,
This is more of a philosophical or "best practices" question.
I have a Cisco 3550 at the home office. Connected to the 3550 is a number of branch offices by way of T1 circuits or VDSL modems. They all come to the home office, where we have a central internet connection and server farm for our entire organization.
Except for one special case branch office, we don't forsee the need for appearances of the home office vlan at the branch office sites. In that case, we bring it into a trunk port at the home office, and at the special case branch office we have a dell 3024 switch and tag some ports as vlan 18 (the home office) or vlan 27 (the special case branch office).
We also do not forsee a need for the vlan from one branch office to appear at another branch office.
They are all (except for the special case mentioned above) currently configured something like this:
interface FastEthernet0/1
description home office
switchport access vlan 18
switchport mode access
interface FastEthernet0/2
description t1 to branch office 1
switchport access vlan 19
switchport mode access
interface Vlan18
description subnet for home office
ip address 192.168.18.1 255.255.255.0
interface Vlan19
description subnet for branch office 1
ip address 192.168.19.1 255.255.255.0
Is it better, in terms of reduced network complexity or performance on my 3550, to do something like this instead?
That is, to make the interfaces router ports as opposed to vlan member ports?
Of course, if we ever DID need to have appearances of the home office vlan at branch office sites, or appearances of one branch office's vlan at another branch office, we would lose that flexibility.
interface FastEthernet0/1
description home office
switchport access vlan 18
switchport mode access
interface FastEthernet0/2
description t1 to branch office 1
ip address 192.168.19.1 255.255.255.0
interface Vlan18
description subnet for home office
ip address 192.168.18.1 255.255.255.0
no vlan 19

Hello,
In my opinion there is no 100% right answer here. I think it depends also about network forecast. I'll try to add here some thoughts:
- if you use trunk interfaces from home to branch and SVI for L3 connection, in terms of scalability is much easier to expand (you have now only one p2p L3 link, but in future you'll need another one; if the port is a trunk one, you just configure another SVI interface, allow vlan on trunk and your good to go)
- trunk interfaces involve more configuration (L2 interface and SVI L3 interface)
- if you add in the home office another switch to existing one, and for some reason you have misconfiguration in STP / VTP, then you can run into problems like loops, vlan database modification (e.g. VTP server mode and the new added switch has a higher revision number than existing one)
- L3 physical interfaces are easier to configure and less complex, but in case you want to scale to additional p2p link will be harder
- L3 configuration is easier to troubleshoot as you avoid the L2 complexity
- in terms of packet exchange a L3 interface will exchange less packets than a L2 trunk with SVI (I'm talking here about control traffic, not user traffic)
- with L2 trunk you can have other problems like if somebody is "smart enough" to add a new switch into the existing switch (if you have a switch there) at the branch location; imagine that the new switch due to misconfigurated STP became root bridge; you have a large STP domain.
As I said, there is no good or bad approach. You have to guide yourself about forecasts in your network. For example if you know that a branch location will not be extended in the next 2 years, then go ahead with L3 interface and that's it. On the other hands if you have doubts you can add for another location L2 trunk with SVI. You can mix this two solution to obtain the best results for your network characteristics.
Cheers,
Calin

Vlan tag issue with Nexus 4001 in IBM Blade Centre

Hi
I have a DC architecture with a pair of Nexus 7010's running 3 VDC's (Core/Aggregation/Enterprise). I have at the edge Nexus 5548's which connect to back to the Aggregation VDC. Also connecting back to the Aggregation VDC is an IBM Blade Chassis which has a Nexus 4001i in slots 7 and slot 9. These blade servers are running ESXi 4.0 and are mapped to the Nexus 4001 blade switch.
I had set up the Native VLAN as VLAN 999 which connects up to the ESXi host and I am trunking up multiple VLANS for the Virtual Machines.
The problem I have is that VM's in all VLANS except the ESXi host VLAN (VLAN 10) cannot see their default gateway, and I suspect that there is an issue with the VLAN tag going up to the ESXi host. I have read enough documentation to suggest that this is where the issue is.
My Nexus 4001 interface configuration is below
interface Ethernet1/1
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 10,30,40-41,60-62,90,96,999
spanning-tree port type edge trunk
speed auto
The Aggregation VDC on the Nexus 7010 is the default gateway for all these VLANS.
I also noted that the Nexus 5000 and Nexus 7000 supports the command vlan dot1q tag native command yet the Nexus 4000 doesn't seem to support this. Any assistance would be useful
Thanks
Greg

Your configuration on the N4K looks correct. You shouldn't use vlan dot1q tag native commands on your N7Ks and N5Ks. Native VLAN tagging is really for QinQ (dot1q tunneling).
My only suggestion is check your configuration of the vSwitch in the ESXi host and the host network profile.
Regards,
jerry

7600 second-dot1q & vlan tag manipulation

Hi,
Does anyone know what the hardware requirements are for using config such as "sencapsulation dot1Q 660 second-dot1q 1" or any of the "service instance" commands such as below to manipulate dot1q tags?
Im running 7600 with SIP-400, IOS 12.2(33)SRD and there are no such commands available at the cli. Suspect ES-20 is needed as a minimum but can't see this mentioned in any docs.
interface FastEthernet1/0.660
encapsulation dot1Q 660 second-dot1q 1
OR
interface GigabitEthernet3/0/0
description Sample Configs
service instance 1 ethernet
encapsulation untagged
rewrite ingress tag push dot1q 3 symmetric
xconnect 10.30.30.173 2 encapsulation mpls
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
service instance 20 ethernet
encapsulation dot1q 20 second-dot1q 200
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
service instance 30 ethernet
encapsulation dot1q 20 second-dot1q any
rewrite ingress tag pop 1 symmetric
bridge-domain 500 split-horizon
I just need to pop the service vlan tag. At the moment I'm using a port per service to peel off the outer tag and this approach isn't going to scale.
Appreciate any advice on this.
Cheers
Kent.

Hi Jerry,
I believe - about to test it - that this only works with SPA-v2 interfaces. I was testing with a SPA-v1 interface previously. Is this your understanding? Docs are pretty light on with hardware requirements.
Show ver:
Cisco IOS Software, c7600s3223_rp Software (c7600s3223_rp-ADVIPSERVICES-M), Version 12.2(33)SRD, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 23-Oct-08 22:32 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
pe1.lab uptime is 19 hours, 5 minutes
Uptime for this control processor is 19 hours, 5 minutes
System returned to ROM by power-on (SP by power-on)
System restarted at 17:09:22 EST Mon Jul 27 2009
System image file is "bootdisk:c7600s3223-advipservices-mz.122-33.SRD.bin"
Last reload type: Normal Reload
cisco CISCO7606-S (R7000) processor (revision 1.0) with 458752K/65536K bytes of memory.
Processor board ID FOX11310AY3
R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache
Last reset from power-on
1 SIP-400 controller (4 GigabitEthernet).
10 Virtual Ethernet interfaces
125 Gigabit Ethernet interfaces
1915K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
Modules are now:
7600-SIP-400 and SPA-2X1GE-V2

Vlan tag preservation span monitoring

Hi
I am spanning multiple vlans as source with the destination as a single ethernet port, though I am able to see the traffic from the VLANs, I am not able to see the VLAN tag in the packet which is a key requirement for me for monitoring.
Does anyone know why the VLAN tagging is stripped or how to preserve it in the monitor session?
Your help is much appreciated.
- Balaji

While I appreciate your response Najaf, we have been monitoring the SVIs on our current CAT6500 switches without any problems as we can "preserve" the vlan tags on the destination monitoring port.
However, we have found a way to see the VLAN tags on the monitoring destination port but we are still carrying out some tests to confirm our findings.
Will keep this thread updated.
-Balaji

Installing OVM X86 3.1.1 with Trunk VLAN tag for ovm management network

Hi Guys
Can anyone help with network config on the OVM server 3.1.1 basically we need to use vlan tags on trunk port... so i have a subnet from following *(Trunk Allowed VLAN XXX)* from which i need to allocate IP for the OVM server component so that the ovm manager can find the OVM server instance...
Can you use vlan tags, on trunk port with OVM server 3.1.1???
Thanks

Your right there as i later found out the engineers weren't selecting the vlan option when installing the vm server...

VLAN Tagging

I am trying to utilize a wireless device in a customer site that extends VLAN to the wireless infrastructure. My device does not support VLAN Tagging, so it will not work. My question is this: Is this the norm, requireing end-point devices to insert VLAN Tags in the normal ethernet frame, or do most environments perform the Tag insertion/stripping at teh acces point level. Since they can use multiplpe SSIDs on their access points, can a new SSID be set up for another wireless VLAN that does not require VLAN Tagging?

In a Cisco environment you configure your VLANs on your switches and configure the switchport the AP is connected to as a trunk port. On the AP you define the VLANs and SSIDs and tie each SSID to a VLAN. End devices connect to an SSID and when connected to that SSID are automatically connected to it's matching VLAN. The end device (be it a PC, barcode reader or whatever) doesn't need to know anything about VLANs or which VLAN it needs to connect to, as long as it's associated to the correct SSID it will be on the correct VLAN.

Span & wireshark to see p-bits and vlan tags

Problem:
I do not see 802.1Q tags nor do I see p-bits (COS) in my wireshark captures. My setup is not working and I have no way to verify (sniff) that the 6509 is setting the p-bits to 3. I need to see them to troubleshoot effectively. Help!
Setup:
I am port mirroring off of my 6509. Port 1/16 should be tagging and setting the p-bits to a value of 3. How can I confirm?
interface GigabitEthernet1/16
description DonkX
no ip address
load-interval 30
mls qos cos 3       ! I've tried my tests with and without this command
mls qos cos trust      ! I've tried my tests with and without this command
switchport
switchport access vlan 941
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 941
switchport mode trunk
no cdp enable
end
sho mon
Session 1
Type                   : Local Session
Source Ports           :
    Both               : Gi1/16
Destination Ports      : Gi8/47
Port G1/16 is the GE uplink to DonkX
Port G8/47 is the Windows 2003 Server with wireshark.
Port G8/9 is my RH4 Linux box with TCPdump.
Steps taken to resolve the problem:
I have followed this document to set this up correctly on my windows box with a Intel Proset 1000MT. I have updated the drivers and made the registry changes with no captures showing tagging/cos information.
http://www.intel.com/support/network/sb/CS-005897.htm
Regardless of my settings, this document says I shouldn't have to worry about drivers:
http://wiki.wireshark.org/CaptureSetup/VLAN
"You'll definitely see the VLAN tags, regardless of what OS the independent system is running or what type of network adapter you're using."
Details:
I am testing a new GPON access product (DonkX) that uplinks via GigE using trunking and setting p-bits. To prioritize my video the new DonkX sets the p-bits to 3 and it instantly ceases that traffic. I have only unidirectional traffic at this point so I can no longer arp, icmp, ftp, tftp, noth'n. The 6509 sends back a response to DonkX but I believe it is dropped because the p-bit is not set to 3. If I remove the priority from 3 to 0 on the DonkX system then it works correctly but without QoS of course.
-JGR

Alright, the saga continues. I saw tagged frames last week but began troubleshooting again this morning and can't see tagged frames!
If I remove the span then I can see tagged traffic on g8/47 (Windows 2003 Server 802.1q not configured on NIC). If I turn on monitoring I see no tagged traffic. I also tried this on a laptop running Fedora 12 (on g8/47) and had the same results. Any ideas?
I've mirrored another trunk port that is in production passing tagged traffic to an 3560 trunked and going to an ASA. The port to the 3560 and ASA (g3/7) requires tagging and works properly; however, I cannot see tags on this port either. Do you see anything obvious here or is this looking like a tac case?
interface GigabitEthernet1/16
description DonkX
no ip address
load-interval 30
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 941
switchport mode trunk
no cdp enable
end
interface GigabitEthernet8/47
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no cdp enable
end
conf t
no mon sess 1
mon sess 1 sourc int g1/16
mon sess 1 dest int g8/47
sho mon
Session 1
Type                   : Local Session
Source Ports           :
    Both               : Gi1/16
Destination Ports      : Gi8/47
Unit details:
WS-C6509 Version 12.2(18)SXD4
NAME: "1", DESCR: "WS-X6516A-GBIC SFM-capable 16 port 1000mb GBIC Rev. 4.2"
PID: WS-X6516A-GBIC
NAME: "8", DESCR: "WS-X6748-GE-TX CEF720 48 port 10/100/1000mb Ethernet Rev. 2.3"
PID: WS-X6748-GE-TX
NAME: "6", DESCR: "WS-SUP720-BASE 2 ports Supervisor Engine 720 Rev. 3.1"
PID: WS-SUP720-BASE
NAME: "msfc sub-module of 6", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev. 2.3"
PID: WS-SUP720
NAME: "switching engine sub-module of 6", DESCR: "WS-F6K-PFC3A Policy Feature Card 3 Rev. 2.4"
PID: WS-F6K-PFC3A

LOM VLAN tagging?

All,
I'm wondering if anyone has had any luck getting LOM to do vlan tagging. According to the manpage for ipmitool, it should support it by going "ipmitool lan set vlan id <vlanidnumber>" but it rejects it and prints the acceptable commands for ipmitool lan set, and none of them are vlan.
So, did Apple just compile ipmitool without the vlan option, does the Apple implementation of ipmi not support it? It's a huge pain in the rear to do MAC based vlanning (requires a radius server), so I'd really prefer to do it with vlan tagging, since it should work.
Thanks!

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Just to muddy the waters, since VLAN edge/access ports don't normally tag frames with VLAN IDs, referencing your question about two computers "talking" to each other, it doesn't matter whether the two ports or on the same switch or even different switches; or in the same VLAN or not.
Also understand trunk ports normally tag frames, and edge/access ports don't, but an exception for the former is the "native" VLAN frames aren't tagged, and an exception for the latter, a Voice VLAN will tag frames.

Srw2008 snmp vlan to port

Hello,
I need to know is there any option to get ports that some vlan is added to with snmp? I found with snmpwalk that oid 17.7.1.4.5.1.1. gives information of port and vlan id's. So far so good, but thats the way to see only untagged vlans on ports. I was not able to found any data about tagged vlans on ports. There are some OID with hex codes that changes by changing port tagging but i cant understand them.
Solved!
Go to Solution.

Configuration is vlan id 3333 name "test" tagged on port 4 and port 8. Output differences :
17.7.1.4.2.1.4.0.3333 = Hex: 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
17.7.1.4.3.1.2.3333 = Hex: 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
17.7.1.4.3.1.3.3333 = Hex: F6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ifMIB.ifMIBObjects.ifStackTable.ifStackEntry.ifStackStatus.103332.4 = active(1)
Configuration is vlan 3333 name "test" tagged on port 5 and port 8 . Output differences:
17.7.1.4.2.1.4.0.3333 = Hex: 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
17.7.1.4.3.1.2.3333 = Hex: 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
17.7.1.4.3.1.3.3333 = Hex: EE 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ifMIB.ifMIBObjects.ifStackTable.ifStackEntry.ifStackStatus.103332.5 = active(1)
There is more of hex code as result but the rest is zero's ...

Collision Domain , Vlan Tagging.

Hi,
Can any one tell me please do we have collisions in a Switch if yes 1. how to avoid Collisions in a switch and 2. Define Vlan Tagging. Can anyone please answer my two questions.
Thanks.

Hi,
1) each port on a switch is a collision domain this is called microsegmentation and you can run full-duplex so the answer is No there are no more collisions in a switched network. apart from shared segment where there is a hub or AP attached
2)on links where multiple VLANS can travel you must have a way of differentiating the VLAN the frame is part of and so you have a field with the VLAN id which is a Tag permitting to recognize the VLAN so the switch knows on which port it can forward the frame when the tag is removed.So a frame enters a port belonging to a particuliar vlan and it is tagged with the vlan id when traversing the trunk( or tagged port) and untagged when forwarded to the destination.
In 802.1Q ther is also the concept of native vlan : frames from this vlan will have no tag, this is a compatibility feature for devices not VLAN aware.
Regards.
Alain.

Vlan tag capturing

I've been trying to capture the vlan tags on a trunk link using the wireshark and port mirroring with no success. Any ideas on what I'm doing wrong or what I'm missing .

You should be looking for packets with ethertype 8100. Check the link for a wiki on this:
http://en.wikipedia.org/wiki/IEEE_802.1Q#Frame_format
Setting the monitor port to trunk mode is an experiment that's certainly worth trying. However, even if you are doing everything correctly, your PC adapter may not recognize the packets and ignore them.
regards,
Leo

Adding & removing VLAN tags?

As I recall, switches will add the VLAN tag on frames entering a VLAN configured port & remove the tag once the frame exits the switch. Assuming VTP is enabled in a LAN topology because all VLAN members do not reside on the same switch, is the VLAN tag added & removed on *each* switch traversed?
Thanks for any clarification provided.

The tags are added and stripped on ingress and egress from access ports.
If a host sends a frame into a VLAN port on switch A, then the frames traverses a trunk port to switch B, then exits to a host from an access port on switch B, the TAG is applied on switch A, then stripped on switch B. THe frame keeps the tag through the trunk.
Good Luck
Scott

HP 1810G-8 vlan tagged port

Similar Messages

Maybe you are looking for