11-14-201703:47 AM - last edited on 11-14-201710:25 PM by Parvez_AL
11-14-201703:47 AM - last edited on 11-14-201710:25 PM by Parvez_AL
Migration from VCM to Oneview 3.1
We want to migrate a couple of enclosures from VCM to Oneview.
We are running into issues that a connection can't be found.
the message does not make sense because we have two VC ethenetnet modules with 6-8 connections from each server in bay 1 and 2 and two Fibre Vc modules (8GB / 20 Port) in bay 3 and 4 connected to a fibre HBA Mezzanine card.
Enclosure Serial Number:Confidential Info Erased
OA firmware 4.60
VC Ethernert firmware: 4.60
VC FC modules firmware: 2.15
HP Oneview version: 3.10.04-0299553
Migration Compatibility Report for Enclosure INWCEC01T2-U1-M1-F11
Overview
The enclosure "INWCEC01T2-U1-M1-F11", and the following resources will be migrated:
Enclosures 1
Virtual Connect interconnect modules 4
Servers 3
Ethernet networks 48
Fibre Channel networks 2
Server profiles 3
Enclosure group LAN_Enc01
Logical interconnect groups LIG__2
Total # of errors 0
Total # of warnings 2
Fibre Channel Fabrics
NGS1LAN
Warnings:
The OneView logical interconnect group "LIG__2" configuration does not match the Virtual Connect configuration. The following element(s) are inconsistent: Fibre Channel network "NGS1LAN" attribute(s) do not match: Typical Bandwidth,Maximum Bandwidth.
Resolution: Continuing with the Virtual Connect to OneView migration will use the existing OneView logical interconnect group configuration "LIG__2". If this OneView configuration is not acceptable, modify the specified OneView logical interconnect group "LIG__2" to be consistent with the Virtual Connect configuration. If no modifications are required, continue with the migration. If modifications were required, retest the compatibility.
NGS2LAN
Warnings:
The OneView logical interconnect group "LIG__2" configuration does not match the Virtual Connect configuration. The following element(s) are inconsistent: Fibre Channel network "NGS2LAN" attribute(s) do not match: Typical Bandwidth,Maximum Bandwidth.
Resolution: Continuing with the Virtual Connect to OneView migration will use the existing OneView logical interconnect group configuration "LIG__2". If this OneView configuration is not acceptable, modify the specified OneView logical interconnect group "LIG__2" to be consistent with the Virtual Connect configuration. If no modifications are required, continue with the migration. If modifications were required, retest the compatibility.
This is the error where the migrastion stopsd in oneview:
Create iusv1079
Server Profiles
11/8/17 4:54:06 pm
1 minute ago
Error1s
Validate configuration.
Issue Port Mezzanine (Mezz) 1:1 was not found for connection 6.
Resolution Select a different port and try again.
MEZZ 1 is not used for an Ethernet connection, it is used and configured for a fibre channel connection.
Can you provide the output from "show server {N}" in the OA (where {N} is the device bay number)? I want to see what adapters are installed. Can you provide a screenshot of your VCM Server Profile?
11-29-201705:13 AM - last edited on 11-30-201710:28 PM by Parvez_AL
11-29-201705:13 AM - last edited on 11-30-201710:28 PM by Parvez_AL
Re: Migration from VCM to Oneview 3.1
Hello Chris,
sorry for the delay, here we go:
Server Blade #13 Information: Type: Server Blade Manufacturer: HP Product Name: ProLiant BL460c Gen9 Part Number: 727021-B21 System Board Spare Part Number: 744409-001 Serial Number: Serial Number (Logical): VCX0000001 UUID: 30373237-3132-5A43-3335-3230584B3853 UUID (Logical): 91561852-1D3F-4A78-97DF-F3A68786764F Server Name: Asset Tag: ROM Version: I36 02/17/2017 Boot Mode: UEFI Secure Boot: Disabled
CPU 1: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (12 cores) CPU 2: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (12 cores) Memory: 524288 MB
