The IP Over NBMA (ION) Archive

["Michael Fischer" <Michael.Fischer@hilan.de>]

>...a different set of PVCs to other members of the LIS. In other 
> words what i am missing is the possibility to define a set of PVCs 
> on a per LIS basis.
> 
> Each PVC would have a ipoaConfigPvcEntry and indexed by:
> 
>      ipoaConfigPvcIfIndex,
>      ipoaConfigPvcVpi,
>      ipoaConfigPvcVci
> > 
> > ipoaConfigPvcIfIndex points to the interface that the PVC is over.
> > ipoaConfigPvcVpi and Vci identify the PVC. The ifIndex via the
> > ipAddrTable should yeild local IP address.
> 
 If i understand you right here, the connection  between a local IP 
 address and a set of PVCs is the ifIndex pointing to the same (ATM) 
 interface.  But this relation would be  ambigous. E.g. it would be 
 able to configure different local IP addresses (from different LISs 
 the client should be member of and which are also configured). The 
 ifIndex of all local IP adresses could also point to the same ATM 
 interface. On this ATM interface i could define a number of PVCs to 
 be used with IPOA with the help of the ipoaConfigPvcTable. 
 Configuring those PVCs i am not able to tell to which LIS a PVC 
 "belongs". One solution i see is the use of logical interfaces (one 
 for each LIS) but there is no hint in the RFC for the need of that. 
 Maybe i am completly wrong with the concept and there is no need to 
 tell to which LIS a PVC belongs. That would lead to all configured 
 LIS being "visible" behind all configured PVCs.Which then would 
 maybe also lead to some confusion in counting the ARP stuff. 
 
 Thanks a lot for any help in that matter,
 Michael

 
------------------------------------
Michael Fischer             Tel.: ++49-721-625180
Fa. HiLan                   Fax.: ++49-721-6251899
Albert-Nestler-Str. 13      Mail: Michael.Fischer@hilan.de
D-76131 Karlsruhe
X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with
X-Info: 'unsubscribe ion' in the body of the message.