flottmedia  Ally Member

In general it would be helpful to have more detailled information on certain events. E.g. "STP topology changes" could also display an added / changed / removed MAC and Port or "Port X - PortX link down" also the MAC, IP, name of the device in the log details similar to the detail field of some NAP log entries.

Thanks for the detailled answer, @Nebula_Jason! Regarding LACP packets, I assume the Nebula switch does try to keep the port up when only one of the server NICs is left up in the team? Otherwise the redundancy simply wouldn't make sense, right? In our case one of the NICs on the Windows Server got (somehow) disconnected…

Good suggestion ... +1!

Thanks for clarification @Nebula_Chris. We thought this speed limitation stated in the datasheet was only based on the additional firewall processing. As the pysical WAN-NIC should (according to the datasheet) have a GbE connection (=1 Gbps?). So, do I get the datasheet right, that there isn't currently any NSG product…

Regarding the setting discussed above: is there meanwhile a way to completely disable the firewall between specific subnets on LAN and WAN on a NSG100 (e.g. in the setting described above 192.168.2.0/24 on WAN and 192.168.10.0/24 on LAN) in order to gain more speed for network transfers? Although the WAN interface of the…

@Nebula_Chris: We would still be interested in an answer to the following question of @ZeRicardo: Ist there any documentation what is possible (and what not) on SNMP side when working in NCC mode with NAW, NSG and NSW devices?

@Nebula_Chris: could you please let us know the result of the eITS discussion here afterwards. The SNMP details would be also relevant to us ...

We currently don't support these 3 features in live tools [...] We saw that, nevertheless it would be very helpful. Are there any plans to implement at least a viewable routing table in one of the upcoming NCC versions? [... ] may I know what do you mean of connection table? I was looking for something like netstat or…

Thanks for your reply, @ivers. The funny thing is, that the setting actually DOES work, otherwise we wouldn't get something like "domain1.loc, domain2.loc" as connection specific DNS suffix. But the question for me rather war: is there any DHCP setting in the NCC for NSGs that would allow us to define a domain search list…

@Nebula_Freda: could it be that there is currently a bug in the naming process of NSG clients. If you rename a client that got its IP from the NSGs DHCP and this IP was formerly given to another (meanwhile offline) client, renaming the new client also renames the old client although it has / had a different MAC address…

OK, @Nebula_Chris, that worked (as expected). Nevertheless, for debugging things like that, it would be very helpful to have a few more "Live tools" in NCC for the NSGs, e.g. a Routing Table as well as an Open Ports / Connection Table would be very helpful. Are there any plans to implement things like that, or are they…

I agree, @RUnglaube, there are already some helpful features in place, but nevertheless, a simple "hardware switch" that takes 100% of the settings over to a new device (independent of the type of device) would be very helpful for RMA. 

Thanks, @Nebula_Chris, "[...] if this gateway support VPN tunnel as well." was a good hint. We indeed already had a tunnel on the external router. After disabling that, the exposed host (NSG) was able to built up the tunnel without errors. Nevertheless, one last and very strange issue is still happening from time to time:…

OK, I understand, @CrazyTacos . As far as I can see, currently there isn't any description in the inventory at all. The introduction of that description rather was the original idea of this thread. But anyhow, if that description will be added, I would definitely argue, that also a device description in inventory should be…

@CrazyTacos: can you provide an example, because if you really want to separate "customers", I would assume you would use different organizations (inside one Nebula account), wouldn't you? Anyhow, as far as I can see, the site-/organization-wide synchronization of the descriptions (as more human readable client / device…