BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

After move HP VC flex fabric modules to other bays I can not access VCM

SOLVED
Go to solution
mc21_hp
Advisor

After move HP VC flex fabric modules to other bays I can not access VCM


I took my VC modules from bays 7,8 and moved it to bays 3,4.

Was:
bay7 IP - 192.168.128.47
bay8 IP - 192.168.128.48

Became:
bay3 IP - 192.168.128.185
bay4 IP - 192.168.128.186


Then I fixed modules IP to previous addresses through OA web interface

Became:
bay3 IP - 192.168.128.47
bay4 IP - 192.168.128.48

Now when I try open VCM (by the way my version - 4.50)

https://192.168.128.48 -> "The active Virtual Connect Manager is not at this IP address currently."

https://192.168.128.47 -> redirect to https://192.168.128.48 -> "The active Virtual Connect Manager is not at this IP address currently."

How can I fix this problem?

21 REPLIES
peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Hello
What type of VC modules ?
What are module located in slot 1 and 2 ?
Thanks
JY
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

I have two HP VC FlexFabric 10Gb/24-Port Module (version 4.50)

Cisco Catalyst Blade Switch 3120X for HP are in bays 1, 2

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Power off one VC and try again
Also try using SSH instead
JY
Torsten.
Acclaimed Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

ssh to the OA and do a

connect interconnect 4

logon and do

show all

Does this work?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

What I got to try after power off one VC ?

mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

>ssh to the OA and do a

>connect interconnect 4

>logon and do

>show all

>Does this work?

 

It doesn't work:

mc-blade-01-oa2> connect interconnect 4

NOTICE: This pass-thru connection to the integrated I/O console
is provided for convenience and does not supply additional access
control.  For security reasons, use the password features of the
integrated switch.

Connecting to integrated switch 4 at 115200,N81...
Escape character is '<Ctrl>_' (Control + Shift + Underscore)

Press [Enter] to display the switch console:

VCEFXTW21480004 login: Administrator
Password:
Virtual Connect Manager not found at this IP address.
The location of Virtual Connect Manager has not yet been established, please
wait for initialization to complete.

Output for interconnect bay 3:

mc-blade-01-oa2> connect interconnect 3

NOTICE: This pass-thru connection to the integrated I/O console
is provided for convenience and does not supply additional access
control.  For security reasons, use the password features of the
integrated switch.

Connecting to integrated switch 3 at 115200,N81...
Escape character is '<Ctrl>_' (Control + Shift + Underscore)

Press [Enter] to display the switch console:

Login timed out
VCEFXTW21050059 login: Administrator
Password:
Virtual Connect Manager not found at this IP address.
Please use IP Address: 192.168.128.48 Or fe80::461e:a1ff:fe78:c718

mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

If it isn't possible to take control of Virtual Connect in my case how can I reset VC modules to factory defaults?

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Did you try with only one VC ?
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

I tried with only one VC module one or another. No success.

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Try to remove lock on oa (clear VC mode button under enclosure setting )
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

After "Clear VC mode" button in OA web-interface I got strange effect. in the OA web-interface I saw "Virtual Connect Mode is currently: Disabled"

I still can not login to VCM on bay 4 IP 192.168.128.48 (result was - The active Virtual Connect Manager is not at this IP address currently.)

I can log in to VCM on bay 3 IP 192.168.128.47. User name and password was accepted and "Virtual Connect Manager Domain Setup Wizard" started. On second screen of wizard I entered "OA User Name" and "OA Password". After I pressed "Next" text "Finding Local Enclosure" arised. Then I got error "The web browser was not able to communicate with Virtual Connect Manager in the allowed time. You will be redirected to the login page."

After relogon I got same as in start of topoic situation:

When I try open VCM:

https://192.168.128.47 -> redirect to https://192.168.128.48 -> "The active Virtual Connect Manager is not at this IP address currently."
https://192.168.128.48 -> "The active Virtual Connect Manager is not at this IP address currently."

And in the OA web-interface (where button "Clear VC Mode" is) I see "Virtual Connect Mode is currently: Enabled"

 

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Seems an issue between module In slot 3 and 4 (no comm)
Please Try to do again with only one module on slot 3 nothing on slot 4 (clear vc mode)
JY
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

>Seems an issue between module In slot 3 and 4 (no comm)
>Please Try to do again with only one module on slot 3 nothing on slot 4 (clear vc mode)

Should I extract module from bay 4 or power off will be enough?

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

remove from slot 4 please

JY

mc21_hp
Advisor
Solution

Re: After move HP VC flex fabric modules to other bays I can not access VCM

>remove from slot 4 please

It didn't help. I got "strange effect" again.

But when I removed both modules from bay 3,4 and installed it back to bay 7,8 "Virtual Connect Manager Domain Setup Wizard" started and completed without problems.

Now I have access to VCM. But I need to install VC modules to bay 3,4 for connecting with mezzanine-1 .

Does correct procedure for transfer VC modules to other bays in same enclosure exist?

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

try to do setup again in bay 7 and 8 then do not complete setup just move to bay 3 and 4
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Let me write checklist:

1. In OA web-interface I got to go to "Enclosure Information"->"Enclosure Settings"->"Reset Factory Defaults" and press button "Clear VC Mode".
2. Then I will go to VCM web-interface and see wellcome screen of "Virtual Connect Manager Domain Setup Wizard".
3. I need to exit from Wizard and power off both VC modules
4. Then I will set IP-configuration for destination bays (3,4) same as in source bays (7,8)
5. Finally I will physically move VC modules from bay 7,8 to 3,4, power ON, continue "Virtual Connect Manager Domain Setup Wizard" and hope for better.

Do I think right?

peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

right
mc21_hp
Advisor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

It works! But one difference in the procedure has place.

On step 2 I didn't get "Virtual Connect Manager Domain Setup Wizard". After I connect to VCM I got message "The HPE Virtual Connect Manager no longer has valid login credentials for the HPE Onboard Administrator (OA). The OA may have been replaced or reset to factory defaults. To ensure proper operation, these credentials must be re-established."

At this point I didn't type any credentials. I turned off VC modules and went to step 4. Then everything was according to plan.

Highlighted
peyrache
Respected Contributor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Good thanks for this feedback
JYP
John Trunik
Occasional Visitor

Re: After move HP VC flex fabric modules to other bays I can not access VCM

Great job fixing this issue!

I had this same issue EXCEPT:  When I saw the message that the Active VC was not in this bay, I connected to what I thought was the backup VC, and tried to type my ID and password.  It makes perfect sense to me that you saw the message that the OA must have been replaced or set back to factory, because my ID and password didn't work.  Now, my question,

Can I fix this issue without reconfiguring the VC Domain from scratch?  Maybe, if I reset one VC module to factory defaults, then let it resynch with the other module I won't lose my settings?  Or maybe if I do them one at a time, I won't lose my settings?