In short, nothing!

I just like to have a loopback address defined coz it tends to be the most
stable thing you have on your router. While physical interfaces may come and
go (change address, NTUs fail) as long as there is at least one other route
to the router you should always be able to get to the loopback interface.

This is particularly true when you're using thngs like RSRB or DLSW in your
case...

Neil Whitehead (x22808)
IT Services (Telecoms)
The Royal Bank of Scotland
Tel: 0131-523 2808
Mobile:07803 501793
e-mail: whitern AT rbos.co DOT uk

> -----Original Message-----
> From: Todd E. Lewis [SMTP:telewis AT PROVIDENTBANKMD DOT COM]
> Sent: Tuesday, May 18, 1999 8:30 PM
> To:   NV-L AT UCSBVM.ucsb DOT edu
> Subject:      Re: Ruleset for Netview NT 5.1.1
>
>
> *** Warning : this message originates from the Internet ****
>
> 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 AT COMMSERV.UCSB DOT 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 AT TIVOLI DOT 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 AT PROVIDENTBANKMD DOT COM> on 05/18/99 11:44:42 AM
> >
> > Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> >       NetView <NV-L AT UCSBVM.UCSB DOT EDU>
> >
> > To:   NV-L AT UCSBVM.UCSB DOT 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.


This e-mail message is confidential and for use by the addressee only.  If the 
message is received by anyone other than the addressee, please return the 
message to the sender by replying to it and then delete the message from your 
computer.

'Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc 
does not accept responsibility for changes made to this message after it was 
sent.'