Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

UCS Manager Update from 2.1(1a) / 2.1(1b) to full 2.1(3b) cause Policy Reference Error on iSCSI

Hello,

I actualy did a UCS firmware upgrade from a mixed 2.1(1a) and 2.1(1b) to a full 2.1(3a) version.

Chassis are 2208XP, Fabrics are 6248UP and blades are all B200-M3.

I use firmware policy to update the firmware on the blades.

Here are the current version of the different componments:

- CIMC, Adapterers and BIOS Server: 2.1(3b)

- UCS Software: 2.1(3b)

- IO Modules:  2.1(1b)

- Fabric Kernel / System : 2.1(1b)

After UCS Software update when I connect on UCS Manager I got several warning referencing the error "Policy reference autProfileName does not resolve to named policy" on different parts.

I have follow some post to resolve some of them:

- iSCSI nic is created without Authentication profile issues:

https://tools.cisco.com/bugsearch/bug/CSCui43905

- Default SOL policy issue:

https://tools.cisco.com/bugsearch/bug/CSCtl88314

This resolve a lot of error but I'm still having errors like this on all my iscsi NIC:

2014-01-10_104558.png

Causing this:

2014-01-10_104454.png

Right now the update of the IOMs and FIs are on standby until I resolve this.

Can I have some help please.

Everyone's tags (5)
2 REPLIES
Cisco Employee

UCS Manager Update from 2.1(1a) / 2.1(1b) to full 2.1(3b) cause

It looks like you are hitting:

https://tools.cisco.com/bugsearch/bug/CSCui43905

Symptom:

Warning with the text "Policy reference  authProfileName  does not resolve to named policy" is seen when creating  an iSCSI nic on a service profile.

Conditions:

Issue happens only when iSCSI nic is created without an Authentication profile

Workaround:

Use Authentication profile

Create a Default Authentication Profile

Existing  warnings from the previous version would still exist even after the  upgrade and that can be isolated only using the above work around. If  new service profiles are created on the 2.2.1b version will not  experience this issue.

Here is how to create an authentication profile:

http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_011111.html#task_5DBBCD17FFA046A395B4493104838B1F

New Member

UCS Manager Update from 2.1(1a) / 2.1(1b) to full 2.1(3b) cause

Thank you for the answer but like I said I have allready follow this two case who make me resolve some warning but not all.

- iSCSI nic is created without Authentication profile issues:

https://tools.cisco.com/bugsearch/bug/CSCui43905

- Default SOL policy issue:

https://tools.cisco.com/bugsearch/bug/CSCtl88314

I do some more tests, dissassociate and reassociate service profile on two different blades make the warning disapear on them.

Look’s like I found the solution but I still have to do it on 14 blades...

579
Views
5
Helpful
2
Replies
CreatePlease login to create content