[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference npss::gigaswitch

Title:GIGAswitch
Notice:GIGAswitch/FDDI Jan 97 BL3.1 914.0 documentation 412.1ion 412.1
Moderator:NPSS::MDLYONS
Created:Wed Jul 29 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:995
Total number of notes:4519

975.0. "IP addresses with multiple bridge domains ?" by UTOPIE::BRAUN_R () Sun Apr 27 1997 06:17

    Hi all,
    
    we would like to implement a second complete independent LAN (as in
    note 969) with 2 logical independent bridge domains. There will be
    IP and DECnet-routing between these LANs.
    For IP this means a seconds IP subnet. 
    For example, having the linecards 2-6 in this additional bridge domain,
    what about IP addresses (and default gateway,...) for sending traps,
    being reachable for ClearVISN or any other SNMP traffic,..  ?
    
    Is there a way to assign IP addresses in the new subnet for only these
    linecards (with their own subnet mask, default gateway,...).
    
    If the primary LAN fails (that's exactly why we introduce the second
    LAN), is it possible to send the traps via the second LAN ?
    Individual trap adresses possible ?
    
    
    Any help will be highly appreciated.
    
    Thanks,
    Ralph
T.RTitleUserPersonal
Name		DateLines
975.1NPSS::MDLYONSMichael D. Lyons DTN 226-6943Thu May 08 1997 17:5368
        No, you can't assign different default gateways for different
    ports.  However, most people would do this by just defining routes for
    those subnets.
    
        IP addresses are assigned on a per port basis, and each assignment
    comes with a mask, which is not necessarily related to other IP address
    assignments/masks.
    
        Traps on the GIGAswitch/FDDI system are sent to those IP addresses
    defined in the ELAN MIB - see eauthTrapUserTable
    
    MDL
    
    

    eauthTrapUserTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF EauthTrapUserEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
               "A list of addresses to which traps will be sent and
               associated information."
    ::= { eauth1 2 }

    eauthTrapUserEntry OBJECT-TYPE
        SYNTAX  EauthTrapUserEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
               "Objects containing information for a given trap address."
        INDEX  { eauthTrapUserAddr }
        ::= { eauthTrapUserTable 1 }

    EauthTrapUserEntry ::=
        SEQUENCE {
            eauthTrapUserAddr
                IpAddress,




                                                                    

            eauthTrapUserStatus
                INTEGER
                 }

    eauthTrapUserAddr OBJECT-TYPE
        SYNTAX  IpAddress
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
               "An IP Address to which all SNMP Trap messages will be sent."
    ::= { eauthTrapUserEntry 1 }

    eauthTrapUserStatus OBJECT-TYPE
        SYNTAX  INTEGER {
                           other(1),
                           invalid(2)
                        }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
               "Writing invalid(2) to this object removes the corresponding
               entry.  When read, this object always returns a value
               of other(1)."
    ::= { eauthTrapUserEntry 2 }