cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4483
Views
15
Helpful
5
Replies

DNA LAN Automation stops after IP assignment

mujeeb2005
Level 1
Level 1

Hey all,

should we stop the "initial configuration dialog"

it goes forward only after i say no, as shown below

 

the IOS-XE version is 16.6.4a

 

DNA version is 1.2.6

 

 

%INIT: waited 0 seconds for NVRAM to be available


--- System Configuration Dialog ---

Would you like to enter the initial configuration dialog? [yes/no]: n

Would you like to terminate autoinstall? [yes]:
%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
%Error opening tftp://255.255.255.255/router-confg (Timed out)
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)



Press RETURN to get started!


*Jan 23 11:19:40.292: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Jan 23 11:19:40.324: %PKI-4-NOCONFIGAUTOSAVE: Configuration was modified. Issue "write memory" to save new IOS PKI configuration
*Jan 23 11:19:41.825: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to administratively down
*Jan 23 11:20:00.498: %AN-6-AN_ABORTED_BY_CONSOLE_INPUT: Autonomic disabled due to User intervention on console. configure 'autonomic' to enable it.
%Error opening tftp://255.255.255.255/network-confg (Timed out)
*Jan 23 11:20:14.436: AUTOINSTALL: Tftp script execution not successful for Vl1.
*Jan 23 11:20:33.768: %PNP-6-PNP_DISCOVERY_STOPPED: PnP Discovery stopped (Config Wizard)
*Jan 23 11:23:59.547: %PLATFORM_PM-6-MODULE_REMOVED: SFP module with interface name Te1/1/1 removed
*Jan 23 11:24:00.610: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to down
*Jan 23 11:24:01.610: %LINK-3-UPDOWN: Interface Vlan1, changed state to down
*Jan 23 11:24:04.511: %PLATFORM_PM-6-MODULE_INSERTED: SFP module inserted with interface name Te1/1/1
*Jan 23 11:24:06.675: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to up
*Jan 23 11:24:06.831: %LINK-3-UPDOWN: Interface Vlan1, changed state to up
*Jan 23 11:24:11.834: %PNPA-DHCP Op-43 Msg: Op43 has 5A. It is for PnP
*Jan 23 11:24:11.834: %PNPA-DHCP Op-43 Msg: After stripping extra characters in front of 5A, if any: 5A1D;B2;K4;I10.4.49.2;J80; op43_len: 26

*Jan 23 11:24:11.834: %PNPA-DHCP Op-43 Msg: _pdoon.3.ina=[Vlan1]
*Jan 23 11:24:11.834: %PNPA-DHCP Op-43 Msg: _papdo.3.eRr.ena
*Jan 23 11:24:11.834: %PNPA-DHCP Op-43 Msg: _pdoon.3.eRr.pdo=-1
*Jan 23 11:24:15.839: %PNPA-DHCP Op-43 Msg: Op43 has 5A. It is for PnP
*Jan 23 11:24:15.839: %PNPA-DHCP Op-43 Msg: After stripping extra characters in front of 5A, if any: 5A1D;B2;K4;I10.4.49.2;J80; op43_len: 26

*Jan 23 11:24:15.839: %PNPA-DHCP Op-43 Msg: _pdoon.4.ina=[Vlan1]
*Jan 23 11:24:15.839: %PNPA-DHCP Op-43 Msg: _papdo.4.eRr.ena
*Jan 23 11:24:15.839: %PNPA-DHCP Op-43 Msg: _pdoon.4.eRr.pdo=-1
*Jan 23 11:24:15.959: %DHCP-6-ADDRESS_ASSIGN: Interface Vlan1 assigned DHCP address 10.128.0.4, mask 255.255.255.192, hostname

5 Replies 5

AndiBuchmann157
Level 1
Level 1

Did you check your routing settings?


Are the assigned IP Adresses rechable from the the DNA Center?

Dear Andi,

 

My DNA is directly connected to Border switch on which i am running LAN automation

 

I am able to ping to the assigned IP of the new switch

 

Border_B#ping 10.128.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.128.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Border_B#
Border_B#
Border_B#
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
% Please answer 'yes' or 'no'.
Would you like to enter the initial configuration dialog? [yes/no]: no

Would you like to terminate autoinstall? [yes]:

 

Press RETURN to get started!


*Jan 24 08:24:22.650: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Jan 24 08:24:22.683: %PKI-4-NOCONFIGAUTOSAVE: Configuration was modified. Issue "write memory" to save new IOS PKI configuration
*Jan 24 08:24:23.661: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to administratively down
*Jan 24 08:24:49.804: %AN-6-AN_ABORTED_BY_CONSOLE_INPUT: Autonomic disabled due to User intervention on console. configure 'autonomic' to enable it.
*Jan 24 08:24:49.852: %PNP-6-PNP_DISCOVERY_STOPPED: PnP Discovery stopped (Config Wizard)
%Error opening tftp://255.255.255.255/router-confg (Timed out)
*Jan 24 08:24:56.773: AUTOINSTALL: Tftp script execution not successful for Vl1.

Hello,

 

No, you should not send any commands to the new switch console while it is progressing through the LAN Automation process. If you send any commands including something as basic as pressing 'Enter' key on on your keyboard then you can break the the automated provisioning.

 

The Cisco DNA Centre needs to be able to reach from its enterprise network Virtual IP to the DHCP assigned IP address of the new switch. Pinging from the border to the new switch doesn't prove that DNAC VIP can reach the new switch.  If you don't know how to access the DNAC CLI then try to ping from the new switch DHCP IP address to DNAC VIP. Note of course that issuing commands to the new switch CLI will break LAN Automation and you will need to reset the new switch and reload it to restart LAN Automation.

 

Also please note the procedure to reset a previously-used switch to factory default before doing PNP or LAN Automation, see section "Bring the device back to the factory defaults by clearing the following from the switch console":

https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/tech_notes/b_dnac_sda_lan_automation_deployment.html

 

Also suggest reading the whole  Cisco DNA Center SD Access LAN Automation Deployment Guide at that same URL as there is some other details in there you should be aware of.

 

Thank you :)

Jerome

Thanks Andi and Jedolphi,

 

The Issue is resolved now.

 

let me explain what was wrong, may be this will help others, who may face the same problem.

 

I had two interface from the DNA connected to the network, 

 

the enterprise (enp9s0)was connected to the test bed and the other interface (enp1s0f0) connected to my corporate network for internet, DNS and NTP connectivity.

 

On the interfaces, as you know, gateway can be assigned to only one interface. 

 

in my case i had assigned gateway to enp1s0f0 and static route to enp9s0

 

when i enable LAN automation, in the DHCP pool on the border(for LAN automation), DNAC was assigning IP address of the enp1s0f0 interface IP in option 43,

 

So the edge switch was not able to reach the DNAC on the enp1s0f0 ip address.

 

Solution:

 

using the below command 

 

“sudo maglev-config update”

 

Assigned the gateway to the enp9s0 interface and restarted the LAN automation 

 

this time the DNAC added the enp9s0 ip in the option 43

 

LAN automation went on smoothly.

 

Thanks once again to both of you.

Nice to hear!

You're welcome!
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: