Announcement

Collapse
No announcement yet.

vlan configuration

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • vlan configuration

    Hi ,

    we are using Cisco 3750 Series L3 Switch and we need to create multiple vlan on this switch. Is it possible that we can make a single port as a member of multiple vlan , as this is a citrix infrastructure and we need a storage connectivity with all the servers.

    please help..

  • #2
    Re: vlan configuration

    A trunk port can carry traffic for all VLAN's or specific VLAN's, but your question doesn't make sense. What do the servers connecting to storage have to do with multiple VLAN's? The storage and the servers should all have a connection to each other in the same VLAN.

    Comment


    • #3
      Re: vlan configuration

      Originally posted by kathy View Post
      we are using Cisco 3750 Series L3 Switch and we need to create multiple vlan on this switch. Is it possible that we can make a single port as a member of multiple vlan , as this is a citrix infrastructure and we need a storage connectivity with all the servers.
      A port cannot be a member of two different access VLANs simultaneously. It can, however, be a trunk.

      If you need to keep the Citrix servers in separate zones while at the same time giving them access to a storage system, they will need separate connections to separate VLANs. That doesn't mean you'll need two physical connections, just make the port a VLAN trunk port. Provided the NIC driver or the OS supports 802.1q tagging, you can then create a virtual NIC with the appropriate VLAN number.

      Comment


      • #4
        Re: vlan configuration

        Hi ,

        Will it be possible , that we can make more than one port as a trunk port. Basically in my case here is the scenario

        There is only single ISP Gateway available and there are 6 Xen Servers . Now on all the xen servers there are about 2 separate domain controller system - virtual machine is running , and there are about 100 vm are member in each domain (abc.com , xyz.com , pqr.com ). There is only a single iomega storage of 8 TB in which all the vm are created , So Now i just want to segregate those dc traffic and make a separate dhcp server so that if a vm start they will be able to get the ip from their dhcp server in differant subnet. At present its everything in a same subnet as 172.30.5.0/24

        Now i want to make it like this..


        ISP router 172.30.5.1

        abc.com in 172.30.6.1

        xyz.com in 172.30.7.1

        pqr.com in 172.30.8.1

        All Xen server are having a 4 Ethernet card and all of them are connected to a common cisco 3750x Layer 3 switch. storage and isp firewall is also connected on same switch.

        So how can we implement vlan in this type of case...

        please help...

        thanks...

        Comment


        • #5
          Re: vlan configuration

          Hi ,

          We have just purchase the Cisco 3750x Layer 3 switch and implement ip services option enable on this to be able to allow inter vlan traffic.

          thanks

          Comment


          • #6
            Re: vlan configuration

            Hi ,

            Will it be fine , if i am creating a vlan and associate the the subnet address on swich and not binding that address to a specific switch port and then create a same vlan number on citrix xen server ..will it work ...will it be able to pass the traffic after matching the vlan number on citrix with cisco switch.


            just a example...

            interface Vlan100
            Ip address 172.30.5.1 255.255.255.0

            interface Vlan101
            Ip address 172.20.6.1 255.255.255.0

            please help...

            thanks...

            Comment


            • #7
              Re: vlan configuration

              In addition to creating the virtual interface 'vlanxxx' with it's ip address, you'll also need to add the vlan info to the vlan database, which is not part of the startup or running configs. The dbase is stored in your system flash under the name 'vlan.dat'.

              First, look at what's there now, from an elevated prompt, use: 'sh vlan' and you'll get a summary screen showing known vlans, their names and physical ports assigned to each.

              To add a new vlan and give it a name, from the same elevated prompt:
              vlan 100 <enter>
              name ISP <enter>
              vlan 101 <enter>
              name ABC <enter>
              and so on.
              *RicklesP*
              MSCA (2003/XP), Security+, CCNA

              ** Remember: credit where credit is due, and reputation points as appropriate **

              Comment


              • #8
                Re: vlan configuration

                "Will it be fine , if i am creating a vlan and associate the the subnet address on swich and not binding that address to a specific switch port and then create a same vlan number on citrix xen server ..will it work ...will it be able to pass the traffic after matching the vlan number on citrix with cisco switch."

                It is totally fine to do not bind the IP address to VLAN and do not have any physical port members assigned to particular VLAN. VLAN members should see each other via trunk posts. I never try to use VLANs like you trying to use - with Citrix clients connected to the same physical port on the switch to trunk interface, but as I understand, it should work the same way as if lets say you have another switch connected to that trunk port and that another switch has a couple ports assigned to different VLANs.

                Comment


                • #9
                  Re: vlan configuration

                  What tank says is partly true, but only if you are NOT using your switches as Layer 3 devices. If those switches must do the routing, they MUST hold addresses in the VLANs they route to/from. Otherwise they have no idea where the routes go.

                  If your switches are only pure switches at Layer 2 because you use a different device as your router, then add the VLANs to the vlan database (on each switch) as stated previously, then assign a vlan to a port for the PCs. For multiple VLANs on one port, put that port in trunk mode, at each end of that link.

                  tank: Since the OP was specifying the switches as L3 and was asking about intervlan traffic, the assumption was that the switches were the routing solution.
                  *RicklesP*
                  MSCA (2003/XP), Security+, CCNA

                  ** Remember: credit where credit is due, and reputation points as appropriate **

                  Comment


                  • #10
                    Re: vlan configuration

                    Originally posted by RicklesP View Post
                    What tank says is partly true, but only if you are NOT using your switches as Layer 3 devices. If those switches must do the routing, they MUST hold addresses in the VLANs they route to/from. Otherwise they have no idea where the routes go.

                    If your switches are only pure switches at Layer 2 because you use a different device as your router, then add the VLANs to the vlan database (on each switch) as stated previously, then assign a vlan to a port for the PCs. For multiple VLANs on one port, put that port in trunk mode, at each end of that link.

                    tank: Since the OP was specifying the switches as L3 and was asking about intervlan traffic, the assumption was that the switches were the routing solution.
                    You are right Rickles, my recomendadions good for layer 2 switchs only, I did not pay attention that we are talking about layer 3 switches. Thanks!

                    Comment

                    Working...
                    X