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

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

236.0. "FDDI controller unavailable after 7.1 upgrade" by DV780::DBARTROP (Have no fear, Underdog is here!) Fri Feb 21 1997 11:33

Hi All,

	After upgrading from 7.0 to 7.1 and installing DECnet plus, The FDDI
controller (DEFZA-A) stopped functioning.  Stopping DECnet plus from starting
did not have any effect on this device.  Currently DECnet is set not to start,
this done via NET$IGNORE_DECNET logical.  ie.  "NET$IGNORE_DECNET" = "TRUE"

The system is a DEC3000 M500, PALCODE, v3.8 loaded, VMS 7.1, UCX 4.1-12 
 w/ECO 41_2 v2.0 

all devices pass hardware startup test....

==============================================================================
Device and driver for the FDDI controller before UCX is started............

$ sh dev fca0: /full

Device FCA0:, device type DEFTA, is offline, network device, error logging is
    enabled, device is a template only.

    Error count                    0    Operations completed                  0
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot              S:RWPL,O:RWPL,G,W
    Reference count                0    Default buffer size                 512
    
================================================================================

SYSMAN> io sh dev

%SYSMAN-I-OUTPUT, command execution on node RISTRA

__Driver________Dev_DDB______CRB______IDB_______Unit__UCB_____

.
.
.
SYS$FCDRIVER
                FCA 811C4C40 811C4CC0 811C4AC0
                                                   0  811C4E00
.
.
.


================================================================================

Part of the UCX$CONFIG procedure reguarding FCA0:


* Do you want to configure CF0 [YES] ?
Enter unqualified host name: ristra2

        Host ristra2 exists in the database.

Enter Internet address [134.253.223.115] :
Enter Internet network mask for ristra2 [255.255.0.0]: 255.255.255.0
Enter broadcast mask for ristra2 [134.253.223.255]:

        The following parameters will be used to define the
        Internet interface CF0:

                Host name:         ristra2.nds.sandia.gov
                Internet address:  134.253.223.115
                Network mask:      255.255.255.0
                Broadcast mask:    134.253.223.255

* Is the above correct [YES] ?

        End of configuration questions for Internet interface CF0
        
At this point all appears to be as it should.......
        
------------------------        
Starting UCX from Configuration Menu.......................

Enter configuration option: 6
Begin Startup...


%UCX$NFS-I-NOMAP, No file system mapping information available.
-UCX$NFS-I-NOMAP, Refer to NFS Server section of
-UCX$NFS-I-NOMAP, Digital TCP/IP Services for OpenVMS Management Guide.

%RUN-S-PROC_ID, identification of created process is 0000013C
The Internet driver and ACP were successfully loaded.
%UCX-I-SETLOCAL, Setting domain and/or local host
%UCX-I-SETCOMMP, Setting communication parameters
%UCX-I-SETPROTP, Setting protocol parameters
%UCX-I-STARTCOMM, Starting communication
%UCX-I-DEFINTE, Defining interfaces                    < about 60 second pause
%UCX-E-INVINTER, Error defining interface: CF0         <<<<<<<<<<<<<<<<<<<<<<<
-UCX-I-ACPQIO, Failure on Internet ACP QIO             <<<<<<<<<<<<<<<<<<<<<<<
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available   <<<<<<
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available   <<<<<<
%UCX-E-INVINTERNAM, Invalid interface name             <<<<<<<<<<<<<<<<<<<<<<<
-UCX-I-DRIVERQIO, Failure on Internet driver QIO       <<<<<<<<<<<<<<<<<<<<<<<
-UCX-E-INVNETMASK, Invalid network mask                <<<<<<<<<<<<<<<<<<<<<<<
%UCX-E-DELINTER, Error deleting interface: CF0         <<<<<<<<<<<<<<<<<<<<<<<
-UCX-I-ACPQIO, Failure on Internet ACP QIO             <<<<<<<<<<<<<<<<<<<<<<<
-UCX-E-INVINTERNAM, Invalid interface name             <<<<<<<<<<<<<<<<<<<<<<<
%UCX-I-ENABSERV, Enabling services
%UCX-I-STARTNAME, Starting name_service
%UCX-I-LOADSERV, Loading UCX Server proxy information
%UCX-I-SERVLOADED, UCX Aux. Server loaded with 1 proxy records
-UCX-I-SERVSKIP,  Skipped 0 communication proxy records
-UCX-I-SERVTOTAL,  Total of 3 proxy records read
%RUN-S-PROC_ID, identification of created process is 0000013E
%PWIP-I-INFO, the PWIP driver and ACP were successfully loaded.
Startup request completed.
Press Return to continue ... 



