03-23-2017 02:47 PM - edited 03-01-2019 01:07 PM
Can you please help me, I cant seem to sort out an issue I’m having.
Trying to associate a service profile to a B200-M3 blade with a ViC 1240 adapter.
it is failing at 25%
Remote Invocation Result: End Point Unavailable
Remote Invocation Error Code: 869
Remote Invocation Description: Adapter:unconfigAllNic failed
seems the DCE is not seeing the B-Side of the chassis
the second attachment is a working blade with same hardware config.
please help!
Solved! Go to Solution.
03-24-2017 06:59 AM
Well you shouldn't be hitting the issue on the blade level firmware you are at.
If this is the issue that that error typically represents, there was an issue within the VIC card firmware where a config file didn't get created. It is pretty easy for TAC to ID the issue if they have a Chassis tech support file, and sometimes requires a debug level access to the adapter to correct. Can't give you much more help at the forum level without having access to the server/tech supports.
I would go ahead and reach out to TAC.
Thanks,
Kirk...
03-23-2017 06:18 PM
Greetings.
What UCSM firmware are you running?
I recall a few cases with your similar config in the 2.13 firmware range that require TAC intervention for a similar set of errors. Depending on whether you are hitting a bug, you may want try bumping your blade/adapter to 2.24b or higher blade bundle level temporarily to see if that resolves.
If you are using a higher version (i.e. 2.26/2.28 ) already, then you'll probably want to open a TAC case.
Thanks,
Kirk...
03-24-2017 06:07 AM
Hi Kirk, below is the firmware levels of the blade. These were tested and upgraded to a 3.1xx package in lab before being sent on site where the UCS environment is running on a 2.2xx firmware.
The funny thing is, we went to install 4 blades with identical config and firmware levels, and this is the only one having problems.
Could there be a problem with the blade or VIC? or more likely the IOM or service profile itself?
Any guidance is much appreciated.
Thanks again
Server 1/1:
CIMC:
Running-Vers: 3.1(22a)
Package-Vers: 3.1(2c)B
Update-Status: Ready
Activate-Status: Ready
Adapter 1:
Running-Vers: 4.1(2d)
Package-Vers: 3.1(2c)B
Update-Status: Ready
Activate-Status: Ready
BIOS:
Running-Vers: B200M3.2.2.6d.0.062220160055
Package-Vers: 3.1(2c)B
Update-Status: Ready
Activate-Status: Ready
RAID Controller 1 SAS:
Running-Vers: 20.13.1-0255|4.38.02.2|NA
Package-Vers: 3.1(2c)B
Activate-Status: Ready
BoardController:
Running-Vers: 15.0
Package-Vers: 3.1(2c)B
Activate-Status: Ready
Local Disk 1:
Running-Vers: 0005
Package-Vers:
Activate-Status: Ready
Local Disk 2:
Running-Vers: 0005
Package-Vers:
Activate-Status: Ready
03-24-2017 06:59 AM
Well you shouldn't be hitting the issue on the blade level firmware you are at.
If this is the issue that that error typically represents, there was an issue within the VIC card firmware where a config file didn't get created. It is pretty easy for TAC to ID the issue if they have a Chassis tech support file, and sometimes requires a debug level access to the adapter to correct. Can't give you much more help at the forum level without having access to the server/tech supports.
I would go ahead and reach out to TAC.
Thanks,
Kirk...
03-24-2017 07:04 AM
Sounds good thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide