Cisco Bug: CSCtc29828 - RHEL kdump kernel fails in large vnic configuration
Oct 04, 2012
- Cisco Unified Computing System
Known Affected Releases
Symptom: RHEL 5.4 kdump does not succeed with M81KR and a large vnic configuration. Conditions: RHEL 5.4 system with kdump setup using the boot parameter: crashkernel=2000M@16M or smaller. A Palo (M81KR) card with a large number of vnics (e.g., 40 enics and 16 fnics). All 40 enics configured up (onboot=yes in ifcfg-ethX files). When a system crash occurs, the kdump kernel doesn't boot successfully and/or its rc scripts don't succeed, and the crash dump is not saved.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases