# Network goes down

**URL:** <https://forum.logik.tv/t/network-goes-down/11285>\
**Category:** Sysadmins\
**Created:** [August 24, 2024, 4:05pm UTC](https://forum.logik.tv/t/network-goes-down/11285 "2024-08-24T16:05:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![pereirasantana](https://avatars.discourse-cdn.com/v4/letter/p/7ba0ec/32.png) [@pereirasantana](https://forum.logik.tv/u/pereirasantana)\
**Post date:** [August 24, 2024, 4:05pm UTC](https://forum.logik.tv/t/network-goes-down/11285/1 "2024-08-24T16:05:08Z")

</div>

Network goes down

I noticed that on some new machines when installing flame 2023.3.2 on Rocky Linux 8.7, when opening flame the entire network drops  
This happened on several machines in different locations.  
Any solution to this or idea what it could be?

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [August 24, 2024, 7:31pm UTC](https://forum.logik.tv/t/network-goes-down/11285/2 "2024-08-24T19:31:56Z")

</div>

@pereirasantana - explain a little bit more about the entire network drops?  
every machine loses network connectivity?  
the switch stops responding?  
or flame can no longer see any other flame?  
or something else?  
does the network recover?

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [August 26, 2024, 10:58am UTC](https://forum.logik.tv/t/network-goes-down/11285/3 "2024-08-26T10:58:37Z")

</div>

If you ask the same question on various forums, please make sure to provide the link so we are not duplicating effort. The Area post: [Network goes down - Autodesk Community](https://forums.autodesk.com/t5/flame-forum/network-goes-down/m-p/12979041#M14310)

---

<div class="post-metadata">

**Author:** ![pereirasantana](https://avatars.discourse-cdn.com/v4/letter/p/7ba0ec/32.png) [@pereirasantana](https://forum.logik.tv/u/pereirasantana)\
**Post date:** [September 4, 2024, 12:20am UTC](https://forum.logik.tv/t/network-goes-down/11285/4 "2024-09-04T00:20:32Z")

</div>

Everything falls and only recovers when it is turned off. Routers, switches, servers. It behaves practically like a DDOS attack

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [September 4, 2024, 12:23am UTC](https://forum.logik.tv/t/network-goes-down/11285/5 "2024-09-04T00:23:35Z")

</div>

ip address conflict?

---

<div class="post-metadata">

**Author:** ![ALan](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@ALan](https://forum.logik.tv/u/ALan)\
**Post date:** [September 4, 2024, 12:50am UTC](https://forum.logik.tv/t/network-goes-down/11285/6 "2024-09-04T00:50:54Z")

</div>

I think Tim is correct here. The default ADSK OS install uses a singular IP address. They are probably not changing it by default.

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [September 4, 2024, 1:03am UTC](https://forum.logik.tv/t/network-goes-down/11285/7 "2024-09-04T01:03:56Z")

</div>

multicast was unmanageable during the 2023 season - the solution was hard coded data for sw\_framestore\_map - miserable for 70 to 100 workstations - thanks god for bash and ansible.  
Also, umm, 2025.1.1…