Reply to Any idea what would cause this box to appear in one zone, but not the other? on Wed, 26 Jun 2013 21:05:26 GMT

bwolfe — Wed, 26 Jun 2013 21:05:26 GMT

Hey Victor,

For what it's worth, that doesn't seem to work. Is it possible I've done something wrong?

mysql> SELECT * from interfaces where ip_addr REGEXP '^128\.*';
+------+---------+-------+------------+-----------------+---------+----------+-------------+----------+----------+--------------+------------+--------------+----------------+-------------+------------+-----------------+---------------------+----------------+
| id | node_id | flags | ip_addr | ip_netmask | if_type | if_index | bridge_port | phy_slot | phy_port | peer_node_id | peer_if_id | mac_addr | required_polls | admin_state | oper_state | dot1x_pae_state | dot1x_backend_state | description |
+------+---------+-------+------------+-----------------+---------+----------+-------------+----------+----------+--------------+------------+--------------+----------------+-------------+------------+-----------------+---------------------+----------------+
| 142 | 124 | 4 | 128.0.0.1 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0001 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 739 | 124 | 4 | 128.0.0.32 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0001 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 919 | 813 | 12 | 128.0.0.1 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 920 | 813 | 12 | 128.0.1.16 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 950 | 124 | 4 | 128.0.0.17 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0001 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 987 | 972 | 4 | 128.0.0.1 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0000 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 1092 | 972 | 4 | 128.0.0.16 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0000 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 1093 | 972 | 4 | 128.0.0.32 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0000 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 2398 | 2349 | 12 | 128.0.0.1 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 2399 | 2349 | 12 | 128.0.0.4 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 2400 | 2349 | 4 | 128.0.0.6 | 255.255.255.255 | 53 | 526 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | sp-0/0/0.16383 |
| 2401 | 2349 | 12 | 128.0.1.16 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 2709 | 2694 | 4 | 128.0.0.1 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0005 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 3169 | 2694 | 4 | 128.0.0.21 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0005 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 3170 | 2694 | 4 | 128.0.0.32 | 192.0.0.0 | 53 | 38 | 0 | 0 | 0 | 0 | 0 | 000BCAFE0005 | 0 | 1 | 1 | 0 | 0 | bme0.32768 |
| 5775 | 5729 | 12 | 128.0.0.1 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 5776 | 5729 | 12 | 128.0.0.4 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
| 5777 | 5729 | 4 | 128.0.0.6 | 255.255.255.255 | 53 | 532 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | sp-0/0/0.16383 |
| 5778 | 5729 | 12 | 128.0.1.16 | 255.255.255.255 | 24 | 22 | 0 | 0 | 0 | 0 | 0 | 000000000000 | 0 | 1 | 1 | 0 | 0 | lo0.16385 |
+------+---------+-------+------------+-----------------+---------+----------+-------------+----------+----------+--------------+------------+--------------+----------------+-------------+------------+-----------------+---------------------+----------------+

Reply to Any idea what would cause this box to appear in one zone, but not the other? on Thu, 13 Jun 2013 13:30:37 GMT

victor — Thu, 13 Jun 2013 13:30:37 GMT

Hi!

Currently server can have interfaces excluded from network topology. The problem is that there are no UI to set this flag on interface object. As a workaround, you can find interface objects with addresses from 128.0.0.0/2 subnet, record their IDs, then stop the server and execute SQL query like this:

UPDATE interfaces SET flags=flags+4 WHERE id=your_interface_object_id

for each such interface object. Then you can start server and delete 128.0.0.0/2 subnet object . It should not appear again.

Best regards,
Victor

Reply to Any idea what would cause this box to appear in one zone, but not the other? on Wed, 12 Jun 2013 19:46:57 GMT

bwolfe — Wed, 12 Jun 2013 19:46:57 GMT

Okay.. 128.0.0.0/2 is a subnet that exists in its own unique vlan, on a juniper switch's 'bme' interface (for creating the switch stack). Apparently there is NO WAY to change this, according to juniper's TAC.. so I'm going to have to proceed in a different direction.

Is there any way that I can get NetXMS to ignore the existence of this subnet?

Reply to Any idea what would cause this box to appear in one zone, but not the other? on Wed, 12 Jun 2013 18:43:26 GMT

bwolfe — Wed, 12 Jun 2013 18:43:26 GMT

Update:
I think what's causing this is the presence of that 128.0.0.0/2 subnet.. I our network admin has that built out as a loopback interface somewhere. It's not really a routeable subnet... but the mere presence of that subnet in the routing tables of the switches seems to be causing some grief.

I guess NetXMS is probably doing the right thing here, because obviously a box in the 172.20.192.0/23 subnet would _also_ be a member of 128.0.0.0/2, even though that's not actually the way it routes.