From vp@goldentele.com Tue Nov 27 03:07:02 2001 Received: from office.gt.com.ua (office.gt.com.ua [212.82.192.58]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fARB6xxM022338 for ; Tue, 27 Nov 2001 03:07:01 -0800 (PST) Received: from wowa.office.gt.com.ua (wowa.office.gt.com.ua [10.100.1.3]) by office.gt.com.ua (8.9.3/8.9.3) with ESMTP id NAA25962 for ; Tue, 27 Nov 2001 13:06:58 +0200 (EET) (envelope-from vp@goldentele.com) Received: by wowa.office.gt.com.ua with Internet Mail Service (5.5.2653.19) id ; Tue, 27 Nov 2001 13:06:58 +0200 Message-ID: From: "Patenko, Vladislav" To: "'users@conserver.com'" Subject: consoles with command Date: Tue, 27 Nov 2001 13:06:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="KOI8-R" Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Hello, I try to setup my console server (vesrion 7.1.3). And, I need to consoles with telnet or rlogin command. I setup conserver.cf like that: term1:|telnet 10.100.1.207::term1: Conserver runs fine: root#mustang:/usr/local/etc console -u term1 up But, when I try to access to console term1, and quit from telnet, I have: root#mustang:/usr/local/etc console -u term1 down Conserver does not run telnet again, and console go to down state, and I can not connect to this console as far as conserver restart. This is conserver feature ? May I disable this feature ? -- Vlad Patenko, Golden Telecom From jdwhite@iastate.edu Tue Nov 27 09:20:25 2001 Received: from zathras.ait.iastate.edu (zathras.ait.iastate.edu [129.186.145.108]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fARHKOxM025215 for ; Tue, 27 Nov 2001 09:20:25 -0800 (PST) Received: (from jdwhite@localhost) by zathras.ait.iastate.edu (8.8.5/8.8.5) id LAA24328; Tue, 27 Nov 2001 11:20:06 -0600 (CST) Date: Tue, 27 Nov 2001 11:20:05 -0600 From: Jason White To: "Patenko, Vladislav" Cc: "'users@conserver.com'" Subject: Re: consoles with command Message-ID: <20011127112005.D20318@iastate.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Tue, Nov 27, 2001 at 01:06PM +0200, Patenko, Vladislav wrote: >Hello, > > I try to setup my console server (vesrion 7.1.3). > And, I need to consoles with telnet or rlogin command. > > I setup conserver.cf like that: > term1:|telnet 10.100.1.207::term1: > > Conserver runs fine: > >root#mustang:/usr/local/etc console -u > term1 up > >But, when I try to access to console term1, and quit from telnet, I have: > >root#mustang:/usr/local/etc console -u > term1 down > >Conserver does not run telnet again, and console go to down state, and I can >not connect to this console as far as conserver restart. I had this same experience using telnet in this manner. I found that using ^Eco to to re-open the console connection would re-establish the telnet connection. -Jason -- Jason White jdwhite@iastate.edu http://www.public.iastate.edu/~jdwhite From jimmy@nccom.com Tue Nov 27 16:21:47 2001 Received: from sinden.nccom.com (exim@sinden.nccom.com [198.51.175.35]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fAS0LlxM028719 for ; Tue, 27 Nov 2001 16:21:47 -0800 (PST) Received: from sunray2.nccom.com ([198.51.175.64]) by sinden.nccom.com with esmtp (Exim 2.12 #1) id 168sTy-0001aP-00 for users@conserver.com; Tue, 27 Nov 2001 16:21:46 -0800 Received: from jimmy by sunray2.nccom.com with local (Exim 2.12 #1) id 168sTx-0001YG-00 for users@conserver.com; Tue, 27 Nov 2001 16:21:45 -0800 Date: Tue, 27 Nov 2001 16:21:45 -0800 From: Jim Gottlieb To: users@conserver.com Subject: lines going "down" Message-ID: <20011127162145.F987@nccom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Hi all. We were using conserver 7.0.0 for several months, but ports seemed to get stuck too often, forcing me to restart the daemon, so I upgraded to 7.1.3. Unfortunately, things have been worse under this version. More often than not, ports suddenly go "down", and restarting the server makes some ports come up and others go down. Is there some better in-bewteen version I should try? I'm starting to get frustrated. oracle1 down pbxp1 down sunray1 up sunray2 up cisco up jtsd07 up jtsd08 up jtsd09 up toro up shasta down tahoe down vodavi up Right now, the four shown "down" should be "up". Five minutes ago, jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no active connection between the conserver and the terminal server for the "down" ports. ^Eco just comes back with "line is still down". We are using a Portmaster PM2e. Any help or suggestions would be appreciated. Thank you. From Ernie.Oporto@viragelogic.com Wed Nov 28 07:44:21 2001 Received: from viragelogic.com ([209.101.115.247]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fASFiLxM009024 for ; Wed, 28 Nov 2001 07:44:21 -0800 (PST) Received: by viragelogic.com; id KAA16504; Wed, 28 Nov 2001 10:45:52 -0500 (EST) Received: from nodnsquery(129.200.11.40) by webshield.viragelogic.com via smap (V1.0) id xma016497; Wed, 28 Nov 01 10:45:12 -0500 From: "Ernie Oporto" To: Subject: RE: lines going "down" Date: Wed, 28 Nov 2001 10:44:05 -0500 MIME-Version: 1.0 Message-ID: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <20011127162145.F987@nccom.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_00C9_01C177F9.9863BD80" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_00C9_01C177F9.9863BD80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit We saw a problem this week where the lines would not come up no matter what. After an hour of coaxing (stoping the daemon and restarting it, stopping and restarting...) they finally came up. Never went through that before, and they seem stable since then. Have to keep an eye on this... Ernie > -----Original Message----- > From: users-admin@conserver.com [mailto:users-admin@conserver.com]On > Behalf Of Jim Gottlieb > Sent: Tuesday, November 27, 2001 7:22 PM > To: users@conserver.com > Subject: lines going "down" > > > Hi all. We were using conserver 7.0.0 for several months, but ports > seemed to get stuck too often, forcing me to restart the daemon, so I > upgraded to 7.1.3. Unfortunately, things have been worse under this > version. More often than not, ports suddenly go "down", and restarting > the server makes some ports come up and others go down. > > Is there some better in-bewteen version I should try? I'm starting to > get frustrated. > > oracle1 down > pbxp1 down > sunray1 up > sunray2 up > cisco up > jtsd07 up > jtsd08 up > jtsd09 up > toro up > shasta down > tahoe down > vodavi up > > Right now, the four shown "down" should be "up". Five minutes ago, > jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no > active connection between the conserver and the terminal server for the > "down" ports. ^Eco just comes back with "line is still down". > > We are using a Portmaster PM2e. Any help or suggestions would be > appreciated. Thank you. > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > ------=_NextPart_000_00C9_01C177F9.9863BD80 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII9DCCApIw ggH7oAMCAQICAwUTKzANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw MC44LjMwMB4XDTAxMDYyMTEzMTUxM1oXDTAyMDYyMTEzMTUxM1owTjEfMB0GA1UEAxMWVGhhd3Rl IEZyZWVtYWlsIE1lbWJlcjErMCkGCSqGSIb3DQEJARYcZXJuaWUub3BvcnRvQHZpcmFnZWxvZ2lj LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA8wJMTF41OXQe5rxW6BROWjGrj9iGlCMn lZvumu950DX7TI8nJOUB3ZeMs01WNkKeuxK7nE3RGwGt2NjeDrYDqBqG1ScNkMpkxuZLhq2IhxUo rjfjmzgE1ln7MD+NvejFENaI4PA5n5x/zJLmZyCqs9oBLjeqtkmhlmX4n5srFP8CAwEAAaM5MDcw JwYDVR0RBCAwHoEcZXJuaWUub3BvcnRvQHZpcmFnZWxvZ2ljLmNvbTAMBgNVHRMBAf8EAjAAMA0G CSqGSIb3DQEBAgUAA4GBAB+KS7IJsyS0Wn61PPM8G9Ke9VA5dwyu3c0si+RnCKNDjvtKuO/8aD8b 8Q18MBU9SrbjJzq0B6yBBSjwj665rE7jCCUR8pMM9uJwQSxUiQfQWWmuV7qr1wknfGcCzXcz3GeG TfygeRqhh7WonJ+H9hUog4f5mvU2RsKVCsK5GkQrMIIDKTCCApKgAwIBAgIBDDANBgkqhkiG9w0B AQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAw MDAwMFoXDTAyMDgyOTIzNTk1OVowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUq bXA8+tyu9+50bzC8M5B/+TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tew kd4c6avgGAOofENCUFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0R BCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAw CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBAHMbbyZli/8VNEtZYortRL5Jx+gNu4+5DWom KmKEH7iHY3QcbbfPGlORS+HN5jjZ7VD0Omw0kqzmkpxuwSMBwgmn70uuct0GZ/VQby5YuLYLwVBX tewc1+8XttWIm7eiiBrtOVs5fTT8tpYYJU1q9J3Fw5EvqZa4BTxS/N3pYgNIMIIDLTCCApagAwIB AgIBADANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UE CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUu Y29tMB4XDTk2MDEwMTAwMDAwMFoXDTIwMTIzMTIzNTk1OVowgdExCzAJBgNVBAYTAlpBMRUwEwYD VQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNV BAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwt ZnJlZW1haWxAdGhhd3RlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1GnX1LCUZFtx 6UfYDFG26nKRsIRefS0Nj3sS34UldSh0OkIsYyeflXtL734Zhx2G6qPduc6WZBrCFG5ErHzmj+hN D3EfQDimAKOHePb5lIZererAXnbr2RSjXW56fAylS1V/Bhkpf56aJtVquzgkCGqYx7Hao5iR/Xnb 5VrEHLkCAwEAAaMTMBEwDwYDVR0TAQH/BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQDH7JJ+Tvj1 lqVnYiqk8E0RYNBvjWBYYawmu1I1XAjPMPuoSpaKH2JCI4wXD/S6ZJwXrEcp352YXtJsYHFcoqzc eePnbgBHH7UNKOgCneSa/RP0ptl8sfjcXyMmCZGAc9AUG95DqYMl8uacLxXK/qarigd1iwzdUYRr 5PjRzneigTGCAqowggKmAgEBMIGaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlm aWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAwLjguMzAC AwUTKzAJBgUrDgMCGgUAoIIBZTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ BTEPFw0wMTExMjgxNTQ0MDNaMCMGCSqGSIb3DQEJBDEWBBSIw7DColL/mB8/5hFZaScgnWEeTDBY BgkqhkiG9w0BCQ8xSzBJMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggq hkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCBqwYJKwYBBAGCNxAEMYGdMIGaMIGSMQsw CQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzAN BgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1Bl cnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAwLjguMzACAwUTKzANBgkqhkiG9w0BAQEFAASBgIpw7Dp6 TnOK4GdeZNYof4lPq243K683yhIQSP3IcCUkT9s2Pkg4qzCjB1M+OJlegSY2BXRiVIsvT5s9yqQf 8YQGBsfEN4f/08IeUJdcqmI0LMFOWtFkUNXUaHJFsor2RgMn3CborU0GQBT6Q18VHzglFKXNcf0G ynUzynE6DpNRAAAAAAAA ------=_NextPart_000_00C9_01C177F9.9863BD80-- From zonker@certaintysolutions.com Wed Nov 28 09:19:23 2001 Received: from yosemite.rwc.gnac.net (yosemite.rwc.gnac.net [198.151.248.221]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fASHJNxM009851 for ; Wed, 28 Nov 2001 09:19:23 -0800 (PST) Received: by yosemite.rwc.gnac.net; id JAA11931; Wed, 28 Nov 2001 09:19:19 -0800 (PST) Received: from unknown(192.168.1.21) by yosemite.rwc.gnac.net via smap (V5.0) id xma011926; Wed, 28 Nov 01 09:19:01 -0800 Received: from tweety.main.gnac.com (localhost.main.gnac.com [127.0.0.1]) by pepe.corp.gnac.com (8.11.0/8.8.7/GNAC-GW-2.1) with ESMTP id fASHIP111112; Wed, 28 Nov 2001 09:18:26 -0800 (PST) Received: (from zonker@localhost) by tweety.main.gnac.com (8.9.3/8.7.3/GNAC-COM-1.1) id JAA11691; Wed, 28 Nov 2001 09:19:00 -0800 (PST) Date: Wed, 28 Nov 2001 09:19:00 -0800 From: David Harris To: users@conserver.com Cc: zonker@gnac.com Subject: Re: lines going "down" Message-ID: <20011128091900.B5454@tweety.main.gnac.com> References: <20011127162145.F987@nccom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20011127162145.F987@nccom.com>; from jimmy@nccom.com on Tue, Nov 27, 2001 at 04:21:45PM -0800 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I've seen a similar scenario in one particular lab, using a Cisco 3640 with NM-32A cards. I don't think this is a brand issue. I merely offer it as another clue.... When we see the failure, we typically see 8 ports in a group go down...all 8 in a modulo-8 group. (i.e. 1-8, 17-24, etc.) All of the affected lines are run by the same OCTART chip. While I could point to a failure in IOS for this (which would only be circumstantial and unsupported by fact), I actually have another working theory, based on looking at the devices attached... In these cases, there was usually a network interruption between the conserver and the console server. This could be a switch/router failure in the network, or a forced reboot of the conserver host without a polite shutdown...and the devices showing 'down' were what I call 'quiet hosts'. (A quiet host is a device that only replies when you talk to it...it doesn't usually offer any log traffic, time stamps, etc. to the logs unless someone is typing to it.) In the case of a network break like this, the TCP session to all of the ports (from Conserver to the Console Server) don't get cleared out when the connectivity failure occurs! Since the host doesn't generate any traffic on the serial port, the console server never tries to send traffic to the conserver host, and the console server leaves the session open, thinking that the conserver host is just idle. The root cause here is that the TCP FIN sequence never occured. So, when you restart your Conserver, and it tries to then connect to these ports on the console server, the console server tells the conserver that the TCP port is busy (since the console server still thinks the old session is still there and idle...) In these cases, our cure has been to log into the console server, and reset each affected line, one by one. This will blow away the (already broken) TCP session, and allow you to either restart your conserver, or just force open each of the lines that were down. While this doesn't happen too often in the data centers, I have seen this in some of the remote locations. Maybe that's another good argument for having a distributed Conserver deployment, and putting a logging host 'closer' to the console servers? :-) Regards, -Z- http://www.conserver.com/consoles/breakoff.html From alfcab@mail.magma.ca Wed Nov 28 12:18:50 2001 Received: from mx2.magma.ca (mx2.magma.ca [206.191.0.250]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fASKIoxM011329 for ; Wed, 28 Nov 2001 12:18:50 -0800 (PST) Received: from mail1.magma.ca (mail1.magma.ca [206.191.0.252]) by mx2.magma.ca (8.9.3/8.9.3) with ESMTP id PAA29391 for ; Wed, 28 Nov 2001 15:18:49 -0500 (EST) Received: from tux (i7.magma.ca [64.26.168.124]) by mail1.magma.ca (8.11.2/8.11.2) with SMTP id fASKImi08885 for ; Wed, 28 Nov 2001 15:18:48 -0500 (EST) Message-Id: <200111282018.fASKImi08885@mail1.magma.ca> Date: Wed, 28 Nov 2001 15:19:36 -0500 (EST) From: alfcab Reply-To: alfcab Subject: Re: lines going "down" PM2e To: users@conserver.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: CdiyEavic7jwvPJJJKMSJg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 i86pc i386 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I have the same setup working as follows : \ internal net / -------------- | TCP V +------------+ | solarisx86 | +------------+ | TCP crossover V +------------+ | portmaster |-------------------------+ +------------+ | | | | Serial | Serial | Serial | Serial V V V V +-------+ +-------+ +-------+ +--------+ | unix1 | | unix2 | | cisco | | cisco2 | +-------+ +-------+ +-------+ +--------+ Each port on portmaster PM2e configured as follows : set cd on set extended on set modem set cd off set speed 1 9600 set speed 2 9600 set speed 3 9600 set idletime 0 set hangup off set prompt : set device /dev/network set service_device telnet set service_login telnet The entry in conserver.cf is as follows : LOGDIR=/var/consoles unix1:!portmaster::& unix2:!portmaster::& cisco:!portmaster::& cisco2:!portmaster::& As well the cabling is important, you don't want to send the break to sparc gear if the portmaster is resetted for any reason. I'm using standard cisco serial connectors on both ends pm2e and sparc gear with straight trough cables, for the cisco gear we use roll-overs ( they come with the cisco stuff ). FYI I tried linux first as a conserver server, and had the same behaviour you are experiencing, I decided to try solaris on x86 and voila my hangups on active connections dissapeared, maybe it's something related to specific's in OS's had no time to troubleshoot, just had to get it working in a reliable way ( no hangups ). Alfredo Cabrera >To: users@conserver.com >Sender: users-admin@conserver.com >Errors-To: users-admin@conserver.com >X-BeenThere: users@conserver.com >X-Mailman-Version: 2.0.5 >Precedence: bulk >List-Help: >List-Post: >List-Subscribe: , >List-Id: Conserver Users >List-Unsubscribe: , >List-Archive: >Message-Id: <20011128200007.160853C7CE@underdog.stansell.org> >Date: Wed, 28 Nov 2001 12:00:07 -0800 (PST) >Content-Length: 11409 > >Send users mailing list submissions to > users@conserver.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.conserver.com/mailman/listinfo/users >or, via email, send a message with subject or body 'help' to > users-request@conserver.com > >You can reach the person managing the list at > users-admin@conserver.com > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of users digest..." > > >Today's Topics: > > 1. lines going "down" (Jim Gottlieb) > 2. RE: lines going "down" (Ernie Oporto) > 3. Re: lines going "down" (David Harris) > >--__--__-- > >Message: 1 >Date: Tue, 27 Nov 2001 16:21:45 -0800 >From: Jim Gottlieb >To: users@conserver.com >Subject: lines going "down" > >Hi all. We were using conserver 7.0.0 for several months, but ports >seemed to get stuck too often, forcing me to restart the daemon, so I >upgraded to 7.1.3. Unfortunately, things have been worse under this >version. More often than not, ports suddenly go "down", and restarting >the server makes some ports come up and others go down. > >Is there some better in-bewteen version I should try? I'm starting to >get frustrated. > > oracle1 down > pbxp1 down > sunray1 up > sunray2 up > cisco up > jtsd07 up > jtsd08 up > jtsd09 up > toro up > shasta down > tahoe down > vodavi up > >Right now, the four shown "down" should be "up". Five minutes ago, >jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no >active connection between the conserver and the terminal server for the >"down" ports. ^Eco just comes back with "line is still down". > >We are using a Portmaster PM2e. Any help or suggestions would be >appreciated. Thank you. > > >--__--__-- > >Message: 2 >From: "Ernie Oporto" >To: >Subject: RE: lines going "down" >Date: Wed, 28 Nov 2001 10:44:05 -0500 > >This is a multi-part message in MIME format. > >------=_NextPart_000_00C9_01C177F9.9863BD80 >Content-Type: text/plain; > charset="us-ascii" >Content-Transfer-Encoding: 7bit > >We saw a problem this week where the lines would not come up no matter >what. After an hour of coaxing (stoping the daemon and restarting it, >stopping and restarting...) they finally came up. Never went through that >before, and they seem stable since then. Have to keep an eye on this... > >Ernie > > >> -----Original Message----- >> From: users-admin@conserver.com [mailto:users-admin@conserver.com]On >> Behalf Of Jim Gottlieb >> Sent: Tuesday, November 27, 2001 7:22 PM >> To: users@conserver.com >> Subject: lines going "down" >> >> >> Hi all. We were using conserver 7.0.0 for several months, but ports >> seemed to get stuck too often, forcing me to restart the daemon, so I >> upgraded to 7.1.3. Unfortunately, things have been worse under this >> version. More often than not, ports suddenly go "down", and restarting >> the server makes some ports come up and others go down. >> >> Is there some better in-bewteen version I should try? I'm starting to >> get frustrated. >> >> oracle1 down >> pbxp1 down >> sunray1 up >> sunray2 up >> cisco up >> jtsd07 up >> jtsd08 up >> jtsd09 up >> toro up >> shasta down >> tahoe down >> vodavi up >> >> Right now, the four shown "down" should be "up". Five minutes ago, >> jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no >> active connection between the conserver and the terminal server for the >> "down" ports. ^Eco just comes back with "line is still down". >> >> We are using a Portmaster PM2e. Any help or suggestions would be >> appreciated. Thank you. >> >> _______________________________________________ >> users mailing list >> users@conserver.com >> https://www.conserver.com/mailman/listinfo/users >> > > > >--__--__-- > >Message: 3 >Date: Wed, 28 Nov 2001 09:19:00 -0800 >From: David Harris >To: users@conserver.com >Cc: zonker@gnac.com >Subject: Re: lines going "down" > > I've seen a similar scenario in one particular lab, using a >Cisco 3640 with NM-32A cards. I don't think this is a brand >issue. I merely offer it as another clue.... > > When we see the failure, we typically see 8 ports in a group >go down...all 8 in a modulo-8 group. (i.e. 1-8, 17-24, etc.) >All of the affected lines are run by the same OCTART chip. > > While I could point to a failure in IOS for this (which >would only be circumstantial and unsupported by fact), I >actually have another working theory, based on looking at >the devices attached... > > In these cases, there was usually a network interruption >between the conserver and the console server. This could be >a switch/router failure in the network, or a forced reboot >of the conserver host without a polite shutdown...and the >devices showing 'down' were what I call 'quiet hosts'. (A >quiet host is a device that only replies when you talk to >it...it doesn't usually offer any log traffic, time stamps, >etc. to the logs unless someone is typing to it.) > > In the case of a network break like this, the TCP session >to all of the ports (from Conserver to the Console Server) >don't get cleared out when the connectivity failure occurs! >Since the host doesn't generate any traffic on the serial >port, the console server never tries to send traffic to the >conserver host, and the console server leaves the session >open, thinking that the conserver host is just idle. The >root cause here is that the TCP FIN sequence never occured. >So, when you restart your Conserver, and it tries to then >connect to these ports on the console server, the console >server tells the conserver that the TCP port is busy (since >the console server still thinks the old session is still >there and idle...) > > In these cases, our cure has been to log into the console >server, and reset each affected line, one by one. This will >blow away the (already broken) TCP session, and allow you to >either restart your conserver, or just force open each of >the lines that were down. > > While this doesn't happen too often in the data centers, >I have seen this in some of the remote locations. Maybe >that's another good argument for having a distributed >Conserver deployment, and putting a logging host 'closer' >to the console servers? :-) > > Regards, > > -Z- http://www.conserver.com/consoles/breakoff.html > > > > > >--__--__-- > >_______________________________________________ >users mailing list >users@conserver.com >https://www.conserver.com/mailman/listinfo/users > > >End of users Digest From lwoods@email.unc.edu Thu Nov 29 11:47:22 2001 Received: from smtpsrv1.isis.unc.edu (smtpsrv1.isis.unc.edu [152.2.1.138]) by underdog.stansell.org (8.12.1/8.12.1) with ESMTP id fATJlLxM025511 for ; Thu, 29 Nov 2001 11:47:21 -0800 (PST) Received: from SYSTEMS-GEIFON (geifon.oit.unc.edu [152.2.22.173]) by smtpsrv1.isis.unc.edu (8.9.3/8.9.1) with ESMTP id OAA07044; Thu, 29 Nov 2001 14:47:13 -0500 (EST) Date: Thu, 29 Nov 2001 14:47:14 -0500 From: "Lorris J. Woods" Reply-To: "Lorris J. Woods" To: alfcab , users@conserver.com Subject: Re: lines going "down" PM2e Message-ID: <2022886789.1007045234@SYSTEMS-GEIFON> In-Reply-To: <200111282018.fASKImi08885@mail1.magma.ca> X-Mailer: Mulberry/2.0.0 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: alfcab I have a setup using PM2E, but I cannot get conserver.passwd and conserver.cf right ttya is the only one I can get to work. BTW my PM2E is coming off a second NIC card and I use a hub for all the PM2E connections. in your what is unix1, unix2, cisco, & cisco2,... routers ???? --On Wednesday, November 28, 2001 3:19 PM -0500 alfcab wrote: > I have the same setup working as follows : > > > \ internal net / > -------------- > | TCP > V > +------------+ > | solarisx86 | > +------------+ > | TCP crossover > V > +------------+ > | portmaster |-------------------------+ > +------------+ | | | > | Serial | Serial | Serial | Serial > V V V V > +-------+ +-------+ +-------+ +--------+ > | unix1 | | unix2 | | cisco | | cisco2 | > +-------+ +-------+ +-------+ +--------+ > > Each port on portmaster PM2e configured as follows : > > set cd on > set extended on > set modem > set cd off > set speed 1 9600 > set speed 2 9600 > set speed 3 9600 > set idletime 0 > set hangup off > set prompt : > set device /dev/network > set service_device telnet > set service_login telnet > > The entry in conserver.cf is as follows : > > LOGDIR=/var/consoles > > unix1:!portmaster::& > unix2:!portmaster::& > cisco:!portmaster::& > cisco2:!portmaster::& > > As well the cabling is important, you don't want to send the > break to sparc gear if the portmaster is resetted for any reason. > I'm using standard cisco serial connectors on both ends pm2e and > sparc gear with straight trough cables, for the cisco gear we use > roll-overs ( they come with the cisco stuff ). > > FYI I tried linux first as a conserver server, and had the same > behaviour you are experiencing, I decided to try solaris on x86 > and voila my hangups on active connections dissapeared, maybe > it's something related to specific's in OS's had no time to > troubleshoot, just had to get it working in a reliable way ( no > hangups ). > > Alfredo Cabrera > > > > >> To: users@conserver.com >> Sender: users-admin@conserver.com >> Errors-To: users-admin@conserver.com >> X-BeenThere: users@conserver.com >> X-Mailman-Version: 2.0.5 >> Precedence: bulk >> List-Help: >> List-Post: >> List-Subscribe: , > >> List-Id: Conserver Users >> List-Unsubscribe: , > >> List-Archive: >> Message-Id: <20011128200007.160853C7CE@underdog.stansell.org> >> Date: Wed, 28 Nov 2001 12:00:07 -0800 (PST) >> Content-Length: 11409 >> >> Send users mailing list submissions to >> users@conserver.com >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.conserver.com/mailman/listinfo/users >> or, via email, send a message with subject or body 'help' to >> users-request@conserver.com >> >> You can reach the person managing the list at >> users-admin@conserver.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of users digest..." >> >> >> Today's Topics: >> >> 1. lines going "down" (Jim Gottlieb) >> 2. RE: lines going "down" (Ernie Oporto) >> 3. Re: lines going "down" (David Harris) >> >> --__--__-- >> >> Message: 1 >> Date: Tue, 27 Nov 2001 16:21:45 -0800 >> From: Jim Gottlieb >> To: users@conserver.com >> Subject: lines going "down" >> >> Hi all. We were using conserver 7.0.0 for several months, but ports >> seemed to get stuck too often, forcing me to restart the daemon, so I >> upgraded to 7.1.3. Unfortunately, things have been worse under this >> version. More often than not, ports suddenly go "down", and restarting >> the server makes some ports come up and others go down. >> >> Is there some better in-bewteen version I should try? I'm starting to >> get frustrated. >> >> oracle1 down >> pbxp1 down >> sunray1 up >> sunray2 up >> cisco up >> jtsd07 up >> jtsd08 up >> jtsd09 up >> toro up >> shasta down >> tahoe down >> vodavi up >> >> Right now, the four shown "down" should be "up". Five minutes ago, >> jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no >> active connection between the conserver and the terminal server for the >> "down" ports. ^Eco just comes back with "line is still down". >> >> We are using a Portmaster PM2e. Any help or suggestions would be >> appreciated. Thank you. >> >> >> --__--__-- >> >> Message: 2 >> From: "Ernie Oporto" >> To: >> Subject: RE: lines going "down" >> Date: Wed, 28 Nov 2001 10:44:05 -0500 >> >> This is a multi-part message in MIME format. >> >> ------=_NextPart_000_00C9_01C177F9.9863BD80 >> Content-Type: text/plain; >> charset="us-ascii" >> Content-Transfer-Encoding: 7bit >> >> We saw a problem this week where the lines would not come up no matter >> what. After an hour of coaxing (stoping the daemon and restarting it, >> stopping and restarting...) they finally came up. Never went through >> that before, and they seem stable since then. Have to keep an eye on >> this... >> >> Ernie >> >> >>> -----Original Message----- >>> From: users-admin@conserver.com [mailto:users-admin@conserver.com]On >>> Behalf Of Jim Gottlieb >>> Sent: Tuesday, November 27, 2001 7:22 PM >>> To: users@conserver.com >>> Subject: lines going "down" >>> >>> >>> Hi all. We were using conserver 7.0.0 for several months, but ports >>> seemed to get stuck too often, forcing me to restart the daemon, so I >>> upgraded to 7.1.3. Unfortunately, things have been worse under this >>> version. More often than not, ports suddenly go "down", and restarting >>> the server makes some ports come up and others go down. >>> >>> Is there some better in-bewteen version I should try? I'm starting to >>> get frustrated. >>> >>> oracle1 down >>> pbxp1 down >>> sunray1 up >>> sunray2 up >>> cisco up >>> jtsd07 up >>> jtsd08 up >>> jtsd09 up >>> toro up >>> shasta down >>> tahoe down >>> vodavi up >>> >>> Right now, the four shown "down" should be "up". Five minutes ago, >>> jtsd0[789] showed "down" for no explicable reason. 'netstat' shows no >>> active connection between the conserver and the terminal server for the >>> "down" ports. ^Eco just comes back with "line is still down". >>> >>> We are using a Portmaster PM2e. Any help or suggestions would be >>> appreciated. Thank you. >>> >>> _______________________________________________ >>> users mailing list >>> users@conserver.com >>> https://www.conserver.com/mailman/listinfo/users >>> >> > >> >> >> --__--__-- >> >> Message: 3 >> Date: Wed, 28 Nov 2001 09:19:00 -0800 >> From: David Harris >> To: users@conserver.com >> Cc: zonker@gnac.com >> Subject: Re: lines going "down" >> >> I've seen a similar scenario in one particular lab, using a >> Cisco 3640 with NM-32A cards. I don't think this is a brand >> issue. I merely offer it as another clue.... >> >> When we see the failure, we typically see 8 ports in a group >> go down...all 8 in a modulo-8 group. (i.e. 1-8, 17-24, etc.) >> All of the affected lines are run by the same OCTART chip. >> >> While I could point to a failure in IOS for this (which >> would only be circumstantial and unsupported by fact), I >> actually have another working theory, based on looking at >> the devices attached... >> >> In these cases, there was usually a network interruption >> between the conserver and the console server. This could be >> a switch/router failure in the network, or a forced reboot >> of the conserver host without a polite shutdown...and the >> devices showing 'down' were what I call 'quiet hosts'. (A >> quiet host is a device that only replies when you talk to >> it...it doesn't usually offer any log traffic, time stamps, >> etc. to the logs unless someone is typing to it.) >> >> In the case of a network break like this, the TCP session >> to all of the ports (from Conserver to the Console Server) >> don't get cleared out when the connectivity failure occurs! >> Since the host doesn't generate any traffic on the serial >> port, the console server never tries to send traffic to the >> conserver host, and the console server leaves the session >> open, thinking that the conserver host is just idle. The >> root cause here is that the TCP FIN sequence never occured. >> So, when you restart your Conserver, and it tries to then >> connect to these ports on the console server, the console >> server tells the conserver that the TCP port is busy (since >> the console server still thinks the old session is still >> there and idle...) >> >> In these cases, our cure has been to log into the console >> server, and reset each affected line, one by one. This will >> blow away the (already broken) TCP session, and allow you to >> either restart your conserver, or just force open each of >> the lines that were down. >> >> While this doesn't happen too often in the data centers, >> I have seen this in some of the remote locations. Maybe >> that's another good argument for having a distributed >> Conserver deployment, and putting a logging host 'closer' >> to the console servers? :-) >> >> Regards, >> >> -Z- http://www.conserver.com/consoles/breakoff.html >> >> >> >> >> >> --__--__-- >> >> _______________________________________________ >> users mailing list >> users@conserver.com >> https://www.conserver.com/mailman/listinfo/users >> >> >> End of users Digest > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users Thanx Much, Lorris