Vcenter Integration issues

[subashchandran]

Hi All,

sub:- Vcenter integration not successful.

Topology:-

++Leaf101----Fiber cable 10Gbase-SR---FIA&B---configured as access port. and 2 cables connected to upstream one leaf node.

++CDP enabled and discovered successfully..

++ All the Mgmt ports are connected to the OOB layer-2 switch.

OOB ports-------OOB Switch----L3_sw

From leaf node ,able to ping all the OOB IPs except Blade IP (2 Blades in the UCS-B series).

UCS_Blade1&2---IOM----FIA&B------one connection go to Mgmt switch and othe data connection goes to Leaf node.

Regards,

Subash

[Robert Burns]

Subash,

When you saw VC integration not successful, do you even see the DVS created by the APIC on vCenter?

Did you correctly configure Disjoint Layer2 on UCS? 

Please connect to the UCS VIP CLI (SSH), and issue the following commands:

connect nxos

show int trunk

show pinning server

This will show you which VLANs are being allowed on your uplinks, and to which uplinks your server interfaces are pinned to.  Typically UCS uplinks are configured as trunks, but per above, sounds like you have them setup as access (untagged) interfaces.  Can you confirm.

Robert

[subashchandran]

Hi Burns,

Thanks for the Quick reply...

We are using vlan 300 for Vcentre and OOB mgmt Ip---10.9.0.0/24

DVS not created in the VMM tab

TENANT-WT-COE-Controller
State:
Unknown
Address:
10.9.0.162
Model:

+++++++++++++++++++

Port1 in FIA--connects to leaf

Port2 in FIB---Connects to leaf.

Did you correctly configure Disjoint Layer2 on UCS? 

I couldn,t find any settings in UCS...

Attached Show commands...

[subashchandran]

Any updates...

[Joseph Ristaino]

Subash,  Can you test IP connectivity from the APIC to the vCenter?  Are you able to ping the vCenter from the APIC?

Did you say that the vCenter is running "in band" to the fabric but you are trying to access it via the OOB?  What faults are shown in the VMM domain that you created in the "Policies' sub tab?

Joey

[subashchandran]

Hi Joey,

I am able to Ping the FIs and Blade CIMC IPs but not OOB IPs for Blades.

We are using 10.9.0.x/24 IP segment for OOB and Vcentre IP's.

FIs(A&B)----1Gcopper----------2950switch(OOB)----6500(L3) SVIs for 10.9.0.0/24

FI's(A&B)----10Gbase-T---------Leaf101)---Integration for Vcentre.

Attached errors(XML file and screenshot)

[Robert Burns]

From your output you have one inband uplink from the interconnects (eth1/2) going up to the leaf switches, then your FI's have their management connection (Mgmt Interfaces) connected to your OOB management network.   If you have a network diagram showing connectivity of the FI's, vCenter, APICs and Leaf switches (including OOB network switches etc) that would help us advise you.

Two questions. 

1. Where does vcenter reside?  Is it on a UCS blade, on a separate rack server etc.  Provide details.

2.  As Joey requested, from the APIC CLI (ssh to your APIC), are you able to ping your vcenter IP?  This tells us if the APIC can communicate with VC.  I assume your APICs are somehow connected to the same OOB management network.

Robert

[subashchandran]

Hi Robert,

Answers are inline...

1. Where does vcenter reside?  Is it on a UCS blade, on a separate rack server etc.  Provide details.

---Vcentre resides in UCS Blade.

2)As Joey requested, from the APIC CLI (ssh to your APIC), are you able to ping your vcenter IP?  This tells us if the APIC can communicate with VC.  I assume your APICs are somehow connected to the same OOB management network.

Not able to ping the Vcentre IPs..

admin@APIC1:~> ping 10.9.0.162
PING 10.9.0.162 (10.9.0.162) 56(84) bytes of data.
From 10.9.0.11 icmp_seq=1 Destination Host Unreachable
From 10.9.0.11 icmp_seq=2 Destination Host Unreachable
From 10.9.0.11 icmp_seq=3 Destination Host Unreachable
From 10.9.0.11 icmp_seq=4 Destination Host Unreachable
^C
--- 10.9.0.162 ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5158ms
pipe 4

+++++++++++++++++++++

We are using 2 Blades in the UCS chasis---Blade-1 and Blade-2

Configured 2 IPs for Blade---1 for CIMC and other for Blade mgmt.

CIMC IP is pingable.

Attached Connectivity diagram..

[Joseph Ristaino]

I'm assuming the CIMC IP's are on the same OOB network (or an accessible network) as the APIC OOB if they are ping-able.

It looks like the vCenter is coming in-band to the fabric so you would need to configure the APIC to use in-band management when creating the VMM domain.  I would recommend opening a TAC case to assist if you have issues getting this working.

Joey

[subashchandran]

Hi Joe/Robert,

Rob---I had watched  your Post "VMM intergration Video"" for understanding the connectivity

The Issue got resolved, find the resolution steps:-

FI Mgmt port connected  to OOB Mgmt switch 

1) Run the new cable between FI (E1/3)to OOB mgmt switch and configured trunk(VLAN300).

after this connection all my management traffic flows to Mgmt switch.

ESXI host IP and Vcentre IP.

2) I need to use E1/2 port for ACI traffic.

Regards,

Subash