nv-l
[Top] [All Lists]

[NV-L] location.conf and ranges

To: NetView mailing list <nv-l@lists.ca.ibm.com>
Subject: [NV-L] location.conf and ranges
From: Jane Curry <jane.curry@skills-1st.co.uk>
Date: Thu, 27 Jul 2006 19:33:20 +0100
Delivery-date: Thu, 27 Jul 2006 19:43:45 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com
User-agent: Mozilla Thunderbird 1.0.8 (X11/20060411)
NetView 7.1.4 - I have Fixpack4 on Linux and AIX platforms, plus a base NV7.1.4 on AIX - same result on all.

I have an environment which includes networks:
172.30.100.0 / 30 bit netmask
172.31.100.0 / 28
172.31.100.16 / 28
172.31.100.32 / 28

I have an entry in location.conf for:
pseudo   172.30-31    Site2

When I create a new map, the 172.31 networks are NOT placed in pseudo location. I dont see the 172.30 because it is actually a point-to-point network - that's OK. I have tested putting another, class C network in the same pseudo location and that works fine. Why don't the networks starting 172.31 go into pseudo???? I have done a separate test with some class C networks in a range entry in location.conf and that works fine - I'm sure I've used location ranges lots of times before!

The really daft thing is....
If I change the location.conf entry to:
pseudo   172.30-32    Site2

Then it works as I would expect - the 172.31 networks go into pseudo. Fortunately I don't actually have any 172.32 networks that I want to position elsewhere!

Has anyone else seen this????? I'm assuming it is an artifact of non-byte-aligned subnet masks. I also remember that there did used to be an issue with networks ending in .0 - in which case I could understand if my 172.31.100.0 network got left out but it still doesn't explain the 172.31.100.16 and 32 networks.

Cheers,
Jane

--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2006 Jane Curry <jane.curry@skills-1st.co.uk>.  All rights 
reserved.

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)

<Prev in Thread] Current Thread [Next in Thread>
  • [NV-L] location.conf and ranges, Jane Curry <=

Archive operated by Skills 1st Ltd

See also: The NetView Web