Cisco nexus 6001 not a supported device on cisco prime infrastructure 2.1?

I have installed Cisco Prime Infrastructure 2.2 and Prime Infrastructure still doesn't seem to support the Nexus 6001 platform? Can someone tell me if Cisco Prime Infrastructure will ever support the Cisco Nexus 6001 platform or is there any plans to support it in any future device packs?

The Nexus 6001 isn't currently supported in PI 2.1. There's no workaround except to wait for a device or product update that adds support. Right now I know the 9000 series is on the 2.2 roadmap but I haven't seen any reference to the 6001 and PI.
Interestingly, Prime LMS does support both the 6001 and 6004. Reference.

Similar Messages

ADE doesn't seem to recognize my Google Nexus (2013) tablet. Is it not a supported device?

ADE doesn't seem to recognize my Google Nexus (2013) tablet. Is it not a supported device?

ADE doesn't seem to recognize my Google Nexus (2013) tablet. Is it not a supported device?

Cisco Prime Infrastructure - I can't see the hardware virtual image when I selected a device managed by Prime Infrastructure. See attached picture

My Cisco Prime Infrastructure ver. 1.2.1.12
Cisco Prime Infrastructure - I can't see the hardware virtual image when I selected a device managed by Prime Infrastructure. See attached picture.
Please let me know how to access or enable the feature.
Thanks,
Tek

This is by no means a full solution, but deleting and re-adding only takes a few minutes if you use the "Export Device" and "Bulk Import" features from the Device Work Center. You can export the desired devices to a CSV file, delete them, then import from the CSV.
Of course, you might lose historical data when deleting the devices, but I'm guessing that's not as relevant since the devices themselves have been replaced by different hardware.

Ask the Expert: Basic Introduction and Troubleshooting on Cisco Nexus 7000 NX-OS Virtual Device Context

With Vignesh R. P.
Welcome to the Cisco Support Community Ask the Expert conversation.This is an opportunity to learn and ask questions of Cisco expert Vignesh R. P. about the Cisco® Nexus 7000 Series Switches and support for the Cisco NX-OS Software platform .
The Cisco® Nexus 7000 Series Switches introduce support for the Cisco NX-OS Software platform, a new class of operating system designed for data centers. Based on the Cisco MDS 9000 SAN-OS platform, Cisco NX-OS introduces support for virtual device contexts (VDCs), which allows the switches to be virtualized at the device level. Each configured VDC presents itself as a unique device to connected users within the framework of that physical switch. The VDC runs as a separate logical entity within the switch, maintaining its own unique set of running software processes, having its own configuration, and being managed by a separate administrator.
Vignesh R. P. is a customer support engineer in the Cisco High Touch Technical Support center in Bangalore, India, supporting Cisco's major service provider customers in routing and MPLS technologies. His areas of expertise include routing, switching, and MPLS. Previously at Cisco he worked as a network consulting engineer for enterprise customers. He has been in the networking industry for 8 years and holds CCIE certification in the Routing & Switching and Service Provider tracks.
Remember to use the rating system to let Vignesh know if you have received an adequate response.
Vignesh might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community discussion forum shortly after the event. This event lasts through through January 18, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

Hi Vignesh
Is there is any limitation to connect a N2K directly to the N7K?
if i have a an F2 card 10G and another F2 card 1G and i want to creat 3 VDC'S
VDC1=DC-Core
VDC2=Aggregation
VDC3=Campus core
do we need to add a link between the different VDC's
thanks

CISCO NEXUS 5020 Not Booting

I have a cisco nexus 5020 switch of 2 nos, but when i try to boot the device its result no image on the flash and it stuck in the boot mode. Is any possibility to boot the nexus from boot mode without having a image from flash.

Hi Michael,
If the unit is not showing anything at all when connecting screen/keyboards, there won't be much more investigation possible. Likely the HW has gone bad and you will have to replace it.
Regards,
Marco

TS1567 what if not mobile support device is in services

Hi
I'm having trouble with iTunes. The Apple Support Device isn't in Services. I have read up and its been suggested to uninstall and then reinstall. This has been done. It has also been suggested deleting all apple from my Laptop and a reinstalling done.
Also there is a newr version on iTunes and my laptop will not install this.
Any suggetions would be greatly received.
Regards Alan.

See the actions for AMDS included here:
iOS: Device not recognized in iTunes for Windows

Nexus 3548 6.0(2)A1(1) within Prime Infrastructure 2.0

