sanderson@tc1ps2.mdc.com (George Sanderson) (02/27/90)
Some AppleTalk Phase II questions
1) When transitioning to AppleTalk Phase II, does an existing Phase I
backbone network number have to be within the range of network numbers
assigned to the same backbone using Phase II routing?
2) Do all AppleTalk Phase II routers have to be configured the same during
and after Phase I?
3) Does CAP perform AppleTalk routing? If so, is there a Phase II
upgrade or patch?
George
morgan@jessica.stanford.edu (02/27/90)
> 1) When transitioning to AppleTalk Phase II, does an existing Phase I > backbone network number have to be within the range of network numbers > assigned to the same backbone using Phase II routing? No, the P1 network number must be different from any numbers used for P2 networks. The P1 network uses a different encapsulation, and is a different AppleTalk network from the P2 network. A "transition" router can route between them because they have different AT network numbers, and it knows which encapsulation to use for which. There's another issue here that may affect what you're trying to do. In an internetwork in which some routers are P1 and some are P2, (ie, a "transition internet"), it's my impression that the P2 feature of multiple network numbers per cable cannot be used. The problem is that P1 routers can't deal with the "network range" concept. So if this feature was one of the reasons you wanted to start using P2, I think you'll be disappointed. On the other hand, if all you need is to hook up some P2-only-speakers (like Ethernet-attached PCs running AppleShare PC), then that can be done in a transition internet. > 2) Do all AppleTalk Phase II routers have to be configured the same > during and after Phase I? Hmm? > 3) Does CAP perform AppleTalk routing? If so, is there a Phase II > upgrade or patch? CAP normally uses AppleTalk-in-UDP encapsulation (sometimes called IPTalk), which as it stands is only a "non-extended" network. Which is to say, IPTalk networks don't support multiple net numbers and multiple zone names per cable. There have been some proposals to extend IPTalk to have P2 features, but none have seen the light of day so far. - RL "Bob" Morgan Networking Systems Stanford
morgan@jessica.stanford.edu (02/28/90)
(Sorry if this is a repeat, I don't know if it got through the first time.) > 1) When transitioning to AppleTalk Phase II, does an existing Phase I > backbone network number have to be within the range of network numbers > assigned to the same backbone using Phase II routing? No, the P1 network number must be different from any numbers used for P2 networks. The P1 network uses a different encapsulation, and is a different AppleTalk network from the P2 network. A "transition" router can route between them because they have different AT network numbers, and it knows which encapsulation to use for which. There's another issue here that may affect what you're trying to do. In an internetwork in which some routers are P1 and some are P2, (ie, a "transition internet"), it's my impression that the P2 feature of multiple network numbers per cable cannot be used. The problem is that P1 routers can't deal with the "network range" concept. So if this feature was one of the reasons you wanted to start using P2, I think you'll be disappointed. On the other hand, if all you need is to hook up some P2-only-speakers (like Ethernet-attached PCs running AppleShare PC), then that can be done in a transition internet. You still have to assign the P2 net a different number than the P1 net on the same cable. > 2) Do all AppleTalk Phase II routers have to be configured the same > during and after Phase I? Hmm? > 3) Does CAP perform AppleTalk routing? If so, is there a Phase II > upgrade or patch? CAP itself does minimal routing: it sends all packets thru its single statically-configured router, no matter whqt the destination. CAP uses AppleTalk-in-UDP encapsulation (sometimes called IPTalk), which as it stands is only a "non-extended" network. Which is to say, IPTalk networks don't support multiple net numbers and multiple zone names per cable. There have been some proposals to extend IPTalk to have P2 features, but none have seen the light of day so far. UAB, a relative of CAP that does do AppleTalk routing (on a few selected Unix boxes) and uses EtherTalk version 1 format, should certainly be made to do Phase 2 (aka EtherTalk version 2) by somebody. There may be difficult issues with getting multicast support from the host OS, though. Is anybody working on this? - RL "Bob" Morgan Networking Systems Stanford