Confirmed here as well -- ASDM 7.6(2) on 9.4(3)11 ... View more

I've run into this issue in the past when I switch my laptop from external monitors to the built-in screen.  ASDM always has a problem when I go back to my external monitors.  In the past it has resolved itself 'magically' but I wish I knew what to change to force it back. Edit:  I'm currently experiencing this issue and want to find a resolution, if any. ... View more

Thanks, Kevin - that's helpful to know. ... View more

Well I gave that a try but still no luck.  I'll have to open a case and see what happens. Thanks for all your help! ... View more

What version are you on?  I'm on 2.2 and it looks like they've added that drop rule by default now, along with two others: __Catch-ALL Drop__ (Priority 0, all else default, action DROP) __Punt ARP__ (Priority 1, Ethernet type 0x806, action CONTROLLER) __Punt LLDP__ (Priority 1, Ethernet type 0x88cc, action CONTROLLER) ... View more

Thanks, Charles.  I was missing a couple of key elements so I'm a little further a long now. Did you have any problems configuring connections?  I've got one setup right now to match all traffic on a few ingress ports, and send to an output port to one of my sniffer boxes, and that's working, but I"m also seeing the same data being sent out ports that are not configured as ingress or egress for a connection. Also, that caveat is pretty huge -- after all, the datasheet for NDB clearly states: Traffic replication and forwarding ●  You can aggregate traffic from multiple input tap and SPAN ports that can be spread across multiple Cisco Nexus switches. ●  You can configure the software to replicate and forward traffic to multiple monitoring tools that can be connected across multiple Cisco Nexus switches. ●  This solution is the only solution that supports any-to-many forwarding across a topology. Did your Cisco contact say if that was a temporary issue? ... View more

Any luck on this?  I'm just getting started with NDB and am also running into problems. The documentation seems pretty thin on this. ... View more

Yeah, you're right -- distribute lists are not supported in NX-OS. I didn't realize that. This page also has a helpful feature comparison -- NX-OS/IOS OSPF Comparison.   Sounds like they added the table-maps to in later versions though, so TAC should be able to tell you which version will support it.     ... View more

With the MPLS network in the middle, your Branch and HQ are effectively in two separate OSPF domains even though they are both configured to be in area 0.  You can see this because the routes from the branch are being received as E2 External routes (ospf-1, type-2), which are learned from Type-5 LSA messages from an ASBR (The HQ CPE where BGP/OSPF interact). The area x filter-list command only filters Type-3 LSA's at ABR's, which is why it doesn't seem to be doing anything for you.   If you want to prevent these routes from being entered into the routing table, I believe you should be using a distribute-list on the HQ router. ... View more

Just wanted to provide an update --  I opened up a case with TAC and worked with an engineer to try and find the cause of the issue.  The TAC engineer was unable to identify the cause, mostly because the usual suspects for mac flapping were not present.  We agreed to a reboot during a weekend change window and since the reboot everything has been working fine.  ... View more

That's not necessarily true -- It covers about 8 hours of time and while the log only contains SSH information, it also *doesn't* contain any other obvious issues -- MAC Flap notifications, link up/downs, etc.  I checked again this morning and it hasn't logged anything since yesterday when I grabbed the output. ... View more

Here are the requested outputs.   This is a stack of four 3750X, connected to a pair of 4500-X in VSS. ... View more

Thanks for the update.  I figured it was cosmetic only, but like you said, the configuration monitor always alerts so it'd be nice to fix. ... View more