Conference netcad::hub_mgnt

2858.0. "fddimibPORTPMDCLass SNMP variable wrong on SMF PMD ?" by BRIEIS::BARKER_E (Ummm...) Fri Oct 13 1995 10:29

    Hi,
    
    	We're working on a customer config where there are two sites
    connecting via two DECconcentrators at each site using DEChub ONE-MX's
    with SMF PMS's (DEFXS-AA) handling the ring connections. Config at each
    site is as shown :-
    
    
         SMF from remote
         site                              SMF to remote site
          |                                |
         _A___________           __________B_
    	| ONE-MX      |         |  ONE-MX    |
    	|_____________|         |____________|
        |             |         |            |
        | 900 MX      |         | 900 MX     |
        |_____________|         |____________|
         M M M M M B              A M M M M M
                   |              |
                   |____MMF_______|
    
    All components are running the Wave 3 firmware, and was set up using
    Hubwatch 4.0.1 for Windows, and configuring the DEChub ONE-MX's as
    necessary to allow the above config.
    
    	When we query the port type using SNMP and the fddi mib (rfc1512) 
    with DECmcc, the port type (A,B,M etc) shows up correctly but on the B 
    ports on the DEChub-ONE MX's, instead of showing a 'fddimibPORTPMDClass' 
    of 'single-mode2' it  shows a value of 'low-cost-fiber'.  
    The A ports report 'single-mode2'. Is this a 'feature' of the response to
    snmp queries on B ports on the DEChub-ONE MX ? Should it be showing
    'single-mode2' ?
    
    	Reason for asking is that no connections are successfully being
    made across the link to the remote site at the moment. We seem to have
    suitable attenuators and have measured the db loss etc. but when we
    plug the SMF in the ports show no change in lights, or connection
    success in SNMP ?  We have also tried connecting 'A' port from once
    concentrator to 'A' port on the other sites concentrator with no luck. 
    We suspect cabling problems are the cause but would like to clear any
    confusion/red herrings or possible problems with the PMD class showing
    incorrectly.
    
    	Thanks for any help/suggestions, 
    
    
    	Euan Barker

    
    Update to .0
    
    We NOW have the ring working so please disregard the last paragraph of
    .0.
    
    What we want to know is why does the port A PMD get reported as
    single_mode2 and the port B PMD as low_cost_fiber?
    
    Is this a feature of the mib or firmware?
    
    
    :J