Type of Install

Options for the "Type of Install"

The most complex decision required for the installation of Network Trace, is the type of installation. There are two possible types of install.

The first and most common is known as the "Integrated" install. This refers to the situation where Network Trace is installed on one or more of the machines which are already part of a network. For example, when tracing all traffic between a client and a server is desired AND the Network Trace is installed on either the server and/or client in question, then this install is integrated.

The second type is known as a "3rd Party" install. This is an installation in which the machine taking the trace does NOT participate in the network in which it traces. It is ONLY, EVER an "observer" of other machine's traffic. For example, when tracing all traffic between a client and a server is desired AND the Network Trace is installed on NEITHER the server and/or client in question, then this install is 3rd party. It would require a 3rd machine for the installation.

It is possible that both of these installation types will be possible, depending on the environment. There are advantages to each type install.

In general, the integrated install will best leverage the systems management infrastructure that already exists. For example, it is highly likely that remote servers have change control technologies and remote access technologies (such as Telnet or Netfinity Manager) built already. These can be easily used to implement and utilize the new Network Trace capabilities. In the service mode of operation, the affect of a strenuous traffic load can be handled with little observable difference to the trace machine.

Using the 3rd party install can have advantages too. The biggest advantage is that it will perform the best in a heavily loaded network. A 3rd party install will not drop frames except in the most strenuous network loads, especially when using service mode.

For example, when tracing using protocol mode in an integrated install, boot times during a large WSOD "boot storm" (30+ machines) will be slower than normal (by a few minutes). However in a 3rd party install there is no effect on the boot times at all.

It is also possible that neither of these installs are possible. If this is the case, please contact technical support.

Determining if a "3rd Party Install" is Required

Number	Description	Criteria	Value
1	Mode of Operation	Protocol or Service (recommended) See Mode of Operation.
2	LAN topology type	Ethernet or Token-Ring See Limitations.
3	MAC driver supports multiple TransferData?	`if ( #1 = SERVICE ) then value = N/A` `else determine value from BINDTREE` A value of "No" means that forced frame slicing will occur when in protocol mode. See Limitations.
4	Is forced frame slicing acceptable?	If the expected use of the traces does not require access to the "payload" of the frames, then the answer is YES. If it is not known how the traces will be used, then it is best to assume the answer to be NO.
5	Is a 3rd party install required?	`if ( #1 = PROTOCOL AND #2 = ETHERNET ) OR ( #3 = NO AND #4 = NO ) then value = YES`

Determining if "Integrated Install" is Required

Number	Description	Criteria	Value
1	NIC hardware and MAC driver support promiscuous mode?	The value can be obtained from BINDTREE utility. (see Limitations)
2	Is a "third party install" possible?	Does any machine exist which can be an independent observer of the network? To meet this critieria, the machine MUST NOT participate in the network in any manner that affects the results of the trace.
3	LAN hardware type	Is the media switched (Ethernet or Token-Ring Switch) or shared (traditional hubs)?
4	If switching is in use, is switched port monitoring available?	Does the switch provide a capability to "redirect" or copy the traffic from a port or a list of ports to the port of the tracing machine?
5	Is an integrated install required?	`if ( #1 = NO ) OR ( #2 = NO ) OR ( #3 = SWITCHED AND #4 = NO ) then value = YES`

Deciding on the "Type of Install"

If neither the 3rd party install or the integrated install are required, then one may choose the install which most closely matches other requirements such as performance or manageability. In this case, Golden Code recommends installing on multiple machines in every remote segment. This will allow the most appropriate install to be chosen at the time of tracing. For example, if one is trying to trace a boot storm, then one would choose a 3rd party machine (perhaps a client machine that is being used only for capturing frames at the time of the trace). However, under normal circumstances, it is most likely that tracing from the server will be most convenient.

If one or the other install type is required, then the choice is reasonably clear. Unless some of the assumptions can be changed by changing hardware, drivers, configuration or otherwise, then this choice is indeed a requirement. If this document does not adequately address the basis for these assumptions, please contact technical support.

Finally, it is possible that a particular environment has a set of assumptions in which BOTH types of install are required! If this is the case, then a conflict exists which may prohibit any install at all. If one or more of the assumptions cannot be changed, then please contact technical support for clarification.