| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1766.1 | How do you control SNMP settings? | SNOFS2::FUNGSIONGMA | | Fri Aug 04 1995 06:40 | 8 |
| RE: -1
Well, then, is there any later driver available? How do we control
the settings of the SNMP agent?
Thanks,
Fung Siong
|
| 1766.2 | | NETCAD::STEFANI | Machines to humanize | Mon Aug 07 1995 19:39 | 27 |
| re: .0 and .1
You should pull the FEKIT240.ZIP kit off the BBS or our other
distribution points. This includes a much more current driver. The
packets in/packets out counters that are part of MIB-II (RFC1213) are
implemented in Novell's SNMP.NLM and TCPIP.NLM modules and you don't
need to do anything special on the DEFEA-side to access that data
remotely.
Make sure the customer is using the latest SNMP modules (check Novell tech
support, CompuServe, or their ftp.novell.com FTP site) for their
version of the OS and follow the accompanying documentation for how to
run it.
We wrote an additional SNMP "co-agent" (DECSNMP.NLM) that supports
both DEFEA and DEFPA and implements RFC 1512 (FDDI SNMP MIB) and DEC
Extended MIB (v2.9). I haven't created a newer DEFEA kit with this SW,
but it's available in the DEFPA FPKIT242.ZIP kit off the BBS in the
\NOVELL\SNMP directory. There are instructions there on how to load
the module.
Again, the DECSNMP.NLM module supports these extended MIBs. For
standard MIB-II counters, the customer should simply use the latest
Novell-supplied modules and not bother with DECSNMP.NLM.
Regards,
Larry
|
| 1766.3 | FEKIT240.ZIP -> Hangs server | SNOFS2::FUNGSIONGMA | | Wed Oct 18 1995 05:11 | 16 |
| RE: .2
Customer downloaded the file from the BBS and installed the driver,
but
it came up w/ the following info and then the server hangs:
Firmware Rev 2.2
Hardware Rev 2.0
Chip Rev 2.0
Anything that we can look into? Could it be because he installed
incorrect driver, say 4.x driver on 3.12 server?
Thanks for any info,
Fung Siong Ma
|
| 1766.4 | | NETCAD::STEFANI | Machines to humanize | Wed Oct 18 1995 11:32 | 16 |
| >> Firmware Rev 2.2
>> Hardware Rev 2.0
>> Chip Rev 2.0
You should upgrade the firmware on your DEFEA. It's two revisions
behind. Use the KALI::PCDRIVERS:[DEFEA.RELEASE]FEFW240.ZIP kit and
upgrade your firmware to v2.46.
>>Anything that we can look into? Could it be because he installed
>> incorrect driver, say 4.x driver on 3.12 server?
There's only one ODI server driver. It works on both NetWare 4.X and
3.1X per the on-line instructions in \NOVELL\SRVODI\README.TXT and
\NOVELL\SRVODI\3_1X\README.TXT.
/l
|
| 1766.5 | Hardware config problem | SNOFS2::MOOREADRIAN | | Thu Oct 19 1995 22:15 | 16 |
| Thanks for the info.
Client resolved problem onsite as an IRQ conflict which allowed the
server to load. OpenView pulls all statistics for the card OK now, due
to the updated FEKIT240.ZIP as well.
I made the client aware of the firmware upgrade. He doesn't want to
stir the pot at the moment though.
What should we recommend to clients - that they get all upgrades
possible whenever they are available? I know this is sound advice but
are there any pitfalls with this?
Regards,
Adrian
|
| 1766.6 | | NETCAD::STEFANI | Machines to humanize | Mon Oct 23 1995 09:19 | 17 |
| >>What should we recommend to clients - that they get all upgrades
>>possible whenever they are available? I know this is sound advice but
>>are there any pitfalls with this?
No pitfalls that I'm aware of. The most important fix in the latest
DEFEA firmware is that it prevents the adapter from halting under
receive overrun (heavy load) conditions. On even a very busy network,
if the end station (workstation or server with DEFEA installed) is
keeping up, you won't see a problem. However, the Digital UNIX and
OpenVMS system folks have seen the crashing, probably because of the
increased ability of Alpha systems to drive I/O very hard.
If the customer has scheduled downtime, I'd suggest upgrading the
firmware at that time. From the DOS prompt it takes all of about two
minutes to complete the operation.
/l
|