Hi there,
I am trying to introduce some Nexus 3548 in my Prime Infrastructure 2.0.
For my 3048 running 6.0(2)U1(1a), no problem, they are discovered well and showing no error in the Device Work Center.
My 3548 are unrecognised (NXOS 6 too).
Is this an expected bahaviour ?
Regards,
Fred

Hello,
Take a thorough look at realease notes for this version and before. This is the only way.
If your doubt is only about VPC and FEX features, it is totally supported, just be aware that upgrade is disruptive.
Regards.
Richard

Cisco Nexus v1000 not connecting to VMWare vCenter

I am trying to deploy Nexus 1000v, but there is a problem - no connection with vCenter. Pings are ok, all ip addresses and port numbers are valid. Console displays following error:
switch(config)#svs connection vc
remote ip address 10.10.10.200 port 5480
protocol vmware-vim
vmware dvs datacenter-name CORE
connect
ERROR: [VMWARE-VIM] Operation could not be completed due to connection failure. End of file or no input: Operation interrupted or timed out after 160s send or 160s receive delay
Thank you.

You should use port 80 instead of 5480 in your svs connection string. Port 5480 is the default port for the management of the vCSA.

Prime InfraStructure 2.2 - Support of Nexus 3524 model

Hello Community,
I am trying to find but I am not sure if Nexus 3524 is supported on Cisco Prime Infrastructure 2.2
Please can someone clarify?
thanks in advance,
G

Hi ,
Cisco Nexus 3548 Switch OID:1.3.6.1.4.1.9.12.3.1.3.1238 (NX-OS\(tm\)), IOS
yes , it is supported , you can check the below link::
http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-device-support-tables-list.html
Thanks-
Afroz
**Ratings Encourages Contributors ****

Cisco Prime Infrastructure 2.2 UCS support (C24)

Hi,
I recently upgraded a CPI 2.1 server to 2.2 hoping that it would support monitoring and managing a customer's C24 server. Unfortunately I hadn't read the Supported Devices list (http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-device-support-tables-list.html) where it is stated that UCS C220 M3 and C240 M3 are supported, but none of the other models.
When can I expect support for C24 M3 (OID:1.3.6.1.4.1.9.1.1685) and the other UCS models?
Mikael

Cisco just added the Compute work center and UCS support in PI 2.2. I suspect they used the C220 as a first target since that's the platform for the upcoming hardware appliance refresh.
While they haven't announced future release plans, typically we see incremental device updates via the update packages - those have been coming out almost monthly with PI 2.1.
I'd encourage you to submit enhancement requests via your Cisco account team if the feature is important to you. Customer feedback is one of the key elements in deciding what features the developers focus on.

Connecting a Dell B22 FEX to Nexus 6001 and storage

Hi Folks,
We have a setup where we are running a Dell B22 FEX in Blade enviornment and want to connect the B22 FEX to a cisco Nexus 6001 switch. As per NX-OS release note, B22 FEX and 6001 Nexus connectivity is supported.
Now after connecting to Nexus 6001, how do i get access to storage pool or SAN fabric ? As per another thread of discussion, Nexus 6001 does not support direct fabric attachment at this point in time. So how do we bridge these two elements to a storage fabric ??
As per 6.02 release note:
"Support for DELL FEX
Added support for the Cisco Nexus B22 Dell Fabric Extender for Cisco Nexus 6000 Series switches starting with the 6.0(2)N1(2) release."
This is the exact reason we bought it. We have a enviornment where we are running Dell B22 FEX. Idea is to connect the B22 FEX into Nexus 6001. We are confuse at this point. After connecting the Dell B22 FEX to Nexus 6001, how to access the storage network or storage fabric ??
Thanks,

Hi Rays,
The function should be the same for all FEXs regardless of what parent switch they connect to. to.
if you are referring to this comment:
You can connect any edge switch that leverages a link redundancy mechanism not dependent on spanning tree such as Cisco FlexLink or vPC
FelxLink is a different technology that does not use STP, but not every switch platform supports FelxLink. FlexLink is not used very often, as other technologies like VSS, VPC and stacking has emerged.
HTH

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Nexus 6001 native FC

