03-10-2025 10:26 PM - edited 03-10-2025 10:27 PM
Hi Team,
I have an issue.
Our Customer ordered and catalyst Center.
after we power on the UCS and do the initial config for the CIMC.
we continue to install the Catalyst Center.
but unfortunately when we try to config for the Interface Enterprise, unable to ping gateway and NTP Server (cant continue the installation)
- cant ping gateway
- cant ping NTP:
the simple topology is like this :
What causing the Enterprise Port unable to ping gateway ?
*even when we try change the Segment/VLAN on the Enterprise port (VLAN 102, become VLAN 250; same as CIMC),
still cant ping gateway and NTP.
Note:
- Enterprise using VLAN 102 : 172.20.102.60 /29
- Intercluster using VLAN 669 (VLAN dummy ) : default generated by DNAC 169.254.6.66
- CIMC using VLAN 250 : 172.20.250.5 /24
- not used port Management and Internet
- Catalyst Center Directly connected to Core
- All gateway VLAN , on Core
- Due Limitation of the Port core, Enterprise & Intercluster Port using 1G - UTP Based GLC-TE
03-10-2025 10:35 PM
Hello @Agung1007
Do you check config ports and SVI on CORE side ?
03-11-2025 02:11 AM - edited 03-11-2025 03:12 AM
Hi,
thanks for the reply,
config on interface is like this :
and on the SVI
*some PBR/Route-map, already check there's deny on the PBR/Routemap BUT not on the NTP network or the gateway (172.20.129.157 GW, or NTP 172.20.224.xx)
03-11-2025 09:52 PM
Hi
just want to confirm,
Do Cisco Catalyst Center "can running" on 1 G interface ? or Support running 1 G ?
*to eliminate that why the catalyst center unable to ping gateway due running on 1 G...
*i know in the documentation that recommended is 10G
03-12-2025 01:20 AM
The screenshot was not clear - i was in guess that ip address 172.20.224.X for the NTP, from switch or gateway you can ping them ?
Looking like routing issue from switch(or router) fix that one to work. - try ping NTP using source vlan 102
03-12-2025 02:53 AM
Hi
thansk for the reply,
the simple topology is like this
- the initial config screenshot (unable to ping gateway and NTP):
- from switch, when I try to show mac-address table on the Port to Enterprise and Intercluster (NOT Detect MAC Address)
while show mac-address table on CIMC is showing:
Is it caused by the issue in L1/physical?
the DNAC not supported SFP (using 1G GLC-TE) and UTP cable ?
03-12-2025 06:01 AM
Is the port up on the switch side? I'm not sure. I've never tried GLC-T, but I'm sure it supports the RJ45 connection. And 1GB - it can not be assured performance guarantee.
03-12-2025 07:02 AM
Yes,
on the switch side, the port is Up:
-to enterprise
- to intercluster
even when show cdp and lldp on the switch,
it not showing anything for the Catalyst Center.
03-13-2025 12:51 AM
if the port up, what is the outcome i have asked before :
Looking like routing issue from switch(or router) fix that one to work. - try ping NTP using source vlan 102
03-13-2025 12:59 AM
from core switch,
by using source vlan 102, it able to ping NTP server, and DNS server.
already try create SVI VLAN 102 in another switch (switch-2) that connect core, the switch-2 able to ping gateway and nTP
prelimenary analysis, i think the DNA Center is not supported the SFP GLC-TE.
that's why it cant ping to gateway, NTP, DNS (even while the interface on the Switch is UP)
03-12-2025 09:21 PM
Can you take a screen shot of config from the enterprise interface in the config wizard setup there and provide that? I'm curious based on the diagram how we expect the enterprise to communicate to the gateway when the gateway is outside the subnet of the enterprise interface.
Per the diagram, the enterprise interface is in vlan 102 with ip inside of:
172.20.129.60/29
However, the default gateway is listed for vlan 250:
172.20.250.254
As it currently stands, there is no way for the enterprise to communicate to this.
03-13-2025 01:09 AM
Hi
thanks for the reply,
sorry i attach the wrong screenshot .
- here's enterprise port using VLAN 102 - 172.20.129.60 /29
cant ping gateway and NTP
-here's the enterprise using VLAN 102 - 172.20.250.41 /24
cant ping gateway and NTP
03-13-2025 07:49 AM
Thanks, for the 172.20.129.60 subnet, I still see it's wrong. In the enterprise port config you put a /24 subnet instead of a /29. Regardless, I would suggest opening a TAC case so we can do some pcaps to see what is happening
03-13-2025 09:35 AM
Hi
to make sure i try again 172.20.129.60 /29, GW : 172.20.129.57 :
still the same cant ping gateway, DNS and NTP :
we already proposed to our customer if possible we install the Switch that support 10G. and already expalined that the issue is caused by the Unsupported SFP GLC-TE on DNA-Center Appliance.
for opening tac case,
maybe we open the case after if we change the switch 10G, still the same.
*eventhough i still curious what happen in the enterprise port, need pcap capture. but the site is remote/unable to access physically.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide