Patch-ID# 101260-09 Keywords: responds, test, bridge, ring, token broadcast, subnet, udp Synopsis: SunLink TRI/S 2.1: Token Ring Jumbo Patch Date: Jan/20/1995 Install Requirements: None Solaris Release: 1.1 1.1C 1.1.1A SunOS Release: 4.1.3 4.1.3C 4.1.3_U1A Unbundled Product: SunLink/TRI/S Unbundled Release: 2.1 Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 1076386 1083712 1089420 1097559 1104805 1108110 1117083 1138122 1139786 1139878 1150270 1155448 1174050 1187715 Changes incorporated in this version: 1187715 Patches accumulated and obsoleted by this patch: 100555-03 100835-02 100882-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: sunlink/tr/4.X/sys/sun4c/OBJ/if_tr.o sunlink/tr/4.X/sys/sun4c/OBJ/if_tr_subr.o sunlink/tr/4.X/sys/sun4m/OBJ/if_tr.o sunlink/tr/4.X/sys/sun4m/OBJ/if_tr_subr.o sunlink/tr/4.X/sys/sun4m_35/OBJ/if_tr.o sunlink/tr/4.X/sys/sun4m_35/OBJ/if_tr_subr.o sunlink/tr/4.X/sys/sunif/if_trreg.h sunlink/tr/4.X/sys/sunif/if_trvar.h sunlink/tr/4.X/sys/sunif/tr_conf.c sunlink/tr/usr.etc/prtsrtab.c sunlink/tr/usr.etc/srtd.README sunlink/tr/usr.etc/srtd.c sunlink/tr/usr.etc/tr_version NOTE: sun4c, sun4m, sun4m_35 NOTE: sunlink/tr/4.X/sys/sun4m_35/OBJ files are for Classic, LX and Aurora Problem Description: (101260-08) Bug ID 1187715 ( Esc# 11575 and Esc# 11688 ) - ******Esc 11688 ******* The customer is attempting to install tri 2.1 on an S5 Aurora, and is getting the following error message during startup: "Jan 3 14:59:30 midcomm1 vmunix: tr0: Ring down. Jan 3 14:59:30 midcomm1 vmunix: tr0: Ring Up!! Jan 3 14:59:30 midcomm1 vmunix: tr0: tr0: Bad token ring adapter card: <11> Jan 3 14:59:30 midcomm1 vmunix: Token ring adapter check parm_0=0x2 Jan 3 14:59:30 midcomm1 vmunix: Token ring adapter check parm_1=0xff64 Jan 3 14:59:30 midcomm1 vmunix: Token ring adapter check parm_2=0x6f48 Jan 3 14:59:30 midcomm1 vmunix: tr0: dma read abort. Jan 3 14:59:30 midcomm1 vmunix: tr0: Ring down. Jan 3 14:59:30 midcomm1 vmunix: tr0: Ring Up!! Jan 3 15:01:14 midcomm1 login: ROOT LOGIN ttyp0 FROM riddler" The same tri board (rev-03) and software versions work ok on an SS-20 connected to the same mau. *******Esc 11575 ****** On sparcclassic running 4.1.3 U1, with TRI 2.1 patch 101260-08, customer gets: tr0:bad token ring adapter card: <11> token ring adapter check parm_0=0x0 token ring adapter check parm_1=1xfff1 token ring adapter check parm_2=0xC218 tr0: dma write abort. tr0: ring down. Part number for the card is 501-1932-00 A REV 50, LSI chip is L64853AQC. Customer should have 501-1932-02. Request for new card for exchanging. *********************** Problem description - Both the FCS and Patch prior to 101260-09 of TRIS 2.1 release do *NOT* have proper packaging information for sun4m_35 architechture. A special memory related handling routine that is required only for the Classic, LX and Aurora machine was not being built correctly which caused the kernel to constantly crash when bring up the Token Ring interface. This problem is fixed in 101260-09 patch. ================================================================= (101260-07) Bug ID #1174050 (Esc. 10201)- On system with TRI 2.1 customer is running server and client programs. Server program receives multiple responses from the same interface with different MAC addresses. Symptoms are easly reproducable on customer site. Server and client programs are available via anonymous ftp from: magda.east:/pub/1607846 In the same directory I am inluding output from ifconfig , netstat -rn and snoop trace and output from test run at customer site. This may not be a bug but CTE requires bug id included in cte escalation. (101260-07) The tr_install script was missing in the previous 101260-06 patch. (101260-06) 1117083 TRI/S 2.1 responds to bridge test. While doing a beidge tes, Sun with TRI/S 2.1 responds. This results in bridge reporting an invalid network route. The Sun TRI/S 2.1 responded to TEST packets or data packets which are addressed to other station (not for Sun TRI/S 2.1) from the IBM PS/2 machine while the Sun TRI/S 2.1 is in promiscuous mode. 1138122 Large number of Ierrs for TRI/S 2.1 from netstat 0i command. When TRI/S 2.1 is in promiscuous mode the system indicates a huge number of Ierrs (inbound erros) on TRI/S from the netstat -i command. (101260-05) 1155448 always panics on aurora / ss5 (101260-04) 1150270 TRI/S 2.1 Patch 101260-03 does not compile correctly under 4.1.3C for Classic/LX (101260-03) Fix for problem running TR 2.1 in Classic/LX under 4.1.3U1 1139786 With TRI/S 2.1 FCS CD and floppy cannot be installed directly on 4.1.3 and later 4.X SunOS, without first resorting to patch 100882-01. However, 100882-01 does not correctly install on 4.1.3/ss10 (escalation 6622) From escalation 6622: PATCH 101181 REQUIRED FOR SUN4M ARCHITECTURE AND 4.1.3 TRI/S 2.1 panicked under 4.1.3C or 4.1.3U1 running on Classic/LX machines. This latter problem was fixed by 101260-02. From escalation 6327: TRI/S 2.1 AND SOLARIS 1.1 REV C NOT COMPATIBLE ON SPARCSTATION LX (from 100835-02) Bug-ID 1104805, 1108110 The TRI/S software was losing the address of the station with which it has LLC link and was broadcasting LLC level message RR. The remote station used to respond two RR frames to this RR which Sun TRI/S did not like there by generating FRMR and bringing down the link. Bug-ID 1097559 TRI/S did not flush source route cache when source route table entry was replaced. Bug# 1089420 Site has Prestoserve, 64MB ram, one 2*Proc Ross, TRI/S, usual SCSI devices, plus 4*1.3GB IPI, and 2*1.2GB 3MB/sec IPI drives.. Sybase applications. Token Ring is the Customer''s only network, is running a ring of PC''s via NFS. Event sequence 1/ Token ring network I/F failure, PCs could no longer ping server, but could ping each other. Server could not ping PCs. 2/ Admin ifconfig''d pr0 down. NFS reported loss of contact 3/ Admin then ifconfig''d pr0 up, this paniced the system. Bug# 1076386 When a sna3270 gateway is running on TR/I, when sna3274 gateway is brought up, the console display "tr0: out of mbufs - dropped packets" every 1-3 seconds. Both system and sna3270 gateway seem to be running fine. This bug also applies to the snap2p gateway. Other problems fixed: 1) receive congestion 2) functional address capability 3) The dynamic source route table patch renders the prtsrtab program useless (bug report #1110091). Instead, srtd.c should be compiled (from 100882-01) 1083712 The installation script of TRI/S 2.1 on SunOS 4.1.3 prints the message OS version not supported by TRI/S. Patch Installation Instructions: -------------------------------------------------------------------- Though this is a ''patch'', it is a full-release of TR 2.1 for SunOS 4.X, updated with all relevant patches. 1. Save off current version of tr cd /usr/sunlink mv tr tr.save 2. Place the directory tr under /usr/sunlink 3. Run tr_install, which creates a new kernel cd /usr/sunlink/tr/install tr_install 4. Save off current kernel, copy new kernel to root and reboot the machine with the new kernel. Special Install Instructions: ---------------------------------- None. README -- Last modified date: Tuesday, January 7, 2003