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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3228.0. "MCC-E-IO_ERROR with bridge communication" by VCSESU::WADE (Bill Wade, VAXc Systems & Support Eng) Mon Jun 22 1992 13:32

    I'm getting the following error when I try to communicate with a
    bridge.
    
            
            DECmcc (T1.2.7)
    
    MCC> register bridge decbridge add=08-00-2b-27-1d-5b
    
    Bridge LOCAL_NS:.decbridge
    AT 22-JUN-1992 12:32:22
    
    Partial registration success. Please retry later to complete the
    registration.
            Reason for Partial Registration = The requested operation
    						cannot be completed
                          MCC Routine Error = %MCC-E-IO_ERROR, error was
    						returned by I/O facility
                          VMS Routine Error = %SYSTEM-F-IVDEVNAM, invalid
    						device name
                                              
    MCC> exit
T.RTitleUserPersonal
Name		DateLines
3228.1QUIVER::HAROKOPUSMon Jun 22 1992 13:5110
I looks like the bridge cannot be reached so it was partially registered 
by MCC.   Try the following command:

MCC> show bridge 08-00-2b-27-1d-5b all id


If this command fails check the bridge to see if it is operating.


Bob
3228.2What could cause this error message???VCSESU::WADEBill Wade, VAXc Systems & Support EngMon Jun 22 1992 14:5023
        
     It is a partial registration but it's cause is related to the error
    message and that's what I need help with.
    
    Thanks,
    Bill
        
        The show comand gives the same error.
    
    
    MCC> show bridge 08-00-2b-27-1d-5b all id
    
    Bridge {08-00-2B-27-1D-5B}
    AT 22-JUN-1992 13:52:45 Identifiers
    
    The requested operation cannot be completed
                          MCC Routine Error = %MCC-E-IO_ERROR, error was
    returned
                                              by I/O facility,
                          VMS Routine Error = %SYSTEM-F-IVDEVNAM, invalid
    device
                                              name
3228.3VCSESU::WADEBill Wade, VAXc Systems & Support EngMon Jun 22 1992 14:533
    
  	I can get to the bridge from ELMS (not DECmcc ELMS) V1.1.
3228.4try via portYAZ8::GUARINOMon Jun 22 1992 17:006
Try using via port xxxx:

There was a problem in a version of t1.2.7, though we hadn't seen it
in the vms version

Vin
3228.5List of Ports...CHRISB::BRIENENDECmcc LAN and SNMP Stuff...Mon Jun 22 1992 18:325
To add to Vinny's suggestion:

 Use the command "SHOW MCC 0 BRIDGE_AM ALL STATUS" to get the list of
 available ports for the VIA PORT qualifier.
3228.6The DEMFA is a problemVCSESU::WADEBill Wade, VAXc Systems & Support EngTue Jun 23 1992 10:4681
    
    Thanks.  The FDDI adapter was the problem.
    
    I've attached some  show commands.  I'm running DECmcc V1.2.7 on a 
    VAX 6000 with a DEMFA and VMS 5.4-3.

    I've tried using VIA PORT FXA0: as a default qualifier and I can access
    the bridges so that was the problem.  The SHOW MCC 0 BRIDGE_AM ALL 
    STATUS command does not get the DEMFA.
    
    

