I am trying to iSCSI boot RHEL6.1 using our B200 and M81KR Palo nic.
Installation of RHEL6.1 is successful, but I encounter a "Kernel panic - not syncing: Attempted to kill init!" error message when I attempt to boot the OS.
-Service profile has four vNICs configured. Two of these vNICs (named 'eth0' and 'eth1') are used for management and on vlan100. The other two vNICs (named 'eth2' and 'eth3') are used for data purposes and are both on vlan7.
-I have one iSCSI vNIC configured with the default iSCSI Adapter Policy applied. iSCSI vNIC is overlayed on 'eth2'.
-native vlan enabled on each interface and vlan.
Storage configuration is a Nimble Storage CS240.
Data ports of the array are directly connected to the FI and FI ports are configured as Appliance ports.
Can someone please explain to me why RHEL is able to iSCSI boot if I have a local disk installed? In my original post, I did installation with the local SAS drives physically removed from the blade. In this setup, booting without SAS drives caused the Kernel Panic after ~80% of the OS had loaded. The only device in this setup, and during installation, is the iSCSI device itself.
Howerver, if I choose the same installation options, but I have SAS drives phyically attached to the blade, then RHEL is able to iSCSI boot??? Your likely thinking in this setup I made a mistake and that I am booting from the local drive. It's posible my loader configuration is wrong, but when I do a 'du -h' is it shows that my root partition is on my 50GB iSCSI disk.
And the question would still remain as to why the Kernel Panic occured if there were no physical disks installed?
For my (in)sanity check, can someone please remove all non-iSCSI disks from their B200, try to install RHEL6.1to an iSCSI device, and then iSCSI boot it? Possible RHEL bug here?
And perhaps it is user error. Below are the installation screenshots of the major installation steps. Can someone please point out what I'm doing wrong that would somehow involve the local SAS disk?
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...