RV320 and WAN VLAN tagging/IPTV

I have a fiber connection on WAN1 which only works with VLAN tagging and I can't find a way to make it work without the provider's middleware router (Comtrend C5813)... Is there a way to connect to my FTTH (Lucent I240G-B) router directly? I'm having problems with my IPTV (multicast) service, if it's connect direct to the middleware I can have multiple channels running at once, but if I go back to the RV320 and do the same, everything start to pixelate.
Using Wireshark I can see that the RV320 is connecting to the different channels with CS4 DSCP marking.
Any ideas?
Thank you!

As you can read above, I'm having problems with my IPTV pixelation/cuts... I need to be able to connect directly to the fiber and have more control over the connection, but I don't see the option on the web admin for PPPOE over VLAN. I don't know if it's a hardware limitation or just software (the GUI).

Similar Messages

RVS4000 WAN VLAN tagging.

I have upgraded this device to Firmware Version: V2.0.2.7 (yes its a v2)
As far as I can see it is missing a critical function; I can not put a tagged VLAN on the wan interface. I intended to use this in router mode with a static wan and all firewalling disabled as my CPE equipment on a 100mbit metro-e.
The provider requires the traffic be tagged on the CPE side. I did not want to use a low end dd-wrt device (who's gui only supports upto vlan 15 but you can define higher by hand) as it is not "standard" and supported. I like to provide clean solutions that can be maintained by persons other then myself if needed.
Is there any way to access the CLI on these small business routers and accomplish this by hand?
Thank you.
Don

As you can read above, I'm having problems with my IPTV pixelation/cuts... I need to be able to connect directly to the fiber and have more control over the connection, but I don't see the option on the web admin for PPPOE over VLAN. I don't know if it's a hardware limitation or just software (the GUI).

C2504 with LAG and VLAN tagging

Having issues with setting up LAG on a Cisco 2504 WLC and implementing VLAN tagging on the different SSID´s.
Without LAG I had this up and running by using dynamic interfaces and assigning the different SSID´s to a perticular interface which was then assigned a specific VLAN.
However once I enabled LAG on the 2504, the dynamic interfaces became disabled and im unable to find documentation on how to configure VLAN tagging on SSID´s when using LAG.
Relevant info:
Cisco 2504 WLC running 7.4.100.0 (FUS 1.8.0)
Cisco 2602 APs
Cisco 3560 switch running IOS 15 (c3560-ipbasek9-mz.150-2.SE3)
Switch output:
C3560-PoE8#show etherchannel 1 summary
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        M - not in use, minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port
Number of channel-groups in use: 1
Number of aggregators:           1
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
1      Po1(SU)          -        Fa0/1(P)    Fa0/2(P)    Fa0/3(P)
                                 Fa0/4(P)
WLC output:
(Cisco Controller) >show lag summary
LAG Enabled
So basically what im trying to achieve is to implement LAG, use 2 SSID´s which are tagged in VLAN 300 and 400 respectively and keep management traffic untagged.

Hi Scott,
Yes I did.. But it seems that after deselecting the "Interface/Interface Group(G)" under the SSID´s and then selecting the dynamic interface again that the problem is resolved.

RV320 loosing WAN and inter VLAN connectivity

I just received a new RV320 V01 router and I am having trouble with the router loosing WAN and inter VLAN connectivity. Anywhere from 2 to 24+ hours the router will stop routing traffic to/from the WAN and other VLANs on the network. I have a ping trace running on one system and all packets are lost when the routing fails to all WAN connections and systems on other VLANs. I am still able to ping all of the router address for the VLANs i.e. 192.168.1.1, 192.168.2.1, 192.168.3.1 etc. Unfortunately I only have one system on this VLAN so I do not know if I can ping other systems on the same VLAN. I also do not have any DNS resolution when the issue occurs.
The router is set up using a single ISP connection on WAN1 using DHCP assignment. WAN2 is disabled in the router settings. The router has version v1.1.1.06 firmware. I have also tried disabling VPN pass-through as noted from other posts. When the issue occurs the WAN1 connection is showing as “Connected (Inactive)” with no assigned IP address, gateway or DNS servers. The router is in gateway mode and everything works fine until the problem.
Any Ideas?

You noted that the WAN 1 connection has no IP address when this occurs.
When it occurred last, I noted the "Connected (Inactive)" on WAN1 and that there were no IP addresses assigned. I have a screen shot of the page attached. I had noticed the "Connected (Inactive)" previously when the problem was occurring but cannot definitely say there were no IP addresses at that time. I do not recall if I noticed this before or after I had disconnected the WAN1 to test a direct PC to modem connection. I did check with the cable company and there are no issues being noted or logged on my connection. The direct PC to modem connection worked fine.
What type of Internet connection is it? (Cable, DSL, T1, etc)
The connection is Cable
Is the WAN port configured for DHCP?
The WAN port is configured for DHCP
Who is the ISP?
The ISP is the local cable company
When the issue occurs, can devices within a subnet ping each other?
As I noted in the original post, at the time I was on a VLAN that only had one system running to monitor ping traces. I will try again next time the problem occurs to have multiple devices on the same network.
Are there any switches in the network?
Yes, there is a switch in the system. I am using a cisco SG200-26. However, the problem persists even when I directly connected a PC to the active LAN port on the router. No issue when the PC was dirrectly connected to the modem.
Can you draw a simple topology showing the network with IP addresses, VLANs, etc?
See attached

Cisco RV180 VLAN tagging WAN interface

Is there by any chance in the future firmware update that this product (RV180) will be able to support VLAN tagging on WAN interface like the Cisco's RV315W router? ISP in Singapore (Singtel) and Malaysia(Unifi) (http://klseet.com/index.php/mikrotik/mikrotik-rb750-750g/setup-for-unifi) requires certain type of vlan tagging on the WAN interface for it to work.
Is there any workaround to this?

I tried with only two vlans and set the DHCP active only for the office "vlan2". Computers receive the correct ip but some of them won't register on the network, i tried to set the ip manualy on the computers but that computer will still be isolated.
Ex: computer A receives ip 192.168.10.25, Subnet 255.255.255.0, Gateway 192.168.10.1, for 2-3 minutes i can access the router on 192.168.10.1 and the internet, after a random time interval the gateway won't even respond to ping.It's not from firewall related issues as i set to accept all both incoming and outgoing. If i set a manual ip corresponding to vlan1 "default" everything works.It's like that computer is isolated so i believe it has to do with the asignment of Tagged, untagged and Excluded settings on the vlans.

RV320 two wan and wifi

Hi,
just buy a RV320 and I have both wan configured to failover.
Wan1 has fix ip and Wan2 has dynamic ip.
I would like to know if i can configure one router to provide WIFI. I tried to create a VLAN in Cisco and isolate wifi but does not work. The router is in bridge mode.
I hope someone can guide me to solve this problem.
thank you very much
pd: sorry for my english but is not my mother tongue....

Hi Marty,
thank you for your answer.
This my configuration:
default Vlan: 172.16.0.1
Vlan2: 192.168.2.1
WAN1: 217.172.x.x
WAN2: dinamic ip PPPoE
The switch is connected to port Lan 1 and an old router to port Lan 2 to provide wifi on an isolated network.
The router has not a special configuration, ip: 192.168.2.2, wifi, dhcp with default gateway 192.168.2.1
i can connect to wifi but i can not ping to 192.168.2.1
any help would be appreciated

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.

Transport dot1q vlan tagging over wan link

Hi,
I would like to transport 802.1Q vlan tagging over a wan link, is it possible ?
I heard about l2tp V3...
Best regards

Hi,
You would have to use a technology such as Ethernet over MPLS (EoMPLS) or VPLS. This technology is referred to as Layer 2 VPNs. You can get more info on this at the following locations:
EoMPLS (part of the Cisco Any Transport over ATM suite):
http://www.cisco.com/en/US/products/ps6646/products_ios_protocol_option_home.html
VPLS:
http://www.cisco.com/en/US/products/ps6648/products_ios_protocol_option_home.html
Hope that helps - pls rate the post if it does.
Regards,
Paresh

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

Dfme and vlan tagging

Hi all,
is it possible that dmfe driver can handle tagged vlans?
I use SunOs5.9 with patch 116561-12, which should give the ability for vlan tagging, but I can�t ping the other boxes.
I�ve configured 2 Ip-addrs on a nic (dmfe1,dmfe1:1) netmasks and routing seems to be ok.
Any help is appreciated

Congratulations. You have successfully confused me.
Do you know the difference between VLAN and Virtual interfaces?
A virtual interfaces are of the form <interface><instance>:<virtual instance> and lives on top of the normal interface and, in a way, just adds another IP to it.
Example of virtual interfaces:
dmfe1:2
Where dmfe is the interface, 1 is its instance and 2 is the virtual instance.
VLAN taging is somewhat more complex, and gives you seperate traffic on each VLAN. A VLAN interface is constructed as:
<interface>.<three digit VLAN><three digit Instance>
To create a VLAN tag for VLAN 888 on dmfe1, the VLAN number would be 888 and the instance 001, which would give you an interface of
dmfe.888001
To create a VLAN tag for VLAN 44 on dmfe0:
dmfe.044000
7/M.

Using Link Aggregation and VLAN tagging with LDOMs

Hi,
Anyone know if Link aggregation combined with VLAN tagging works for LDOMs?
Any links or references would be appreciated.....
It would be very handy if each LDOM could have multiple interfaces on different VLANs....
Regards,
Daniel

I agree with bzptlx. While you can have vswitch plumbed without net-dev, and then route traffic inside the control domain, so that you can utilize aggregation, it adds complexity, and in some environments it's just impossible.
I would say that this is number 1 deficiency with LDOM's in general.

Tagging and Untagging VLANS

Hi all. I think this is a terminology question more than anything, but I have a co worker that says I should configure switch with "untagging" vlans. Im not sure what he means, does he mean a access port? I would thing a trunk port "tags" vlans, but does an access port not do that? Can someone help explain this to me please? Thank you.

To tag or not to tag?
This type of question is constantly returning in this forum. A search would bring up quite some usefull info but I will make a final attempt anyway:
A switch-port can be configured as access or trunk. In access mode, incoming frames are tagged with the vlan-id that the port belongs to. An access port expects untagged frames.
In trunk mode, the port is expecting tagged frames. As you know, trunks are used to interconnect switches.
In the outgoing direction, an access port removes all tagging, a trunk preserves it.
With all this, there is one special case: the native vlan. Each port has one vlan (vlan1 by default) that is used as the native vlan. For compatability with non-vlan capable equipment, this vlan is sent & received untagged. This is hardly used as most trunks are point-to-point between vlan-capable devices. Make sure that the native vlan is set the same on both sides of the link.
Ports that connect IP phones have a mix between trunk and access. The data from the PC is forwarded on the access-vlan, the voice traffic utilizes the voice vlan as specified with the comand: switchport voice vlan, and this vlan must be tagged to preserve the 802.1p field that is part of a dot1Q tag and contains the priority info. voice is prio 5.
Hope this solves your question about to tag or not to tag.
Regards,
Leo

802.1Q VLAN Tagging on DSL WAN Connection

Hi
Does anybody know if SRP527W supports 802.1Q VLAN tagging on DSL WAN connection for RFC1483 bridged connections?
Thanks
Justin

Hi Justin,
Sorry for the delay in responding. Yes, this feature is now supported by the SRP527W using the MR3 release. (Please see https://supportforums.cisco.com/docs/DOC-13853).
Andy

VLAN Tagging ESW-540 and 3750g

Hi everyone!
I'm a self taught cisco type person who really specialises in ASA rather than routers, but have fumbled my way through many a task with the help of this site and google... However! I am currently tasked with setting up a network, pretty much from scratch, that requires some fairly hefty VLAN deployment.
My hardware on hand (already existed so can't can't change anything easily) 5x ESW-540-48 Switches, 1x3750g switch, 1x2811 router.
I don't believe the router should be required as the 3750 is capable of intervlan routing. So what i'm trying to achieve is as follows:
VLAN 1 - 172.16.8.0/22 (A)
VLAN 2 - 10.0.2.0/24     (B)
VLAN 3 - 10.0.3.0/24     (C)
VLAN 4 - 10.0.4.0/24     (D)
VLAN 5 - 10.0.5.0/24     (E)
VLAN 6 - 10.0.6.0/24     (F)
VLAN 7 - 10.0.7.0/24     (G)
VLAN 8 - 10.0.8.0/24     (H)
VLAN 9 - 10.0.9.0/24     (I)
Server Room - Servers connected to the 3750G
3750G connected to 5 ESW switches distributed around the building.
ESW-1 Will have VLAN(A) and VLAN(B) devices connected, specified at port level.
ESW-2 Will have VLAN(A) and (C) devices connected, specified at port level.
ESW-3 Will have VLAN(A), (D), (E) and (F) devices connected, specified at port level.
ESW-4 Will have VLAN(A), (G) devices connected specified at port level.
ESW-5 Will have VLAN(A), (H) and (I) devices connected, specified at port level.
Now at one point I actually had the VLAN's *working* in that I could specify an IP address and could ping to and from it! However DHCP wasn't passing despite numerous attempts with DHCP relay and IP-Helper configurations.
Also I was having issues with VLAN 1 as the native VLAN, the ESW switches don't allow you to do much with them, as they 'weren't created by the user'. So tried switching that out to VLAN11 also but with very little success there (I had to change the native vlan on all trunks to VLAN 11)
All the 10.x.x.x addresses need to be able to communicate with each other
All the ESW switches need to be able to handle their respective VLAN's as well as VLAN 1 (for Printers and wireless access points distributed around the building).
Partly i'm doing this in the hope that maybe some helpful soul can make some sense of it, but also just the fact of writing it down MAY firm it up in my head somewhat
Thanks in advance!
Simon

Ok so - i gave up at 2am this morning, and going back to it with a fresh head! Here's the situation as it has unfolded...
I have configured up 4 of my vlans for the purpose of testing, so you'll note there are a few missing.
I have moved the Native to VLAN 11 because the ESW's were doing something weird, and wouldn't allow me to do anything with trunking... If anyone can see a MUCH easier way of doing this, please feel free to chime in!
Primarily my question though is - why isn't DHCP working? Do I need to configure DHCP relaying on the ESW switches? Or should the DHCP REQ be passed across the entire vlan back to the 3750 regardless. And if I do need to configure relaying on the ESW - how?
In my server room I have a 3750 and a bunch of servers.
One of these servers - 172.17.10.229 is a win 2k3 dhcp server (physical not virtualised)
On my dhcp server I have configured scopes for each vlan (not superscoped)
My servers are sitting on the first 16 ports of said 3750. I have set their ports to native vlan 11 and allow vlans 1-3 and 11.
My ESW switches are on ports 46, 47 and 48. Likewise, their native has been moved to vlan11 and allowed vlans 1-3 and 11.
My ESW switches have been moved to native vlan11 and trunked each of their port 48's to allow all vlans.
Test 1: Unmodified port #10 on ESW1 (default vlan 11).
Connect DHCP device.
IP address assigned from vlan 11: 172.17.10.101.
Can ping all VLAN interface addresses.
Test 2: Modified port #11 on ESW1 (VLAN 2).
Connect DHCP device.
No IP address assigned.
Set static IP address 10.0.2.55/24.
Can ping all VLAN interfaces, DHCP server, entire network.
Change IP address of test device to 172.17.10.102 for testing.
No ICMP responses from anywhere - this is good!
So as you can see i've done my homework - well most of it obviously. Because it still isn't working
Here's the config of the 3750, the ESWs of course are a bit harder to just post my config, but the general state is something like this...
ESW Switch 1
Native VLAN 11
IP Address:     172.17.8.101 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
ESW Switch 2
Native VLAN 11
IP Address:     172.17.8.102 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
ESW Switch 3
Native VLAN 11
IP Address:     172.17.8.103 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
hostname 3750switch
enable secret 5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
enable password xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
no aaa new-model
switch 2 provision ws-c3750g-48ts
system mtu routing 1500
udld aggressive
ip subnet-zero
ip routing
ip domain-name mydomain.com
ip name-server 172.17.10.216
ip name-server 172.17.10.229
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos srr-queue input bandwidth 90 10
mls qos srr-queue input threshold 1 8 16
mls qos srr-queue input threshold 2 34 66
mls qos srr-queue input buffers 67 33
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 2 threshold 1 2
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 3 5
mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 1 threshold 3 32
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 2 4
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
mls qos queue-set output 1 threshold 1 138 138 92 138
mls qos queue-set output 1 threshold 2 138 138 92 400
mls qos queue-set output 1 threshold 3 36 77 100 318
mls qos queue-set output 1 threshold 4 20 50 67 400
mls qos queue-set output 2 threshold 1 149 149 100 149
mls qos queue-set output 2 threshold 2 118 118 100 235
mls qos queue-set output 2 threshold 3 41 68 100 272
mls qos queue-set output 2 threshold 4 42 72 100 242
mls qos queue-set output 1 buffers 10 10 26 54
mls qos queue-set output 2 buffers 16 6 17 61
mls qos
macro global description cisco-global
errdisable recovery cause link-flap
errdisable recovery interval 60
no file verify auto
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree extend system-id
vlan internal allocation policy ascending
interface GigabitEthernet2/0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/3
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/4
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/5
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/6
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/7
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/8
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/9
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/10
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/11
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/12
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/13
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/14
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/15
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/16
switchport access vlan dynamic
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
snip
interface GigabitEthernet2/0/47
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/48
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/49
interface GigabitEthernet2/0/50
interface GigabitEthernet2/0/51
interface GigabitEthernet2/0/52
interface Vlan1
ip address 10.0.1.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan2
ip address 10.0.2.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan3
ip address 10.0.3.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan11
ip address 172.17.8.253 255.255.252.0
ip default-gateway 172.17.8.1
ip classless
ip route 0.0.0.0 0.0.0.0 172.17.8.1
ip http server
control-plane
line con 0
line vty 0 4
password xxxxxxxxxxxxxxxxxxxxx
login
length 0
line vty 5 15
password xxxxxxxxxxxxxxxxxxxxx
login
length 0
end
3750switch#

Jumpstarting changes with U6: VLAN tagged interfaces and sysidcfg

Hello,
I've been banging my head on U6 for a few days and finally have to give up and cry for help. I can no longer build a jumpstarted server which ends up on a separate VLAN tagged LAN after first reboot.
I have an existing U5 SPARC jumpstart environment setup. We use VLAN tagging a lot in our environments and by default the only time a non VLAN tagged interface is used is during jumpstart. With the existing jumpstart we are using the following profiles:
root_password=mypassword
security_policy=NONE
timezone=GB
timeserver=localhost
terminal=vt100
network_interface=none {hostname=hostname}
system_locale=en_GB
name_service=NONE
system_locale=CIn the U5 profile we let the jumpstart server obtain its network configuration via DHCP and then obtain the profile above, which excludes all network settings. All the network settings were added as part of a finish script. This worked fine with U5. As far as I can see, with U6 at the point where the sysidcfg is first evaluated it removes the network settings and obviously then kills the jumpstart. So I have had to try a different approach. I have tried both of the following:
network_interface=PRIMARY { default_route=none protocol_ipv6=no}
network_interface=PRIMARY { dhcp default_route=none protocol_ipv6=no}However, using either of these causes the ce0, bge0 or whatever to remain defined, instead of the ce200000 and ce206000 interfaces that I have explcitly defined in hostname.ce200000 separately. I also get a number of arp errors on initial reboot, such as
Nov 20 20:27:29 unknown ip: ip_arp_done: init failed
Nov 20 20:27:29 unknown /sbin/dhcpagent[44]: configure_v4_lease: cannot set interface flags for ce0: Cannot assign requested addressI don't know if I am barking up the wrong tree but I believe I need to get the server on initial boot (or during finish) to reevaluate a different sysidcfg file. Alternatively, it might need some combination of presence/absence of /reconfigure or /etc/.UNCONFIGURED. I think I might also need to stop /sbin/netstrategy return dhcp specific results (I only use DHCP for jumpstart booting and not for normal boot), but I have no idea how to do that...
# /sbin/netstrategy
ufs ce0 dhcpAny help much appreciated!
thanks
Paul

Paul,
I don't want to suggest that I understand your problem but have you seen the comments about tagged vlans on the Opensolaris LDoms forum?
Near the bottom of thread [Solaris 10 10/08 (update 6)|http://www.opensolaris.org/jive/thread.jspa?threadID=81505&tstart=0] there is some discussion of tagged vlan support changes with U6.
It sounds like tagged vlans are going to be a problem with U6.
have a good weekend,
Glen

RV320 and WAN VLAN tagging/IPTV

Similar Messages

Maybe you are looking for