First Cisco Nexus VLAN infrastructure detects not

Hello

We have recently added 2 Nexus 5010 to our first Infrastructure 2.0.

Once the synchronization is complete, the device comes as managed.

When you look through the details of the device, everything seems to be ok, just at the point where research on the VLANs tab, it says:

"none detected.

In fact, there are a lot of VLANS on this unit.

Someone at - it a similar problem?

Thank you

Jörg

Hi Jörg,

I have checked and confirmed that unfortunately this function is not supported for NEXUS. I mean information of VLAN.

and I think that "port-channels" are also not taken in charge.

Thank you-
Alya
[Note the useful post]
Ratings encourage contributors *.

Tags: Cisco Network

Similar Questions

  • Cisco Nexus 5596 does not start after NX-OS upgraded from 5.1.3.N1.1 to 6.0.2.N2.5 [CSCun66310]

    Hello friends,

    I want just to save your valuable time & effort, while Nexus 5596 upgrades so I wanted to share some useful information that you can have a quick glance before your Cisco Nexus 5596 device updates.

    Recently, I ran into trouble when upgarding 5596 Nexus data center switch does not boot and after investigation of the Cisco TAC it comes out to be Bug described below.

    https://Tools.Cisco.com/bugsearch/bug/CSCun66310/?reffering_site=dumpcr

    My way of upgrading the device was: 5.1 (3) (1) to 6.0 (2) N2 N1 (5).

    As this upgarde involves an upgrade of Bios and power purposes, I had some doubts to get this properly upgraded, but he had more twist involved in this upgrade I got to know after contacting Cisco TAC for my death 5596 Nexus device and got info if you have version impacted in your Nexus 5596 device and you plan to upgrade , then you migh RUN in this serious BUG aftre which device will not come at all and only Option left is to replace with device of RMA.

    Material affected PID versions Versions updated

    UCS-FI-6296UP                                            1.0                                       1.1

    N5K-C5596UP                                              1.0                                        1.1

    N5K-C5596T                                                 1.1                                         1.2

    You can check with hardware version command from your device below.

    5596 # display sprom sup | H/W Inc.

    H/W Version: 1.1

    So please be careful when you plan your Nexus 5596 update and check over things that this Bug is not present anywhere in the docuemntations upgrade unfortunately.

    Hope this will help and save valuable time of a person.

    This bug affected me. Before upgrade you the equipment, to track:

    It's procedure, there will be no allocation to apply.
    Is attached to the case of the dplugin for each NXOS, check out the name associated with each version.
     
     
    Step 1
     
    -------------------------------
    Copy the file dplugin and update, load Plugin
    Copy the ucd - update.tar to the bootflash
    Copy the debug plugin into the bootflash
    Load the image via the load control
     
     
    Note You can access the command line without leaving the plugin to debug via command vsh
     
    Example:
     
    n5K-1 # dir bootflash:. grep debug
    3023275 23 Jan 15:28:48 2013 ucd - update.tar
    283423 23 Jan 15:12:28 2013 nuova-or-dplug - mzg.5.2.1.N1.5.bin
    n5K-1 # load bootflash:nuova - or - dplug - mzg.5.2.1.N1.5.bin
    Loading of plugin version 5.2(3a)
    ###############################################################
    WARNING: debug plugin is for engineering for internal use only!
    For reasons of security, plugin image has been removed.
    ###############################################################
    Debugging properly load-plugin!
    Linux (Debug) #.
     
     
     
    Step 2
     
    -------------------------------
    After you load the dplugin file into NX - OS, please follow the steps to update the module of TI.
     
     
    Copy the ucd - update.tar of bootflash to the tmp directory and unzip the file
     
    Linux (Debug) # cp /bootflash/ucd-update.tar/tmp
     
    Linux (Debug) # cd /tmp/
     
    Linux (Debug) # tar - xvf ucd - update.tar
     
    UCD.bin
     
    Address_91_A.csv
     
    Address_92_A.csv
     
    Linux (Debug) #.
     
    Step 2
     
    ----------------------------------
     
    Run the ucd.bin file:
     
    Linux (Debug) #./ucd.bin
     
     
     
    You will see the prompt on the version 1.1 update.
     
    --------------------------------------------------
     
    principal: correctly upgraded TI inst 2 to version 5.
     
    New SPROM HW version 1.1. Charging must reflect in 'show the sprom' output.
     
    Release Linux (Debug) #.

    The problem is how to get the plugin. Only Cisco can provide this.

  • Mobile application Infrastructure first, Cisco

    Hi all

    I need to download the mobile application for the PI and I donot find?

    I need your help.

    Hi Mohamed,

    It is available on the Apple App Store.  I just checked the store from my iPhone and see.  Try searching on "First Cisco" and you should see the first Cisco application as well as the Cisco Plug-And-Play application.

    See you soon,.

    Chris

  • Cisco Nexus 3548/3524 SNMP Interface traffic problem

    Hi all!

    I would like to share with you the problem I've encountered SNMP interface respect tracking on the Cisco Nexus 3500 of traffic devices.

    We is transferring our network infrastructure in the Nexus and we encountered a problem with the interface bitrate of tracking traffic on Nexus 3548: deltas SNMP counter ifHCInOctets and ifHCOutOctets show no valid data.

    We have investigated this issue and figured he could be linked with the refresh rate of the meter.
    I measured, by snmpwalk, the time between simple increments the counter ifHCInOctets to Interface VLAN and it apears to about 140seconds. But for physical interfaces (Eth), the interval of interface SNMP counters are 15 seconds and with sampling frequency of the 1960s for the queries we can still observe the problems on graphs (see attached screnshot).

    We get the same results when testing the question on various physical devices (3548 Nexus) on versions of different software - including the last being.

    And for Ethernet interfaces (same NMS - ZABBIX-config):

    We tested a wide Huawei s6700 switches and the range of Cisco IOS devices and there is no such problems.

    The main problem is that we cannot monitor our crucial nexus, via SNMP devices (as you can see from the attached chart).  Results are the same when configure us Cacti or Zabbix to monitor Nexus devices.

    The results of this monitoring not having meritorical value or use.

    We are working on this case with Cisco TAC, and they manage to reproduce the problem in their LAB environment. But for now, they cannot provide any solution and they claim that this isn't a bug. If we get any final statement for this case, I'll post here for your information.

    I'll be more than happy if you can post ideas that help me solve the problem described.

    Thank you in advance!

    Michal

    Looks like a bug to me.  His return of erroneous data.

    Maybe try asking your file be traced back to the team leader.

  • The limit of the device must be less than or equal to the limit of life cycle license in first cisco 2.2

    Hi all

    I have seen under error in the tool main 2.2 Cisco infrastructure

    The limit of the device must be less or equal to the limit of license of life cycle and also secondary device ISE inaccessible since premium.

    Could you please suggest how we can solve your problem.

    Thanks in advance...

    Kind regards

    Sachin

    Yes. Life cycle license are by smart device managed. See this page for a good overview:

    http://www.Cisco.com/c/en/us/support/docs/cloud-systems-management/Prime...

    .. as well as this page:

    http://www.Cisco.com/c/en/us/products/collateral/cloud-systems-Managemen...

    .. who States:

    Life cycle license: allows access to all the features of the life cycle, which includes the configuration of the devices, image management software, basic health and performance monitoring, fault management, troubleshooting and customer visibility on the network. The license of the life cycle is based on the number of managed devices. Life cycle of the licenses are available in sizes from package of 25, 50, 100, 500, 1000, 2500, 5000, 10,000 and 15 000 devices and can be combined as needed to reach a total number of device under license.

    A device is uniquely identified through the assigned IP address and system object ID (SysOid). Routers, switches, light/unified access points and network first Cisco (NAMs) analysis Modules are charged on the number of licenses. If a switch stack is managed via a single IP address, it counts as a single device. A single frame will, however, be counted as multiple devices if the chassis is configured with several IP addresses. For example, a switch with several service cards, such as a firewall and so forth, or a stackable switch with an IP address assigned to each switch who is involved in the stack is considered multiple devices within the first Cisco Infrastructure. Cisco Wireless LAN controllers (WLCs), autonomous and peripheral access points third are not counted against the number of licenses.

    When you have more devices that licenses, you will receive the error see you and prevented from adding additional devices to your inventory.

    We see it more often when it is light (i.e. not independent) APs are added to a wireless controller. PI will not prevent the new APs to be added, they are managed under their association with the WLC. However, if you try to add a new switch it would prevent you to do until the deficit of licenses has been sent.

  • Cisco Nexus 1000V Virtual Switch Module investment series in the Cisco Unified Computing System

    Hi all
    I read an article by Cisco entitled "Best practices in Deploying Cisco Nexus 1000V Switches Cisco UCS B and C Series series Cisco UCS Manager servers" http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.html

    A lot of excellent information, but the section that intrigues me, has to do with the implementation of module of the VSM in the UCS. The article lists 4 options in order of preference, but does not provide details or the reasons underlying the recommendations. The options are the following:

    ============================================================================================================================================================
    Option 1: VSM external to the Cisco Unified Computing System on the Cisco Nexus 1010

    In this scenario, the virtual environment management operations is accomplished in a method identical to existing environments not virtualized. With multiple instances on the Nexus 1010 VSM, multiple vCenter data centers can be supported.
    ============================================================================================================================================================

    Option 2: VSM outside the Cisco Unified Computing System on the Cisco Nexus 1000V series MEC

    This model allows to centralize the management of virtual infrastructure, and proved to be very stable...
    ============================================================================================================================================================

    Option 3: VSM Outside the Cisco Unified Computing System on the VMware vSwitch

    This model allows to isolate managed devices, and it migrates to the model of the device of the unit of Services virtual Cisco Nexus 1010. A possible concern here is the management and the operational model of the network between the MSM and VEM devices links.
    ============================================================================================================================================================

    Option 4: VSM Inside the Cisco Unified Computing System on the VMware vSwitch

    This model was also stable in test deployments. A possible concern here is the management and the operational model of the network links between the MSM and VEM devices and switching infrastructure have doubles in your Cisco Unified Computing System.
    ============================================================================================================================================================

    As a beginner for both 100V Nexus and UCS, I hope someone can help me understand the configuration of these options and equally important to provide a more detailed explanation of each of the options and the resoning behind preferences (pro advantages and disadvantages).

    Thank you
    Pradeep

    No, they are different products. vASA will be a virtual version of our ASA device.

    ASA is a complete recommended firewall.

  • Configuration of Cisco Nexus

    Hi, wondered about the Configuration of the Cisco Nexus 100v.

    First of all, the MSM will have three vNIC used to:

    1. the Control Interface - NIC1

    2. Management Interface - NIC2

    3 packet Interface - NIC3

    The management interface is on the same VLAN as VMconsole (service console) because it is used to communicate with vCenter and ESX hosts for management traffic?

    Addresses IP should be assigned for control and packet Interfaces?

    Thank you

    When you use L3 control we encapsulate the control traffic and the package on the default management interface. Only IP you need is the IP address that you have assinged to the management interface 0. Interfaces and control packets never get used and never need a IP address.

    Louis

  • Cisco Nexus 1000v switch

    Hi, I have 2 questions about the Switch Cisco Nexus 1000v.

    First of all, why use it rather than the standard vswitch distributed?

    Second, if an environment currently works using distributed vswitches, what are the impacts and the problems likely to introduce a Switch Cisco Nexus 1000v? Is there a process for the upgrade?

    See you soon

    Here is a comparison for the most up-to-date between the optioins network:

    http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/solution_overview_c22-526262.PDF

    The great driver with most of the people running the 1000v I talked to is give visibility to the network team and streamlining changes made to the virtual network environment. In a great organazation with a network operations team, they will create an IVR to route a new VLAN, and then create the new VLAN on all switches distribution and access in the area of layer 2, just 1000v allows them to move forward and it create on the hypervisor using a set of commands that they already know.

  • Installation of Cisco Application Centric Infrastructure Simulator

    Morning,

    I want to know if it is possible to install Cisco Application Centric Infrastructure Simulator on ESXI or VMWare WorkStation. If so, what is requirements.

    Thank you.

    Morning,

    I regret to inform you, there is no VM for ACI Simulator. There is a hardware Simulator that can be purchased, it is a series of UCS - C that runs a modified version of IPEC and virtualizes the cluster three APIC and fabric Nexus 9000 sheets/thorns switches. Its a great place to get acquainted with the GUI to configure policies, interact with vCenter and L2/L3 network but is limited to the configuration of the policy, there is no traffic data plan.

    Here is the Simulator "APIC-SIM-S =" product ID

    Hope that answers your question, thank you for the use of forms of support of Cisco: ACI have a good day.

  • First Cisco 3.0 crashed after installing pi_technology_package - 3.0.2 - 1.0.56

    Hello

    Our first Cisco 3.0 after installing pi_technology_package - 3.0.2 - 1.0.56 crashed. SSH is available but not Web.

    Here is the story:

    1-. OVA installed

    2-. Installed the following hotfixes:

    Feature-Pack-3 - PI3.0 - 25.ubf

    4-Pack-device - PI3.0 - 15.ubf

    pi302 - 16.ubf

    pi303 - 10.ubf

    Server rebooted and everything seems to work fine.

    3-. Installed pi_technology_package - 3.0.2 - 1.0.56, rebooted and web server doesn't work anymore.

    We tried to restore a previous backup, perform a reset of db ncs and restart the ESXi machine, but without success.

    genpro01 / ncs status admin #.
    Health Monitor runs with an error. (Primary [role] [State] not configured HA)
    initHealthMonitor(): cannot start DB
    Database server is stopped
    FTP server is running
    TFTP Server is running
    MATLAB Server is running
    MATLAB Server Instance 1 is running
    MATLAB Server Instance 2 is running
    NMS server is stopped.
    Gateway of CNS with port 11011 is down
    CNS with port 11012 SSL gateway is down
    Gateway of CNS with 11013 port is down
    CNS with port 11014 SSL gateway is down
    Plug-and-Play bridge with port 61617 broker is down
    Plug n Play bridge config, image and resources are declining over https
    Plug-and-Play gateway is stopped.
    SAM Daemon is stopped.
    DA Daemon is stopped.
    genpro01 / admin #.

    Any suggestions?

    Kind regards

    David

    David,

    Unfortunately things can get really watered (technical term) with the database if the application (ncs) server is not restarted after each pack of patch installation or device. Later versions of patch began by pointing out that right from the start.

    I would say that you have two options-

    1 rebuild from scratch and just re - import devices. It is a self-service option.

    2 open a TAC case and see if they can recover the current state. The reports I got colleagues and read elsewhere here is the recovery of a failed installation of this tech pack was difficult at best.

    Sorry to be the bearer of bad news.

  • Switch Cisco Nexus 6004 removes more than 300 bytes IP packets

    Hi all

    We have a circuit of wave level 3 10 G running between two switches Cisco Nexus 6004. The circuit came online between our two data centers (in the same city) without problem.

    When attempting to ping to the remote-end 10G interface, it works very well with packets of 64 bytes. CDP is enabled and that we see the CDP information remote switch. However, if we increase the size of the ping to more than 300 bytes packets, we lose 1 in every 20.

    We settings MTU verifed, type of cable of 10G and duplex settings.

    Level 3A tested clean and we will move forward with more testing.

    Any ideas on the problem? We feel the carrier out and end to test with their testers. But so far, the circuit's own test. I was not sure if it is something related to Cisco. I am at a loss at the moment.

    Thank you.

    Mike

    Hi Mike,.

    There is nothing wrong with your switches or circuit.  NEXUS devices have a default COPP on the control plan that limit the size and the amount of traffic that must be the CPU process.

    http://www.Cisco.com/en/us/docs/switches/Datacenter/SW/6_x/NX-OS/security/configuration/guide/b_Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_6.x_chapter_011001.html

    HTH

  • RV110W inter-VLAN-routing is not possible

    In Cisco RV110W, I set up 2 VLANS, a 192.168.1.xxx (Green Net) and the second with only a fixed address 192.168.2.100 192.168.2.xxx (Server), which is configured in the DMZ area. I enabled in Cisco "inter-VLAN-Routing", described "routing between separate VLANs on Cisco RV110W" I can Ping the server in a direktion, the other I got an error. It is just expected and ok! All other abilities expected work well!

    Now, I want to see the Green network server. (firewall on the server is off)

    I configured the network/router with exactly the values of the index and has been an error: "destination LAN IP may not be the same as the router's IP subnet.

    Sorry, I don't understand this. Can anyone help?

    Thank you in anticipation

    Anton

    If I understand correctly, you have a second vlan, 192.168.2.x. The RV110W is a member of this subnet so that's why we do not have a static route for something that the router knows that she welcomes this subnet.

    -Tom
    Please evaluate the useful messages

  • Cisco Nexus to use authentication Radius AAA using Microsoft 2008 NPS

    I have a Nexus 7010 running

    I was wondering if you can help me with something. I'm having a problem with the approval of the order through our aaa config. We have not an authentication problem of command approval that does not work. From what I've seen and read Nexus NX - OS 6.x has not all orders for the aaa authorization, unless you configure GANYMEDE +. My basic config is below if you can help would be much appreciated.

    > ip source interface mgmt radius 0

    > key RADIUS-server XXXXX

    > host X.X.X.X key radius server authentication XXXXX accountant

    > RADIUS-server host X.X.X.X XXXXX key authentication accountant aaa

    > authentication login default group aaa authentication Radius_Group

    > RADIUS server logon group console local aaa Radius_Group

    > server X.X.X.X

    > server X.X.X.X

    > mgmt0 interface-source

    Also nobody how to configure Microsoft 2008 NPS as Raduis server to work with Nexus? I read a few post that suggests to change the

    Shell: roles = "vdc-admin" in the value field of the attribute in the RADIUS server

    Anyone know if it works?

    Thank you

    I haven't used NPS before but sounds like you are on the right track. As Ed mentioned in his post, GBA, you can set the type of protocols that you will accept during an authentication session. Authentication Nexus sessions is considered as PAP/ASCII, so you should be good to go. I don't have a Nexus switch to test with, but if you can use wireshark to capture the session and see the exact protocol / method used. However, I am sure that PAP is the way to go:

    http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/SW/4_1/NX-OS/se...

    I also found the link that you might find useful:

    http://www.802101.com/2013/08/Cisco-Nexus-and-AAA-authentication.html

    Thank you for evaluating useful messages!

  • Cisco Nexus 5548UP switch current Version 5.2 (1) N1 (4)

    Hi, we are currently have Cisco Nexus 5548UP switch current Version 5.2 (1) N1 (4)

    It is not listed as affected version:

    Known affected releases:
    (5)
    5.2 (1) N1(8A)
    6.0 (2) N2 (5)
    7.0 (3) N1 (0.125)
    7.0 (4) N1 (1)
    7.1 (0) N1 (0.349)

    The fixed versions known as follows:

    Known fixed releases:
    (7)
    6.0 (2) N2 (4.3)
    6.0 (2) N2(5A)
    7.0 (1) ZN (0.615)
    7.0 (5) N1 (0.173)
    7.0 (5) N1 (1)
    7.1 (0) N1 (0.371)
    7.1 (0) N1 (1)

    It needs to be updated to the latest versions?

    If Yes, what version of the fixed known better adapt our current version

    Cisco Nexus 5548UP switch current Version 5.2 (1) N1 (4)

    Thank you.

    I had the same question, so I opened a folder of TAC to find the version of the software. I was told that the software listed as available in the bug report are versions of NX - custom OS and that there was no version patched for the 5548p. The support engineer also said that the updates of Nexus 5 k should not until November or December. The best advice I could get was to subscribe to the bug report and wait to be notified of an available upgrade.

  • Why is - that someone would need Cisco Nexus 1000v when DvSwitch is so Kool

    Why is - that someone would need Cisco Nexus 1000v when DvSwitch is so Kool

    Or is it something that DvSwitch cannot always do that Cisco Nexus 1KV possible?

    Use of 1kV Nexus are clear enough, if you want to segregation, the advanced settings of COS, use Cisco VSG, etc. etc., you must use Nexus 1kV. But if you do not use one of these, why would you pay more money to use a Nexus 1kV, while you can use dvSwitch, giving you more or less the same basic features. After all, the 1kV has been developed using the dvSwitch framework.

Maybe you are looking for