Nexus 5500 Licencing question

I have Nexus 5596UP switch running ver 5.2.1, I recently added Layer 3 card to the swicthes, L3 cards by default comes with  LAN_BASE_SERVICES_PKG licence. According to Cisco web site, I need LAN_ENTERPRISE_SERVICES_PKG in order to use VRF lite..
However I was able to create many VRFs on the swicthe and they work very fine. I assume that could be the grace period for LAN_ENTERPRISE_SERVICES_PKG licence, but according to Cisco I will get a daily notification about the grace period, which I don't. Also looking to the licence usage, I don't see LAN_ENTERPRISE_SERVICES_PKG being used..
N5K#sh license usage
Feature                      Ins  Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                No    -   Unused             -
FC_FEATURES_PKG               No    -   Unused             -
VMFEX_FEATURE_PKG             No    -   Unused             -
ENHANCED_LAYER2_PKG           No    -   Unused             -
LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
Here is sample of the VRFs I created on the swicth.
vrf context management
  ip route 0.0.0.0/0 10.239.10.1
vrf context vrf2
  ip route 0.0.0.0/0 10.239.240.5
vrf context vrf3
  ip route 0.0.0.0/0 10.239.240.205
vrf context vrf 3
  ip route 0.0.0.0/0 10.239.240.29
vrf context vrf 4
  ip route 0.0.0.0/0 10.239.240.213
vrf context vrf 5
  ip route 0.0.0.0/0 10.239.240.37
Also many SVIs are attached to several vrfs
example
interface vlan 123
vrf member vrf1
ip address 10.1.1.1/24
So my question, for these VRFs, do I really need LAN_ENTERPRISE_SERVICES_PKG? or what I have is enough?
Thanks for your help

According to license description and as you noted, you need enterprise service license to do VRF, but if it is working without it, than I guess you don't need it.  Also check the the routing protocols you are going to be using.
HTH 

