The IP addresses 10.134.189.12 and 10.134.189.13 are server physical ip's. the cluster ip for these servers is 10.134.189.50. all these servers connected to cisco linksys switch1 and linksys switch2. linksys1 connected to Cisco6513 switch 1, linksys2 connected to cisco6513 switch 2 for redundancy. HSRP is configured.
The problem is i cannot ping cluster ip from outside subnet, and even i cannot ping from Core switch itself, But, if i ping any one physical ip from outside subnet, then i can ping cluster ip.
Even the outside subnet users can able to ping (after pinging physical ip), but still the core switch cannot ping cluster. but the path from outside users going via Core switch only.
I entered the static entry for arp as #arp 10.134.189.50 00bd.00af.bf32 arpa (alias)
subnet /25 Linksys1 Core C6513 Sw1
def gw-10.134.189.126----->ip10.134.189.122/25 --------->vlan 5- ip 10.134.189.25/25
Cluster ip 10.134.189.50 def gw 10.134.189.126 Def gw-10.134.189.126 (HSRP)
ip-10.134.189.13 Linksys2 Core C6513 Sw2
subnet /25 -------->ip10.134.189.123 -------->vlan 5- ip 10.134.189.30/25
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...
RBAC users like email@example.com may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...