[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

973.0. "Reliability Groups " by CSC32::CULP () Mon Apr 21 1997 17:19

    Hi All,
    
    I have a customer trying to implement reliability groups on a
    gigaswitch. Customer attempted to use reliablity group 37- 37:(12,16)
    SPN Port 12 and SPN 16. They also have inverted the bridge to only
    pass LAT, SCA traffic. When they enable reliability groups for failover 
    purposes the customer claims that LAT and SCA do not flow across the 
    FDDI link. When they remove the reliability group LAT and SCA work again.
    Customer is running 6.0 Clearvision Multichassis manager, 3.1
    Gigaswitch firmware. It is my understanding that the original ports
    12 and 16 have a copy of the same forwarding database and they are
    tagged to port 37, thus loosing there physical nature and becoming
    virtual.  Any thoughts would be appreciated!! 
    
    Regards, 
    Kevin Culp (NSU Team)
    Customer Support Centre 
T.RTitleUserPersonal
Name
DateLines
973.1NPSS::MDLYONSMichael D. Lyons DTN 226-6943Tue Apr 22 1997 09:548
         They probably have the filters set up improperly.  Get them to
    provide the filter settings, and see if they have forgotten to set them
    for port 37.  Remember - any filters set before hunt group support
    (also reliablity groups) was added to the GIGAswitch/FDDI firmware will
    *not* include the virtual port numbers.  They don't magically expand to
    include those ports, you must specifically add them.
    
    MDL
973.2Config issue not GIGASwitch issueCSC32::J_SOBECKIJohn Sobecki, DTN 592-4101, CXO3-2/D2Tue May 06 1997 20:3611
    Hello,
    
    Here's a follow-up on this issue that Kevin posted.
    
    Reliability groups and filtering works fine.  The customer
    (specifically the Telco) had the 2 fddi pairs going to separate
    concentrators in different central offices and this was the 
    configuration problem.
    
    Good Day,
    John