--LAA09692.864584115/snuffy.sandisk.com
**********************************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************
The original message was received at Sat, 24 May 1997 23:09:34 -0700 (PDT)
from bert [89.0.0.247]
----- The following addresses had transient non-fatal errors -----
jlorenz@elmo
(expanded from: <jlorenz@snuffy>)
----- Transcript of session follows -----
jlorenz@elmo... Deferred: Connection reset by elmo.sandisk.com
Warning: message still undelivered after 12 hours
Will keep trying until message is 5 days old
--LAA09692.864584115/snuffy.sandisk.com
Content-Type: message/delivery-status
Reporting-MTA: dns; snuffy.sandisk.com
Arrival-Date: Sat, 24 May 1997 23:09:34 -0700 (PDT)
Final-Recipient: RFC822; <jlorenz@snuffy>
X-Actual-Recipient: RFC822; jlorenz@elmo.sandisk.com
Action: delayed
Status: 4.5.0
Remote-MTA: DNS; elmo.sandisk.com
Diagnostic-Code: SMTP;
Last-Attempt-Date: Sun, 25 May 1997 11:15:15 -0700 (PDT)
Will-Retry-Until: Thu, 29 May 1997 23:09:34 -0700 (PDT)
--LAA09692.864584115/snuffy.sandisk.com
Content-Type: message/rfc822
Return-Path: <portmaster-users@livingston.com>
Received: from bert (bert [89.0.0.247])
by snuffy.sandisk.com (8.8.4/8.8.4) with SMTP
id XAA08084 for <jlorenz@snuffy>; Sat, 24 May 1997 23:09:34 -0700 (PDT)
From: portmaster-users@livingston.com
Received: from cc:Mail by bert
id AA864540615; Sat, 24 May 97 23:10:05 PST
Date: Sat, 24 May 97 23:10:05 PST
Encoding: 360 Text, 19 Text
Message-Id: <9704248645.AA864540615@bert>
To: portmaster-users-digest@livingston.com
Subject: Portmaster Users Digest V97 #139
Portmaster Users Digest Saturday, 24 May 1997 Volume 97 : Number 139
Re: US West -> BRI hunting feature
Re: Some Advice. (fwd)
Re: BGP
Re: BGP
WTB PM2...
ISDN Office router problem
Cisco 2501 <> IRX-114
Turn off VFC on Zoom
Port 40 on PM2eR
Re: BGP
Re: BGP
----------------------------------------------------------------------
From: "David S. Kenzik" <dsk1@one.net>
Date: Sat, 24 May 1997 02:32:41 -0400 (EDT)
Subject: Re: US West -> BRI hunting feature
On Fri, 23 May 1997, Sherwood Pekelo wrote:
: A combination is in effect... tariffing in many locales precludes going
: any further in most cases... otherwise, if the groups are not on the same
: switch then I believe you can't hunt across them... say a 455-xxxx number
: CT1 on a DMS-100 and a 456-xxxx PRI on a GTD-5... so our telco says they
: can't program the switches to hunt/call-forward across switches....
:
: Personally, I think it is/should be technically possible, but perhaps it's
: too much of a programming pain to do?
Well, we were told it couldn't be done when we converted from analog
to T1 for incoming calls.
After 6 months of rants from Bell that it couldn't be done, we now
have it.
We have about 30 trunks scattered around the local calling area, and
they all hunt from a single number. I believe we use a total of 10
switches according to our last report (all flowing into our wonderful
PM3's that hangup randomly on our USR userbase *COUGH*.)
I'm not sure what specific hardware/software our "Bell" uses, but
believe me, it was a pain the _ass_ to get them to sell us the
service.
The whole process took about 6 months.
(Of course, they are our largest regional competitor.) :)
- ---
David S. Kenzik
OneNet Communications, Inc.
------------------------------
From: Chris Gauthier <chris@kinderfeld.icenter.net>
Date: Sat, 24 May 1997 10:19:21 -0500 (CDT)
Subject: Re: Some Advice. (fwd)
On Thu, 22 May 1997, MegaZone wrote:
> You're probably better comparing it to the IRX family, or even the OR-SYNC
> models.
>
Ok, I gotcha. There probably is very little use in getting such a low-end
router to begin with.
/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/
Chris Gauthier - Administration, Development chris@icenter.net
IC Enternet - Winnipeg's Premier ISP (204)958-9400 V o i c e
17 St. Mary's Rd. - Winnipeg, MB, R2H 1H2 (204)958-9411 F a x
- -- If you think the problem is complicated now, just wait until we've got
it solved.
/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/=/
------------------------------
From: Ian McLaughlin <ian@okjunc.junction.net>
Date: Sat, 24 May 1997 08:31:52 -0700 (PDT)
Subject: Re: BGP
On Fri, 23 May 1997, Jon Lewis wrote:
> On Fri, 23 May 1997, Fernando da Silveira Montenegro wrote:
>
> > It seems that a Cisco guy (Sam Hasabi, if I'm not mistaken) has a new book
>
> That's Halabi...I think. He also wrote a BGP Case Study that's probably
> worth reading...its available in ps and possible html format from cisco.
I picked up "Internet Routing Architectures" by Bassam Halabi, Cisco
Press/New Riders, ISBN 1-56205-652-2 last week. Just about finished it.
A very informative book about BGB. Slanted towards the Cisco
implementation (obviously), but it's taught me a whole bunch about BGP,
which we're going to have to implement here shortly. I recommend it to
anyone trying to learn BGP.
___ __ __ __ _ _ _ _
|_ _|__ _ _ _ | \/ / _| | __ _ _ _ __ _| |_ | (_)_ _ Okanagan
| |/ _` | ' \ | |\/| \__| |_/ _` | | / _` | ' \| | | ' \ Internet
|___\__,_|_||_| |_| |_| |___\__,_|___\__, |_||_|_|_|_||_| Junction
Network Operations Centre |___/ Phone +1 (604) 549-1036
------------------------------
From: "Damien T." <damient@livewire.comsec.net>
Date: Sat, 24 May 1997 11:09:34 -0700 (PDT)
Subject: Re: BGP
At 04:12 PM 5/23/97 -0300, montenegro@nutec.com.br wrote:
>If you're looking for info on BGP, you might want to check these
>references:
>- www.boardwatch.com has some tutorials by Avi Freedman, who *KNOWS* this
>stuff inside and out. He posts periodically to inet-access, and has a
>regular column at Boardwatch. May's issue is about multihoming and BGP :-)
Yep, I just read this article recently.
>- "Routing in the Internet", by Christian Huitema, former president of the
>IAB. I don't have the ISBN handy, but all major online bookstores (amazon,
>bookpool, b&N, ...) should carry it.
Bought this book about a year and a half ago. Learned everything I never
wanted to know about RIP from it <g>! But - the BGP section seemed a lot
more theoretical. I'm one of those people who would learn more from seeing
how someone else's router were configured, along with an explaination of
why, than I would from tons of theory. I guess I've the victim of far too
much on-the-job training <g>!
>It seems that a Cisco guy (Sam Hasabi, if I'm not mistaken) has a new book
>out on Internet routing, and it is sure to cover BGP. Haven't read it yet
>though, so I don't have an opinion yet.
Hmm. I'll have to look for this one.
>Of course, there's always the RFCs...
Uh, yeah. I'm interested in CONFIGURING a router for BGP, not BUILDING one!
<g>!
>Hope this helps!
Thank you, Fernando.
Damien
------------------------------
From: Jeff Tuttle <jtuttle@sanantonio.net>
Date: Sat, 24 May 1997 16:20:50 -0500
Subject: WTB PM2...
Looking for a used PM2
Plz email me directly
Thanks,
Jeff
------------------------------
From: James Courtier-Dutton <James@superbug.demon.co.uk>
Date: Sun, 25 May 97 00:11:39
Subject: ISDN Office router problem
- -----BEGIN PGP SIGNED MESSAGE-----
Hello
I have a customer with 2 office routers. 1 in US and 1 in England
I have the dial on demand locations working fine.
If England calls US all is fine.
If US calls England all is fine for 1 min, then the England end sends a LCP
disconnect request and the
Line drops. Then imediately the England end dials up the US end and all is then
fine. Idle timeout set to 2
mins both ends. US has ComOS 3.4.2, England has ComOS 3.5. Is there a good
reason for this problem. I
saw some bug fix in 3.5 regarding ISDN forcing idle in some situations. If this
is what is happening I will get
them to upgrade.
Also, How safe is it to upgrade ComOS over the ISDN link. And if so, is it wise
for me to set up a network user
on their OR so that I can dial in and do the work. I have had major issues about
upgrading IRX over leased
line link. I don't want that to happen to the US one.
Thanks
James
My PGP Public key is at http://www.superbug.demon.co.uk/public.asc
PGP Public Key Fingerprint = 9C A0 3E 42 E2 C8 39 E1 37 0A 10 8F E6 69 86 89
- -----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: cp850
iQCVAwUBM4eDu0SAh7t1S1t5AQFbngP/fpLckDQIqfFyWi88ZWuEATcvl2E312P7
yfUrF2oWcy9ubWpbnLJKTpv9DY6HUY5aQiafNcx3rEFs+fBhoJE/JvkpmuwZNHM9
qFxVCjUkzcsgfs/prQdBdsPcIbBkreQ17ds369jURPA2x3copoaf/FfwBjI42Dm6
DbbY6M2ceOY=
=ArKx
- -----END PGP SIGNATURE-----
------------------------------
From: Irve Towers <irvet@knight-hub.com>
Date: Sat, 24 May 1997 20:43:11 -0700
Subject: Cisco 2501 <> IRX-114
Can someone please shed some light on this.
- ---------------------------
| Serial IP 205.177.169.130 CISCO 2501
| NM 255.255.255.224
- ---------------------------
DLCI 300 DLCI 301
| |
| \ DLCI 204
| \----------------------------
| | IP 205.177.169.131 LIVINGSTON IRX-114
| | NM 255.255.255.224
| ----------------------------
| / DLCI 205
| /
| |
DLCI 500 DLCI 501
- ---------------------------
| Serial IP 205.177.169.129 CISCO 2501
| NM 255.255.255.224
- ---------------------------
I'm at home with the Livingston portion but need assistance on what needs
to be done with the Cisco 2501's. What series of commands need to be
executed to set the 2501 serial interfaces up to support the two DLCI. The
.128 network is our frame cloud and each Cisco will be routed a class-C.
The customer doesn't know how to setup the Cisco and could use some help.
TIA
------------------------------
From: Luther Keal <dkeal@primenet.com>
Date: Sat, 24 May 1997 17:39:35 -0700 (MST)
Subject: Turn off VFC on Zoom
I've got a Zoom VFP 28.8 modem that will only connect at 14.4. I believe
he is a non-standard protocol, maybe v.fast.
Anyone have an init string to force it to V.34?
Thanks
Dave Keal
SIERRA INTERNET
- ------------------------------------------------------------------------------
-
------------------------------
From: Fraser Campbell <fraser@greynet.net>
Date: Sat, 24 May 1997 22:35:22 -0400 (EDT)
Subject: Port 40 on PM2eR
We have a couple of PM2eR-30s and when we run the raport script on the
detail files from each we used to see a port 40 in the summary. This
month strangely that port is not in the results from the script. Anyone
have any idea what this port is?
*****************************************************************
* Fraser M. Campbell, Hanover, Ontario, Canada N4N 3C4 *
* Email: fraser@greynet.net Phone: (519) 364-6115 *
* URL: http://www.greynet.net/fraser/ *
*****************************************************************
------------------------------
From: "James D. Butt" <jbutt@mwci.net>
Date: Sat, 24 May 1997 22:27:39 -0500 (CDT)
Subject: Re: BGP
>
> >Of course, there's always the RFCs...
>
> Uh, yeah. I'm interested in CONFIGURING a router for BGP, not BUILDING one!
> <g>!
I think that it is very important to understand what you are
implementing. The RFC's are not bad reading in fact I would recommend
reading all the RFC's about all of the protocols you are using....
I will tell you that knowing the RFC will allow you to quickly jump from
one hardware vendors equipment to another...Also when trying to get
things to play nice with each other in multi-vendor networks "knowing"
the protocol can be very important...
- --------------------------------------------------------------------------
James D. Butt 'J.D.'
Network Engineer Voice 319-557-8463
Network Operations Center Fax 319-557-9771
MidWest Communications, Inc. Pager 319-557-6347
241 Main St. noc@mwci.net
Dubuque, IA 52001 jbutt@mwci.net
- --------------------------------------------------------------------------
------------------------------
From: Jake Messinger <jake@ams.com>
Date: Sat, 24 May 1997 22:56:12 -0500 (CDT)
Subject: Re: BGP
On Sat, 24 May 1997, James D. Butt wrote:
> >
> > >Of course, there's always the RFCs...
> >
> > Uh, yeah. I'm interested in CONFIGURING a router for BGP, not BUILDING one!
> > <g>!
>
> I think that it is very important to understand what you are
> implementing. The RFC's are not bad reading in fact I would recommend
> reading all the RFC's about all of the protocols you are using....
It is also important to understand that the RFC's are just that. RFC's.
They are not necessarily the standard. Way back in the olden days, when I
was learning about routing and subnetting, I placed too much faith in the
older RFC's I read, assumeing that they were the "law". They have since
been either superceded, or don't apply anymore.
Id say that it is a good STARTING place but just becuase you read
something in an RFC, does not make it come to pass.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger 713-772-6690 jake@ams.com
Advanced Medical Systems, Inc. jake@uh.edu
9919 S. Gessner #201
Houston, Texas 77071 http://www.ams.com/~jake
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
------------------------------
End of Portmaster Users Digest V97 #139
***************************************
Received: by ccmail from snuffy.sandisk.com
>From owner-portmaster-users-digest@livingston.com
X-Envelope-From: owner-portmaster-users-digest@livingston.com
Received: from sunnyvale.sandisk.com (firewall-user@sunnyvale [89.253.0.2])
by snuffy.sandisk.com (8.8.4/8.8.4) with ESMTP
id XAA08080 for <jlorenz@bert.sandisk.com>; Sat, 24 May 1997 23:09:10 -0700 (PDT)
From: owner-portmaster-users-digest@livingston.com
Received: by sunnyvale.sandisk.com; id XAA02161; Sat, 24 May 1997 23:10:21 -0400 (EDT)
Received: from bast.livingston.com(149.198.247.2) by sunnyvale.sandisk.com via smap (3.2)
id xma002158; Sat, 24 May 97 23:10:00 -0400
Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id XAA12542; Sat, 24 May 1997 23:06:55 -0700 (PDT)
Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id XAA25003; Sat, 24 May 1997 23:00:03 -0700 (PDT)
Date: Sat, 24 May 1997 23:00:03 -0700 (PDT)
Message-Id: <199705250600.XAA25003@server.livingston.com>
To: portmaster-users-digest@livingston.com
Subject: Portmaster Users Digest V97 #139
Reply-To: portmaster-users@livingston.com
Errors-To: owner-portmaster-users-digest@livingston.com
Precedence: bulk
--LAA09692.864584115/snuffy.sandisk.com--