HP3000-L Archives

August 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mike Church <[log in to unmask]>
Reply To:
Mike Church <[log in to unmask]>
Date:
Sat, 26 Aug 2000 11:31:58 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (152 lines)
Just a thought...

Ensure that the router is defined as a gateway via the NMMGR.
You probably have already done this, but it is just an idea.

example

NMMGR/3000 (B.06.00) #158  Neighbor Gateway Reachable Networks
Data: Y
When Data Flag is "N", press "Save Data" to create the data record.

Command:

Path:  NETXPORT.NI.LAN1.INTERNET.WANGW1


[B 190.182 001.001]  Neighbor Gateway IP Internet Address

                        Configured Reachable Networks

         IP Network Address      IP Mask (Optional)    Hops
         [@                ]     [               ]     [3    ]
         [                 ]     [               ]     [     ]
         [                 ]     [               ]     [     ]
         [                 ]     [               ]     [     ]


Next, check to see if your HP e3k IP address is in the routing table of the
Cisco router.
Cisco can be set up to be rather dynamic, and can drop an entry in a routing
table if it is reset (or loses power - or some one accidentally resets it).

If you have a firewall/DNS server, check the "tables" are correct there too.

We have had problems with that too.

If you are passing through a switch (Cisco? or UB?) you want to check the
port config on the
switch (or maybe change ports).  BTW, check the cable from the 3k to the
switch, if you are
like us, it may run along/under the floor and some one may have done a tap
dance on the cable.

We have had problems similar to this on two occasions.

  1) our local carrier (GTE) made a configuration change,
     wiped out the Cisco router config, and did not add IP for e3k back
in...

  2) the second time, the router itself was failing, replaced it and all
worked well.

A good product is NetXray by Network General (think they have been purchased

by Network Associates, or someone), used it in the past. Cost is around 1k,
runs on a PC or laptop. Good graphical interface, great for monitoring.

btw...

If you run a mixture of NT/Novell on you LAN/WAN, be careful.  IPX can be a
bear on
network traffic and can cause a big bottle neck.

JetDirects can too... If you are using only TCP/IP, remember to disable the
JDs for
things like Apple Talk and IPX if they are not needed.  We have shaved a lot
of band width
this way...

Hope this helps, and let me know if I was close or off base.

I love technical mysteries...

;-)


mc


Mike Church
Technical Support Manager
Information Services
Our Lady of Bellefonte Hospital
Saint Christopher Drive
Ashland, Kentucky 41101
-----------------------------------
Phone : (606)833-3727
Pager : (606)327-0965
  Fax : (606)833-3342
-----------------------------------
   Alternate e-mail : [log in to unmask]
-----------------------------------
MY URL: http://members.tripod.com/mike_church/
OLBH: http://www.olbh.com
-----------------------------------
Daily Quote: Few are those who see with their own eyes and feel with their
own hearts. - Albert Einstein


-----Original Message-----
From: Ken Nutsford [mailto:[log in to unmask]]
Sent: Saturday, August 26, 2000 10:24 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] network problems


Donna,

What is the sniffer program you are using on the HP e3000?

Ken Nutsford

-------------Original Message-----------------

From:   Donna Garverick, INTERNET:[log in to unmask]
To:     [unknown], INTERNET:[log in to unmask]

Date:   25-08-00 14:17

RE:     Re: [HP3000-L] network problems


Bruce Toback wrote:

> Have you tried running nettool/resource?

oh yes...

> I have seen at least one case
> similar to this where the outbound buffer pool was too small. The system
> would sometimes not recover gracefully from an overflow condition.
> Perhaps you could monitor network resource usage closely and see if
> you're running up against one limit or another.

so far we've not seen anything unusual via nettool.  we did see something
interesting yesterday once we put a sniffer on.  we were pinging from one of
the two 'problem' mpe systems to the router.  the ping (from the 3000) would
eventually stall yet on the sniffer you could see that packets were still
being received and answered.  in the words of our sr. network engineer: 'it
appears that LAYER 2 (MAC) communications continues until the target number
of
frames has been transmitted.  At the application layer, communications is
lost
and the total send/receive count is under reported.'             - d 'off to
call hp'

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<

ATOM RSS1 RSS2