Hello Matthew,
we have updated the list of affected versions per device type in the Release Notes of CSCuw84708. Please take a look at it.
While the developers are still working to patch all the NX-OS releases, it appears that 7.2(1)D1(1) for N7K is still vulnerable. I suggest to open a TAC case if you would like to receive more info about the availability of the fix.
Hope it helps!
Andrea Baldan
... View more
Hello, this seems to be due to: CSCub58778 - DM download for single sup using switch URL returns error 403. Release note is here: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCub58778 You may want to install DCNM-SAN and use the version of device manager that comes with that and that is aligned with NX-OS 5.2(6a). You can either use DCNM 5.2(2e) or 6.1(1b) for example. Hope it helps! Andrea
... View more
Hi David, what is exactly the issue and the help you need here? Is it the NetApp fc ports showing up as "enabling"? And are the ports 25-32 configured as FCoE or FC? Regards, Andrea Baldan
... View more
Consider the following basic topology: When configured in multicast mode, MS NLB will use a 03xx.xxxx.xxxx multicast address outside of the IANA range. Normally, when there is no FWSM in path between client and NLB servers, you configure the switch in the way described here: http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a0080a07203.shtml or here: https://supportforums.cisco.com/thread/2052888 In short, you need to add static ARP entries to your switches that route into the NLB VLAN (this is necessary as the clients are going to access the NLB cluster at its unicast IP which is tied to the multicast MAC, and Cisco devices do not accept an arp reply for a unicast IP address that contains a multicast MAC address. ) arp 172.16.63.241 <multicast MAC of the VIP> and to add static MAC entries (fa2/3 and 2/4 are the switch ports the servers are connected to): mac-address-table static <multicast MAC of the VIP> vlan 200 interface fa2/3 fa2/4 Now, consider the following topology, where we add a transparent FWSM bridging vlan 200 and 300: If the NLB cluster is configured in multicast mode, the traffic going to the servers will be dropped by the FWSM, even though the switch is configured correctly. This is because the FWSM does not allows multicast MAC addresses outside of the IANA range through, when in bridged mode: http://www.cisco.com/en/US/docs/security/fwsm/fwsm40/configuration/guide/fwmode_f.html#wp1222689 The solution is to configure the NLB cluster in Multicast mode with IGMP support, so that the virtual mac-address of the NLB VIP will be in the IANA range 0100.5Exx.xxxxx. Here is a link showing how to configure the NLB cluster accordingly: http://support.microsoft.com/kb/323437/EN-US/
... View more
Hi Matt, thanks for sharing this. To add more details as to why we need to sync the DM running on the standby ACE: http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/device_manager/guide/UGha.html#wp1059949
---- snip ----
When an ACE appliance is in a standby state, if you make configuration changes on the active ACE appliance this change is also synchronized with the standby ACE appliance. However, when you access the Device Manager GUI you will not observe the configuration changes on the standby ACE.
...
As a result, it is important for you to manually synchronize the ACE
Appliance Device Manager on the standby appliance to observe the entire
configuration.
---- snip ----
Cheers, Andrea
... View more
