<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>It sounds like the only way to tell what’s happening is to wireshark the connection and see the conversation.</div>
<div><br>
</div>
<div>If the device really got the config file, then there’s something in it the device doesn’t like. What I usually do in this situation is dump the running config file and the one that’s being downloaded and diff them to see if there are any obvious differences,
then start removing stuff from the config file to download until it works.</div>
<div><br>
</div>
<div>Your vendor’s SE should be doing this work for you too. In the end, only the vendor knows what can and can’t be in a config file.</div>
<div>
<div>
<div>-- </div>
<div>Manny Veloso</div>
</div>
<div>Sr. Solutions Engineer</div>
<div>Smartrg.com</div>
</div>
</div>
<div><br>
</div>
</body>
</html>