Options for Managing a DTC Remotely

and an upgrade may be needed. It is also possible, that the remote
networking layout may be architected in a way that the DTC
management traffic over the network takes too long to reach the HP
3000, causing the HP 3000 management tools to fail the
management of the DTC. If this occurs, the MPE/iX lab would need
to investigate and provide a patch that would address this issue.
There is also the potential that IT staff would need to have updated
training in the use of the routers in order to make this configuration
change. While most router functionality is self evident out of the
box, having to specify bridging of specific packets would be more
complex, leading to a potential increase in configuration problems
and more support calls.
4. Recommendations
Each option presented above is a potential solution for each customer,
depending on the circumstances and the customer’s environment. However,
it is thought that open 3.4 Bridge/Router Configuration offers the least
intrusive method of keeping configurations while still using supported method.
Since all of the NMMGR configuration and management functionality is
controlled within the CSY lab, there is no danger of losing support for this
solution. By also adding full functionality to this product, there is no loss of
connection methodologies, which keeps the environment transparent to he
end users. Plus, the ability to manage the remote locations from a central
system provides more control for the IT staff to manage DTCs and address
problems if that occurs. Failure of the networking equipment connecting the
remote site is not an issue, as normal connections to the DTCs would be lost
anyway, something that the OVDTCMGR solution cannot prevent. It is
thought that solution 3.4 is the cleanest solution and provides the most
capability for support as the end of the HP 3000 draws near.