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.
Default vsan (vsan0001) in UCSM is showing as Admin status okay but Operational status down (major alarm from Monintoring system)=========================================================================================================================...
What naming guidelines to use for Cisco UCS Chassis and Blade / Server?======================================================================1. Our Monitoring Tool Dicovers the UCS manager and all its components including FI's, Chassis, Servers etc i...
Cisco Fabric Interconnect is having some Pmon Services as failed
==================================================
FI-B(local-mgmt)# show pmon state
SERVICE NAME STATE RETRY(MAX) EXITCODE SIGNAL CORE------------ ----- ---------- -------- ------ ----...
Hmmm. is there any way to basically disable / suspend this vsan in order to avoid the alarms for VSAN0001 being down.
All we want to accomplish is to get rid of the alarms for the VSAN0001 by not breaking anything in the environment.
Hi Riaan,Looks like we are also using the same monotoring tool, Sciencelogic. But problem somehow is we don't have the right options enabled so Naming is simmilar for all domains and it is hard to differntiate for us. Can you please guide me as how t...
Hmmm, that looks preety okay. But are you using UCS central for managing Differnt Domains?Because in our case we are using 5 diifernt UCS managers altogether for managing 5 differnt environments.ThxImran
I am happy to inform you that the issue with the UCS GUI has been resolved. I worked with TAC and they confirmed that it was the same bug that Steven had identified. We followed the steps suggested to kill and restart the pmon process for user1&2 & ...