Cisco DNA (Catalyst) Center fix network setting error

[ossniper]

Hello.

I am working on Cisco DN3-HW-APL Server.

After setting up as Standalone, via the maglev-config wizard step. 

The enterprise IP address, i configured 10.60.x.x was reachable via ping and i can access the DNA center via web. 

I shutdown the server for the holiday and decided to input management route, But i keep getting error message to fix network setting.

I have rebooted and tried again, still can't go beyond this page or access the "enterprise" interface via ping or web.

[ammahend]

It means the enterprise interface is not able to reach the gateway or the DNS that you have configured, make sure they are reachable. 

[ossniper]

This are my information on Cisco Catalyst center

IP address: 10.60.4.100
Subnet: 255.255.254.0
Gateway: 10.60.4.1
DNS: 4.2.2.2 8.8.8.8

config on SWITCH

Twe1/0/5
switchport mode access
seitchport access vlan 10

It worked during the first setup and now it's not validating. 

[ammahend]

Connect a laptop to the switch in vlan 10, make sure from the laptop you can ping gateway and dns. 

[ossniper]

Yes. I can ping the gateway and access the internet on my laptop.

while on the catalyst center. 
I can learn mac address on the interface with vlan using "sh mac address-table interface twentyFiveGigE 2/0/41".

I used this command "sudo maglev-config update". or "maglev-config wizard". yet it's not reaching the internet or validating.

[ammahend]

can you try maglev wizard again through KVM and try just one DNS may be 4.2.2.2 or 208.67.222.222, see if you still get the error

[ossniper]

Thank you very much as I tried this steps with 8.8.8.8, i decide to try linux commands and can observe the interface are down, even tho then interface LED lights are blinking.

I don’t know what command to get them UP.

[ammahend]

try  "ip link set <interface-name> up"

[ossniper]

I think cisco TAC should be my next step or re-image. Thank you very much

[maflesch]

It's because you are not out of the restricted shell so you cannot use that command.

Also, please do not use the maglev-config wizard command, that attempts to onboard the appliance as though it was reimaged.

Ens1f0 should be the cluster port, not the enterprise port. Can you provide the following please:

ip a | grep -e en1f -e enterprise -e cluster -e internet -e management

[ossniper]

Thank you for your response

I typed the command but no output, screenshot below.

Here's a snapshot of the interface.

It's surprising that the interface are blinking, and it enterprise interface was reachable the first day i powered on the device but now it's not/

[maflesch]

Yea, I apologize, it was supposed to be ens1f, I forgot the "s". However, something still should have showed for all the other ones.

ip a | grep ens1f
ifconfig -a ens1f1
ifconfig -a ens1f0

[ossniper]

Yes, so i used ens1f

ip a | grep -e ens1f -e enterprise -e cluster -e internet -e management

It's says interface is down, i have 10G-SFP-S-SR plugged to the port, blinking orange and green light. 

I'm curious what could be the issue and when i tried "ip link set ens1f1 up" or "sudo ip link set ens1f1 up" i get display message "operation not permitted".

[maflesch]

Yea, the network interface is failing to initialize. We would need to look into the logs. If you opened a TAC case, what is the SR? If you haven't, please do so.

[ossniper]

I will open TAC in few days, so i can resolve this issue as it's beyond normal issue.