1) ASM cannot be updated with rollup updates
Error message: „Additional information: cannot take additional install request. Rollup updates are being applied.“
Solution:
Please do an RDP-session into the ASM and delete all files in C:\UX\PUBLIC\XFER and reboot again.
Also, make sure to turn off Windows update for automatic updates (from Group policies)
Then try again. 🙂
2) ASM Operational Status not available on the SBC GUI (all: unknown)
1.Uninstall the comm service from the ASM
2.Reinstall the comm service with the latest version.
3.After the reinstall in complete restart the ASM (from Windows RDP)
4.Wait until the ASM reboots and power-cycle the SBC
3) How to check the communication status between SBC and ASM host
One can reboot the ASM and do the following:
Go to Diagnostics / Debug Facility / SBA Service / Show / discovery report on SBC.
*********************************************
„SBC reports I2C device:“ reports if ASM and SbcComms use network or I2C serial bus to communicate.
Check the state:
0/8: COMMS_NET_HELLO: Waiting for ASM to give sign of life.
1/8: COMMS_NET_DISC: Got a sign of life from ASM.
2/8: COMMS_UX_SLEEP: Waiting for the ASM to come back, low activity mode
3/8: COMMS_UX_UP: SBC received the IP address in use by ASM (usefull for DHCP case).
4/8: COMMS_WAIT_SBA_UP: Waiting for ASM to complete basic IP CONFIG (IP and Mask eth0).
5/8: COMMS_SEND_CONFIG: Waiting for ASM to complete full IP CONFIG (GW, DNS, additional NICs,…).
6/8: COMMS_START_SERVICES: Requested ASM to start the SBA services
7/8: COMMS_WAIT_SERVICES_UP: Waiting for ASM to start SBA services
8/8: COMMS_READY: Communication is running
