On May 23, 2016 2:14 AM, "Lukas Tribus" <[email protected]> wrote: > > > Been hit by this: > > > > http://www.cisco.com/c/en/us/support/docs/field-notices/641/fn64110.html > > https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuw75381/?reffering_site=dumpcr > > > > and looking for an SNMP OID to establish monitoring and alerting across all > > models and code version, while planning for upgrades. Cisco TAC provided no > > feedback, so far, and we have no high hopes for throughout the weekend, in > > this regard, on their part (the severity is being addressed, from their > > stand point, by upgrading) > > According to the field notice TAC has a workaround: > > > If an upgrade cannot be performed immediately, contact the Technical > > Assistance Center (TAC) in order to load a debugging plugin. This grants > > access to the Linux shell where the ports can be temporarily blocked via > > the CLI. Note that this workaround does not survive a reload, and the > > NX-OS upgrade is suggested as a long-term fix. > > > So you should probably insist on that workaround. > > Lukas >
It's the monitoring and alerting part I was interested in, necessary prior to the blocking. Stefan _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
