Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi ,
I just upgraded My APICs from 5.2(3e) to 5.3(2f) upgrade went smooth with no issues ,
When I tried to start upgrading the Fabric as Below :
During validation i received the below critical issue :
Before I continue I double checked that ...
Hello , I have a Customer that wants to enable encryption for a production cluster but he wants to understand what will be the impact of enabling the feature on exciting date on the cluster. RegardsAmr
As I was trying to rebuild a cluster one of the nodes failed deployment as per attached Have anyone seen this before ? Do you know a work around ? RegardsAmr
whenever I start a KVM session it terminates with the below message :" Client has been shut down as a result of the network connection has been dropped. " have anyone seen this before
I have replication Network config failure on 2 clusters Cluster-1: Failed to post the Replication Network jobHX does not even touch UCSM or Vcenter , I am using HXDP 35.(2d) Cluster-2: [137] : Configure Bandwidth on Nodes - Failure: Error: Failed to ...
Thanks Robert That works ,
Another Issue came up is One of the Spines is Completely unreachable now after the upgrade
How Can I rollback ?
What troubleshooting Actions I can take ?
Regards
Amr
Setting a different ip worked and by the way , KVM access failed while HX installer was in the UCSM configuration stage with the message SOL access failed. Also ,While expanding the Cluster with compute-only node , it failed to detect installed ESXi ...
Thanks Kirk , i tried it , did Not work , reset CIMC ip on service profile did not work neither , I configured static ip on KVM and vola , works as a charm
DC-1 : expanded with 8 compute-only node clusters DC-2 : expenses with 3 compute-only node clusters is there any other way of adding compute-only node to the cluster ?
