One of the (sadly numerous) issues I’ve run into while upgrading to Cisco UCSM version 2.2(1b) is this little error message indicating that a service failed to start:


This gives us an error code of F0867 and it’s letting us know that the UCSM process failed on one of our Fabric Interconnects.

For those that don’t know, you can get a list of processes within UCSM by connecting to local management and running “show pmon state”.

DCB6296FAB-A# connect local-mgmt
DCB6296FAB-A(local-mgmt)# show pmon state 

------------             -----     ----------    --------    ------    ----
svc_sam_controller     running           0(4)           0         0      no 
svc_sam_dme            running           0(4)           0         0      no 
svc_sam_dcosAG         running           0(4)           0         0      no 
svc_sam_bladeAG        running           0(4)           0         0      no 
svc_sam_portAG         running           0(4)           0         0      no 
svc_sam_statsAG        running           0(4)           0         0      no 
svc_sam_hostagentAG    running           0(4)           0         0      no 
svc_sam_nicAG          running           0(4)           0         0      no 
svc_sam_licenseAG      running           0(4)           0         0      no 
svc_sam_extvmmAG       running           0(4)           0         0      no               running           0(4)           0         0      no           failed           5(4)           0         0      no 
svc_sam_sessionmgrAG   running           0(4)           0         0      no 
svc_sam_pamProxy       running           0(4)           0         0      no 
sfcbd                  running           0(4)           0         0      no 
dhcpd                  running           0(4)           0         0      no 
sam_core_mon           running           0(4)           0         0      no 
svc_sam_rsdAG          running           0(4)           0         0      no 
svc_sam_svcmonAG       running           0(4)           0         0      no

As you can see, this process is indeed failed. Now - the UCS fault reference will tell you that if this happens, regardless of which process it happens to be, you should generate a show-tech UCSM and call TAC. I have to agree with this, because usually it’s not a good idea to take any action to fix this yourself.

However - since this happened to me within a TAC call, I learned that this particular process is actually new in UCSM 2.2 - you now have the ability to use a web browser (HTTP) to go directly to a blade’s IP address in order to launch the KVM window.


The process “” is the process that allows UCSM to manage these connections. The reason this process wasn’t starting was because I hadn’t upgraded my Fabric Interconnects firmware yet - only the UCSM application itself. UCSM wasn’t able to find the proper binaries to run this process because they didn’t exist. So, finishing the upgrade and rebooting the FIs took care of this for me.

Always err on the side of caution, however. Always follow upgrade guides to the letter, and if you’re in doubt as to what these processes do, get on the support forums or call TAC.

Matt Oswalt

Matt Oswalt is an all-around technology nerd, currently focusing on networking, software development, and everything in between. He is at his happiest in front of a keyboard, next to a brewing kettle, or wielding his silo-smashing sledgehammer. He spends his days diving deep into the intersection of networking and software, and likes to blog about his experiences when he comes up for air. You can follow him on Twitter or LinkedIN.