I have One UCS 210M2 server and two Nexus 7K.We want to configure portchannel(etherchannel) UCS two NIC card and connect to each nexus 7K.Is this design supported, connecting UCS port-channel on two nexus 7K? we dont have 5K or 2K switches.What configuration required from Nexus 7K to achieve this vPC directly with UCS 210M2 servers?
We are facing issue of continous packet discards On nexus4001L link (int po2) to Nexus5020 switch. Nexus4001L is installed in IBM blade center server and we have FCOE enabled in this setup. [code]
I have been tasked to replace the existing Cat 6500 and 3750 switches by Nexus 7000 and Nexus 2000.I was told initially my boss plans to get 2 x Nexus 7000 and then eventually blow up to 4 x Nexus 7000s.For Nexus, is there a list of tasks / points that i need to consider for building the initial design?
Can i just link the Nexus 7000 like the following?
N7k-A ========= N7k-B | | lots of N2ks lots of N2ks
we are planning a Nexus datacenter project with this layout:Our experiences with Nexus switches are not so large until now and the manuals are very extensive.Both N5K´s should be connected directly with all 4 N2K switches. I did not find a layout like this in the manuals. Only a design,where only 2 N2K are connected to one N5K, with this fex config:Now I´m not sure if it is right to make a config like this with the same slots and fex´s or with different slots and fex´s.
Trying to implement PBR in N7K? I found that there is not track mechanism can use in "set next-hop ip", so if the next-hop is unreachable that the route might be died.
I have multicast routing setup between two Nexus 7K's.These Nexus 7K's act as the distribution layer and they connect to 48 different 4507 access layer switches (VPC) and 3 6509 core layer switches.The 4507 swiches have two supervisor modules. One acting as active and the other as hot standby. Let's assume that multicast is working on the active module. If I pull out the active module the hot standby takes it's place. This is where multicast stops working on the switch.How can I get both Nexus 7K's to work with multicast at the same time. Here is an example of show ip mroute from both Nexus 7K's:note that DR02 has a lot more entries in the routing table. Is this working as designed?
DR01-C7018# sh ip mroute IP Multicast Routing Table for VRF "default" (*, 224.0.0.0/4), bidir, uptime: 1y11w, pim ip Incoming interface: Ethernet3/1, RPF nbr: 172.18.254.109 Outgoing interface list: (count: 1) Ethernet3/1, uptime: 29w3d, pim, (RPF)
I am trying to determine why hosts off our Nexus 7010s are being picked up in UT. Since LMS 4.0.1, UT should be supported on these devices.When adding the Nexus devices to DCR, provide the netadmin SNMP RO credential.When other SNMP RO credential is provided, user tracking will not collect end host data.I think I have this setup correctly as the device center test passes when cehcking snmp ro credentials.Our 7010s are running NX-OS 5.0(3) - earlier than the recommended version - might that cause issues? We are not using VRFs other than the default and management.
Here is my snmp section:
sh run | sec snmp ip access-list copp-system-acl-snmp 10 permit udp any any eq snmp 10 permit udp any any eq snmp 20 permit udp any any eq snmptrap
I was trying to get Netflow setup on one of my 7K VDCs and ran into a problem. While netflow data was reaching the collector, IP src/dst information was not appearing in the analyzer tool. I could not see any information about conversations. So I contacted the company that makes the collector/analyzer and the directed me to a blog on their site and told me to setup the 7K exactly as it is described in the blog post. I did and a bit later the ip src/dst address information appeared. So the only difference between the two configurations was that in the first case I tried to define a record and in the second case, no record was defined and instead the orginial-netflow parameter was used in the "flow monitor" section. [code]
I referenced the document "Cisco Nexus 7000 Series NX-OS System Management Configuration Guide,Release 6.x", Chapter 19 - Configuring NetFlow.It's clear to me that I didn't do something right in defining my own record since that's really the only difference between the config that worked vs the config that didn't. However, the documentation I referenced doesn't really provide useful information about how to create a record (above and beyond what I can already see by typing '?' at the CLI).
For example, the "match" command makes no sense to me. Usually when you have a match command it is accompanied by some sort of ACL. In the "flow record" section a match command would be something like "match ipv4 source address" but that's it. What does that mean? Match anything that has a IPv4 source address?? That doesn't make much sense. The collect commands are equally as bewildering. If I want to define my own record (and not use the original-netflow parameter) what do I need to do in the "flow record" sub-configuration to get Nexus to send ip src/dst information to the collector (which, I would think, is basic information to send - what good is netflow data without it)?
I am trying to upgrade IOS on my Nexus7018 from version 5.12 to 5.13. I have managed on all my three out of four Nexus succesfully but one of them is keep coming with this error,
""""N1K-7018-1# install all kickstart bootflash:n7000-s1-kickstart.5.1.3.bin system bootflash:n7000-s1-kickstart.5.1.3.bin
Another install procedure may be in progress. Please try later.
how to find out which other install is running or stop any install procedure.?
i have a couple of nexus 7010 (5(2)3a) connected to a checkpoint in HA(active/active)I have now to configure multicast mac..i found this commmand: [code]
We have configured multicasting for our Nexus 5K switches. and for the most part everything seems to be working until recently.
Setup is we have 2 Nexus 5k switches connected via Dark FIber from Site A to Site B. Site A is sending the multicast traffc and Site B is receiving it.
I am looking to configure PBR in Nexus. The current setup in IOS is :
interface Vlan10 ip address 172.27.206.1 255.255.255.0 ip address 172.27.208.1 255.255.254.0 secondary ip policy route-map Vlan_10_to_Corp route-map Vlan_10_to_Corp permit 10match ip address Vlan_10_to_Corp set ip next-hop 172.27.209.250!route-map Vlan_305_to_EFH permit 30
[code]....
But, Nexus PBR will not work with deny statements init. Now, what options do I have ?
I am trying to connect my sever with daual homed to two Nexus 2232 fex which are part of two Nexus 5548 vPC pair( topologyu attached) but getting error on Nexus 5548 as below,
Not sure its allowed under Nexus 2000.
""Port-channel members across FEXes is not allowed, new member Ethernet101/1/12(0x1f6402c0) existing membe: : Ethernet100/1/12 command failed: port not compatible [All HIF member ports not in same pinning group]"""
I can't find any configuration info for any MPLS layer 2 extension features for the Nexus 7k devices, is this a strategic decision by Cisco to promote OTV?
I want to apply QoS policy on a particular VM for specified port range only. I have created following script file but that doesnt work. I mean it doesnt apply any policy on vm residing on Veth1.
config t ip access-list acl_in 101 deny tcp any any eq 443 exit
I have a nexus 7009 that used to work connecting via SSH. However now I cannot connect to it via ssh. It appears the SSH is connects but doing a show users from the console shows nothing connected other than the console connection.
N5K will be running on Layer 2 mode. vPC configured between N5K and N2K Servers are part of Vlan 10, 20, 30 and Juniper SRX firewall is the gateway for all the servers. SRK firewall is Active/Standby mode.
Questions are
1) Is there any non-vPC link required between N5K in this scenario?
2) N5K will pass in/out traffic to juniper SRX firewall durining SRX failover as well as normal operation
We run 6509 core routers as NTP servers to other IOS routers/switches & servers of several OS flavours.All good. Recently added some Nexus 5000s and cannot get them to lock.No firewalls or ACLs in the path
I have two different model's of GLC-T SFP's. One is PN 30-1410-02 the other is PN 30-1410-03. The -02 will not work in Nexus 5020 or an ASR-1000 router that I have, but works fine in my Cisco Wireless Controller. The -03 works fine in any device. My problem is when ordering, you can not specify the -03 they get ordered as GLC-T and none of my suppliers can assure me that I would get the -03.What is the difference between these two?
With most of my Layer2/Layer3 switches, I'm accustom to giving them a SVI on my management VLAN, and calling it a day. I can't find in the Cisco Nexus guides how to do something similar; everything points to the mgmt0 physical interface, which seems like I need to uplink it to an access port on another switch. Can somebody point me in the right direction for how to do give the Nexus an IP that I can ssh/snmp into it across a trunk for management? I must just be missing the keyword.. NX-OS is still quite a different beast.I see in the manual it says: "SSH has the following prerequisites: You have configured IP on a Layer 3 interface, out-of-band on the mgmt 0 interface or inband on an Ethernet interface." Cisco Nexus 5000 Series Switch CLI Software Configuration Guide page 284, How do I configure an IP on a Layer 3 interface on a Nexus?
I am looking how to see the mac table on a Nexus 5000 switch running NX-OS and confirm the mac address on a certain port. Similar to the Sh mac-address-table in IOS and sh cam in Cat-os.
I am sure this is simple I just cannot find the command.
There are times the Nexus CPU goes high around 70% but its not a constant occurance. Is there something to worry. Quite hard to find out which process caused it as it happens very brief. [code]
I'm busy on configuring the backup of the configuration from Nexus switches 5K and 7K.I have installed COPSSH on my windows server and try to confiugre the sftp credentials. [code] I have tested from the CLI from the switch and i have the issue but if i use the default vrf 'default' it works fine.How can i change the command sent by DCNM to the Nexus in order to specify vrf default and not vrf management ?