Options for Managing a DTC Remotely

This takes everything on the segments and bridges it except ip (it routes ip).
Great way to find out what is on your WAN.
TO LOCK IT DOWN TO ONLY THE DTC EQUIPMENT...
configure terminal
access-list 200 permit 0xf8f8 0x0000
access-list 200 permit 0xfcfc 0x0000
Now apply the access-list to the interface where the DTC's come into...
configure terminal
int eth x\x
bridge-group 1 input-lsap-list 200
This turns the bridge group access-list into a filter for only the protocol
type required by the DTC's. Do this on both sides of the WAN link.
Much thanks to Scott M. at Cisco for coming up with this!
3.4.1. Advantages
By bridging the DTC traffic to the remote site, the customer
eliminates the need to have an OVDTCMGR PC or another piece
of equipment at a remote location. All DTC management is
centralized a main IT center. Given that the NMMGR program is
being enhanced to support all functionality currently configurable on
the DTC, no drop off of functionality would be noticed. Also,
problem resolution and data collection would be more consistent as
this would be done from one location with a single tool, instead of
requiring information from both the system based tools and the
OVDTCMGR utility. This would also free up the need to have
trained staff at every remote location to monitor and use the
OVDTCMGR or require the need to have remote access to the
OVDTCMGR PC. It also removes the OVDTCMGR PC as being a
point of failure at the remote location and establishes the capability
of having several MPE/iX systems capable of managing the same
DTC farm. If one of the MPE/iX systems goes down, the others
could be configured quickly to take over management of the DTCs,
while a failure of the remote OVDTCMGR PC would render that
remote site dead until a new PC could be brought up on a new PC,
requiring a trip to the remote site with a new PC or expertise at the
site to setup the new PC. With trends pointing at centralization of
IT staffs, this possibility is not ideal.
3.4.2. Disadvantages
Depending on the type of equipment linking the remote site with the
local HP 3000 system, it may require an upgrade or purchase of
new equipment. Most newer switches and routers from known
companies as HP and Cisco have the capability of bridging traffic
across routers so no routing capability is required in the networking
protocol. If the router is an older model, this may not be capable