Extending VLANs across routed interfaces

Hello;
I'm trying to create a L3 core network. The core equipment will be Cisco 3750 enhanced. My idea is make each link between core 3750 a routed interface, with /30 IP addresses.
The problem is the customer needs some VLANs extended across the full enterprise. Is there any way to encapsulate the VLAN inside routed interface?
Thanks in advance.

I realize this thread is 5+ years old, but I feel like commenting anyway.
If you want to encapsulate the vlan across that link, you won't be able to use routed interfaces.  You will need to use a layer 2 trunk(dot1q).  Therefore, I wouldn't bother with the /30 addresses unless you want to monitor that specific link by IP.  In that case, use a special VLAN just for those two interfaces and put your /30 addresses on the vlan interfaces.
If you want fast fail over on a layer 2 link, well then, use Rapid STP.  The goal should be to get rid of those flat VLANs that span the core and switch to your original plan of routed interfaces using EIGRP or OSPF.

Similar Messages

  • Extending VLAN across Data centers

    I hope you can help, I have 2 data centers connected via a L3 10gb (dark fiber) now I have a few more fiber strands available between the 2 data centers; so for Disaster Recovery and server clustering (requiring same subnet) does it make sense to extend certain vlans across using these extra fiber strands or is it best practice to keep the layer 3 separation, thanks in advance!

    Borman
    It does make sense in terms of clustering. Not sure exactly what you mean in terms of disaster recovery, that really depends on your topology/addressing.
    Basically i would route where you can and extend L2 when you have to. Be aware you are extending L2 between data centres and tha brings STP issues. Obvioulsy make sure you only allow the vlans you need on this link and route all else.
    There are other ways to extend a L2 vlan across a L3 link - L2TPv3 springs to mind.
    Jon

  • How to span vlans across core layer in core/distribution/access campus design?

    Hi,
    I studied Cisco Borderless Campus Design Guide 1.0 (http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/Borderless_Campus_Network_1-0/Borderless_Campus_1-0_Design_Guide.html) last week because we plan to redesign our campus backbone to a three tier Core/Distribution/Access Design.
    Today we use a collapsed backbone where a lot of vlans are spanned across the backbone because they are needed in different buildings.
    Could anybody give me a hint how Cisco recommends to deal with that kind of vlans in the multi-tier design?
    In my eyes between core and distribution layer there is only routing functionality and no l2 transport of vlans.
    So using the same vlan in different buildings seems not to be supported?
    Best Regards,
    Thorsten

    Thorsten
    Just to add to Joseph's post.
    It is quite common for a vlan to be spanned when it doesn't actually need to be ie. the network has evolved that way.
    Most things do not need L2 adjacency, they can happily use L3. Servers sometimes do but in the campus design your servers are usually located in one site so you don't need to extend vlans to other sites in your campus.
    Not suggesting this is the case for you but it may be worth checking whether you really do. (apologies if you already have)
    As Joseph mentioned you really want to avoid it if at all possible ie. ideally all connections to the core switches are L3 ie. no need for vlans at all in the core.
    If you need to extend a few vlans then you can do this but still route for all other vlans ie. you would configure your distribution to core connections as trunks and then allow the vlans you need to extend plus one other vlan, unique per distribution pair, to route all other vlans. So per site your distribution switches route all vlans except the extended vlans and of they need to route to a vlan in another site they use that unique vlan.
    But this is not ideal because you then need to extend certain vlans across the core and because you are using L2 connections STP could come into it although that does depend on your core switch selection eg. 4500/6500 VSS etc. would alleviate this.
    There are ways to extend vlans across a L3 network but the solutions available are very much dependant on the kit you use and their capabilities so if you do need multiple vlans in multiple sites but still want to keep a L3 core you may want to investigate some of those before purchasing kit (unless of course you have already purchased it).
    What you do really depends on just how many vlans you actually need to extend between sites.
    Jon

  • Sending specific Vlan across wireless bridge

    Hello All,
    I would like to know how I can send a specific VLAN across a wireless bridge.  Currently, we have a building across the street from our main office that's connected via a wireless bridge (no physical cabling).  One of the switches in building 1 has a port in VLAN 206 (10.20.6.0/24) which connects to the wireless bridge (10.20.6.3) on that building.  The wireless bridge in building 2 is 10.20.6.4 and connects to a router on the same subnet.  So both bridges, the switch in building 1, and the router in building 2 are all on the same subnet.  I need to send VLAN 60 across this wireless bridge so that the workstations in building 2 can go out to the Internet.  As a side note, VLAN 60 is unrouted and is it's own subnet which has it's own firewall and web filter.  My thought on this is that if I can get the wireless bridges to send VLAN 60 to building 2, then all I would need to do is add the workstations to that VLAN on the switch in that building and all should be well.  I'm just not sure what I need to configure on the bridges and how building 2 should be configured seeing that the 2nd bridge connects to a router instead of a switch.  Any tips, suggestions, and help would be great!
    Thanks,
    Terence                  

    assume that i have two bridges Br-root , and Br-nonroot and i want to send traffic from multiple vlans across the wireless link, all you need to have is infrastructure-ssid on the native vlan. Then define the required subinterfaces on both radio and ethernet of root and non-root.
    Example: ( vlan 1 , 2 , and three )
    Root(config)#dot11 ssid test             
                     #authentication open
                     #vlan 1
                     #infrastructure-ssid
                    #exit
    Root(config)#interface dot11radio 0
                     #ssid test
                     #station-role root bridge
                     #no shut
                    #exit
    Root(config)#interface dot11rdio0.1
                     #encapsulation dot1q 1 native
                    #bridge-group 1
                   #exit
    Root(config)#interface dot11rdio0.2
                     #encapsulation dot1q 2
                    #bridge-group 2
                   #exit
    Root(config)#interface dot11rdio0.3
                     #encapsulation dot1q 3
                    #bridge-group 3
                   #exit
    Root(config)#interface fa0.1
                     #encapsulation dot1q 1 native
                    #bridge-group 1
                   #exit
    Root(config)#interface fa0.2
                     #encapsulation dot1q 2
                    #bridge-group 2
                   #exit
    Root(config)#interface fa0.3
                     #encapsulation dot1q 3
                    #bridge-group 3
                   #exit
    for the non-root , same config but the station-role should be non-root
    Enjoy

  • Extending vlan 301 through ASR 1006 (extending the broadcast domain)

    Good evening everyone. My brain hurts trying to figure this out. I'm used to Layer 3 switches so this is different. 
    According to the documentation, this should be allowed using EVC and Bridge Domains. But there is one disclaimer in the documentation... if you've configured a channel-group on a physical ports, you can't have port-channels (or something like that). 
    I have configured multiple port-channels (for port redundancy), each port-channel having multiple sub-interfaces (for vlan creation on this beast). Each sub-interface has an ip address. Now it has come to my attention that there are two vlans that need to be extended from a remote office (via port-channel 3) to our Core (via port-channel 1). I want to be clear, I am trying to get this router to simply forward layer 2 traffic from port-channel 1 to  port-channel 3. I tried the following:
    example: vlans 300 and 301 need to be extended.
    create additional sub-interfaces like this,...
    int port-channel 1.300
    encapsulation dot1q 300
    int port-channel 1.301
    encapsulation dot1q 301
    int port-channel 3.300 
    encap dot1q 300
    int port-channel 3.301
    encap dot1q 3.301
    But that didn't work. I tried evc and bdi but it's confusing as heck. Anyone got any ideas? Is this possible? Can you point me to a resource that can make it crystal clear for me?

    Thank you Reza. I was worried about that.
    So I have an opportunity to re-configure this entire beast because of this. If I need to make this work, is the ASR the wrong choice or am I just going about it wrong? 
    I've read that if I had two ASRs I could implement OTV. Does that make sense? 
    http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/wan_otv/configuration/xe-3s/wan-otv-xe-3s-book/wan-otv-confg.html#GUID-DCB20ADF-1F8E-434B-AE97-54802879F34F

  • Unable to create extended vlan

    Dear All,
    Is there anyway to create extended vlan(from 1006 to 1010) on my cisco 7604? These are existing customer vlan which I planned to move to this 7604 but unfortunately cant. I believe only FDDI and Token ring vlan unable to remove. Expert please advice.
    PBR#sh ver
    Cisco Internetwork Operating System Software
    IOS (tm) s3223_rp Software (s3223_rp-IPSERVICES_WAN-M), Version 12.2(18)SXF17, R
    ELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2009 by cisco Systems, Inc.
    Compiled Fri 25-Sep-09 06:10 by ccai
    Image text-base: 0x40101040, data-base: 0x42A509B0
    ROM: System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1)
    BOOTLDR: s3223_rp Software (s3223_rp-IPSERVICES_WAN-M), Version 12.2(18)SXF17, R
    ELEASE SOFTWARE (fc1)
    PBR uptime is 11 weeks, 1 day, 21 hours, 33 minutes
    Time since PBR switched to active is 11 weeks, 1 day, 21 hours, 33 min
    utes
    System returned to ROM by  power cycle (SP by power on)
    System image file is "sup-bootdisk:s3223-ipservices_wan-mz.122-18.SXF17.bin"
    cisco CISCO7604 (R7000) processor (revision 2.0) with 458752K/65536K bytes of me
    mory.
    Processor board ID FOX1340GBXD
    R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache
    Last reset from power-on
    SuperLAT software (copyright 1990 by Meridian Technology Corp).
    X.25 software, Version 3.0.0.
    Bridging software.
    TN3270 Emulation software.
    18 Virtual Ethernet/IEEE 802.3 interfaces
    57 Gigabit Ethernet/IEEE 802.3 interfaces
    1915K bytes of non-volatile configuration memory.
    65536K bytes of Flash internal SIMM (Sector size 512K).
    Configuration register is 0x2102
    PBR#
    PBR#sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Gi3/14, Gi3/44
    2    HPeP_Terrestrial_Side            active
    3    HPeP_Satellite_Side              active    Gi3/23, Gi3/24
    5    Management                       active    Gi3/1, Gi3/2, Gi3/3, Gi3/4
                                                    Gi3/5, Gi3/6, Gi3/7, Gi3/8
                                                    Gi3/9, Gi3/12, Gi3/13, Gi3/15
                                                    Gi3/31, Gi3/35
    6    Customer_Traffic                 active    Gi3/11, Gi3/37, Gi3/38
    8    GCU                              active    Gi3/33, Gi3/34
    20   SIME                             active
    45   Petrofac                         active
    51   140.176.51.0/24-client-vlan      active
    101  Internet_Connection              active    Gi1/1, Gi1/2, Gi3/16, Gi3/26
    190  BUK_FVSB                         active
    201  Customer_VLAN_201                active
    202  GITNS2A                          active
    203  Internet_Connection_New          active    Gi3/17, Gi3/48
    204  Sports_Toto_Malaysia             active
    205  XOM_EXXONMOBIL                   active
    206  PCSB                             active
    990  Unused_Ports                     active    Gi1/3, Gi1/4, Gi1/5, Gi1/6
                                                    Gi1/7, Gi1/8, Gi1/9
    999  RSPAN                            active
    1002 fddi-default                     act/unsup
    1003 token-ring-default               act/unsup
    1004 fddinet-default                  act/unsup
    1005 trnet-default                    act/unsup
    VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
    1    enet  100001     1500  -      -      -        -    -        0      0
    2    enet  100002     1500  -      -      -        -    -        0      0
    3    enet  100003     1500  -      -      -        -    -        0      0
    5    enet  100005     1500  -      -      -        -    -        0      0
    6    enet  100006     1500  -      -      -        -    -        0      0
    8    enet  100008     1500  -      -      -        -    -        0      0
    VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2
    20   enet  100020     1500  -      -      -        -    -        0      0
    45   enet  100045     1500  -      -      -        -    -        0      0
    51   enet  100051     1500  -      -      -        -    -        0      0
    101  enet  100101     1500  -      -      -        -    -        0      0
    190  enet  100190     1500  -      -      -        -    -        0      0
    201  enet  100201     1476  -      -      -        -    -        0      0
    202  enet  100202     1500  -      -      -        -    -        0      0
    203  enet  100203     1500  -      -      -        -    -        0      0
    204  enet  100204     1500  -      -      -        -    -        0      0
    205  enet  100205     1500  -      -      -        -    -        0      0
    206  enet  100206     1500  -      -      -        -    -        0      0
    990  enet  100990     1500  -      -      -        -    -        0      0
    999  enet  100999     1500  -      -      -        -    -        0      0
    1002 fddi  101002     1500  -      -      -        -    -        0      0
    1003 tr    101003     1500  -      -      -        -    -        0      0
    1004 fdnet 101004     1500  -      -      -        ieee -        0      0
    1005 trnet 101005     1500  -      -      -        ibm  -        0      0
    Remote SPAN VLANs
    999
    Primary Secondary Type              Ports
    PBR#
    PBR# sh vlan internal usage
    VLAN Usage
    1006 online diag vlan0
    1007 online diag vlan1
    1008 online diag vlan2
    1009 online diag vlan3
    1010 online diag vlan4
    1011 online diag vlan5
    1012 PM vlan process (trunk tagging)
    1013 Control Plane Protection
    1014 L3 multicast partial shortcuts for VPN 0
    1015 Egress internal vlan
    1016 Multicast VPN 0 QOS vlan
    1017 GigabitEthernet3/27
    1018 GigabitEthernet3/47
    1029 IPv6 Multicast Egress multicast
    1030 L3 multicast partial shortcuts for VPN 1
    1031 Multicast VPN 1 QOS vlan
    1032 L3 multicast partial shortcuts for VPN 3
    1033 Multicast VPN 3 QOS vlan
    1034 L3 multicast partial shortcuts for VPN 5
    1035 Multicast VPN 5 QOS vlan
    1036 L3 multicast partial shortcuts for VPN 6
    1037 Multicast VPN 6 QOS vlan
    PBR#

    As Cisco Freak said, those vlans are being allocated for internal use
    Layer 3 LAN ports, WAN interfaces and subinterfaces, and some software features use internal VLANs in the extended range. You cannot use an extended range VLAN that has been allocated for internal use.
    In order to use them, you will need to use a descending vlan allocation option, to start allocation from vlan 4094 and down, to do this you will need to apply the command:
    vlan internal allocation policy descending
    And then reboot your switch, so the internal vlans get reallocated
    For more info refer to this configuration guide:
    http://www.cisco.com/c/en/us/td/docs/routers/7600/ios/15S/configuration/guide/7600_15_0s_book/vlans.html#pgfId-1038695

  • VLANS across WANS

    I am working on a project for CCNA class. I want to maintain VLAN identities across multiple WAN sites...i.e. My central Core will be in LA, remote offices at Dallas and St Louis. If I define VLANs 10, 20,30, and 40 at LA for 4 departments, with network 10.0.10.0/22, 10.0.20.0/22 etc..I have considered using EoMPLS to maintain the VLAN structure and the ability to not have to change or reassign different  network address at the remote sites. In essence, I wish to have the same subnets at all sites for all VLANS and implement NMC from the LA office. I want to have VLAN 10, with 10.0.10.0/22 at all 3 sites. Is this possible and maintainable from a management standpoint using EoMPLS. What am I missing here? Other posts I have researched state that this is not possible and not recommended. The objective is to maintain VLANs across all 3 sites.    
    If not, then how do we maintain VLAN identities and membership across all 3 sites with different Subnets? I am just looking for ideas, not solutions. Just some guidance, since I am a student. 

    I haven't personally used EoMPLS, but it seems a viable option.  The other L2 extension technologies to consider are:
    VPLS
    OTV (ASR1k or CSR1k)
    L2TPv3 (can use regular IOS routers)
    Typically you'd only consider extending L2 VLANs across a WAN for DCI (data center interconnect) and not branch to branch. 
    L2TPv3 is a neat feature that can be done cheaply using 800-series routers.  It does transmit all L2 traffic so it's possible to have spanning tree loops over the WAN (fun in the lab, but not in production).

  • 3750 qos on routed interface

    I have 2 3750G-24 as the core of my voice/data network. I have 2 vlans (voice,data) and it seems like when I cross the routed interfaces (virtual vlanX interfaces) I lose my qos tagging. I have tried route-maps and policy maps but they are not working (the policy maps are not supported on virtual interfaces)
    Anyone with a solution?? I have searched cisco.com and unless i am blind, have not found what I am looking for.

    Here is the edge switchport config-
    End user port-----
    interface FastEthernet0/1
    switchport access vlan 50
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 50
    switchport mode trunk
    switchport voice vlan 10
    mls qos trust device cisco-phone
    mls qos trust cos
    auto qos voip cisco-phone
    wrr-queue bandwidth 20 1 80 1
    wrr-queue min-reserve 1 5
    wrr-queue min-reserve 2 6
    wrr-queue min-reserve 3 7
    wrr-queue min-reserve 4 8
    wrr-queue cos-map 1 0 1 2 4
    wrr-queue cos-map 3 3 6 7
    wrr-queue cos-map 4 5
    priority-queue out
    spanning-tree portfast
    Gigabit uplink port------------
    interface GigabitEthernet0/1
    switchport trunk encapsulation dot1q
    switchport mode trunk
    mls qos trust cos
    auto qos voip trust
    wrr-queue bandwidth 20 1 80 1
    wrr-queue queue-limit 80 1 20 1
    wrr-queue cos-map 1 0 1 2 4
    wrr-queue cos-map 3 3 6 7
    wrr-queue cos-map 4 5
    priority-queue out
    end
    Here is the core switch-
    interface GigabitEthernet1/0/24
    switchport trunk encapsulation dot1q
    switchport mode trunk
    srr-queue bandwidth share 10 10 60 20
    srr-queue bandwidth shape 10 0 0 0
    mls qos trust cos
    no mdix auto
    auto qos voip trust
    end
    Core Vlan Interfaces----
    interface Vlan1
    no ip address
    interface Vlan2
    description Data Vlan
    ip address 10.199.0.29 255.255.252.0
    interface Vlan10
    description Voice Vlan
    ip address 10.199.10.1 255.255.255.0
    All of the qos settings are a result of using Auto QoS

  • Router Interface Cards - Routing Feature

    Dear Team,
    I have a Cisco 3945 Router and have all the slots available with me. The interface card that I am looking for should have the same functionality as HWIC-2FE.
    I need a 4 or 8 port Routed Ethernet Card. I looked for "VWIC3-4MFT-T1/E1" interface card as I was unable to find 8 port card.
    Please let me know if this card can be used as a Routed Interface Card (I need to terminate different ISP Links on this card).
    Regards,
    Farhan.

    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
    Believe the module you mention provides serial ports, not Ethernet ports.  Also believe it supports routing.
    Higher density Ethernet cards often support routing via VLANs (you can dedicate a VLAN per port), but not as routed ports.
    What you also do, if you have VLAN capable switch, use subinterfaces on a router port to a trunk port on the switch.

  • OTV-Extended VLAN Gateway

    I am working on this design where the DC VLANs that need to be extended to DRC via OTV have their gateways as SVIs on a server agg VSS. So there is no FHRP in DC. The other side (DRC) server aggregation is a pair of VDCs on N7K. See figure for connectivity summary.
    I need to maintain the gateway IP address on both sides for each extended VLAN. So for VLAN100 the gateway in DC is SVI-100 on the VSS pair with IP address 10.0.0.254 while in the DRC side it is an HSRP VIP address of 10.0.0.254. This is required to maintain the server network card configuration once it is moved from DC to DRC.
    In order to avoid tromboning traffic destined across VLANs and prevent it from traversing the OTV link, what possible solutions are available? I have been reading OTV design and best practices documentation and I think FHRP isolation is irrelevant, or is it?

    Although FHRP is not issue here, but you still need to block 'ARP for default gateway' and 'MAC address of default gateway' which is advertised by IS-IS.
    you can refer this link for more details:
    http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro.pdf

  • Private vlan across switches in NX-OS

    Hi,
    I'm trying to make a scenario to span private vlan across multiple switches but I couldn't get this to work in NX-OS N7K.
    My topology is similar to the one in the picture attached.
    I tried to ping from isolated host vlan 201 in switch A to isolated host vlan 202 in switch B. Promiscuous trunk port has been configured to upstream router in Switch A. From switch a to switch b is a normal trunk port.
    But still, I can't establish any connectivity from host vlan 201 to host vlan 202.
    Any suggestion?
    thanks

    Jerry -
    Any idea why? This breaks the ability to use moderately complex ACLs. For example - how would you configure scavenger class traffic to ignore some traffic, and mark other?
    Carole

  • RVS4000 Multiple VLANs Not Routing

    I have a couple RVS4000's and I use one of them as a router on a stick with two VLANs in it.
    Two VLANs works fine.
    However, when I add another VLAN, it will not route it.
    I looked in the routing table and it doesn't show any routes for the new VLAN.
    I can see the routes for the other two VLANs but my third VLAN is nonexistent.
    The most I can get it to do is ping the routers VLAN IP interface.
    I can't access the switches' interface on that VLAN or anything else on the new VLAN.
    Is this a known problem?
    Does this thing only route two VLANs?

    Thanks for the quick reply...
    Here is what I'm working with now (currently works):
    Cable Modem 1 ---> RVS4000 (Master) ---> Swtich (L3)
    Cable Modem 2 ---> RVS4000 (No VLANs) ----> Switch (L3)
    The Master RVS4000 routes all the VLANs (Trunk) and NAT/PAT Internet for the servers.
    The Other RVS4000 is just running the default VLAN and routes NAT/PAT Internet for the clients.
    The L3 switch is an SGE2010P and I distrubte the VLANs through this switch.
    I also have a WAP4410N that is trunked to the Client VLAN right now.
    IP Addressing:
    RVS4000 (Master): 10.1.0.1/24 (VLAN 1)
                                 10.100.0.2/24 (VLAN 100)
    RVS4000 (Clients): 10.100.0.1/24 (VLAN 1 - Router is not aware of the VLANs)
    Switch: 10.1.0.254 (VLAN 1)
                10.100.0.254 (VLAN 100)
    The problem is when I make another VLAN:
    RVS4000 (Master): 10.110.0.2 (VLAN 110)
    Switch: 10.110.0.254 (VLAN 110)
    I am unable to communicate with the new network.
    Nothing shows up in the RVS40000 (Master)'s routing table for the new network.

  • Need basic Help - SG300 with vlan and routing

    Hi,
    i need some basic help with configuring vlan/routing.
    Situation:
    DSL Router - Cisco 300 - XenServer
    192.168.1.253 - 192.168.1.19 - 192.168.1.10 (mgmt ip)
    goal is, to reach from inside xenserver vms the internet.
    vms = 192.168.2.x
    gateway ip = 192.168.2.1
    what i did:
    - configured vlan 102, tagged, with the xenserver port
    - configured on xenserver a network with vlan id 102, attached to the vm
    - this network is conntected to an external bond
    - configured ipva4 interface: vlan102 - Static - IP 192.168.2.1 (this is the gateway ip of the vms)
    - automatic configured IPv4 Route: 192.168.2.0/24 next hop 0.0.0.0, Directly connected
    So at the moment i cant ping from inside a vm to the DSL Router (192.168.2.2 to 192.168.1.253)
    any ideas what i misconfigured or whats wrong?
    cheers,
    -Marco

    Hi Tom,
    ok, that make sense. I can ping the router now inside vms from 192.168.2.x network.
    But i cant ping external adresses, error: Destination net unreachable.
    My other problem i have, i cant reach any server from outside over router portforwarding.
    How do i have to configure the upload port to the dsl router? Is it a access port or a trunk
    port with all vlans (tagged or untagged?) At the moment ive a tagged Trunkport with all vlans.
    IPv4 Interface Table
    Interface
    IP Address Type
    IP Address
    Mask
    Status
    VLAN 1
    Static
    192.168.1.19
    255.255.255.0
    Valid
    Should the VLAN1 ip adress not the router ip adress ? Do i need an additional vlan for
    the router ? At the end i like to change the switch ip from dhcp to static (change automaticly
    when switching to layer 3 mode), but ive to look for the ios commands first.
    What else do i missing ?
    Thanks a lot,
    Marcus

  • Vlan name vs interface vlan ip address

    Hello,
    What is consider for ports to be in the same Vlan subnet, is it Vlan name or the ip address given to the SVI or the subnet advertise for that vlan on a layer 3 switch.  Like for example say have 4  layer 3 switches connected where some ports on each switch are put under vlan 802. The SVI ip address for vlan 802 is different on each switch and under eigrp advertises 802 vlan svi with there subnet. Are all those ports under 802 vlan in the same subnet because the vlan name is still 802 but the svi for each 802 vlan is different subnet just the vlan name is the same.  So that mean I have 4 subnets under vlan 802 or there all act as one subnet because the vlan name is the same?
    Thanks,

    It's not really to do with the name or subnet. It really depends on how the switches are connected.
    So in general terms for any vlan if all the switches are interconnected with -
    1) access port links where each end of the link was in that vlan
    or
    2) trunk links where that vlan was allowed on that link
    or a combination of the above then that vlan would be the same L2 broadcast domain across all your switches.
    Usually it is one subnet per vlan but you can if you want use multiple subnets per vlan although if you do this generally you add secondary addressing to the one L3 SVI for that vlan and have a different SVI per switch.
    However, if your switches are interconnected with - 
    1) access port links where the access port is not that vlan
    2) trunk links but that vlan is not allowed on that link
    3) L3 routed links
    then the vlan is a different vlan per switch.
    From the sounds of what you are describing each switch has it's own vlan with it's own subnet and they are not the same vlan across all the switches.
    Usually it is a good idea if this is the case not to reuse the same vlan number on multiple switches because it just leads to confusion.
    Jon

  • Bill and Routing Interface concurrent program is not processing component

    Hi All,
    While running Bill and Routing Interface concurrent program,not processing the component item(Line Item) from bom_inventory_comps_interface,still it show process flag as 1. where as billing item(Header Item) is successfully done..i have tried with all the option by giving component sequence id and batch id still it is not processing component item..
    Is it recommendable to give bill sequence id and component sequence id in interface table using bom_inventory_component_s sequence..
    I will be very pleased if i listen from u guys... Plz help me in resolving this issue..
    My Header Insert Stmt..
    INSERT INTO apps.bom_bill_of_mtls_interface@system_link_visma
    (assembly_item_id, organization_id,
    alternate_bom_designator, last_update_date,
    last_updated_by, creation_date, created_by,
    revision, item_number, item_description,
    implementation_date, transaction_type,
    process_flag, assembly_type, batch_id
    VALUES (l_inv_item_id, l_org_id,
    NULL, SYSDATE,
    1318, SYSDATE, 1318,
    l_revision, l_item_num, l_description,
    SYSDATE, 'CREATE',
    1, 1, 10003535
    Component Insert stmt
    INSERT INTO apps.bom_inventory_comps_interface@system_link_visma
    (operation_seq_num, component_item_id,
    item_num, basis_type, component_quantity,
    auto_request_material, effectivity_date,
    disable_date, planning_factor,
    component_yield_factor,
    enforce_int_requirements,
    include_in_cost_rollup, wip_supply_type,
    supply_subinventory, supply_locator_id,
    check_atp, optional,
    mutually_exclusive_options,
    low_quantity, high_quantity,
    so_basis, shipping_allowed,
    include_on_ship_docs, required_to_ship,
    required_for_revenue, component_remarks,
    transaction_type, process_flag,
    assembly_item_id, component_item_number,
    batch_id,component_sequence_id
    VALUES (l_operation_seq, l_comp_item_id,
    cur2.item_sequence, l_basis, cur2.quantity,
    l_auto_request_mtls, cur2.from_date,
    cur2.TO_DATE, cur2.planning_factor,
    cur2.yield_factor,
    l_enforce_int_requirements,
    l_include_in_cost_rollup, l_supply_type,
    l_supply_subinventory, NULL,
    l_check_atp, l_optional,
    l_mutually_exclusive_options,
    cur2.minimum_quantity, cur2.maximum_quantity,
    l_sale_order_basis, l_shippable_flag,
    l_include_on_ship_docs, l_required_to_ship,
    l_required_for_revenue, cur2.comments,
    'CREATE', 1,
    l_inv_item_id, l_comp_item_num,
    10003535,apps.bom_inventory_components_s.nextval@system_link_visma
    For Subcomponent Insert Stmt
    INSERT INTO apps.bom_sub_comps_interface@system_link_visma
    (substitute_component_id,
    substitute_item_quantity,
    assembly_item_id, component_item_id,
    operation_seq_num, organization_id,
    substitute_comp_number,
    component_item_number,
    assembly_item_number,
    transaction_type, process_flag,
    enforce_int_requirements,
    effectivity_date,component_sequence_id,batch_id
    VALUES (l_sub_comp_item_id,
    cur3.quantity,
    l_inv_item_id, l_comp_item_id,
    cur2.operation_sequence, l_org_id,
    l_sub_comp_item_num,
    l_comp_item_num,
    l_item_num,
    'CREATE', 1,
    l_enforce_int_requirements,
    SYSDATE,apps.bom_inventory_components_s.currval@system_link_visma,10003535
    Thanks
    Raman Sharma
    Edited by: 929841 on May 4, 2012 12:28 AM
    Edited by: 929841 on May 4, 2012 2:58 AM

    You need to populate the organization_id or organization_code in bom_inventory_comps_interface.
    Here is a minimal insert
    INSERT INTO bom.bom_inventory_comps_interface
                (operation_seq_num, last_update_date, last_updated_by,
                 creation_date, created_by, process_flag, transaction_type,
                 bom_item_type,
                 effectivity_date, organization_code, assembly_item_number,
                 item_num, component_item_number, component_quantity
         VALUES (1                                                   -- op_seq_num
                 ,SYSDATE, 1433
                 ,SYSDATE, 1433, 1                                  -- process_flag
                 ,'Create',
                 4 -- bom_item_type 1 Model; 2 Option class; 3 Planning; 4 Standard; 5 Product family
                 ,SYSDATE - 1, 'PUB', 'SSGPARENT1'          -- assembly_item_number
                 ,10                                                     --item_num
                 , 'SSGCOMP1'                           -- component_item_number
                 , 10                                          --qty
                )Sandeep Gandhi

Maybe you are looking for