Conference npss::gigaswitch

993.0. "IP Packet Switching, Routing, ATM over AGL-2" by SCASS1::auodial1_port7.auo.dec.com::korns () Mon Jun 02 1997 13:15

Will the "IP Packeting Switching" support in the GIGAswitch/FDDI
(I'm assuming in V3.2) work over ATM links/PVCs? 

In other words, could I create a PVC that runs from a GS/FDDI 
AGL-2 to a VNswitch 900EA that terminates one end of a bridge 
tunnel and have the GS/FDDI IP Switching logic treat that PVC
as a routed port (terminology???). ... or assign an address range
to that PVC? 

Is there a limit to the number of PVCs an AGL-2  can terminate?

I'm thinking of a configuration that has many PVCs going to 
different sites connected thru a GIGAsw/ATM to remote VNsw900EAs

                      
                  +---------+
                  | GS/FDDI |
                  +---AGL---+
                      ||
                      || ATM-155
                      ||
                  +---------+
                  | GS/ATM  |
                  +---------+
                   / / | \ \ 
                  / /     \ \ ATM-T1s
                 /           \
            +---------+    +---------+
            | VN900EA |    | VN900EA |
            +---------+    +---------+

I believe I could do this using bridge tunnels but I'd
like to contain multicast to avoid burdening the T1s
with un-nessecary MC traffic.

I know I can eventually enable routing over a bridge 
tunnel on the VN side but it's the central site's broadcast
I'd like to keep off the T1s.

Dave
          

>Will the "IP Packeting Switching" support in the GIGAswitch/FDDI
>(I'm assuming in V3.2) work over ATM links/PVCs? 

        Sure - from the perspective of the SCP (which is doing all this
    work), an AGL-2 or AGL-2+ port is just another bridge port.  The fact
    that the data temporarily becomes ATMized is not relevant to the
    packet level.  What goes on between two consenting AGLs is not
    important to the SCP.
    
>In other words, could I create a PVC that runs from a GS/FDDI 
>AGL-2 to a VNswitch 900EA that terminates one end of a bridge 
>tunnel and have the GS/FDDI IP Switching logic treat that PVC
>as a routed port (terminology???). ... or assign an address range
>to that PVC? 

        There is no support for routing on the GIGAswitch/FDDI system.
    Address ranges are assigned to ports.
    
        There is no "tagging" of frames happening, so there would be no way
    to identify from which "PVC" an arriving frame originated.
    
>Is there a limit to the number of PVCs an AGL-2  can terminate?

    Yes, one on each port.
    
>I'm thinking of a configuration that has many PVCs going to 
>different sites connected thru a GIGAsw/ATM to remote VNsw900EAs

    ...sorry.
                      
    MDL

Thanks Michael.

Opps, I'd assumed multiple PVCs per physical port ... never mind!

Dave