VIPOSA1 STACK=&1(C,C,8),IPA=&2(C,C,64) VTCPPARM error for stack
A VIP agent has tested its communications pipe for sending OSA MIB data to a VIP server, and found that the pipe is inadequately defined in agent configuration.
Message VIP1043 will probably be accompanied by the following message in //VIPOUT.
VIP01490000ME VTCP failure: EZASMI TYPE=BIND. PORTRANGE not reserved.
And message VIP1043 probably be accompanied by the following messages in //VTCPMSGS.
VTCP884E: BPX1BND=BIND failure ==> PORTRANGE not reserved etc.
VTCP894T: BPX1BND=BIND ==> EXECUTION FAILED FOR VI42WORK(SOCKET
VTCP895T: BPX1BND=BIND ==> Flags=0x00 RtnCode=0xFFFFFFFF ErrNo=
Description: The member hlq.agentnam.VIPINST(VIPOSA1) names the TCP/IP stack by which a VIP agent sends OSA data to a VIP server. And the member hlq.agentnam.VIPINST(VTCPPARM) defines the communications pipe for that stack, i.e. IP address and port number for TCP and UDP messages.
An agent generates this message because that pipe definition lacks a UDP port value, for example.
The VIP agent cannot send SNMP data, including OSA MIB data, to the VIP server.
Action: If the agent is not meant to monitor OSA MIB data, do nothing. The agent will issue this message at roughly 60 minute intervals, but it is safe to ignore it.
If the agent is meant to monitor OSA, then…
1. Double-check the stack name in VIPOSA1 and the UDP pipe definition for that stack in VTCPPARM.
2. If they don’t match, or are incomplete, use the VIP CCM tool to fix them.
3. Bounce the VIP agent.
In the VIP manual Customize, see the sections Agent Communications Ports and Pipes and OSA Monitoring.