anyone come across a problem before where a blade with Suse/Redhat linux installed loses connectivity when one of the HBA is disconnected? we have a situation where we have a blade with Suse linux 11 installed (SAN boot) & we configured 2 vHBA's (one on each Fabric) plus Powerpath is installed & configured correctly (as advised by SAN vendor).
we "disabled" one of the vHBA's & immediately we lost connectitity even though the 2nd vHBA was still "connected". as soon as we re-enabled the vHBA, it started working. we then tested by disabling the 2nd vHBA & left the 1st vHBA running & it still lost connectivity.
we will be looking at the powerpath logs, but i thought i would ask the forum to see if anyone can give some pointers,
have not tested without powerpath but i guess it will be the same.
reason for saying the above is that we found out the problem yesterday when SAN vendor was carrying out a FLARE code upgrade on the SAN & when SPA rebooted, our Suse server fell over. all other ESXi hosts continued working.
we checked the powerpath install & found that it was installed but was not registered. below was the output when querying the powerpath install:
# rpm -qa EMCpower*
# powermt check_registration
There are no license keys now registered.
# powermt display dev=all
PowerPath modules are not loaded.
Ensure that the modules are loaded and try again.
so i guess this "might" equate to powerpath not been installed as its un-usable.
we did get it registered & configured & asked SAN vendor to confirm the config & they were happy with it.
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...