IT46719: PROBE SETTINGS UPDATED BY THE COMMIT OF THE GATEWAY PEERING MANAGER

APAR status

• Closed as program error.

Error description

• `probe-settings` should not be updated by the commit of
  `gateway-peering-manager` when there is no manual commit of
  `apiprobe-settings` with `admin disabled` is executed.
  
  1. confirm that the three objects are admin disabled
  
  `gateway-peering` assigned for `apiprobe` in
  `gateway-peering-manager`
  `apiprobe-settings`
  `probe-settings`
  idg(config)# sh gateway-peering-m
  
  gateway-peering-manager: default [down]
  --------------------------------
  admin-state disabled
  apic-gw-service default-gateway-peering [down]
  rate-limit default-gateway-peering [down]
  subscription default-gateway-peering [down]
  apiprobe (deprecated) default-gateway-peering [down]
  ratelimit-module default-gateway-peering [down]
  
  idg(config)# sh apiprobe-s
  
  apiprobe-settings: default [down]
  --------------------------
  admin-state disabled
  max-records 1000
  expiration 60 minutes
  gateway-peering default-gateway-peering [down]
  
  idg(config)# sh probe-s
  
  probe-settings: default [down]
  -----------------------
  admin-state disabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering default-gateway-peering [down]
  2. enable `probe-settings` and assign an op-state up
  `gateway-peering`
  
  idg(config)# probe-s
  Modify Probe settings configuration
  
  idg(config probe-settings)# admin enabled
  idg(config probe-settings)# gateway-peering api-probe
  idg(config probe-settings)# exit
  idg(config)# sh probe-settings
  
  probe-settings: default [up] (modified)
  -----------------------
  admin-state enabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering api-probe [up]
  3. commit `gateway-peering-manager` with no changes
  
  idg(config)# gateway-peering-manager; exit
  Modify Gateway-peering manager configuration
  
  
  Expected result: `probe-settings` is enabled with
  `gateway-peering` `api-probe`.
  
  idg(config)# sh probe-settings
  
  probe-settings: default [up] (modified)
  -----------------------
  admin-state enabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering api-probe [up]
  Actual result: `probe-settings` is disabled.
  
  idg(config)# sh probe-settings
  
  probe-settings: default [down]
  -----------------------
  admin-state disabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering default-gateway-peering [down]
  `probe-settings` should not be updated by the commit of
  `gateway-peering-manager` when there is no manual commit of
  `apiprobe-settings` with `admin disabled` is executed.
  

Local fix

Problem summary

• `probe-settings` should not be updated by the commit of
  `gateway-peering-manager` when there is no manual commit of
  `apiprobe-settings` with `admin disabled` is executed.
  
  1. confirm that the three objects are admin disabled
  
  `gateway-peering` assigned for `apiprobe` in
  `gateway-peering-manager`
  `apiprobe-settings`
  `probe-settings`
  idg(config)# sh gateway-peering-m
  
  gateway-peering-manager: default [down]
  --------------------------------
  admin-state disabled
  apic-gw-service default-gateway-peering [down]
  rate-limit default-gateway-peering [down]
  subscription default-gateway-peering [down]
  apiprobe (deprecated) default-gateway-peering [down]
  ratelimit-module default-gateway-peering [down]
  
  idg(config)# sh apiprobe-s
  
  apiprobe-settings: default [down]
  --------------------------
  admin-state disabled
  max-records 1000
  expiration 60 minutes
  gateway-peering default-gateway-peering [down]
  
  idg(config)# sh probe-s
  
  probe-settings: default [down]
  -----------------------
  admin-state disabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering default-gateway-peering [down]
  2. enable `probe-settings` and assign an op-state up
  `gateway-peering`
  
  idg(config)# probe-s
  Modify Probe settings configuration
  
  idg(config probe-settings)# admin enabled
  idg(config probe-settings)# gateway-peering api-probe
  idg(config probe-settings)# exit
  idg(config)# sh probe-settings
  
  probe-settings: default [up] (modified)
  -----------------------
  admin-state enabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering api-probe [up]
  3. commit `gateway-peering-manager` with no changes
  
  idg(config)# gateway-peering-manager; exit
  Modify Gateway-peering manager configuration
  
  
  Expected result: `probe-settings` is enabled with
  `gateway-peering` `api-probe`.
  
  idg(config)# sh probe-settings
  
  probe-settings: default [up] (modified)
  -----------------------
  admin-state enabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering api-probe [up]
  Actual result: `probe-settings` is disabled.
  
  idg(config)# sh probe-settings
  
  probe-settings: default [down]
  -----------------------
  admin-state disabled
  max-records 1000
  expiration 3600 seconds
  gateway-peering default-gateway-peering [down]
  `probe-settings` should not be updated by the commit of
  `gateway-peering-manager` when there is no manual commit of
  `apiprobe-settings` with `admin disabled` is executed.
  
  Show more
  

Problem conclusion

• Fix is available in 10.6.1, 10.5.0.13, 10.6.0.1
  
  For a list of the latest fix packs available, please see:
  https://www.ibm.com/support/pages/node/83105
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels