Black Box Explains…Wizard.NET
One software solution to rule them all.
Wizard.NET is a professional enterprise management suite that delivers total IP device control, management, and connectivity. Black Box KVM over IP (KVMoIP) devices provide... more/see it nowthe ability to control large numbers of host computers from remote locations. When controlling larger groups of dispersed computers using numerous KVMoIP devices, the major challenge becomes one of management—retaining active control over a complex mix of devices, host computers, and registered users. Wizard.NET was developed as a common interface to help you remotely manage any number of KVMoIP devices together with all of their connected host computers and the access rights of the users.
Wizard.NET is delivered as a software solution only, and operates as a server application running on a system that can be completely separate from any of the KVMoIP devices?—?it merely requires an IP network or Internet connection. Wizard.NET uses an intuitive HTML user interface, which means that registered users can access and control it remotely using a standard Web browser. Like all Wizard KVMoIP products, Wizard.NET employs high specification security techniques to ensure that only authorized users may gain access.
Wizard.NET has two main modules, the manager and the connector. The manager module is accessible only to managers and administrators. It is where the details about all connected devices, hosts, and users are configured and stored. The connector module can be used by registered users to enable quick access to all of the targets for which they have access rights. Targets may be devices, hosts, or device groups as appropriate.
To ensure maximum security, Wizard.NET does not retain any passwords within its database for the devices that it controls. Instead, a valid password is used once only to gain access to each device during the “acquire” stage, when Wizard.NET establishes a Secure Ticket with the device. In all subsequent accesses to each device, the relevant secure ticket is used to gain access. collapse
- Visio Stencil Drawing...
ServSwitch DTX, Dual-Head, Firmware
Firmware for the DTX5002, DTX5002-T, and DTX5002-R (Version 4.0)
Black Box Explains...Multicasting video over a LAN: Use the right switch.
In KVM extension applications where you want to distribute HD video across a network, you need to understand how it works and what kind of networking equipment to use with... more/see it nowyour extenders.
Think of your network as a river of data with a steady current of data moving smoothly down the channel. All your network users are like tiny tributaries branching off this river, taking only as much water (bandwidth) as they need to process data. When you start to multicast video, data, and audio over the LAN, those streams suddenly become the size of the main river. Each user is then basically flooded with data and it becomes difficult or impossible to do any other tasks. This scenario of sending transmissions to every user on the network is called broadcasting, and it slows down the network to a trickle. There are network protocol methods that alleviate this problem, but it depends on the network switch you use.
Unicast vs. multicasting, and why a typical Layer 2 switch isn’t sufficient.
Unicasting is sending data from one network device to another (point to point); in a typical unicast network, Layer 2 switches easily support these types of communications. But multicasting is transmitting data from one network device to multiple users. When multicasting with Layer 2 switches, all attached devices receive the packets, whether they want them or not. Because a multicast header does NOT have a destination IP address, an average network switch (a Layer 2 switch without supported capabilities) will not know what to do with it. So the switch sends the packet out to every network port on all attached devices. When the client or network interface card (NIC) receives the packet, it analyzes it and discards it if not wanted.
The solution: a Layer 3 switch with IGMPv2 or IGMPv3 and packet forwarding.
Multicasting with Layer 3 switches is much more efficient than with Layer 2 switches because it identifies the multicast packet and sends it only to the intended receivers. A Layer 2 switch sends the multicast packets to every device and, If there are many sources, the network will slow down because of all the traffic. And, without IGMPv2 or IGMPv3 snooping support, the switch can handle only a few devices sending multicasting packets.
Layer 3 switches with IGMP support, however, “know” who wants to receive the multicast packet and who doesn’t. When a receiving device wants to tap into a multicasting stream, it responds to the multicast broadcast with an IGMP report, the equivalent of saying, “I want to connect to this stream.” The report is only sent in the first cycle, initializing the connection between the stream and receiving device. If the device was previously connected to the stream, it sends a grafting request for removing the temporary block on the unicast routing table. The switch can then send the multicast packets to newly connected members of the multicast group.
Then, when a device no longer wants to receive the multicast packets, it sends a pruning request to the IGMP-supported switch, which temporarily removes the device from the multicast group and stream.
Therefore, for multicasting, use routers or Layer 3 switches that support the IGMP protocol. Without this support, your network devices will be receiving so many multicasting packets, they will not be able to communicate with other devices using different protocols, such as FTP. Plus, a feature-rich, IGMP-supported Layer 3 switch gives you the bandwidth control needed to send video from multiple sources over a LAN.
ServSwitch Brand KVM Extender Software
ServSwitch Ultra Remote User Manual
User Manual for the ACR9000A (Version 1)