DHCP in 6509E in VSS mode

Hi,
I am in the process of installing two 6509Es in VSS mode. Our enviroment uses the core switches as the DHCP server for the IP Phones; however, I was wondering how this would work in case they go on standalone mode. Which one would be the dhcp server in this case? Or, will both act as dhcp server? something I don't believe since they won't know which IP has been already assigned creating multiple conflicts.
Is this possible?
Thanks in advanced.

Hi,
I think you should use a SXJ Software.

Similar Messages

  • FWSM Active/Standby in VSS mode

    hello,
    i do have two 6500 in VSS mode , and one FWSM module on each 6500, i want to configure these modules as Active/Standby, how do i start , should i  follow this (not in VSS mode):
    http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/fail_f.html
    or are there other things should i do to make it work,
    thanks

    up!

  • CS-MANAGER: Catalyst 6500 in VSS mode not supported????

    We have recently moved from CSM 3.2 to CSM 3.3.1 Service Pack 3.
    We are now trying to add a Cisco Catalyst 6513 configured in VSS mode using 12.2(33)SXI5 software. When we try to add th device from network, it starts Discovering the configurations, and when it reaches the 15%, we got the message "Discovery Failed - Invalid Device: Catalyst in VSS mode is not Supported"
    I´ve attached to this post the screenshot showing the error
    Any idea of what can i do to manage this device on CSM??
    BEst Regards,
    Nicolás

    Hello Nicolas
    VSS is not supported even in the latest CSM release 4.1 AFAIK
    http://www.cisco.com/en/US/docs/security/security_management/cisco_security_manager/security_manager/4.1/compatibility/information/csmsd410.html
    Check with your Cisco account team whether it is going to be added anytime soon.
    Please rate if you find the input helpful.
    Regards
    Farrukh

  • Installing New network card on a Cisco Catalyst 6500 VSS mode

    Hi All.
    I need to install a new network card on Cisco Catalyst 6500 VSS mode, I need to follow any special procedures or is it only insert the new card and the Catalyst automatically recognizes the card?
    Thank you So mucho. 

    Hi,
    Just insert the blade and the switch should recognize it. For the 6500 series the blades are hot swap able.
    HTH

  • WLC5508 with SW6500 VSS mode

    Hi all,
    Unfortunatelly, I haven't enough experience on CISCO wireless controller and I'm not able to find an official answer for this question:
    My customer has two SW6500 on VSS mode connected via VSL. I wish to know if anyone have already connected WLC5508 with SW6500 VSS using LAG feature ?
    I wish to connect one uplink from LAG to the first switch and the second uplink to the other. The two switches are considered like one logical software.
    I have already read the best practice from CISCO when we connect a 5508 to a switch regarding the port-channel but nothing regarding VSS and VSL link.
    Thanks in advance.

    It does work as long as the two chassis are in vss:)  Make sure the the etherchannel load balancing is configured for src--dst-ip
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • CatC6K in VSS mode / interface modules provisionning after reboot

    Hello,
    I am using 2 Cat 6509 in VSS mode. Everything is OK. My problem is the following : it takes interface modules approximately 15 min to be detected and brought up after rebooting of one physical switch. Is this normal ? I found nothing in the documentation related to this point.
    Is there any tuning available to reduce this time ?
    Thank you for your help, kind regards,

    Assume the installation disk is an OS X disk? If it's the original one that came with the system (grey-colored disk versus black retail disk) have you tried to hold the alt key down when you boot? This would allow you to choose the Apple hardware test. If you can do this, choose the Apple hardware test, click the arrow to the right, and when prompted choose the extended test. Does that give you any errors or messages about a hardware problem?
    Are you able to hold the C key down when you reboot, to boot off the installation disk?

  • Issues with deploying 6880-X in VSS Mode

    Hi Everyone,
    I wanted to query the support community to see if folks are encountering issues in deploying the 6880-X in VSS mode.  We first looked at this soluition when it was running 15.1(2) SY2 as the recommened GA code.  We ran into several issues:
    1) VSL Link Timeout - Workaround:modify LMP timer or upgrade to 15.1(2)SY4
    2) Port-member goes into suspendstate when using 1000BASE-SX - shut/no shut suspended interface
    We ran into this and some other issues even with the eFSU upgrade process.  So my question is have you run into similiar difficulties in running the 6880 in VSS mode.  Did you go ahead and deploy?  If so did you deploy with 15.1(2)SY4 (new Cisco GA code) or did you live with the state you are in?
    Were there ways that you mitigated these issues?
    Thanks,
    Patnaik

    Hi Reza,
    Here you go.  Just so you know I resolved the suspended port-member by OIR the optic that was displayed as a 10G interface.
    lab6880#sh run inter te1/3/14
    Building configuration...
    Current configuration : 1546 bytes
    interface TenGigabitEthernet1/3/14
     no switchport
     mtu 9216
     no ip address
     no ip proxy-arp
     platform qos queue-mode mode-dscp
     wrr-queue bandwidth 100 150 125 150 0 0 100 
     wrr-queue queue-limit 20 40 10 10 0 0 5 
     wrr-queue random-detect min-threshold 1 50 60 80 100 
     wrr-queue random-detect min-threshold 2 70 100 100 100 
     wrr-queue random-detect min-threshold 3 70 100 100 100 
     wrr-queue cos-map 4 1 3 
     wrr-queue cos-map 5 1 4 
     wrr-queue dscp-map 1 1 1 2 3 4 5 6 7 8 
     wrr-queue dscp-map 1 1 9 11 13 15 16 17 19 21 
     wrr-queue dscp-map 1 1 23 25 27 29 31 33 35 37 
     wrr-queue dscp-map 1 1 39 41 42 43 44 45 47 49 
     wrr-queue dscp-map 1 1 50 51 52 53 54 55 57 58 
     wrr-queue dscp-map 1 1 59 60 61 62 63 
     wrr-queue dscp-map 1 2 0 
     wrr-queue dscp-map 2 1 10 12 14 
     wrr-queue dscp-map 3 1 18 20 22 
     wrr-queue dscp-map 3 2 26 28 30 
     wrr-queue dscp-map 4 1 24 32 34 36 38 
     wrr-queue dscp-map 7 1 48 56 
     rcv-queue dscp-map 1 1 1 2 3 4 5 6 7 8 
     rcv-queue dscp-map 1 1 9 11 13 15 17 19 21 23 
     rcv-queue dscp-map 1 1 25 27 29 31 33 35 37 39 
     rcv-queue dscp-map 1 1 41 42 43 44 45 47 49 50 
     rcv-queue dscp-map 1 1 51 52 53 54 55 57 58 59 
     rcv-queue dscp-map 1 1 60 61 62 63 
     rcv-queue dscp-map 1 2 0 
     rcv-queue dscp-map 1 3 16 
     rcv-queue dscp-map 2 1 10 12 14 
     rcv-queue dscp-map 3 1 18 20 22 
     rcv-queue dscp-map 3 2 26 28 30 
     rcv-queue dscp-map 4 1 24 32 34 36 38 
     rcv-queue dscp-map 7 1 48 56 
     macro description UPLINK
     arp timeout 300
     channel-group 100 mode active
    end
    lab6880#sh run inter te2/5/14
    Building configuration...
    Current configuration : 1546 bytes
    interface TenGigabitEthernet2/5/14
     no switchport
     mtu 9216
     no ip address
     no ip proxy-arp
     platform qos queue-mode mode-dscp
     wrr-queue bandwidth 100 150 125 150 0 0 100 
     wrr-queue queue-limit 20 40 10 10 0 0 5 
     wrr-queue random-detect min-threshold 1 50 60 80 100 
     wrr-queue random-detect min-threshold 2 70 100 100 100 
     wrr-queue random-detect min-threshold 3 70 100 100 100 
     wrr-queue cos-map 4 1 3 
     wrr-queue cos-map 5 1 4 
     wrr-queue dscp-map 1 1 1 2 3 4 5 6 7 8 
     wrr-queue dscp-map 1 1 9 11 13 15 16 17 19 21 
     wrr-queue dscp-map 1 1 23 25 27 29 31 33 35 37 
     wrr-queue dscp-map 1 1 39 41 42 43 44 45 47 49 
     wrr-queue dscp-map 1 1 50 51 52 53 54 55 57 58 
     wrr-queue dscp-map 1 1 59 60 61 62 63 
     wrr-queue dscp-map 1 2 0 
     wrr-queue dscp-map 2 1 10 12 14 
     wrr-queue dscp-map 3 1 18 20 22 
     wrr-queue dscp-map 3 2 26 28 30 
     wrr-queue dscp-map 4 1 24 32 34 36 38 
     wrr-queue dscp-map 7 1 48 56 
     rcv-queue dscp-map 1 1 1 2 3 4 5 6 7 8 
     rcv-queue dscp-map 1 1 9 11 13 15 17 19 21 23 
     rcv-queue dscp-map 1 1 25 27 29 31 33 35 37 39 
     rcv-queue dscp-map 1 1 41 42 43 44 45 47 49 50 
     rcv-queue dscp-map 1 1 51 52 53 54 55 57 58 59 
     rcv-queue dscp-map 1 1 60 61 62 63 
     rcv-queue dscp-map 1 2 0 
     rcv-queue dscp-map 1 3 16 
     rcv-queue dscp-map 2 1 10 12 14 
     rcv-queue dscp-map 3 1 18 20 22 
     rcv-queue dscp-map 3 2 26 28 30 
     rcv-queue dscp-map 4 1 24 32 34 36 38 
     rcv-queue dscp-map 7 1 48 56 
     macro description UPLINK
     arp timeout 300
     channel-group 100 mode active
    end
    interface Port-channel100
     no switchport
     dampening 20
     mtu 9216
     ip address 172.16.2.250 255.255.255.254
     ip pim sparse-dense-mode
     ip ospf network point-to-point
     logging event link-status
     logging event nfas-status
     logging event bundle-status
     load-interval 30
     carrier-delay msec 0

  • Upgrading 6509 in VSS mode

    Hi guys,
    we have two 6509 running in VSS mode and we encountered the bug described here
    https://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtc41114
    so basically we can't ssh into the chassis.
    So we're planing on upgrading the chassis to fix it, which I couldn't practice in lab...
    The current image is "sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI3.bin" and we wou'd like to upgrade to s72033-ipservicesk9_wan-mz.122-33.SXI8.
    I read the guidelines for upgrading here http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vss.html#wp1172503
    but I noticed something I'm not familiar with :
    eFSU Upgrade on an Installed Modular Image Example
    This example shows how to perform an an eFSU upgrade on an installed modular image:
    Router# copy ftp://172.18.108.26/s72033-advipservicesk9_wan-vz.122-33.SXI2 sup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin
    Router# copy ftp://172.18.108.26/s72033-advipservicesk9_wan-vz.122-33.SXI2 slavesup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin
    Router# install file sup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin sup-bootdisk:/newsys
    Router# install file slavesup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin slavesup-bootdisk:/newsys
    The thing is, the install command is not available on my switch :
    ecore#ins?
    % Unrecognized command
    So I guess I'm not running a modular IOS.
    I read a bunch of things about monolithic and modular IOS but I'm kinda lost here...
    Could you tell me how can I tell the difference between a modular and a monolithic image?
    And in my case, what should I do after copying the image on the sup-bootdisks?
    Is there any other impact on the upgrade process?
    Thank you for your answers!!
    by
    Sim

    Hi Friend,
    I believe this is what you want.
    http://www.cisco.com/en/US/partner/products/hw/switches/ps708/products_configuration_guide_chapter09186a008022f2d7.html#wp1071832
    Just follow the instructions and you will be good to go.
    HTH
    Ankur

  • 6880 in VSS Mode and OSPF maximum paths

    Hi Folks,
    I have an issue observed in testing.  We have implemented a VSS solution on the 6880-X-LE.  We have two MEC L3 PO's upstream and thus two OSPF path's for our default route.  After creating an event in the lab to put the boxes in Active - Active (pulled VSL links off SW1) and then go through the process of restoring the VSS (put VSL links back in) I noticed my additional path did not restore.
    From the restoration perspective, it went as follows:
    Sw1 - Active SW2-standby - pull VSL links
    VSL PO goes down
    SW1 - Active SW2 - Active (sub second traffic impact)
    SW1 - enters recovery mode SW2 - Active
    VSL links back in  - VSL PO up
    SW1 - reboots and comes up standby SW2 - Active
    Routing table now only shows entry for PO200 and no routes can go out PO100.
    6880#sh ip route
    <cut>  
    0.0.0.0/0 [110/1000] via 192.168.0.253, 00:38:34, Port-channel200
          1.0.0.0/24 is subnetted, 2 subnets
    O        1.1.1.0 [110/151] via 10.86.50.253, 00:31:55, Port-channel200
    O        1.1.2.0 [110/151] via 10.86.50.253, 00:31:55, Port-channel200
          192.168.0.0/16 is variably subnetted, 59 subnets, 8 masks
    O        192.168.1.0/25 [110/150] via 1192.168.0.253, 00:31:55, Port-channel200
    O        192.168.1.128/25 [110/350] via 192.168.0.253, 00:31:55, Port-channel200
    O        192.168..3.0/25 [110/350] via 192.168.0.253, 00:31:55, Port-channel200
    6880#sh ip ospf ne
    Neighbor ID     Pri   State           Dead Time   Address         Interface
    192.168.0.253     0   FULL/  -        00:00:31    192..168.50.253    Port-channel200
    192.168.0.251     0   FULL/  -        00:00:32    192.168.50.251    Port-channel100
    Can anyone help? 
    Thanks,
    Rash

    Hi Reza,
    I can't post the configuration. However, I can tell you that I have a TAC case open with Cisco and they agree with me that this behavior requires further investigation.  So the "PO" in question disappears seems to match when I get the error related to the a port-member not being compatible:
    Jan 26 15:18:17 est: %EC-SW2_STBY-5-CANNOT_BUNDLE2: Te2/3/14 is not compatible with Te1/5/14 and will be suspended (speed of Te2/3/14 is 10G, Te1/5/14 is 1000M)
    So what happens is that in PO100 you'll see only one bundled port and the other is suspended.  This causes OSPF to withdraw the PO from the routing table (hypothesis but reproducible).  
    In our trial production launch, I performed the same test above redundancy force-switchover and you'll see both entries in the routing-table. Once the other modules come up and I get a suspended port-member that particular PO disappears from the routing table. 
    If you shut/no shut that PO, the PO returns as an available path in the routing table.  In production we are not using GLC-T (as in the lab) but are using GLC-SX-MM.  The bug that puts this member into a suspended state falls under the this bug id:
    CSCur17071
    What I missed initially is the fact, that the routing table removes that PO from being an available path even though it still has an active port-member.
    Cheers,
    Rash

  • ACE card reboots in VSS mode

    Hello, and sorry for the lenghty message.
    Yesterday we implemented VSS in our network and encountered a problem with the ACE module that I am trying to resolve.
    Here's the hardware layout
    two 6509 with the following line cards:
    Mod Ports Card Type                              Model              Serial No.
      1   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1329U0TN
      2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1327T950
      3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1325SHWN
      5    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAL1327T9A7
      6   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1328TM43
      9    1  Application Control Engine Module      ACE20-MOD-K9       SAD133201AN
      1  Centralized Forwarding Card WS-F6700-CFC       SAL1327TH0F  4.1    Ok
      2  Centralized Forwarding Card WS-F6700-CFC       SAL1317NUCC  4.1    Ok
      3  Centralized Forwarding Card WS-F6700-CFC       SAL1322R6K6  4.1    Ok
      5  Policy Feature Card 3       VS-F6K-PFC3C       SAL1326T3ME  1.0    Ok
      5  MSFC3 Daughterboard         VS-F6K-MSFC3       SAL1326T183  2.0    Ok
      6  Centralized Forwarding Card WS-F6700-CFC       SAL1327TA00  4.1    Ok
    Mod  Online Diag Status
      1  Pass
      2  Pass
      3  Pass
      5  Pass
      6  Pass
      9  Pass --More--
    Switch Number:     2   Role:  Virtual Switch Standby
    Mod Ports Card Type                              Model              Serial No.
      2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1327TG40
      3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1328TM1R
      4   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1328TQCP
      5    5  Supervisor Engine 720 10GE (Hot)       VS-S720-10G        SAL1327T9B1
      6   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1328TQDS
      8   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL1324S80K
      9    1  Application Control Engine Module      ACE20-MOD-K9       SAD133201A3
      2  Centralized Forwarding Card WS-F6700-CFC       SAL1327T9ZY  4.1    Ok
      3  Centralized Forwarding Card WS-F6700-CFC       SAL1327T80P  4.1    Ok
      4  Centralized Forwarding Card WS-F6700-CFC       SAL1327TCWJ  4.1    Ok
      5  Policy Feature Card 3       VS-F6K-PFC3C       SAL1327T9X8  1.0    Ok
      5  MSFC3 Daughterboard         VS-F6K-MSFC3       SAL1326T4QY  2.0    Ok
      6  Centralized Forwarding Card WS-F6700-CFC       SAL1326T2GC  4.1    Ok
      8  Centralized Forwarding Card WS-F6700-CFC       SAL1252EA2J  4.1    PwrDown
    Mod  Online Diag Status
      2  Pass
      3  Pass
      4  Pass
      5  Pass
      6  Pass
      8  Not Applicable
      9  Not Applicable
    =================================================
    Here's the problem:
    On the standby switch 2, the ACE module keeps rebooting. I first thought may be the power was not sufficient, so I checked the power utilization, and I have about 425 watts available.
    I shut the power to one of the 10/100/1000 line card and I still had the same problem.
    I moved the ACE module to SW1, trying to see if it would follow the problem and it did not have any issues.
    I shut down two (2) modules on switch 2, and I still have the same problem.
    Here's the log:
    odulee
    sm(cygnus_oir_bay slot9), running yes, state wait_til_online
    Last transition recorded: (disabled)-> stay_disabled (operator_power_on)-> can_p
    ower_on (yes_power)-> powered_on (real_power_on)-> check_power_on (timer)-> chec
    k_power_on (power_on_ok)-> wait_til_online (reset_timer_online)-> wait_til_onlin
    e (reset_timer_online)-> wait_til_online (reset_timer_online)-> wait_til_online
    (reset_timer_online)-> wait_til_online xit
    N-MSFC-VDR1-PRI#
    Dec 19 13:14:50 UTC: %C6KPWR-SW2_SPSTBY-4-DISABLED: power to module in slot 9 se
    t off (Module  Failed SCP dnld)
    Dec 19 13:14:52 UTC: %SYS-5-CONFIG_I: Configured from console by console
    =================================================================
    Does VSS shut down the ACE module because it sees two cards in one virtual switch?
    Also we have no configuration setting on the either one of the ACE module. We are doing this implementation in phases, and I was planning on applying some basic Load-balancing in a couple of weeks.
    I am not sure if this is a Chassis issue or VSS.
    Any help would greatly be appreciated.

    Hi,
    ACE software version A2(1.2) or later and installed in C6k running IOS 12.2(33)SXI or later support VSS.
    If the ACE is running lower version then you could see this issue. To resolve this issue you need to upgrade ACE modules.
    You could follow below process to Upgrade ACE from EOBC,
    You can follow  below process to boot from EOBC where ACE is in Switch 1 , slot 2.
    Make sure ACE A2(1.2) or later image is on flash/disk0 on SUP,
    Step 1: On Switch configure ACE module to boot from Switch disk0
    conf term
    boot device switch 1 module 2 disk0:c6ace-t1k9-mz.A2_1_5a.bin
    end
    Step 2: Power off ACE module in slot 2 by using command,
    (Config t) no power enable switch 1 module 2
    Step 3: To boot ACE module using EOBC
    hw-module switch 1 module 2 boot eobc
    Step 4: Then power on ACE module in slot 2 by using command,
    (Config t) power enable switch 1 module 2
    Step 5: Make sure ACE boots up and has correct version running.
    If ACE is already running support version for VSS or if you need any assistance to upgrade then please raise Service request with TAC.
    Hope this helps,
    Best Regards,
    Rahul

  • Two wism module in vss mode

    i have two switches 6509 connected by vss technology
    i add two wism module ( one in each switch 6509 )
    i need to know if  two wism are operate active - active in vss or active - standby ?

    Hi Mohammad,
    Redundancy for the APs is achieved by configuring primary, secondary and tertiary controllers.
    There is no redundancy between controllers in a way that one controller is in standby mode and keeps verifying whether another active controller is operational.
    In your case, you could for example consider the following options:
    N + N redundancy:
    150 APs with primary controller A and secondary controller D for example.
    150 APs with primary controller C and secondary controller B for example.
    This will allow an easier redundancy configuration.
    (pseudo) N + 1 redundancy:
    100 APs with primary controller A; 50 of them with secondary controller C and other 50 with secondary controller D.
    100 APs with primary controller B and secondary controller D.
    100 APs with primary controller C; 50 of them with secondary controller A and other 50 with secondary controller B.
    This is a bit trickier, but it would allow less load per controller and still a fairly robust redundancy in case one of the two Cat6k's goes down.
    Regards,
    Fede
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • VirtualBox 4.0.2 internal DHCP problem in Host-only mode?

    Hi,
    dos anyone have experience problems with VirtualBox 4.0.2 internal DHCP not working when running Oracle Linux and a Host-Only adapter.
    More detailed described my problem is that Oracle Linux don't get a ip from the internal DHCP server om my system. My host is Win 7 (64 bit) and Guest Oracle Linux (64 bit). I have read that there are several ohers who experienced the same problem with the open source version, but that patching the Guest Tools to 4.0.3 helped them. Sadly this is not the case for me. Any suggestions are welcome and thanks in advance.

    Thanks for your reply - my problem is that the build in dhcp server is not working for some reason and i dont't gen any ip address assigned. I can see from the VBoxManager that it is running, but i can't get i contact with it from the linux guest.

  • 6509E VSS w/Quad-Sup 720 - Traffic Forwarding Issue

    Hello all,
    I ran into an interesting problem yesterday evening while performing a quad-sup upgrade to an existing dual-sup 6509E VSS architecture. Unfortunately, the expiration of my maintenance window forced me to roll back the changes before I had the opportunity to truly discover the root issue, however, I wanted to post my experience on Support Forums with the hope that someone else has run into it before.
    The customer I was working with has an existing dual-sup (720) environment operating in VSS mode. Both sup's were installed an operational in slot 5 of each chassis. The switch ID's had been assigned as 1 and 2, and the VSL was comprised of the two 10GE interfaces connected between each of the sup modules (1/5/4-2/5/4 and 1/5/5-2/5/5). The customer wanted to increase their intra-chassis redundancy by installing two additional sup 720 modules in slot 6 of each chassis, and adding these 10GE interfaces to the VSL.
    The overall upgrade went very well. I began by physically installing an additional sup 720 in slot 6 of the VSS standby chassis, and the sup module came up into RPR-Warm status (which is the desired state). I then physically installed an additional sup 720 in the VSS active chassis, and it too came up into RPR-Warm status. After reviewing the VSS redundancy state, I determined that everything looked good, and proceeded to add the additional 10GE links (1/6/4-2/6/4 and 1/6/5-2/6/5) into the VSL configuration. I then physically connected the additional VSL links (but shifted them around as to achieve diversity between the chassis (1/5/4-2/5/4, 1/5/5-2/6/5, 1/6/4-2/6/4, 1/6/5-2/5/5). I then reviewed the VSL link state and EtherChannel state, and everything looked great.
    At that point, we were pretty much done with the switch configuration, and proceeded to verify that server/network resources were not affected. I found that there seemed to be an issue sending traffic across the VSL. For example, some physical servers connected to switch ID 1 were having a difficult time communicating to physical servers connected to switch ID 2 (this customer is still working on dual-homing hosts). I looked at all of the obvious things - physical VSL interfaces, EtherChannel status, etc., and everything looked good. I then proceeded to remove physical VSL interfaces from the configuration, eliminating those that were added that evening (e.g., all interfaces except the original 1/5/4-2/5/4 were removed) - nothing. At this point, I was 10 minutes from the expiration of the maintenance window and was forced to roll back. It wasn't until the newly added sup's were physically removed from the chassis that the issue subsided. That said, I was able to conclude that the VSL wasn't the problem at all, but perhaps the installation of the sup's was??
    All of the sup 720's were running 12.2(33)SXI6 code, which I had verified to be a safe harbor version (although there are known bugs, none appear to be related to this issue).
    Has anyone run into this issue before? Any thoughts would be appreciated!

    You bring up VSS outside of the current environemnt. Create all vlans with a spanning tree priority higher than the existing.
    Create all the vlan interfaces and leave them shutdown.
    Connect the existing core to the new VSS core. Make sure that all vlans are properly crossing the trunk between old and new cores. Depending on how you're routing is set up, you might need to create a vlan to use for routing updates only.
    At this point, you can start changing spanning tree priorities to move the root of the vlans to the vss. Once these have been moved, you can start to manipulate hsrp.
    Whichever switch has the backup interface, shut those interfaces down. After this is done, shut the vlan inteface on the old core and no shut on the vss. Since vss doesn't use hsrp, it's hard to manipulate the vss since you want the vlan interface to be the previous standby ip.
    Flipping the vlan intefaces shouldn't cause any issues. I've done this method several times in large hospitals with no issues.
    Once you have the vss running, you can move the access switches 1 link at a time. Make sure you're running rapid pvst.
    The method I've used for this is to create a port channel on both the access switch and the vss. On the vss, you can assign the interfaces into the port channel immediately. On the access switch, disconnect one of the interfaces that goes to the old core. Add the disconnected inteface into the port channel then plug it back in. It should come up as the only member of the etherchannel. After you verify this link is up properly, perform the same with the second uplink on the access switch. When you plug it in, it should join the channel and you should be fine. With rapid pvst, nothing should be noticeable when the links block and unblock.

  • DHCP Switch mode

    I have a Windows 2012 Essentials server in my house and then a separate VM running a secondary Windows 2012 server. Don't say what I do is overkill please, it's in a lot of ways for learning more than anything. Essentials is my primary and VM instance is
    secondary domain controllers. I have both running as DHCP servers in hot standby mode. I had an outage yesterday of the primary and for some reason the secondary didn't take over very fast. Took over an hour for a computer to get an IP. May have even been
    more specific to my WiFi devices but not sure why that matters once they connect to a wifi hotspot in the house. Anyway, was thinking of switching to load balanced as thinking there wont be any delay in serving up IP's if one goes down as they are both active
    all the time. How would I go about switching modes? Is there a walkthrough anywhere? Specific to my situation.
    Thanks.
    Steve

    Dhcp Failover cluster configuration settings you can do;
    Maximum client lead time:Partner Down state of time to wait for the server to come back.During this time the server is down does not rise up over the server task that is still standing.
    State Switchover Interval: In case there is no one down from DHCP server,realizing that the standing down of the dating site with a DHCP server down time to enter the state stage.
    For example;
    DHCP Server1 was shut down,15 min(time mentioned in this field) during the DHCP server2 will understand that 1 is the server does not receive a notice from the server down no 1,so be immediately activated to deploy IP?NO! to enter the "maximum client
    lead time" will wait until the time in the field.Why?DHCP server1 back to the uprising is hope,when the maximum client lead time mentioned until now is still time to start making all transactions regarding the scope news from the server can not be number
    1

  • Windows Server 2012R2 DHCP Load Sharing Mode

    Hello,
    I am planning to migrate a standalone DHCP Server on Windows 2003 to Windows Server 2012R2. With this migration, I like to use the 2012R2 Load Sharing Mode feature for DHCP. This implementation cover TWO sites.
    My initial plan was to have two Windows 2012R2 DHCP Servers (virtual) at each site thus servers at each offers site redundancy  as well. So two at Site 1 and two at Site 2 on load sharing mode. If ServerA at Site 1 goes down for some reason Server B
    at Site1 will service the DHCP clients in load sharing mode without going to Site 2. I came across a MS document that says:
    Number of Servers: DHCP failover is not supported for more than two DHCP Servers. The failover relationship is always comprised of two DHCP servers.
    Does this mean I can have only TWO DHCP Servers in a load sharing mode. One at Site 1 and the second one at Site 2??
    Thanks in advance
    TIA TP

    Hi,
    The DHCP failover relationship is comprised of DHCP server and its partner.  In a relationship there are just 2 DHCP servers.
    But this doesn’t mean you can just use 2 DHCP servers in your sites.  The DHCP failover setting is based on DHCP scope, for one DHCP scope there could be just one DHCP failover relationship including 2 DHCP servers. If you have more than 1 DHCP scope,
    for example, set DHCP failover relationship between DHCP server 1 and DHCP server 2 for scope A. then set DHCP failover relationship between DHCP server 1 and DHCP server 3 for scope B.
    The document Step-by-Step: Configure DHCP for Failover(http://technet.microsoft.com/en-us/library/hh831385.aspx) is a introduction about this function and for your reference.
    Depends on the DHCP scope’s configuration and the requirements of your network. You may enhance or customize the architecture of implementation.
    Best Regards,           
    Eve Wang  

Maybe you are looking for