We also have many ISDN backup links and use Cisco routers. This approach
works for us - 1) we unmanage the ISDN interfaces 2) we turn on the
Cisco ISDN traps so that we are aware of ISDN status. To do this, the
following must be configured on each cisco router in question:
snmp-server enable traps isdn
The cisco router (not sure which IOS is required at minimum) will then
send cisco enterprise specific ISDN traps to our NetView server which we
key on for operator notifications and ISDN status awareness.
Blaine Owens
Eastman Chemical Company
Email - bowens@eastman.com
Phone - (423)229-3579
Fax - (423)229-1188
> -----Original Message-----
> From: Leslie Clark [SMTP:lclark@us.ibm.com]
> Sent: Monday, November 30, 1998 12:24 AM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Re: ping ISDN interface
>
> I recently asked the same question here and the advice was to unmanage
> and
> hide the
> ISDN interfaces. You then monitor whether or not they come up as
> needed by
> monitoring
> the status of devices on the far lan. If it fails to come up, the
> router
> will show Down, and so
> will the remote lan. If it comes up, the router will show Marginal and
> the
> remote lan will
> show up.
>
> I have run into this at the last two sites where I installed Netview.
> I'm
> not entirely satisfied
> with this approach either. Maybe this would be a good forum for
> discussing
> alternatives. I would
> wish for a way to selectively monitor interfaces via SNMP - both for
> those
> that are
> unnumbered, and for some, like ISDN interfaces, that ARE numbered. But
> how
> would
> you identify the interfaces? Is there a consistent identifier, like
> ifType,
> that tells which
> interfaces are ISDN? Does it vary with the vendor? What about
> subinterfaces?
>
> What I am trying to come up with is a way, maybe via collections, to
> quickly identify
> which routers are running on their backup connections, and so need
> attention, and
> also which routers are still running on backup connections even after
> the
> primary
> has come back up. We can only do that if the backup interfaces are
> monitored.
>
> Any thoughts?
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
>
>
>
>
> From: Dimitri Setti@ITFCCRT0 on 27/11/98 08.03
>
>
> To: Discussion of IBM NetView and POLYCENTER Manager on NetView et
> alia
> <NV-L@UCSBVM.UCSB.EDU>
> cc:
> Subject: ping ISDN interface
>
>
> Hi at all.....
> I use Netview 5.0 on Aix 4.2.1.
>
> I have some routers CIsco with interface BRI0 having IP address, that
> I use
> only for backup (when
> serial line go down).
> With Netview I see router's interfaces and their status.
> I have this doubt: if I set managed ISDN interface , nv6 pings it and
> so
> activates this line,
> but I don't want this !!
> In order to not ping ISDN interface, I set BRI interface as unmanaged:
> doing so, I'm not able to locate when this interface go up (Call
> Active)
> (with traps)
> Is there any options in Netview that permits to not ping some
> interface
> card?
>
> In "Netview for windows NT user's guide, (ver 5.0)", on page 8-20 I
> read
> that "netmon daemon
> explicitly ping every IP address by default............To turn off
> explicitly pinging every IP address, select
> OPTIONS..SERVER SETUP..DAEMONS..NETMON DAEMON, then click on Discover
> using
> Spray Ping" .
> I think this option can help me to not ping BRI0 interface, but I use
> Netview6000 on AIX,
> so I don't know where to find this same option. Is it maybe
> "Topology/status polling IP" ? If so, which options
> I must choose? No poll for Status? No poll for Discover New Nodes ? I
> don't
> know..........
>
> Maybe there is some others better solutions for my question,
> I hope someone can help me
>
>
> thanks
>
> dimitri
>
>
>
>
> **********************************************************************
> *
> Dimitri Setti
> Fondo Comune Casse Rurali Trentine
> via Segantini n.18
> 38100 TRENTO
> ITALY
>
> Tel: +39 461 874.111 centralino
> +39 461 874.266 diretto
> Fax: +39 461 874.123
>
> e-mail: Dimitri.Setti@fccrt.it
> **********************************************************************
> *
|