Service Profile Not Associate

[fantasy24]

Hi Guys,

I am currently encounter this issue. I am not sure what is this. It is something on the association service profile.

Can you guys advise?

Thanks in advance.

ABC /chassis/server # show detail

Server:

    Slot: 1

    Name:

    User Label:

    Overall Status: Config Failure

    Oper Qualifier: N/A

    Service Profile: ABC-C5-5108-1

    Association: Failed

    Availability: Unavailable

    Discovery: Complete

    Conn Path: A,B

    Conn Status: A,B

    Managing Instance: A

    Admin Power: Policy

    Oper Power: On

    Admin State: In Service

    Product Name: Cisco UCS B200 M2

    PID: N20-B6625-1

    VID: V01

    Vendor: Cisco Systems Inc

    Serial (SN): -

    HW Revision: 0

    Memory (MB): 98304

    Effective Memory (MB): 98304

    Operating Memory Speed (MHz): 1067

    Operating Memory Voltage: Low Voltage

    Cores: 8

    Num Of Cores Enabled: 8

    Adapters: 1

    Eth Host Interfaces: 4

    FC Host Interfaces: 0

    Burned-In UUID: 4c8e3c3c-520c-11e0-a744-d8d3857fae00

    Dynamic UUID: b1465590-900f-11e0-0000-00000000000a

    Current Task 1: Configure secondary fabric interconnect for server host OS (service profile: org-root/ls-ABC-5108-1)(FSM-STAGE:sam:dme:ComputePhysicalAssoci

ate:SwConfigHostOSPeer)

    Current Task 2:

    Current Task 3:

[padramas]

Hello,

From the service profile section, can you please share the FSM / failure reason displayed by UCSM ?

Also, what is the version of UCSM ?

Padma

[fantasy24]

Any idea? Thanks in advance.

[padramas]

Thanks for the screen shot.

Has this service profile worked before ?

UCSM version ?

Padma

[fantasy24]

Yes. It worked before.

UCSM is

Version 1.4(2b)

Thanks lot.

[Gregory Scarlett]

Hi,

You're running a version of UCSM that was deferred, which caused problems such as the one you are experiencing.

Please open a TAC case so that we can perform the workaround.  You will need to upgrade to a 1.4.3 release to fully resolve the issue, but the workaround will need to be applied first.

Regards,

Greg.

[fantasy24]

I see. So can I say that the version in my environment having bug?

[padramas]

I believe system is running into following defect

Blade Issue - Discovery and Dis-association of SP failing [mts queue up]

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&b
ugId=CSCtq03411

you can confirm it by running following commands

connect nxos a
show system internal mts buffer summary

connect nxos b
show system internal mts buffer summary

Please open a TAC service request so that we can help you out.

Padma

[fantasy24]

Yup.

show system internal mts buffer summary

node    sapno   recv_q  pers_q  npers_q log_q

sup     1489    2       0       0       0

sup     1440    5       0       0       0

sup     1438    5       0       0       0

sup     1436    209700  0       0       0   <-----

sup     284     0       2       0       0

sup     396     0       0       4       0

sup     761     0       0       1       0

[Gregory Scarlett]

Thanks - that confirms that you are hitting the bug.

We'll need to login to the system and perform the workaround.  Please raise a TAC case and we'll be happy to assist.

Regards,

Greg Scarlett

[fantasy24]

Hi Gregory,

Last Q.

For the workaround to be done, is there any downtime for that?

Thanks.

[Gregory Scarlett]

Hi,

There should not be any impact to services.  The workaround will take around 20-30mins to complete.  The problem will eventually return until the code upgrade is done.

[fantasy24]

Thanks guys

Sent from Cisco Technical Support iPhone App