robelr@bronze.ucs.indiana.edu (Allen Robel) (02/19/91)
I've come across a problem in getting the 2.0 MacVAP to work with cisco routers (cisco version 8.2(3)). The problem doesn't appear to be with cisco but, rather with the MacVAPs. On page 7-11 of Inside AppleTalk, 2nd edition, there is a note about extended networks that says (direct quote): Note: On an internet, nodes on extended networks performing lookups in their own zone must replace a zone name of astrisk (*) with their actual zone name before sending the packet to A-ROUTER. All nodes performing lookups in their own zone will receive LkUp packets from themselves (actually sent by a router). The node's NBP process should expect to receive these packets and must reply to them. [thanks to David Edwards of cisco for the reference...] On booting the server and loading the MacVAPs the following is shown on the console of the cisco router (using cisco's NBP debugging) fddi6#debug apple-nbp NBP packets debugging is on fddi6# AT: NBP ctrl = LkUp, ntuples = 1, id = 0 AT: 45.142, skt 2, enum 0, name: JOHNNY_APPLESEED:AFPServer@* AT: LkUp JOHNNY_APPLESEED:AFPServer@* AT: Invalid nbp brrq '*' for extended net AT: Invalid nbp brrq '*' for extended net AT: Invalid nbp brrq '*' for extended net AT: Invalid nbp brrq '*' for extended net A Sniffer trace of the NBP portion of the offending packets looks like: - - - - - - - - - - - - - - - Frame 32 - - - - - - - - - - - - - - - - NBP:----- NBP header ----- NBP: NBP: Control = 1 (Broadcast Request) NBP: Tuple count = 1 NBP: Transaction id = 0 NBP: NBP: ---- Entity # 1 ---- NBP: NBP: Node = 45.142, Socket = 2 (NBP) NBP: Enumerator = 192 NBP: Object = "JOHNNY_APPLESEED" NBP: Type = "AFPServer" NBP: Zone = "*" NBP: NBP:[Normal end of "NBP header".] NBP: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Anyone know if Novell is aware of this? Is anyone successfully using the 2.0 MacVAPs on extended networks? This looks like a simple fix to me as the MacVAPs already knows about what zone its in (you supply that when you configure it). Seems to me a matter of taking the user-specified zone name and replacing the astrisk in the above with it. thanks, Allen Robel robelr@mythos.ucs.indiana.edu University Computing Services ROBELR@IUJADE.BITNET Network Research & Planning voice: (812)855-7171 Indiana University FAX: (812)855-8299