ACF2

Expand all | Collapse all

why update calls to facility resource HWI.TARGET.netid.nau.imagename not being logged in acf2?

Jump to Best Answer
  • 1.  why update calls to facility resource HWI.TARGET.netid.nau.imagename not being logged in acf2?

    Posted 07-20-2016 11:04 AM

    Apparently update calls to facility resource HWI.TARGET.netid.nau.imagename are not being logged to ACF2. We placed the LOG option on all of our HWI.*** facility class profiles to see who was accessing them and at what level. After months of monitoring the reports, no user/task accessed the resources above the access of READ. We adjusted the rules and removed the LOG option and our BCPII HWISET process apparently fails because it requires UPDATE access. Our ZDYNACAP task issues their own HWISET error message but nothing is logged in ACF2. Why?      



  • 2.  Re: why update calls to facility resource HWI.TARGET.netid.nau.imagename not being logged in acf2?
    Best Answer

    Broadcom Employee
    Posted 07-20-2016 03:50 PM

    Martin,

    A RACROUTE EXTRACT call is made for the BCPii connection to retrieve
    the BCPii community from the APPLDATA field. The RACROUTE EXTRACT call
    does not allow for LOG like a RACROUTE AUTH call.        
                                                                                
    So there is no way to log who gets access. This is based on the RACROUTE
    call that is issued by BCPII. Normal ACF2 tracing does not allow for
    logging the call either. ACF2 SECTRACE can be used to trace the RACROUTE
    EXTRACT calls for the BCPII community name.                                             
                                                                                
    In order to change that processing we recommend contacting the BCPii product
    vendor and open a Ticket to request a change. 

     

    regards,

    Michael Blaha

    ACF2 Technical Support