Does the Nexus 6001 support native FC? I'm having issues changing the port type;
show ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 1.5.0
loader: version N/A
kickstart: version 7.0(5)N1(1)
system: version 7.0(5)N1(1)
Power Sequencer Firmware:
Module 1: version v4.0
Module 2: version v4.0
Fabric Power Sequencer Firmware: Module 1: version v4.0
Microcontroller Firmware: version v1.2.0.5
QSFP Microcontroller Firmware:
Module 2: v1.3.0.0
SFP Microcontroller Firmware:
Module 1: v1.1.0.0
BIOS compile time: 12/29/2012
kickstart image file is: bootflash:///n6000-uk9-kickstart.7.0.5.N1.1.bin
kickstart compile time: 10/29/2014 22:00:00 [10/30/2014 11:46:56]
system image file is: bootflash:///n6000-uk9.7.0.5.N1.1.bin
system compile time: 10/29/2014 22:00:00 [10/30/2014 11:47:58]
Hardware
cisco Nexus 6001 Chassis ("Nexus 64 Supervisor")
Intel(R) Xeon(R) CPU @ 2.00 with 8238120 kB of memory.
Processor Board ID FOC181506P3
Device name: xxxxxxxxxxxxxx
bootflash: 7823360 kB
Kernel uptime is 3 day(s), 17 hour(s), 25 minute(s), 49 second(s)
Last reset at 642096 usecs after Fri Feb 27 15:24:40 2015
Reason: Disruptive upgrade
System version: 6.0(2)N2(3)
Service:
plugin
Core Plugin, Ethernet Plugin, Fc Plugin
xxxxxx# conf t
Enter configuration commands, one per line. End with CNTL/Z.
xxxxxx(config)# slot 1
xxxxxx# port 47-48 type fc
ERROR: Module type doesn't support this CLI
Any help would be appreciated. Thanks

Sorry, should have mentioned that I'd already enabled feature fcoe;
xxxxx(config)# show feature
Feature Name          Instance State
Flexlink              1         disabled
amt                   1         disabled
bfd                   1         disabled
bfd_app               1         disabled
bgp                   1         disabled
bulkstat              1         disabled
cable-management      1         disabled
cts                   1         disabled
dhcp                  1         disabled
dot1x                 1         disabled
eigrp                 1         disabled
eigrp                 2         disabled
eigrp                 3         disabled
eigrp                 4         disabled
eth_port_sec          1         disabled
evmed                 1         disabled
extended_credit       1         disabled
fabric-access         1         disabled
fabric-binding        1         disabled
fabric_mcast          1         disabled
fc-port-security      1         disabled
fcoe                  1         enabled
xxxxxxxxx(config)# slot 1
xxxxxxxxx(config-slot)# port 47-48 type fc
ERROR: Module type doesn't support this CLI

Upgrade Cisco Prime LMS 4.0 to Cisco Prime Infrastructure 2.1

My company has asked me to migrate Prime LMS 4.0 to Prime Infrastructure 2.0 for a client and can not find the guide, the questions are? the migration is possible without an intermediate step? and There is a guide to update LMS 4.0 to PI 2.0 ??
Thanks in advance.

Prime LMS 4.2.2 added support for the PI template directly:
Export Data for Prime Infrastructure
Cisco Prime LAN Management Solution supports data migration to Prime Infrastructure 1.2. This feature enables user to export the Device Credentials Repository (DCR) data from LMS 4.2.x versions to Prime Infrastructure 1.2. The data backup status and backup location are displayed at the bottom of the Export Data for Prime Infrastructure page. The data being exported from LMS and the data imported back to PI are listed as follows.
Data exported from LMS
•Device Credentials Repository (DCR)
•Software Image Management
•Config Archive
•Change Audit
•Syslog
Data Imported to PI
Device Credentials Repository

Upgradding Prime Infrastructure version 1.2 and LMS 4.x to Cisco Prime Infrastructure 2.0

Hello,
A customer currently have 2,500 Cisco Prime Infrastructure Lifecycle device license using Prime Infrastructure version 1.2 and LMS 4.x. the customer wants to upgrade to Cisco Prime Infrastructure 2.0.
Does anyone know if it is possible to upgrade to version 2.0 without additional cost? the licenses from
Cisco Prime Infrastructure 1.2 has to be upgraded or we need only to rehost the VUDI.
Also could be possible to upgrade LMS 4.x to Cisco Prime Infrastructure 2.0?
thanks!

The two features you mention are two big missing ones. Another is full syslog capability. I don't believe CiscoView or day one support via package updates is included either.
Another is less tangible - the depth of experience and documentation available for LMS vs. Prime Infrastructure (particularly the wired management features). I agree for wireless PI 2.0 looks good. Some new features are coming for wired that look promising but they are new as of PI 2.0 so I'm taking a wait and see on them.
I hope to get 2.0 up in my lab in the next week or so and will hope to be pleasantly surprised but that's seldom the case with a major new release.

Cisco nexus 6001 not a supported device on cisco prime infrastructure 2.1?

Similar Messages

Maybe you are looking for