Re: Imanager - Access rules act weird
Craig Johnson
> I rambled, sorry. It just am at my wits end about this and it is
> getting to be a little crunch time for me. Any help would be
> appreciated. thank you.
>
Sorry for the slow response - I've been traveling again.
I am not sure what is causing your symptoms, but I recently have found
a client where 2 of 3 BM servers quit applying changes. In those case
(even though I have BM39SP2IR1 applied), I've had to delete a BMgr
attribute (Event Logging), which allows the changes to be saved once.
(It recreates the attribute at the same time, so next change requires
another delete). Just starting to debug that one.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***
Mysterious
> In article <jpeteet...@no-mx.forums.novell.com>, Jpeteet wrote:
>> I rambled, sorry. It just am at my wits end about this and it is
>> getting to be a little crunch time for me. Any help would be
>> appreciated. thank you.
>>
> Sorry for the slow response - I've been traveling again.
>
> I am not sure what is causing your symptoms, but I recently have found
> a client where 2 of 3 BM servers quit applying changes. In those case
> (even though I have BM39SP2IR1 applied), I've had to delete a BMgr
> another delete). Just starting to debug that one.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and books on
> BorderManager, go to http://www.craigjconsulting.com ***
>
>
that was fixed in bm39sp2_ir1, tid7000354, so make sure you're using the
correct iman snapins
Craig Johnson
> work. When I restart Tomcat on my machine or even reboot, the versions
> to not seem to change on any of my installed plugins. Any ideas? I saw a
> thread about some of the plugins would not work with BM3.7 and it has
> been reported to engineering....Any thoughts?
>
If you are using BM 3.7, you won't be using iManager for any BM
configuration (except filtering, if you want to use iManager instead of
FILTCFG). If you use BM 3.8, you need the plugins for VPN (and filtering,
optionally). Only if you use 3.9 do you use all the iMan BM plugins, and
even then can still use FILTCFG.
Did you also check RBS to see if you needed to update there?
Craig Johnson
> that was fixed in bm39sp2_ir1, tid7000354, so make sure you're using the
> correct iman snapins
>
Mysterious
let me check the code to verify that it is there.
Mysterious
> I worked on a client with 3 BM 3.9sp2ir1 servers, and two of the three
> would not update proxies. The other was fine. The Event Logging
> attribute was different (3 entries present) on the working one. Only
> one entry was in place on the 2 problem servers. Each time I deleted
> the attribute and updated the proxy, the same entry was recreated.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and books on
> BorderManager, go to http://www.craigjconsulting.com ***
>
>
I've checked the code and it is not there, dammed!.
I've got a new bmpxy.jar with the fix on it. I need an email address to
send it.
Copy it to sys:tomcat\5.0\webapps\nps\WEB-INF\lib, delete the Event
logging attribute and restart tomcat. Now it will create the attribute
with the right values.
Craig Johnson
would not update proxies. The other was fine. The Event Logging
attribute was different (3 entries present) on the working one. Only
one entry was in place on the 2 problem servers. Each time I deleted
the attribute and updated the proxy, the same entry was recreated.
Craig Johnson
Craig Johnson
> ones that came with BM3.9 sp2Ir1 - will not install for me. Any
> suggestions?
>
First off, check the basics on everything. (Server health check). The
server should have a read/write or master replica on it holding the server
object. Time should be in sync. NDS should be synching fine with
(hopefully) no stuck obits. Etc.
Check iManager version and available plugins. You should be at 2.7.3 if it
is up to date (check for iManager Framework plugin updates. I like to
update ALL the plugins, though it can take quite a while). The bm39sp2ir1
plugins should work with 2.7.3.
If you are having NDS issues, especially if no replica was on the server, I
could see it having a lot of problems consistently reading access rules.
Mysterious
>
> I've checked the code and it is not there, dammed!.
>
> I've got a new bmpxy.jar with the fix on it. I need an email address to
> send it.
> Copy it to sys:tomcat\5.0\webapps\nps\WEB-INF\lib, delete the Event
> logging attribute and restart tomcat. Now it will create the attribute
> with the right values.
or you can manually add the right values thru console1:
Click over the event logging attribute and select add. Enter the value
here. Repeat it 3 times with this values
- 65536
- 197632
- 131072
Then delete the value 0 created previously by the snapin.
Now apply changes should work.
Craig Johnson
> or you can manually add the right values thru console1:
>
> Click over the event logging attribute and select add. Enter the value
> here. Repeat it 3 times with this values
>
> - 65536
> - 197632
> - 131072
>
> Then delete the value 0 created previously by the snapin.
>
> Now apply changes should work.
>
other two entries.
Updates are working fine now.
Until I added those values, I got a java error when trying to look at
the DNS or Transport menus.