nv-l

RE: ISDN port colour problem through Netview

2001-11-12 01:02:01
Subject: RE: ISDN port colour problem through Netview
From: anand anupam <ananda AT bharatpetroleum DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 12 Nov 2001 11:32:01 +0530
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
Hi Bill / Leslie,

I have put $ before some of the routers having ISDN port in seed file as
suggested by you but is of no help. I am skeptical that this is going to
help in our case because what I believe  this $ is to force a node to use
SNMP for its Admin/Oper status update instead of ICMP ping if it is not
having serial interfaces.

One more thing I wanted to share that in our case  ISDN call can be
initiated from router side only and it can not be initiated from the central
place  where our NetView is sitting. But, again this is the case for all
routers having isdn port as fall up arrangement and NetView treating them
differently.

When I do snmp poll for these pink/red color interface, the output comes
differently. Also, I do not understand why TNV marks it red/Critical when it
is actually in stand by mode?


Regards.....Anupam

-----Original Message-----
From: Bill Evans [mailto:wvevans AT attglobal DOT net]
Sent: Sunday, November 11, 2001 11:42 PM
To: IBM NetView Discussion
Subject: Re: [NV-L] ISDN port colour problem through Netview


I'd like to believe that the system automatically handles admin down but 
we've just put in a number of 6.0.2 NT systems where the admin down were 
discovered as critical.  We added the "$" entry to the seed file and 
they turned pink when we restarted netmon and the GUI and looked.

The reason I'm tentative about the topic is that I didn't follow up on 
the situation and find out why they weren't automatically polled with 
SNMP -- I expected the SNMP poll due to the presence of serial 
interfaces on the box.  It might also be a Unix vs. NT difference.  One 
of these days I'm going to figure out how ATM, Frame Relay and 
Point-to-Point interfaces interact with SNMP polling and if there are 
differences not documented.

It's moot now with 7.1 available but there might be something support 
should have addressed in the area which is bypassed with the forced use 
of SNMP.

Bill

Leslie Clark wrote:

> There might be something to that, but I don't think it should be
> permanent. Even when status-polled with ping, an admin-down
> interface should show as user1. If it were admin-up when first
> discovered, then went admin-down later, it would be red, true. But
> it should switch on the next configuration poll, or demandpoll,
> I think, to user1. If it does not, it might be a case for Support.
> 
> Oh - perhaps it is the Oper status that is the problem. If it is
> Dormant, then regardless of what the Admin status is, it will
> show as down. That is one of the things enhanced in V7.1.
> 
> Cordially,
> 
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
> 
> 
> 
>

>                     Bill Evans

>                     <[email protected]       To:     IBM NetView Discussion
<nv-l AT tkg DOT com> 
>                     obal.net>            cc:

>                     Sent by:             Subject:     Re: [NV-L] ISDN port
colour      
>                     [email protected]        problem through Netview

>                     .com

>

>

>                     11/10/01 04:05

>                     PM

>                     Please respond

>                     to IBM NetView

>                     Discussion

>

>

> 
> 
> 
> Check whether both routers are being polled by SNMP.  If one is polled
> by ICMP and the other by SNMP it could explain the difference.  The
> archives and product manuals explain the details but there are a couple
> ways to force SNMP polling; a "$" entry in the seed file or a "P" in the
> oid_to_type file entry.
> 
> anand anupam wrote:
> 
> 
>>Hi,
>>
>>As you rightly said that backup isdn line with  a status of AdminDown
>>will also be USER1 ( it should not be critical ).
>>
>>But, the problem in our case is  NetView assigns USER1(7) with pink
>>color and Critical(4) with red color for the same situation on different
>>routers.
>>
>>Any idea what could be possible reason and where to look into?
>>
>>
>>Regards,
>>
>>Anupam
>>
>>
>>
>>-----Original Message-----
>>From: Oliver Bruchhaeuser [mailto:oliver.bruchhaeuser AT de.ibm DOT com]
>>Sent: Friday, November 09, 2001 7:13 PM
>>To: IBM NetView Discussion
>>Subject: Re: [NV-L] ISDN port colour problem through Netview
>>
>>
>>Tim,
>>
>>update to NetView 7.1 !
>>In this version the dormant status of ISDN interfaces is managed
>>
> correctly.
> 
>> From the release notes 7.1:
>>
>>Monitor ISDN Backup Interfaces
>>By default, interfaces with an SNMP ifOperStatus of DORMANT are handled
>>as if the status is NORMAL and the icon status color will be NORMAL.
>>However, in the special case of ISDN backup lines, when the status is
>>NORMAL, it usually means the primary line has a problem, and when
>>DORMANT, the primary line is usually okay. In this case the status
>>transitions to UP, and DORMANT might indicate the need for operator
>>intervention.
>>The following features are intended to help operators handle ISDN backup
>>lines:
>>* The status of a backup line in DORMANT state is USER1, otherwise the
>>status is as usual (NORMAL, DOWN). Note that the backup line with a
>>status of AdminDown will also be USER1.
>>* When the status changes to UP (from any state) the event Backup Line is
>>ACTIVE is sent.
>>* When the status transitions to DORMANT (from any state, including
>>AdminDown) the event Backup Line is DORMANT is sent.
>>
>>
>>Kind regards
>>
>>Oliver Bruchhaeuser
>>Tivoli NetView EMEA L2 Support
>>
>>IBM Deutschland GmbH - ITS Tivoli - Dept. 7977 - Hechtsheimer Str. 2 -
>>55131 Mainz - Germany
>>Phone: +49-6131-84-5108 - Fax: +49-6131-84-6585 - email:
>>bruchhae AT de.ibm DOT com
>>
>>Need help with Tivoli Software Products?
>>Ask Tivoli!
>>http://www.tivoli.com/asktivoli (login with your customer account)
>>
>>
>>
>>
> 
>>
>>
>>[email protected]
>>
> 
>>
>>                    its-eu.com              To:
>>nv-l AT tkg DOT com
>>
>>                    Sent by:
>>cc:
>>
> 
>>
>>                    owner-nv-l AT tkg DOT co       Subject:     Re: [NV-L] 
>> ISDN
>>port colour problem through Netview
>>
>>
>>m
>>
> 
>>
>>
> 
>>
>>
> 
>>
>>                    09.11.2001
>>12:55
>>
> 
>>
>>                    Please respond
>>to
>>
> 
>>
>>                    IBM
>>NetView
>>
> 
>>
>>
>>Discussion
>>
> 
>>
>>
> 
>>
>>
> 
>>
>>
>>
>>
>>
>>Hi,
>>
>>so far as I know, all ISDN Interfaces are treated as down when inactive.
>>Pink only shows up when the Port is manually shut down (administratively
>>shutdown)
>>
>>We use a solution, where we catch the ISDN traps to operate a "backup
>>
> icon"
> 
>>which turns red when ISDN becomes active.
>>
>>Gruesse - Best regards
>>
>>Tim Uekermann
>>European Information Management
>>GE CompuNet Computer Distribution
>>Europaring 34-40, 50170 Kerpen, Germany
>>Phone: +49 (0) 22 73/597-7560, Fax: +49 (0) 22 73/597-186, Mobile:
>>01728348119
>>E-Mail : Tim.Uekermann AT gecits-eu DOT com
>>Visit us on the Internet: http://www.gecits-eu.com
>>
>>
>>This email is confidential. If you are not the intended recipient,
>>you must not disclose or use the information contained in it.
>>If you have received this mail in error, please tell us
>>immediately by return email and delete the document.
>>
>>
>>
>>
>>
>>ananda AT bharatpetroleum DOT [email protected] on 09.11.2001 12:38:30
>>
>>Please respond to nv-l AT tkg DOT com
>>
>>Sent by:  owner-nv-l AT tkg DOT com
>>
>>
>>To:     nv-l AT tkg DOT com
>>cc:
>>Subject:  [NV-L] ISDN port colour problem through Netview
>>
>>
>>
>>
> --------------------------------------------------------------------------
> 
>>
>>
>>
>>
>>Hi All,
>>
>>I am having NetView 6.0.2 on AIX 4.3.3.
>>
>>We are monitoring ISDN ports configured on different cisco routers. ISDN
>>port has been configures mainly as fall back arrangement.
>>
>>When these ports are not in use, it goes into inactive stage.
>>
>>The problem is Netview detects these inactive interface differently on
>>different routers. In some cases, it shows pink color ( IP status -
>>User1(7) and in some cases it gives red color ( IP status - Critical(4).
>>Because of these different behaves, other different related actions are
>>initiated.
>>
>>We have checked the configuration for these interfaces on routers and it
>>appears to be the same.
>>
>>Has anybody experienced the same problem? What could be the possible
>>reasons and where to look into?
>>
>>How NetView treats ISDN/port when in inactive stage ?
>>
>>Please reply ASAP.
>>
>>Thanks in advance,
>>
>>Regards,
>>
>>Anupam
>>
>>
>>
>>
>>
>>
>>_________________________________________________________________________
>>NV-L List information and Archives: http://www.tkg.com/nv-l
>>
>>
>>
>>_________________________________________________________________________
>>NV-L List information and Archives: http://www.tkg.com/nv-l
>>
>>
> 
> 
> --
> Bill Evans  --  Consultant in Enterprise Systems Management
> reply-to: wvevans AT prodigy DOT net  (or Bill_Evans AT sra DOT com)
> Phone: 919-696-7513
> Send short text messages to 9196967513 AT messaging.sprintpcs DOT com
> 
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
> 
> 
> 
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
> 
> 


-- 
Bill Evans  --  Consultant in Enterprise Systems Management
reply-to: wvevans AT prodigy DOT net  (or Bill_Evans AT sra DOT com)
Phone: 919-696-7513
Send short text messages to 9196967513 AT messaging.sprintpcs DOT com

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l

Hi Bill / Leslie,

I have put $ before some of the routers having ISDN port in seed file as suggested by you but is of no help. I am skeptical that this is going to help in our case because what I believe  this $ is to force a node to use SNMP for its Admin/Oper status update instead of ICMP ping if it is not having serial interfaces.

One more thing I wanted to share that in our case  ISDN call can be initiated from router side only and it can not be initiated from the central place  where our NetView is sitting. But, again this is the case for all routers having isdn port as fall up arrangement and NetView treating them differently.

When I do snmp poll for these pink/red color interface, the output comes differently. Also, I do not understand why TNV marks it red/Critical when it is actually in stand by mode?


Regards.....Anupam

-----Original Message-----
From: Bill Evans [mailto:wvevans AT attglobal DOT net]
Sent: Sunday, November 11, 2001 11:42 PM
To: IBM NetView Discussion
Subject: Re: [NV-L] ISDN port colour problem through Netview


I'd like to believe that the system automatically handles admin down but
we've just put in a number of 6.0.2 NT systems where the admin down were
discovered as critical.  We added the "$" entry to the seed file and
they turned pink when we restarted netmon and the GUI and looked.

The reason I'm tentative about the topic is that I didn't follow up on
the situation and find out why they weren't automatically polled with
SNMP -- I expected the SNMP poll due to the presence of serial
interfaces on the box.  It might also be a Unix vs. NT difference.  One
of these days I'm going to figure out how ATM, Frame Relay and
Point-to-Point interfaces interact with SNMP polling and if there are
differences not documented.

It's moot now with 7.1 available but there might be something support
should have addressed in the area which is bypassed with the forced use
of SNMP.

Bill

Leslie Clark wrote:

> There might be something to that, but I don't think it should be
> permanent. Even when status-polled with ping, an admin-down
> interface should show as user1. If it were admin-up when first
> discovered, then went admin-down later, it would be red, true. But
> it should switch on the next configuration poll, or demandpoll,
> I think, to user1. If it does not, it might be a case for Support.
>
> Oh - perhaps it is the Oper status that is the problem. If it is
> Dormant, then regardless of what the Admin status is, it will
> show as down. That is one of the things enhanced in V7.1.
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
>
>
>
>                                                                                       
>                     Bill Evans                                                        
>                     <[email protected]       To:     IBM NetView Discussion <nv-l AT tkg DOT com>
>                     obal.net>            cc:                                          
>                     Sent by:             Subject:     Re: [NV-L] ISDN port colour     
>                     [email protected]        problem through Netview                     
>                     .com                                                              
>                                                                                       
>                                                                                       
>                     11/10/01 04:05                                                    
>                     PM                                                                
>                     Please respond                                                    
>                     to IBM NetView                                                    
>                     Discussion                                                        
>                                                                                       
>                                                                                       
>
>
>
> Check whether both routers are being polled by SNMP.  If one is polled
> by ICMP and the other by SNMP it could explain the difference.  The
> archives and product manuals explain the details but there are a couple
> ways to force SNMP polling; a "$" entry in the seed file or a "P" in the
> oid_to_type file entry.
>
> anand anupam wrote:
>
>
>>Hi,
>>
>>As you rightly said that backup isdn line with  a status of AdminDown
>>will also be USER1 ( it should not be critical ).
>>
>>But, the problem in our case is  NetView assigns USER1(7) with pink
>>color and Critical(4) with red color for the same situation on different
>>routers.
>>
>>Any idea what could be possible reason and where to look into?
>>
>>
>>Regards,
>>
>>Anupam
>>
>>
>>
>>-----Original Message-----
>>From: Oliver Bruchhaeuser [mailto:oliver.bruchhaeuser AT de.ibm DOT com]
>>Sent: Friday, November 09, 2001 7:13 PM
>>To: IBM NetView Discussion
>>Subject: Re: [NV-L] ISDN port colour problem through Netview
>>
>>
>>Tim,
>>
>>update to NetView 7.1 !
>>In this version the dormant status of ISDN interfaces is managed
>>
> correctly.
>
>> From the release notes 7.1:
>>
>>Monitor ISDN Backup Interfaces
>>By default, interfaces with an SNMP ifOperStatus of DORMANT are handled
>>as if the status is NORMAL and the icon status color will be NORMAL.
>>However, in the special case of ISDN backup lines, when the status is
>>NORMAL, it usually means the primary line has a problem, and when
>>DORMANT, the primary line is usually okay. In this case the status
>>transitions to UP, and DORMANT might indicate the need for operator
>>intervention.
>>The following features are intended to help operators handle ISDN backup
>>lines:
>>* The status of a backup line in DORMANT state is USER1, otherwise the
>>status is as usual (NORMAL, DOWN). Note that the backup line with a
>>status of AdminDown will also be USER1.
>>* When the status changes to UP (from any state) the event Backup Line is
>>ACTIVE is sent.
>>* When the status transitions to DORMANT (from any state, including
>>AdminDown) the event Backup Line is DORMANT is sent.
>>
>>
>>Kind regards
>>
>>Oliver Bruchhaeuser
>>Tivoli NetView EMEA L2 Support
>>
>>IBM Deutschland GmbH - ITS Tivoli - Dept. 7977 - Hechtsheimer Str. 2 -
>>55131 Mainz - Germany
>>Phone: +49-6131-84-5108 - Fax: +49-6131-84-6585 - email:
>>bruchhae AT de.ibm DOT com
>>
>>Need help with Tivoli Software Products?
>>Ask Tivoli!
>>http://www.tivoli.com/asktivoli (login with your customer account)
>>
>>
>>
>>
>
>>
>>
>>[email protected]
>>
>
>>
>>                    its-eu.com              To:
>>nv-l AT tkg DOT com
>>
>>                    Sent by:
>>cc:
>>
>
>>
>>                    owner-nv-l AT tkg DOT co       Subject:     Re: [NV-L] ISDN
>>port colour problem through Netview
>>
>>
>>m
>>
>
>>
>>
>
>>
>>
>
>>
>>                    09.11.2001
>>12:55
>>
>
>>
>>                    Please respond
>>to
>>
>
>>
>>                    IBM
>>NetView
>>
>
>>
>>
>>Discussion
>>
>
>>
>>
>
>>
>>
>
>>
>>
>>
>>
>>
>>Hi,
>>
>>so far as I know, all ISDN Interfaces are treated as down when inactive.
>>Pink only shows up when the Port is manually shut down (administratively
>>shutdown)
>>
>>We use a solution, where we catch the ISDN traps to operate a "backup
>>
> icon"
>
>>which turns red when ISDN becomes active.
>>
>>Gruesse - Best regards
>>
>>Tim Uekermann
>>European Information Management
>>GE CompuNet Computer Distribution
>>Europaring 34-40, 50170 Kerpen, Germany
>>Phone: +49 (0) 22 73/597-7560, Fax: +49 (0) 22 73/597-186, Mobile:
>>01728348119
>>E-Mail : Tim.Uekermann AT gecits-eu DOT com
>>Visit us on the Internet: http://www.gecits-eu.com
>>
>>
>>This email is confidential. If you are not the intended recipient,
>>you must not disclose or use the information contained in it.
>>If you have received this mail in error, please tell us
>>immediately by return email and delete the document.
>>
>>
>>
>>
>>
>>ananda AT bharatpetroleum DOT [email protected] on 09.11.2001 12:38:30
>>
>>Please respond to nv-l AT tkg DOT com
>>
>>Sent by:  owner-nv-l AT tkg DOT com
>>
>>
>>To:     nv-l AT tkg DOT com
>>cc:
>>Subject:  [NV-L] ISDN port colour problem through Netview
>>
>>
>>
>>
> --------------------------------------------------------------------------
>
>>
>>
>>
>>
>>Hi All,
>>
>>I am having NetView 6.0.2 on AIX 4.3.3.
>>
>>We are monitoring ISDN ports configured on different cisco routers. ISDN
>>port has been configures mainly as fall back arrangement.
>>
>>When these ports are not in use, it goes into inactive stage.
>>
>>The problem is Netview detects these inactive interface differently on
>>different routers. In some cases, it shows pink color ( IP status -
>>User1(7) and in some cases it gives red color ( IP status - Critical(4).
>>Because of these different behaves, other different related actions are
>>initiated.
>>
>>We have checked the configuration for these interfaces on routers and it
>>appears to be the same.
>>
>>Has anybody experienced the same problem? What could be the possible
>>reasons and where to look into?
>>
>>How NetView treats ISDN/port when in inactive stage ?
>>
>>Please reply ASAP.
>>
>>Thanks in advance,
>>
>>Regards,
>>
>>Anupam
>>
>>
>>
>>
>>
>>
>>_________________________________________________________________________
>>NV-L List information and Archives: http://www.tkg.com/nv-l
>>
>>
>>
>>_________________________________________________________________________
>>NV-L List information and Archives: http://www.tkg.com/nv-l
>>
>>
>
>
> --
> Bill Evans  --  Consultant in Enterprise Systems Management
> reply-to: wvevans AT prodigy DOT net  (or Bill_Evans AT sra DOT com)
> Phone: 919-696-7513
> Send short text messages to 9196967513 AT messaging.sprintpcs DOT com
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>


--
Bill Evans  --  Consultant in Enterprise Systems Management
reply-to: wvevans AT prodigy DOT net  (or Bill_Evans AT sra DOT com)
Phone: 919-696-7513
Send short text messages to 9196967513 AT messaging.sprintpcs DOT com

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l