Wireless Access

I have an old implementation of MPE (no IP stack) which needs to communicate with remote DTC16s. I don't know too much about the MPE system.

I have configured new cisco805 routers with simple transparent bridging over a pt-to-pt 64K Frame Relay link. The MPE host and remote DTCs are standard ethernet connected and I am bridging these two segments. The DTCs fail on boot up - looks like timeout problem. I've put MAC ACL filters on the routers to no avail. Is there some host or DTC tweak which may help ? Any ideas ?

Hi Paul

I take it these are 16TN dtc's ?

Can you linkloop the dtc from the remote host ?

On HP-UX 11.X the downloading LAN Card must be specified for these types of
DTCs:

In /etc/rc.config.d/netdaemons

export START_RBOOTD=1
export RBOOTD_DEVICES=lan0

(Note: The /dev/ prefix must not be used on HP-UX 11.X here.
Both 10base and many 100BT cards can be indicated
use 'lanscan' to determine lan physical paths)

IMPLEMENTATION:

/sbin/init.d/dtcmgr stop
/sbin/init.d/rbootd stop
/sbin/init.d/rbootd start
/sbin/init.d/dtcmgr start

Powerfail the DTC



On HP-UX 10.X DTC, a 10Base LANIC card must be used to download these types of
DTCs. (use 'lanscan' and 'ioscan -kfC LAN' to see physical path and type of
LAN card).

Example: If your system has a 10Base and a 10/100Base card, the 10Base LAN card
must be specified for downloading the DTC.

In /etc/rc.config.d/netdaemons

export START_RBOOTD=1
export RBOOTD_DEVICES=/dev/lan0

RBOOTD_DEVICES must point to the 10BASE LAN card.

IMPLEMENTATION:

/sbin/init.d/dtcmgr stop
/sbin/init.d/rbootd stop
/sbin/init.d/rbootd start
/sbin/init.d/dtcmgr start

Powerfail the DTC.

HTH

Steve

I assume your filters are working correctly? One good thing you can do with a filter besides cut down on garbage traffic is log your traffic. Redo the filter and put the word "log" at the end of each permit statement. Turn off console logging and turn on buffering.

no logg cons
logg buff

Then try a boot up and afterwards you can see what traffic went through by

sh log

You might want to put a filter in both directions on both routers so you can see what's happening. This way you can verify that your routers are passing the packets from one LAN to the other.

filter logging is a bit odd. The first packet which passes a filter statement will generate a log then at 5 minute intervals you get an update on the number of packets which have passed the filter.

Of course you can get more detailed info with a debug but that can be more than your router or you can stand. It is possible to associate a filter with a debug so that only packets which pass the filter will show up.

What are your ping times over the WAN? How much do they go up if you do an extended ping with a 1500 byte size?

Ron