Complexity of the NAT Solution

The extensive use of IP addresses in Sun Management Center complicates deployment in environments that involve simple address or proxy translations. The addresses appear at the driver, library, application, and console integration levels. The solution is further complicated by the types of communication that occur in Sun Management Center.

This software is a distributed application with the following layers:

• Console

• Multicomponent server

• Multicomponent agent

The software layers can reside on a different host or on different networks that could be subject to routing rules or NAT.

Furthermore, the console, server, or agent components of one Sun Management Center system can potentially communicate with components of another Sun Management Center system on another network. These aspects add to the complexity of the solution.

NAT enables Sun Management Center 4.0 to operate in a network environment where the consoles, servers, and agents are deployed in one or more network addressing realms. As a result, the consoles, servers, and agents must communicate across one or more NAT environments.

The functionality also supports cross-server context operation such as remote reference domains across NAT environments. With NAT, Sun Management Center components can also communicate with other Sun Management Center components in the same addressing realm. Without NAT, Sun Management Center consoles, servers and agents cannot operate across NAT environments.