Switching

last person joined: yesterday 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.

  • 1.  Problem with vlans merging one core to another core

    Posted 10-28-2016 05:30

    So we have a COLO core in the 10.20.9.254/24, and we are moving the entire server farm attached to this core to our corporate MDF, which has a core of 10.11.9.254/24. I want to change the vlan IDs to the COLO segments, and merge to the CORPORATE core.

     

    I beliwve this will work, just wanted some of the guru's to check my details.

    So 10.20.0.0 ---->  10.11.0.0  changing the vlan id by adding 200 to it's current value.

     

    FROM CORE 10.11.9.254/24 current
set interfaces vlan unit 1 family inet address 10.1.0.1/16
set interfaces vlan unit 2 family inet address 10.2.0.253/16
set interfaces vlan unit 3 family inet address 10.3.0.253/16
set interfaces vlan unit 9 family inet address 10.11.9.254/24
set interfaces vlan unit 10 family inet address 10.11.10.254/24
set interfaces vlan unit 11 family inet address 10.11.11.254/24
set interfaces vlan unit 12 family inet address 10.11.12.254/24
set interfaces vlan unit 13 family inet address 10.11.13.254/24
set interfaces vlan unit 20 family inet address 10.11.20.254/24
set interfaces vlan unit 30 family inet address 10.11.30.254/24
set interfaces vlan unit 32 family inet address 10.11.32.254/24
set interfaces vlan unit 33 family inet address 10.11.33.254/24
set interfaces vlan unit 34 family inet address 10.11.34.254/24
set interfaces vlan unit 35 family inet address 10.11.35.254/24
set interfaces vlan unit 60 family inet address 10.10.60.254/24
set interfaces vlan unit 110 family inet address 10.11.110.254/24


FROM CORE 10.20.9.254/24 current
set interfaces vlan unit 9 family inet address 10.20.9.254/24
set interfaces vlan unit 10 family inet address 10.20.10.254/24
set interfaces vlan unit 11 family inet address 10.20.11.254/24
set interfaces vlan unit 12 family inet address 10.20.12.254/24
set interfaces vlan unit 13 family inet address 10.20.13.254/24
set interfaces vlan unit 20 family inet address 10.20.20.254/24
set interfaces vlan unit 30 family inet address 10.20.30.254/24
set interfaces vlan unit 32 family inet address 10.20.32.254/24
set interfaces vlan unit 33 family inet address 10.20.33.254/24
set interfaces vlan unit 100 family inet address 10.20.100.254/24


PROPOSED CHANGE for CORE 10.20.9.254/24 above
set interfaces vlan unit 209 family inet address 10.20.9.254/24
set interfaces vlan unit 210 family inet address 10.20.10.254/24
set interfaces vlan unit 211 family inet address 10.20.11.254/24
set interfaces vlan unit 212 family inet address 10.20.12.254/24
set interfaces vlan unit 213 family inet address 10.20.13.254/24
set interfaces vlan unit 220 family inet address 10.20.20.254/24
set interfaces vlan unit 230 family inet address 10.20.30.254/24
set interfaces vlan unit 232 family inet address 10.20.32.254/24
set interfaces vlan unit 233 family inet address 10.20.33.254/24
set interfaces vlan unit 200 family inet address 10.20.100.254/24



FROM CORE 10.11.9.254/24 current
set vlans NETWORK-9 description "Network Infrastructure Devices (Routers, Switches, FW)"
set vlans NETWORK-9 vlan-id 9
set vlans NETWORK-9 l3-interface vlan.9
set vlans SERVERS vlan-id 2
set vlans SERVERS l3-interface vlan.2
set vlans SRV-10-GENERAL description "Servers - General (DHCP, AD, File, Print, Utility)"
set vlans SRV-10-GENERAL vlan-id 10
set vlans SRV-10-GENERAL l3-interface vlan.10
set vlans SRV-11-DB description "Servers - Database (Microsoft SQL, mySQL)"
set vlans SRV-11-DB vlan-id 11
set vlans SRV-11-DB l3-interface vlan.11
set vlans SRV-12-CITRIX description "Servers - Citrix & Terminal Servers"
set vlans SRV-12-CITRIX vlan-id 12
set vlans SRV-12-CITRIX l3-interface vlan.12
set vlans SRV-13-APP description "Servers - Application Front-End (IIS, Apache)"
set vlans SRV-13-APP vlan-id 13
set vlans SRV-13-APP l3-interface vlan.13
set vlans SRV-20-DEV description "Servers - Development & QA"
set vlans SRV-20-DEV vlan-id 20
set vlans SRV-20-DEV l3-interface vlan.20
set vlans UTILITY-30-iSCSI description "Utility - iSCSI Storage Traffic 1GbE (SAN, iSCSI traffic)"
set vlans UTILITY-30-iSCSI vlan-id 30
set vlans UTILITY-30-iSCSI l3-interface vlan.30
set vlans UTILITY-31-vMOTION description "Utility - VMware vMotion Traffic (VM & Storage vMotion)"
set vlans UTILITY-31-vMOTION vlan-id 31
set vlans UTILITY-32-DBLTAKE description "Utility - Double-Take Replication"
set vlans UTILITY-32-DBLTAKE vlan-id 32
set vlans UTILITY-32-DBLTAKE l3-interface vlan.32
set vlans UTILITY-33-MGMT description "Utility - Management Devices (HP iLO, Dell DRAC, IP KVM, PDUs)"
set vlans UTILITY-33-MGMT vlan-id 33
set vlans UTILITY-33-MGMT l3-interface vlan.33
set vlans UTILITY-34-vFT description "Utility- VMware Fault Tolerance"
set vlans UTILITY-34-vFT vlan-id 34
set vlans UTILITY-34-vFT l3-interface vlan.34
set vlans UTILITY-35-iSCSI10 description "Utility - iSCSI Storage Traffic 10GbE (SAN, iSCSI traffic)"
set vlans UTILITY-35-iSCSI10 vlan-id 35
set vlans UTILITY-35-iSCSI10 l3-interface vlan.35
set vlans VOIP-60-SAMSUNG vlan-id 60
set vlans VOIP-60-SAMSUNG l3-interface vlan.60
set vlans WORKSTATIONS_PRINTERS description "Workstations and Printers"
set vlans WORKSTATIONS_PRINTERS vlan-id 3
set vlans WORKSTATIONS_PRINTERS l3-interface vlan.3





