Jump to content

Recommended Posts

  • 2 weeks later...
  • 2 weeks later...
  • 2 weeks later...
Posted (edited)

DNAC-SW-2.3.7.4-VA.ova

Cisco Catalyst Center SW Virtual Appliance 2.3.7.4
and more...

magnet:?xt=urn:btih:db4b2533e3a0f7669c53abbe90152f988464a427&xt=urn:btmh:12209ced47e1dfe0c86dc912cb6beeaa00202048d65aad4d215b0d1e15b43835be9a&dn=DNACv

29 GB

Enjoy guys

Edited by ipmanyak
  • Like 11
  • Thanks 1
  • 4 weeks later...
  • 2 weeks later...
  • 2 weeks later...
Posted (edited)

  

On 1/20/2024 at 11:03 PM, ipmanyak said:

DNAC-SW-2.3.7.4-VA.ova

Cisco Catalyst Center SW Virtual Appliance 2.3.7.4
and more...

magnet:?xt=urn:btih:db4b2533e3a0f7669c53abbe90152f988464a427&xt=urn:btmh:12209ced47e1dfe0c86dc912cb6beeaa00202048d65aad4d215b0d1e15b43835be9a&dn=DNACv

29 GB

Enjoy guys

 

Thanks!

I was able to get this running with all mandatory packages DEPLOYED on ESXI6.5 with 48vCPU and 224 GB Ram on none-SSD disks.

The trick is to:

1- convert the DNAC-SW-2.3.7.4-VA.ova to a DNAC-SW-2.3.7.4-VA.ovf with ovftool. (ovftool DNAC-SW-2.3.7.4-VA.ova DNAC-SW-2.3.7.4-VA.ovf)

2- edit DNAC-SW-2.3.7.4-VA.ovf file and change VM hardware type to vmx-13 (<vssd:VirtualSystemType>vmx-13</vssd:VirtualSystemType>)

    ※The original DNAC-SW-2.3.7.4-VA.ova has hardware type vmx-14 which can only be deployed on ESXI7.0 and higher so change it to vmx-13 if you want to deploy on ESXI6.5 and to vmx-12 if you want to deploy to ESXI6.0.

3- after deploying the VM but before powering on, edit the settings and remove the hardcoded 64000mhz CPU reservation by changing it to "none" and hardcoded 256 gig RAM memory reservation by changing it to "none"

image.png.ec9cebc0f9fe5ebccb276ac246b7b393.png

image.png.9eef8b7fc9f8b95a4487e5f70e391a4d.png

 

4- You can then give the DNACv VM more than the OVA file hardcoded 32 vCPUs to compensate for the weak CPU cores which cannot manage 64000mhz CPU reservation on 32 vCPUs. (For mine I gave it 48 vCPUs and that was enough to DEPLOY all applications on the DNACv and keep them running in a stable state)

 

image.png.455b717c24755bb87dcc054d6eeefcdc.png

 

That's all. Good luck and happy labbing!!

Edited by benbu
added quoted post reply
  • Like 2
  • 4 weeks later...
Posted
On 5/29/2023 at 12:45 AM, ipmanyak said:
    • 0
  •  

If need  anybody     DNAC-SW-2.3.3.7

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

 

Hidden Content

  • Give reaction or reply to this topic to see the hidden content.

 

Thanks

  • Like 3
  • Haha 1
Posted
On 3/3/2024 at 10:30 AM, benbu said:

  

 

Thanks!

I was able to get this running with all mandatory packages DEPLOYED on ESXI6.5 with 48vCPU and 224 GB Ram on none-SSD disks.

The trick is to:

1- convert the DNAC-SW-2.3.7.4-VA.ova to a DNAC-SW-2.3.7.4-VA.ovf with ovftool. (ovftool DNAC-SW-2.3.7.4-VA.ova DNAC-SW-2.3.7.4-VA.ovf)

2- edit DNAC-SW-2.3.7.4-VA.ovf file and change VM hardware type to vmx-13 (<vssd:VirtualSystemType>vmx-13</vssd:VirtualSystemType>)

    ※The original DNAC-SW-2.3.7.4-VA.ova has hardware type vmx-14 which can only be deployed on ESXI7.0 and higher so change it to vmx-13 if you want to deploy on ESXI6.5 and to vmx-12 if you want to deploy to ESXI6.0.

3- after deploying the VM but before powering on, edit the settings and remove the hardcoded 64000mhz CPU reservation by changing it to "none" and hardcoded 256 gig RAM memory reservation by changing it to "none"

image.png.ec9cebc0f9fe5ebccb276ac246b7b393.png

image.png.9eef8b7fc9f8b95a4487e5f70e391a4d.png

 

4- You can then give the DNACv VM more than the OVA file hardcoded 32 vCPUs to compensate for the weak CPU cores which cannot manage 64000mhz CPU reservation on 32 vCPUs. (For mine I gave it 48 vCPUs and that was enough to DEPLOY all applications on the DNACv and keep them running in a stable state)

 

image.png.455b717c24755bb87dcc054d6eeefcdc.png

 

That's all. Good luck and happy labbing!!

 

  • 2 weeks later...
Posted

I used the same disk sizes (thin provisioned) and virtual nic configurations that were originally configured on the ova file.

image.png.0d3a551db4263fa557aeab0fbed7533f.png

 

image.png.daed2565988414ea42e68149a75e22bc.png

 

4 nics = VNXNET 3

image.png.af814ed594c12d3260f0aaf7f6b89a74.png

 

 

image.png

  • 3 weeks later...
  • 2 weeks later...
Posted (edited)

Cisco Catalyst Center SW Virtual Appliance 2.3.7.4  and  2.3.7.5
68.6 GB
magnet:?xt=urn:btih:83b38c853dc0f1b383d31e5d97d0525faaef978c&xt=urn:btmh:12207d892e3330292b76b8f113cfc26acf172fedb71b4edaaacd9be32bbbe827ce95&dn=DNACv

Edited by ipmanyak
  • Like 1
  • Confused 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...