DComTalk.com

Hi,

Does anyone know if the SNMP agent in the Nortel Baystack 450-24T is
single or multi-threaded? That is, can multiple NMS applications on
different systems (i.e. different SNMP sessions) simultaneously and
reliably poll the switch with GET_BULK_REQUEST, for example?

Many thanks, Gary.

Gary wrote:

Hi,

Does anyone know if the SNMP agent in the Nortel Baystack 450-24T is
single or multi-threaded? That is, can multiple NMS applications on
different systems (i.e. different SNMP sessions) simultaneously and
reliably poll the switch with GET_BULK_REQUEST, for example?

Many thanks, Gary.

I can't say if the agent is multi-threaded,but I use multiple Nortel
NMS tools to monitor Baystack 450/470/8600 switches. No problems with
SNMP hanging.

These switches OS are compliled as somewhat a real-time operating system,
They are not really like a multi-user OS even though they are running
multiple processes. Really depends on platform, but most of these switches
do consume CPU resources when having to manage tasks and traffic and not
just forwarding traffic through the switch which depending on what is is and
intense could impact the performance of the switch.

It is best to limit duration of SNMP or even pings to any interface on your
switch, only poll MIBs that you need to monitor, do not do a complete walk
through all MIB's is best.


<rick.harris@scdmv.net> wrote in message
news:1111068281.532224.28100@z14g2000cwz.googlegroups.com...

Gary wrote:
Hi,

Does anyone know if the SNMP agent in the Nortel Baystack 450-24T is
single or multi-threaded? That is, can multiple NMS applications on
different systems (i.e. different SNMP sessions) simultaneously and
reliably poll the switch with GET_BULK_REQUEST, for example?

Many thanks, Gary.

I can't say if the agent is multi-threaded,but I use multiple Nortel
NMS tools to monitor Baystack 450/470/8600 switches. No problems with
SNMP hanging.

In article <two_d.38613$5T6.31716@bignews4.bellsouth.net>,
MC <mwclarke1@yahoo.com> wrote:
:These switches OS are compliled as somewhat a real-time operating system,

:It is best to limit duration of SNMP or even pings to any interface on your
:switch, only poll MIBs that you need to monitor, do not do a complete walk
:through all MIB's is best.

Unfortunately the Baystack 450's have a bug in the mac to ether table
handling. If you request information about a particular MAC, you might
or might not get information returned. If you walk progressively larger
supersets, the item may or may not appear. In practice, the only way
to be sure of getting the entry for the MAC you are interested in is to
walk the entire subtree: if you attempt to narrow it down at all,
then the last entry in the table will be missed more often than not.
(This applies for SNMPv1; I have no tried with BULK GET.)
--
This signature intentionally left... Oh, darn!