We are configuring this for the first time, only for Avaya to access as we will not have our own SAL software in house. (We will use cust supplied VPN)
We registered the system with Avaya and got back an SE ID and code for VAES,VSP,VSPU and VSALGW (as shown below)
However the CM 6 install manual is unclear about how the SAL Gateway itself is configured:
Do they each need a seperate IP on the customers LAN or do they share one?
Does the hostname need to be a FQDN or can it be anything?
It it just a case of adding the new elements or is there any other configuration required?
Thanks in advance!
#---------------------------------------------------------
# SE ID SE Code Alarm ID
#---------------------------------------------------------
# jjjjjjjjjjj VAES xxxxxxxxx
# iiiiiiiiiii VSP (NOT DISPLAYED)
# hhhhhh VSPU ccccccc
# ggggggg VSALGW dddddddddd
#
# INSTRUCTIONS ON SETTING SE ID/PID ON SP
# =======================================
#
# To set PID's on System Platform, access the gateway UI by going to
# https://CDOMIPaddress:7443/ and add VSP(SEID only), VUS, VSPU,
# and VSALGW as managed elements. While adding the managed elements,
# enter the SEID's and PID's which will configure the appropriate
# files to set the ID's.
#
# NOTE: For adopters of System Platform 6.0 or greater, ART will
# continue to generate Product IDs for VSP [dom0] but ART does 'NOT'
# include this Product ID in this script file as it is not
# administered in the product.
We registered the system with Avaya and got back an SE ID and code for VAES,VSP,VSPU and VSALGW (as shown below)
However the CM 6 install manual is unclear about how the SAL Gateway itself is configured:
Do they each need a seperate IP on the customers LAN or do they share one?
Does the hostname need to be a FQDN or can it be anything?
It it just a case of adding the new elements or is there any other configuration required?
Thanks in advance!
#---------------------------------------------------------
# SE ID SE Code Alarm ID
#---------------------------------------------------------
# jjjjjjjjjjj VAES xxxxxxxxx
# iiiiiiiiiii VSP (NOT DISPLAYED)
# hhhhhh VSPU ccccccc
# ggggggg VSALGW dddddddddd
#
# INSTRUCTIONS ON SETTING SE ID/PID ON SP
# =======================================
#
# To set PID's on System Platform, access the gateway UI by going to
# https://CDOMIPaddress:7443/ and add VSP(SEID only), VUS, VSPU,
# and VSALGW as managed elements. While adding the managed elements,
# enter the SEID's and PID's which will configure the appropriate
# files to set the ID's.
#
# NOTE: For adopters of System Platform 6.0 or greater, ART will
# continue to generate Product IDs for VSP [dom0] but ART does 'NOT'
# include this Product ID in this script file as it is not
# administered in the product.
Comment