Point-to-Point fiber connection - Can see CDP neighbor, but cannot ping across links

Disclaimer: I don't have console access to the remote side of this connect yet. Someone in transit now, so my visibility is limited.

Here's the deal. Setting up a new P2P L2 fiber between our office and a data center. We see the fiber links as green on both sides. I can see the remote switch via sh cdp neighbor, but I'm unable to ping it.

This is how it's setup: 4 x 3172 Cisco Nexus switches

172.16.222.1 - HSRP - Office

172.16.222.2 - Switch A - Office

172.16.222.3 - Switch B - Office

172.16.222.4 - HSRP - Data Center

172.16.222.5 - Switch A - Data Center

172.16.222.6 - Switch B - Data Center

I have static routes on the office side to route DC traffic to 172.16.222.4 and routes on the DC side to route office traffic to 172.16.222.1. (However, I'm just trying to get the 172.16.222.x network to ping across first)

Also, I had this working with both sets of switches connected via copper in the office before they were shipped out.

If I do a sh cdp neigh detail, I can see the detail of the remote switch, along with the correct VLAN (222) and the IP address of the switch that is directly connected to it.

​

Looking for ideas on what I might be missing....

​

This is the CDP output from the Switch B - Office (connected through fiber to Switch B - Data Center)

-----------------------------------------

Device ID:XXXXXXXXXXXXXXXXXXX

System Name: Switch-3172B

VTP Management Domain Name: XXXXXX

Interface address(es):

IPv4 Address: 172.16.220.6

Platform: N3K-C3172PQ-10GE, Capabilities: Router Switch IGMP Filtering Supports-STP-Dispute

Interface: Ethernet1/2, Port ID (outgoing port): Ethernet1/1

Holdtime: 177 sec

Version:

Cisco Nexus Operating System (NX-OS) Software, Version 7.0(3)I7(3)

Advertisement Version: 2

Native VLAN: 222

Duplex: full

MTU: 1500

Mgmt address(es):

IPv4 Address: 172.16.220.6