SHOW BRIDGE *
!Using default ALL IDENTIFIERS
!
!Bridge LOCAL_NS:.bridge.lan234 
!AT 23-JUN-1992 09:48:50 Identifiers
!
!The requested operation cannot be completed
!                      MCC Routine Error = %MCC-E-IO_ERROR, error was returned 
!                                          by I/O facility,
!                      VMS Routine Error = %SYSTEM-F-IVDEVNAM, invalid device 
!                                          name
SHOW MCC 0 BRIDGE_AM all status
!
!MCC 0 BRIDGE_AM 
!AT 23-JUN-1992 09:27:28 Status
!
!Cannot communicate with target
!
SHOW MCC 0 BRIDGE_AM all attrib
!
!MCC 0 BRIDGE_AM 
!AT 23-JUN-1992 09:27:31 All Attributes
!
!Cannot communicate with target
!                      Component Version = T1.2.7
!               Component Identification = "DECmcc Bridge AM"
!
SHOW MCC 0 ethernET_AM all attrib
!
!MCC 0 ETHERNET_AM 
!AT 23-JUN-1992 09:27:36 All Attributes
!
!Cannot communicate with target
!                      Component Version = T1.2.7
!               Component Identification = "DECmcc Ethernet AM"
!
SHOW MCC 0 DNA4_AM     all attrib
!
!MCC 0 DNA4_AM 
!AT 23-JUN-1992 09:27:39 All Attributes
!
!               Component Identification = "DECmcc DECnet DNA4 AM"
!                      Component Version = "T1.2.7"
!
USE DEF QUALIF VIA PORT FXA0:
!%MCC-S-DEFQUAL, via port fxa0: will be used as the default qualifier
!
SHOW BRIDGE *
!Using default ALL IDENTIFIERS
!
!Bridge LOCAL_NS:.bridge.lan234 
!AT 23-JUN-1992 09:42:41 Identifiers
!
!Examination of attributes shows:
!                                   Name = LOCAL_NS:.bridge.lan234
!                                Address = { 08-00-2B-27-1D-5B,
!                                            08-00-2B-67-1D-5B,
!                                            08-00-2B-27-21-0E,
!                                            08-00-2B-67-21-0E }
!
SHOW MCC 0 BRIDGE_AM ALL STATUS
!
!MCC 0 BRIDGE_AM 
!AT 23-JUN-1992 09:43:04 Status
!
!Cannot communicate with target
!
exit
!
3228.7Autopology and the DEMFAVCSESU::WADEBill Wade, VAXc Systems & Support EngTue Jun 23 1992 12:378
    
    It looks like another problem with the DEMFA is the LAN Autopology 
    Spanning Tree Map Listener won't recognize FXA0:.
    
    I know not many customers will be using  a 6000/9000 as the DECmcc
    platform but...
3228.8FDDI Host Ports not "supported"CHRISB::BRIENENDECmcc LAN and SNMP Stuff...Thu Jun 25 1992 10:388
The MCC_EA (Ethernet Access) Exec Routines do not completely support
FDDI devices: they are not autosized and thus do not appear in the
list of supported devices (e.g. SHOW MCC 0 BRIDGE_AM AVAILABLE PORTS).

Using VIA PORT <fddi-device> was viewed as a workaround for FDDI-only
systems until formal support for these devices can be added.

					Chris Brienen
3228.9Via port for bridge polling does not work.VCSESU::WADEBill Wade, VAXc Systems &amp; Support EngThu Jun 25 1992 16:1919
    Using VIA PORT is not a workaround.  For example what do I do
    for alarm polling of bridges?  
    
    MCC> use def qual via port fxa0:
    %MCC-S-DEFQUAL, via port fxa0: will be used as the default qualifier
    MCC> enab domain ltnip rule bridge-deviceframessent
    
    Domain LOCAL_NS:.ltnip Rule bridge-deviceframessent
    AT 25-JUN-1992 15:23:53
    
    This request cannot use the 'Via Port' qualifier
                   Unsupported Qualifier Id = Via Port
    
    
    
    Any workaround?
    
    Thanks,
    Bill
3228.10FDDI-only access not supported.CHRISB::BRIENENDECmcc LAN and SNMP Stuff...Mon Jun 29 1992 20:4214
DECmcc V1.2 does not (fully) support access to an Ethernet (or FDDI) device
from a Host FDDI controller.

A potential workaround is to use VIA PORT. This only works in cases where
the VIA PORT qualifier is supported by the DECmcc SYSTEM. Missing support
for the VIA PORT qualifier should result in QARs against the related MCC
component.

Real support (and not just Ethernet compatible mode) for FDDI host devices
sounds like a good function to incorporate for DECmcc V1.3...

						Chris