FROM CORE 10.20.9.254/24 current
set vlans CLIENT-100-GEN vlan-id 100
set vlans CLIENT-100-GEN l3-interface vlan.100
set vlans NETWORK-9 vlan-id 9
set vlans NETWORK-9 l3-interface vlan.9
set vlans SRV-10-GENERAL vlan-id 10
set vlans SRV-10-GENERAL l3-interface vlan.10
set vlans SRV-11-DB vlan-id 11
set vlans SRV-11-DB l3-interface vlan.11
set vlans SRV-12-CITRIX vlan-id 12
set vlans SRV-12-CITRIX l3-interface vlan.12
set vlans SRV-13-APP vlan-id 13
set vlans SRV-13-APP l3-interface vlan.13
set vlans SRV-20-DEV vlan-id 20
set vlans SRV-20-DEV l3-interface vlan.20
set vlans UTILITY-30-iSCSI vlan-id 30
set vlans UTILITY-30-iSCSI l3-interface vlan.30
set vlans UTILITY-31-vMOTION vlan-id 31
set vlans UTILITY-32-DBLTAKE vlan-id 32
set vlans UTILITY-32-DBLTAKE l3-interface vlan.32
set vlans UTILITY-33-MGMT vlan-id 33
set vlans UTILITY-33-MGMT l3-interface vlan.33


PROPOSED CHANGE for CORE 10.20.9.254/24 above
set vlans CLIENT-200-GEN vlan-id 200
set vlans CLIENT-100-GEN l3-interface vlan.200
set vlans NETWORK-209 vlan-id 209
set vlans NETWORK-9 l3-interface vlan.209
set vlans SRV-210-GENERAL vlan-id 210
set vlans SRV-210-GENERAL l3-interface vlan.210
set vlans SRV-211-DB vlan-id 211
set vlans SRV-211-DB l3-interface vlan.211
set vlans SRV-212-CITRIX vlan-id 212
set vlans SRV-212-CITRIX l3-interface vlan.212
set vlans SRV-213-APP vlan-id 213
set vlans SRV-213-APP l3-interface vlan.213
set vlans SRV-220-DEV vlan-id 220
set vlans SRV-220-DEV l3-interface vlan.220
set vlans UTILITY-230-iSCSI vlan-id 230
set vlans UTILITY-230-iSCSI l3-interface vlan.230
set vlans UTILITY-231-vMOTION vlan-id 231
set vlans UTILITY-232-DBLTAKE vlan-id 232
set vlans UTILITY-232-DBLTAKE l3-interface vlan.232
set vlans UTILITY-233-MGMT vlan-id 233
set vlans UTILITY-33-MGMT l3-interface vlan.33


  • 2.  RE: Problem with vlans merging one core to another core
    Best Answer

    Posted 10-29-2016 05:05

    Looks good, but you seem to have a typo in the last VLAN update

     

    set vlans UTILITY-233-MGMT vlan-id 233
set vlans UTILITY-33-MGMT l3-interface vlan.33

    should be
    set vlans UTILITY-233-MGMT vlan-id 233
set vlans UTILITY-233-MGMT l3-interface vlan.233


  • 3.  RE: Problem with vlans merging one core to another core

    Posted 11-01-2016 15:29

    Steve,

     

    IF I take the config, and add new ports, but keep the active ports as they are, then do a load overide.term.

    Will that cause the switch to drop the active ports for a couple seconds.?



  • 4.  RE: Problem with vlans merging one core to another core

    Posted 11-01-2016 15:47

    When you have the final configuration loaded as the Candidate config do a compare to the running config

     

    #show | compare

     

    The sections of the config that show the - sign to delete followed by the + sign to add the revised configuration will bounce.

     

    New config with the + sign only will simply be added.

     

    Any existing config that does not show up in the compare will have no change during a standard commit.

     

    Using commit full will force the update of the entire config with a bounce then for all settings.



  • 5.  RE: Problem with vlans merging one core to another core

    Posted 11-02-2016 17:40

    Steve,

     

    thanks

     

    Best Wishes