Conference noted::atm

904.0. "ATMswitch900 LANE/SNMP?" by SNOFS1::63496::CHIUANDREW () Tue Apr 15 1997 22:31

    Hi,
    
    Just a quick questions on ATMswitch900 (if this is not the right place
    to ask about ATMswitch900, could someone tell me which notes should it
    be)?
    
    1) If we use ATMswitch900 as LANE server (LECS/LES/BUS), is there any
    limitation on how VCs can be supported as a BUS?
    
    2) How many (is there any rule of thumb for an ATMswitch900, served 
    as a BUS) LANE Clients can be supported on an ATMswitch900?
    
    3)	Is there any plan to put PNNI on ATMswitch900 (someone mentioned
    V2.5, how far is it from now)?
    
    4) To manage the ATMswitch900, we have to use SNMP, and we can send the
    snmp commands from Ethernet or RAW AAL5 on VCI=16 on ATM link, could
    some explain the differences? If we have to manage 5 ATM900, then how
    can it be done via RAW AAL5? Or it is not possible?
    
    
    
    thanks again for help!
    Andrew Chiu - NSIS Sydney

>   4) To manage the ATMswitch900, we have to use SNMP, and we can send the
>   snmp commands from Ethernet or RAW AAL5 on VCI=16 on ATM link, could
>   some explain the differences? If we have to manage 5 ATM900, then how
>   can it be done via RAW AAL5? Or it is not possible?

SNMP over raw AAL5 on VCI 16 is there for ILMI purposes, such as ATM address
registration and keep-alive handshaking.  It's not intended to be a way that
a network management station could access the switch.

In fact, most of our MIB handlers explicitly test for and block all requests
from ILMI sources.  By design, ILMI has no community string protection - you
can have any read-write community string you like so long as it's the string
the Forum publishes for the whole world to read.

    re .1,
    thanks for answer to 4).
    
    
    Is there anyone who can help to other 3 questions?
    
    
    thanks in advance for help!
    Andrew Chiu - NSIS Sydney