Similar Messages

  • Nexus 5500 FCoE

    Hi,
    If I use a SFP-10G-SR transceiver in a Nexus 5500, can I have FCoE in this port?
    Sorry for the question but i'm begining in the FCoE world
    Thanks

    Thanks Vinayak
    I'm very excited to be working with Nexus switches. Currently we only going to use ethernet, but with the new servers will be able to use FCoE.

  • Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

    Hi,
    I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
    What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
    The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
    Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
    Thanks!

    That should not be an issue.  You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
    HTH

  • Mix of Nexus 5500 & Catalyst 6500

    Hi there,
    Does Nexus 5500 series require a Nexus 7000 parent device? or it will be supported with Catalyst 6509?
    If this is the scenario :
    CAT6509 - Core Layer 3
    CAT6509 - Distribution Layer 2/3
    NX-5548 - Access Layer 2
    And FYI, no VSS on Catalyst 6509.
    Thanks in advance,
    Gerard

    Hello Chad,
    Cool thanks ... that is perfect. We're eventually moving towards NX at the Core and Distribs really soon. Yeah, that's what I've known with the Extenders requirement with parent 5k or 7k too ... 
    Gerard

  • Nexus 5500 duplicate ICMP echo-replay

    I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
    In some cases I receive normal response when pinging from one Nexus,  but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
    5501# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms
    5502# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=0.985 ms
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=254 time=0.884 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=0.875 ms
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=254 time=3.105 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=254 time=8.378 ms
    Thanks
    Jarek

    Hi
    I found this in the configuration guide for the Nexus 7000 configuring VPCs
    "When you enable this feature (peer-gateway), Cisco NX-OS automatically disables IP redirects on all interface VLANs mapped over a vPC VLAN to avoid generation of IP redirect messages for packets switched through the peer gateway router."
    However this is not happening automatically on the 5K, so you need to manually add "no ip redirects" on each VPC vlan interface to prevent duplicate pings.

  • Connecting the nexus 5500 with multiple vsans

    Hi,
    it's my first experience in the fibre channel world and i have a few doubts about the best way to connect the nexus 5500 to a EMC storage.
    This is my scenario
    this is my configuration:
    vsan database
    vsan 2
    vsan 2 interface fc 1/1
    vsan 3
    vsan 3 interface fc 1/2
    interface fc1/1
    switchport mode f
    no shut
    interface fc1/2
    switchport mode f
    no shut
    now I don't know how can I connect the port fc1/3 to the vnx storage, I think I can't make a trunk like ethernet, can anyone help me?
    Or i only can do this with zoning
    Thanks
    Fred

    Hello Fred,
    All interfaces must be in the same vsan for them to see each other
    vsan database
    vsan 2 interface fc1/1, fc1/2, fc1/3
    exit
    Then you can zone each separately
    example:
    zone name host1 vsan 2
    member pwwn 11:11:11:11:11:11:11:11    (host1 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zone name host2 vsan 2
    member pwwn 22:22:22:22:22:22:22:22    (host2 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zoneset name Zoneset1 vsan 2
    mem host1
    mem host2
    zoneset activate name Zoneset1 vsan 2
    Thanks

  • Uplink-ID 0 in Nexus 5500 with FEX 2248.

    Hi all,
    I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
    On the log of the first Nexus 5500 I see this:
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    On the log of the second nexus 5500, I see this:
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
    Thanks in advace for your assistance.

    Hi Sonu,
    I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
    sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
    Did you find the fix7workaround of this problem ?
    Regards,
    Umair

  • Cannot InterVlan on Cisco Nexus 5500

    Dear All,
    I have problem with my nexus 5500,
    Intervlan on my nexus not work,
    i dont know why..
    Before i have only this kind of license:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         No    -   Unused        -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    and feature i used is :
    - feature privilege
    - feature telnet
    - feature interface-vlan
    - feature hsrp
    - feature dhcp
    - feature lldp
    I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
    And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
    and then i read this article:
    http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
    Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
    But, the other vlan is still DOWN. and Intervlan is not work to.
    Anyone, can help me please?
    I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
    Thanks.

    Marvin,
    This is the output.
    `show module`
    Mod Ports Module-Type                       Model                  Status
    1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.2(1)N1(1b)    1.0     --
    `show interface brief`
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  trunk  up      none                        10G(D) --
    Eth1/2        1       eth  trunk  up      none                        10G(D) --
    Eth1/3        1       eth  trunk  up      none                        10G(D) --
    Eth1/4        1       eth  trunk  up      none                        10G(D) --
    Eth1/5        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/6        1       eth  trunk  up      none                        10G(D) --
    Eth1/7        1       eth  trunk  up      none                        10G(D) --
    Eth1/8        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/31       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/32       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/33       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/34       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/35       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/36       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/37       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/38       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/39       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/40       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/41       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/42       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/43       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/44       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/45       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/46       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/47       1       eth  trunk  down    SFP not inserted            10G(D) --
    Eth1/48       1       eth  trunk  down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           down   --                                      --       1500
    Interface Secondary VLAN(Type)                    Status Reason                
    Vlan1     --                                      down   Administratively down 
    Vlan199   --                                      up     --       
    Vlan999   --                                      down   Non-routable VDC mode 
    sh ip int bri
    IP Interface Status for VRF "default"(1)
    Interface            IP Address      Interface Status
    Vlan199              192.168.36.10   protocol-up/link-up/admin-up      
    Vlan999              192.168.99.1    protocol-down/link-down/admin-up  
    sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/9, Eth1/10, Eth1/11
                                                    Eth1/12, Eth1/13, Eth1/14
                                                    Eth1/15, Eth1/16, Eth1/17
                                                    Eth1/18, Eth1/19, Eth1/20
                                                    Eth1/21, Eth1/22, Eth1/23
                                                    Eth1/24, Eth1/25, Eth1/26
                                                    Eth1/27, Eth1/28, Eth1/29
                                                    Eth1/30, Eth1/31, Eth1/32
                                                    Eth1/33, Eth1/34, Eth1/35
                                                    Eth1/36, Eth1/37, Eth1/38
                                                    Eth1/39, Eth1/40, Eth1/41
                                                    Eth1/42, Eth1/43, Eth1/44
                                                    Eth1/45, Eth1/46, Eth1/47
                                                    Eth1/48
    5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    199  B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    391  C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    392  D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    393  E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    394  F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    395  G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    500  H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    526  I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    VLAN Type  Vlan-mode
    1    enet  CE    
    5    enet  CE    
    199  enet  CE    
    391  enet  CE    
    392  enet  CE    
    393  enet  CE    
    394  enet  CE    
    395  enet  CE    
    500  enet  CE    
    526  enet  CE    
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports

  • DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

    When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
    Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

    Here is the solution:
    in the menubar on the top, in the lower one go to Admin > Server Properties
    scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false 
    restart the DCNM Servers

  • Nexus 5548UP SFP question

    Is SFP-GE-T supported on the 5548UP?  And can one run it at 100BaseT speed?  Or only at 1000baseT?
    The SFP appears to support 100baseT,  but is there a restriction on the 5548UP?
    Brian Holmes
    Verizon Enterprise for Chrysler       

    Hello Brian,
    Although the transceiver SFP-GE-T is supported on the Nexus 5500 platform, it will only work at 1Gbps. This is a hardware restriction.
    Richard

  • Nexus 5596 Licensing question

    Hi this might be an easy one but doing my head in.
    Do the ports on the 5596up (all 48) come fully licensed?
    We're looking at installing the following modules into the above N2K-C2232PP and N2K-C2248TP.
    What we need to figure out is basic licensing for this model.
    I know from dealing with the 6248up that only 12 ports come licensed.
    Does anyone have a link to default licenses enabled on Nexus kit.
    Thanks for the help.
    Regards,
    Liam

    Hello Liam,
    Licenses for Nexus 5500 are based on the features that you want to run on it.
    Fabric EXtenders ( FEX ) does not require licenses.
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_6_0/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_6_0_chapter_01.html#concept_99509AB7BE8F4DFB9EF49B702F768E62
    Features that require licenses are listed here
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/licensing/guide/b_Cisco_NX-OS_Licensing_Guide_chapter_01.html
    Licenses are granular that it allows N number of ports to be activated for the feature.
    HTH
    Padma

  • Nexus 5500 Questions

    Hello -
    Are the Nexus 5548P, 5548UP and 5596UP switches shipping?
    Also, do they offer Fabric Path?
    Thanks

    Ex,
    Yes, all three Nexus products are available for order as of today.
    As for Fabric Path, it's currently only supported on the Nexus 7K, with the F1 Line cards running NXOS 5.1 or later.  Fabric Path will be available on the 5548/5596 running 5.1(3)N1(1) codename "Fairhaven" release of NXOS.  Currenlty targeting mid-late 2011.
    FYI - Fabric Path will require a separate license.
    Regards,
    Robert

  • Nexus 5500 storage licensing questions

    Hi,
    On the 55xxUP switches, do I need to purchase the N55-8P-SSK9 license to use FCoE as well as native FC, or is this license specific to native FC ports?
    Does the N55-M16UP module require the license as well? I seem to recall seeing a document indicating this module is capable of running FCoE and native FC withouth an additional license.
    Thanks!

    I have the information from Cisco that no storage license is required for FCoE and NPV (with the "feature fcoe-npv") when no FC ports are required. So when only FCoE and NPV (and no native FC) will be used, the storage license is not required.
    Instead only the following license is required:
    Nexus 5548 FCoE NPV License
    N5548-FNPV-SSK9    $3,200.00

  • Windows 8.1 Pro - Licencing Question

    I am about to buy a new laptop.  I also intend to buy a full retail copy of Windows 8 Pro so that I can install (and reinstall) windows as required without having to endure the manufacturer's "extras".  I will therefore effectively be
    discarding the OEM licence of Windows 8.1 Pro that comes with the laptop - I will boot the machine straight into the installation media if that makes a difference to the scenarios below.
    My questions are as follows:  
    I would like to install my full Retail copy of Win8 into two separate hard drive partitions on the
    same computer.  Let's call the partitions "Work" and "Play", the intention is to separate any games I install away from my work config (and also stop my work machine from getting slowed down waiting for Steam).  Obviously,
    only one of the installations could possibly be active at one time and the hardware would be identical.  Would Microsoft expect me to buy two licences for this or can I use the same key twice?  (I know that the OEM key cannot be used on a fresh install).
    Is it legal to install my retail copy of Win8 into a Virtual Machine on the laptop running the same retail copy?  The VM will only ever be used on the laptop that is running the licensed copy of Windows.
    Thanks in anticipation.

    Hi,
    According to Windows 8.1 license terms:
    Under our license, we grant you the right to install and run that one copy on one computer (the licensed computer), for use by one person at a time, but only if you comply with all the terms of this agreement. Typically, this means you can install one
    copy of the software on a personal computer and then you can use the software on that computer.
    It's not allowed to use one personal license at two system at the same time.
    For more questions, you can check Windows license terms in your computer:
    System\About Windows\Microsoft Software License Terms
    Also you can access the link below to read the license:
    http://download.microsoft.com/download/7/2/1/72103B1C-DE58-478C-BECF-4D846C2B4A15/UseTerms_Retail_Windows_8.1_Pro_update_(to_Windows_8_Pro_which_was_acquired_from_retail_or_Microsoft)_English.pdf
    Roger Lu
    TechNet Community Support

  • Nexus 5500 - Fabricpath Core Port - Error disabled. Reason:DCX-No ACK in 100 PDUs

    Has anyone seen Fabricpath Core Interfaces between two Nexus 5596UP switches error-disabled because of missing DCBX Acks after 50mins?
    I do not see interface errors and the peer is another 5500.
    Both switches are running 5.1(3)N2(1) with this port config:
    int e1/3
    switchport mode fabricpath
    ! Cisco 5m Twinax cables
    Log messages
    2012 May 25 17:40:59 nexus1 %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet1/3 down in fabricpath topology 0 - Interface down
    2012 May 25 17:40:59 nexus1 %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/3 is down (None)
    2012 May 25 17:40:59 nexus1 %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [3365]  P2P adj L1 nexus5 over Ethernet1/3 - DOWN (Delete All) on MT-0
    2012 May 25 17:40:59 nexus1 %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor nexus5(FOX1550GDH1) on port Ethernet1/3 has been removed
    2012 May 25 17:40:59 nexus1 %LLDP-5-SERVER_REMOVED: Server with Chassis ID 547f.ee63.fa88 Port ID Eth1/1 on local port Eth1/3 has been removed
    2012 May 25 17:40:59 nexus1 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/3 is down (Error disabled. Reason:DCX-No ACK in 100 PDUs)
    Robert

    Can you send the output of
    show lldp interface ethernet 1/3
    show lldp dcbx interface ethernet 1/3
    a workaround may be to disable lldp on both sides on these physical interfaces

Maybe you are looking for