===============================================================================

No changes occured to the device or driver after the startup attempt was made.

SH DEV FC /FULL         Same as above
SYSMAN IO SHOW DEVICE   Same as above

The same errors occur during a boot (cold or warm) if the interface is left
configured with in UCX.

Any ideas on the issue would be greatly appreciated.


	Dale

T.R	Title	User	Personal Name	Date	Lines
236.1	check the SPD - DEFZA is not supported by TCP/IP or Clusters on Alpha	CERN::HOBBS	Congrats to the Ignoble Peace Prize winner! (http://www.eecs.harvard.edu/ig_nobel)	`Fri Feb 21 1997 12:53`	67
	$search OLD$:<DOCS.SPD.VMSV71>.txt defza,defta/win=5 *************************** OLD$:<DOCS.SPD.VMSV71>CLUSTER_SPD.TXT;1 information. The DEFZA FDDI adapter is supported on VAX systems only. Note: VAX systems cannot be booted over an FDDI. *********** connect and can be booted as a satellite node over this interconnect. [5]Using DEFTA only. [6]Some models may provide slightly different interconnect ************************** OLD$:<DOCS.SPD.VMSV71>DECNET_PLUS_ALPHA_SPD.TXT;1 Adapter___Definition______________________________________ DEFZA A high-performance network adapter that connects DEFTA TURBOchannel systems to ANSI FDDI LANs (direct memory access receive only) ************************** OLD$:<DOCS.SPD.VMSV71>DECNET_PLUS_VAX_SPD.TXT;1 Adapter___Definition______________________________________ DEFZA A high-performance network adapter that connects DEFTA TURBOchannel systems to ANSI FDDI LANs (DMA receive only) ************************** OLD$:<DOCS.SPD.VMSV71>OVMS_SPD.TXT;1 LAN Options (VAX and Alpha) DEFTA A high-performance network adapter that connects TURBOchannel systems to ANSI FDDI local area net- works. DEFZA A high-performance network adapter that connects TURBOchannel systems to ANSI FDDI local area net- works. (DMA receive only.) *********** DEFQA FDDI to Q-bus controller. DEFZA FDDI to TURBOchannel controller. DEFTA FDDI to TURBOchannel controller. KFE52 DSSI/Ethernet adapter for the VAXft 3000. Minimum of **************************** OLD$:<DOCS.SPD.VMSV71>TCPIP_SPD.TXT;1 Ethernet DEFTA A high-performance network adapter that connects TUR- BOchannel systems to ANSI FDDI local area networks.
236.2	Check Ring Status	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Fri Feb 21 1997 13:10`	14
	See if the controller is connected to an operational FDDI ring (the DEFZA tends to stay in an `offline' state if not connected to a working FDDI ring), check the DEFZA firmware (V1.3 was the most recent and last version -- OpenVMS should print out a warning during bootstrap if the revision is too low), what's the state (on, off, blinking) and what's the color (green, red) of the LED on the DEFZA bulkhead? In SDA, issue a SHOW LAN/FULL command, looking for the DEFZA. Note that the DEFZA is supported for VMScluster operations only under OpenVMS VAX V7.1, not under OpenVMS Alpha V7.1. It is supported under OpenVMS. Check the other relevent SPDs -- UCX, DECnet, etc. -- too.