Another observation - if the router also has a LAN interface (Ethernet or
whatever) then the LAN interface is likely to be reachable whether on
primary or ISDN backup. With this in mind it is not always necessary to
define a loopback to achieve the desired results. As others have noted we
also unmanage the BRI interfaces so that the icons reflect "normal" status.
I believe you said that these were Cisco routers. If so, I recommend adding
"snmp-server enable traps isdn" to the configuration. These traps spell out
in plain English ISDN status - much more user friendly as well as
informative for the operations staff than just the BRI up/down traps.
Blaine Owens
Eastman Chemical Company
Phone - (423)-229-3579
Fax - (423)-229-1188
bowens@eastman.com
> -----Original Message-----
> From: Todd E. Lewis [SMTP:telewis@PROVIDENTBANKMD.COM]
> Sent: Tuesday, May 18, 1999 4:30 PM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Re: Ruleset for Netview NT 5.1.1
>
> I'm not really a router guy so what does the loopback port have to do with
> the BRI port ? According to our router guy, loopback is setup for DLSW
> (ATM Machine purposes). He's not sure either. Thanks.
>
>
> >>> Steve Francis <steve.francis@COMMSERV.UCSB.EDU> 05/18 2:15 PM >>>
> Probably an easier way to manage this situation is not to rely on rules.
>
> What I would do is create a loopback interface in the routers (always a
> good idea for a variety of reasons anyway). Manage the loopback and
> serial interfaces, but unmanage the ISDN interface.
>
> Then in normal state, your router will be green. If the serial interface
> dies and the ISDN works, it will be yellow (with a red serial and green
> loopback). If serial and ISDN fail, you get a red router.
>
> This is probably the behaviour you want.
>
> "Todd E. Lewis" wrote:
>
> > I guess what I mean is: when the 56kb line drops (thus turning the
> serial interface red) the BRIO port should turn from red to green. Right
> now netview is telling all the time that my BRIO ports are down when in
> fact they should be down unless the 56kb link dies. Maybe the ruleset
> needs to written in TEC. I'm not sure. I hope this is a little clearer.
> >
> > >>> James Shanks <James_Shanks@TIVOLI.COM> 05/18 12:23 PM >>>
> > Todd -
> >
> > Please elaborate more on what you are trying to accomplish.
> >
> > (1) What is your ruleset supposed to do? The scenario is not obvious
> to
> > me.
> >
> > (2) How do you propose to write the ruleset when there is no ruleset
> editor
> > on NT?
> >
> > James Shanks
> > Tivoli (NetView for UNIX) L3 Support
> >
> > "Todd E. Lewis" <telewis@PROVIDENTBANKMD.COM> on 05/18/99 11:44:42 AM
> >
> > Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> > NetView <NV-L@UCSBVM.UCSB.EDU>
> >
> > To: NV-L@UCSBVM.UCSB.EDU
> > cc: (bcc: James Shanks/Tivoli Systems)
> > Subject: Ruleset for Netview NT 5.1.1
> >
> > We have cisco 2503 routers deployed in all of our bank branches. There's
> to
> > serial ports and one BRIO (ISDN Dial-up port).
> >
> > The serial port connects to a 56kb frame relay link. So a normal status
> of
> > the router should show serial port up and BRIO down. When the 56kb link
> > goes down the BRIO should dial-up to get the branch back online.
> >
> > I need help with writing a rule set that will cover the above scenerio.
> Any
> > help would be much appreciated, since I'm very green at writing rule
> sets.
|