[comp.dcom.sys.cisco] Ungerman Bass NIU's resolving names across cisco Router

Tim.Raymond@UVM.EDU (Tim Raymond) (01/10/91)

We have many Ungerman Bass NIUs sitting on subnets.  The subnets are
connected by a cisco AGS router.  We have the NIUs configured to
resolve names using DNS.  We are running UB Netone Software Ver. 16.1.
Our AGS is running 8.0(13) -- soon to be 8.2(1).

Scenario:
	Person on PC connected by serial line to NIU wants to connect
	to printer/host connected by serial connection to a different
	NIU.

The problem:
	For names in the DNS db, all is well (the correct address is found).
	For names not in DNS:
		For two NIUs on the same subnet, all is well (the correct
						address is found.)
		For two NIUs not on same subnet, the name
			is not resolved to an address.

Whatever UB NIUs send out to resolve names is not getting passed by
the cisco box.


Has anyone faced this problem?  And more importantly, has anyone resolved
this problem?

Thanks in advance.

-- 
Tim Raymond
raymond@newton.uvm.edu
uvm-gen!raymond

kla@kampi.hut.fi (Kimmo Laaksonen) (01/11/91)

In article <31375@boulder.Colorado.EDU> Tim.Raymond@UVM.EDU (Tim Raymond) writes:
> Our AGS is running 8.0(13) -- soon to be 8.2(1).

*descriptions deleted*

> Whatever UB NIUs send out to resolve names is not getting passed by
> the cisco box.
>
>
> Has anyone faced this problem?  And more importantly, has anyone resolved
> this problem?

We don't have Ungermann-Bass but 3COM/ESD (previously Bridge) terminal
servers. They use a mix of Ethernet level protocols (their own & XNS &c)
for various purposes: type (hex) 9002 broadcasts for "netmaps" (so each
server shows what servers are alive), XNS for booting software from a
network control server, and the latest addition, IEEE 802.3 SNAP for a
secondary bootstrap with multicasting to speed up booting in case eg.
a powerout causes a lot of servers to boot at the same time (cute!).

Anyway my solution is to bridge (you'll need the HyBridge option in
your AGS) 3COM/ESD traffic (excepting IP, but that's dealt with the
routing processes in the AGS). Set up like this:

 bridge 1 ieee		! I used IEEE, because we have some 3COM/ESD
			! bridges sitting on the network; they use
			! DEC spanning tree, which might give headaches
			! with the AGS - unless disabled (not default
			! with the 3COM/ESD bridges!)

 interface ether N	! repeat for all Ethers, where you have UB NIUs
 bridge-group 1
 bridge-group 1 input-address-list 701
 ...
 access-list 701 permit 00DD.0000.0000 0000.FFFF.FFFF
 access-list 701 deny   0000.0000.0000 FFFF.FFFF.FFFF

The input-address-list 701 filters out all non-UB Ethernet packets
(excepting IP & other protocols you route with the AGS). Ethernet addresses
assigned to UB start with 00DD (hex); in fact my docs tell me they
have 00DD00 & 00DD01 assigned to them. I put 3COM/ESD Ethernet
addresses there (0800.02000.0000 0000.00FF.FFFF for those interested),
and it works all right.

You'll definitely need at least 8.1, but if you're upgrading to 8.2,
it'll be there, too. (Cisco never drops anything they've added to
the router software :-) But you'll have to upgrade to HyBridge, too,
if you don't have it, yet.

BTW, we use bridging for Apollo Domain, too, although Domain routing
is supported by Cisco. Our Apollo system maintenance didn't like the
idea of routing a few (1-2) workstations all to different Domain networks.
I agree. Maybe Domain will go away altogether after a while, now that it
is in the hands of HP... The solution is similar: use Apollos assigned
Ether addresses in the access list (0800.1E00.0000 0000.00FF.FFFF).

Unless it's vamped up in 8.2, show bridge will show you lots of other
addresses (all sources of non-IP, or non-whatever-you're-routing Ether-
net packets on those interfaces you bridge). Don't be alarmed (I was
first :-), only UB addresses (starting with 00DD) will have something in
their Tx & Rx count fields to show packets are being forwarded.

> Thanks in advance.

You're welcome.

> -- 
> Tim Raymond
> raymond@newton.uvm.edu
> uvm-gen!raymond

------------------------------------------------------------------------
  Kimmo Laaksonen                       Internet: kla@hut.fi
  Helsinki University of Technology     BITNET: KLA@FINGATE
  Computing Centre                      
  Otakaari 1, SF-02150 Espoo,  Finland  phone: int'l 358 0 451 4308