Perform the following steps to work around the mgmt Port Access issue on SBC nodes instantiated using VNFM With OAM:

 

1. Log in to the Active OAM node.

2. Check if any variables matching IFOAM0 were created. If they weren't there is no need for this work around. If there are, use the bold values shown below:

admin@ssbc-oam1-192.168.20.6> show table system metaVariable | match IFOAM0
ssbc-oam1-192.168.20.6 IFOAM0.DHCP True
ssbc-oam1-192.168.20.6 IFOAM0.GWV4 10.34.224.1
ssbc-oam1-192.168.20.6 IFOAM0.IPV4 10.34.224.50
ssbc-oam1-192.168.20.6 IFOAM0.Port Mgt0
ssbc-oam1-192.168.20.6 IFOAM0.FIPV4 172.29.50.201
ssbc-oam1-192.168.20.6 IFOAM0.PrefixV4 24
ssbc-oam2-192.168.20.10 IFOAM0.DHCP True
ssbc-oam2-192.168.20.10 IFOAM0.GWV4 10.34.224.1
ssbc-oam2-192.168.20.10 IFOAM0.IPV4 10.34.224.45
ssbc-oam2-192.168.20.10 IFOAM0.Port Mgt0
ssbc-oam2-192.168.20.10 IFOAM0.FIPV4 172.29.50.95
ssbc-oam2-192.168.20.10 IFOAM0.PrefixV4 24

 

3. Create dynamic metaVariables for IF0 for OAM-Active and OAM-Standby:

> set system metaVariableDynamic ssbc-oam1-192.168.20.6 IF0.IPV4 value 10.34.224.50
> set system metaVariableDynamic ssbc-oam1-192.168.20.6 IF0.PrefixV4 value 24
> set system metaVariableDynamic ssbc-oam2-192.168.20.10 IF0.IPV4 value 10.34.224.45
> set system metaVariableDynamic ssbc-oam2-192.168.20.10 IF0.PrefixV4 value 24
> commit

 

4. Configure the mgmtIpInterfaceGroup to use IF0 instead of IFOAM0 by entering the following commands:

> set system mgmtIpInterfaceGroup mgmtGroup mgmtIpInterface mgmtIntf1 ipVarV4 IF0.IPV4 prefixVarV4 IF0.PrefixV4 state enabled

> commit

 

4. Save and activate the configuration to push the configuration to all nodes in the VNF.

 

> request system admin vsbcSystem saveAndActivate

 

5. Reboot all nodes in the VNF. 

There is no need to reboot OAM nodes.