RE: IP Map object attribute on Add Object Window dissapear s from GUI

[John Mackney <john.mackney@uk.logical.com>]

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.

NetView had no trouble discovering objects, but it did not connect many
objects correctly (mostly leaving them floating on the map as isolated
network bubbles). The cause of this appears to have been that we subnet a
class C address (10.254.1.0) into a large number if 255.255.255.252 subnets
in order  to link adjacent routers together.

When we add objects individually, the IP MAP attribute allows us to specify
not only the IP number of a router, but the exact subnet mask. Then when we
add the interfaces, NetView kindly joins up the dots for us. We have defined
about 30 objects this way on our map.

However, now we can not add any more this way - NetView is adding them the
user plane as you have rightly pointed out.

Maybe adding objects manually isn't a good idea. If we knew how to tell
NetView how our network was subnetted , we could let netmon discovery do the
work and perhaps paint a better picture for us. Any views?

John Mackney
Technical Design Authority
Logical eBOC
Logical (UK) Ltd.

Tel:        +44 (0) 1753 777354
Mobile:   +44 (0) 7767 804038
Email:      john.mackney@uk.logical.com

 -----Original Message-----
From:   James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com] 
Sent:   16 May 2001 12:33
To:     IBM NetView Discussion
Subject:        Re: [NV-L] IP Map object attribute on Add Object Window
dissapears from GUI


I will bet that these objects you are adding wind up with a shadow box
behind them after you add them, right?
That is because they are in the user plane and not the application plane.
The box for ipmap goes away because ipmap does not manage things in the
user plane, only in the application plane.  You are basically adding your
own objects to map and so ipmap does not know how to manage them, so he
doesn't.    You can add whatever you want, but then you have to provide
your own program to alter the map status.  If you need further
clarification, read up on adding objects to the map and the user plane in
the Admin Guide.

Basically, you should not be adding things to the map if they represent
real objects in your network that you expect netmon to report status on.
Instead, such things should be discovered, not added.  If you are having
trouble with that, then I recommend you tell the user community here about
it and get their suggestions on that.


James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



John Mackney <john.mackney@uk.logical.com>@tkg.com on 05/16/2001 06:43:56
AM

Please respond to IBM NetView Discussion <nv-l@tkg.com>

Sent by:  owner-nv-l@tkg.com


To:   "'nv-l@tkg.com'" <nv-l@tkg.com>
cc:
Subject:  [NV-L] IP Map object attribute on Add Object Window dissapears
      from GUI





Can anyone help with this problem?

We have a new NetView implementation and are getting problems with the GUI.
We have successfully added some objects to our RootMap, but now some of
the object attributes disappear from the object attributes field of the Add
Objects window  (particularly we do not see the IP Map application name
when we try to add a gateway connector or interface card object).  Closing
down NetView and restarting does Not cure the problem, neither does a
reboot of the Sun Solaris system supporting NetView.

We have checked resources and there seems to be sufficient memory, file
system space and inodes free on the Sun Solaris8 platform supporting
NetView so we do not think it is a resource issue.

John Mackney

Technical Design Authority

Logical eBOC

Logical (UK) Ltd.






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

NetView had no trouble discovering objects, but it did not connect many objects correctly (mostly leaving them floating on the map as isolated network bubbles). The cause of this appears to have been that we subnet a class C address (10.254.1.0) into a large number if 255.255.255.252 subnets in order  to link adjacent routers together.

When we add objects individually, the IP MAP attribute allows us to specify not only the IP number of a router, but the exact subnet mask. Then when we add the interfaces, NetView kindly joins up the dots for us. We have defined about 30 objects this way on our map.

However, now we can not add any more this way - NetView is adding them the user plane as you have rightly pointed out.

Maybe adding objects manually isn't a good idea. If we knew how to tell NetView how our network was subnetted , we could let netmon discovery do the work and perhaps paint a better picture for us. Any views?

John Mackney
Technical Design Authority
Logical eBOC
Logical (UK) Ltd.

Tel:        +44 (0) 1753 777354
Mobile:   +44 (0) 7767 804038
Email:      john.mackney@uk.logical.com

 -----Original Message-----
From:   James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com]
Sent:   16 May 2001 12:33
To:     IBM NetView Discussion
Subject:        Re: [NV-L] IP Map object attribute on Add Object Window dissapears from GUI

I will bet that these objects you are adding wind up with a shadow box
behind them after you add them, right?
That is because they are in the user plane and not the application plane.
The box for ipmap goes away because ipmap does not manage things in the
user plane, only in the application plane.  You are basically adding your
own objects to map and so ipmap does not know how to manage them, so he
doesn't.    You can add whatever you want, but then you have to provide
your own program to alter the map status.  If you need further
clarification, read up on adding objects to the map and the user plane in
the Admin Guide.

Basically, you should not be adding things to the map if they represent
real objects in your network that you expect netmon to report status on.
Instead, such things should be discovered, not added.  If you are having
trouble with that, then I recommend you tell the user community here about
it and get their suggestions on that.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT

John Mackney <john.mackney@uk.logical.com>@tkg.com on 05/16/2001 06:43:56
AM

Please respond to IBM NetView Discussion <nv-l@tkg.com>

Sent by:  owner-nv-l@tkg.com

To:   "'nv-l@tkg.com'" <nv-l@tkg.com>
cc:
Subject:  [NV-L] IP Map object attribute on Add Object Window dissapears
      from GUI

Can anyone help with this problem?

We have a new NetView implementation and are getting problems with the GUI.
We have successfully added some objects to our RootMap, but now some of
the object attributes disappear from the object attributes field of the Add
Objects window  (particularly we do not see the IP Map application name
when we try to add a gateway connector or interface card object).  Closing
down NetView and restarting does Not cure the problem, neither does a
reboot of the Sun Solaris system supporting NetView.

We have checked resources and there seems to be sufficient memory, file
system space and inodes free on the Sun Solaris8 platform supporting
NetView so we do not think it is a resource issue.

John Mackney

Technical Design Authority

Logical eBOC

Logical (UK) Ltd.

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