Start a Conversation

Unsolved

This post is more than 5 years old

919

February 23rd, 2007 04:00

EMC Smarts Adapter 1.1 for Alcatel 5620-SAM: about emsConfig.import

Hello,

I'm currently installing and configurating the EMC Smarts Adapter 1.1 for Alcatel 5620-SAM by setting parameters in the related emsConfig.import file.

It seems that the "JmsPort" parameter is not correctly set.

Thank you for your help.
Regards,
Renato VISTA
renato.vista@artesys-osiex.com
ARTESYS-OSIEX, France
EMC Smarts Partner


Please find the following information in order to understand the following emsConfig.import configuration:

Platform1: EMC Smarts
EMC Smarts SAM + IP AM/PM + OSPF DM + MPLS/VPN DM: 10.93.80.193

Platform2: Alcatel 5620-SAM primary server: 10.80.20.1
Platform3: Alcatel 5620-SAM primary server: 10.69.20.1

Please also find the emsConfig.import file below: please note that some error messages within the ALCATEL-SAM.log file seem to be due to the bad setting of the JmsPort parameter:

#
# Copyright (C) 2002 System Management ARTS (SMARTS)
# All Rights Reserved
#

#
# Import file for InCharge Alcatel SAM EMS adapter
#

# This file is local to the EMS adapter, and contains all configuration parameters
# required to run the adapter, against the simulator or the actual EMS
#
# It contains configuration information for connecting to:
# - Alcatel 5620 SAM
#
# Other parameters not specified in this file are retrieved directly by the adapter
# by connecting to the local and InCharge servers. These parameters are:
# - Local adapter name
# - Broker host name and port
# - InCharge server username and password
#
# Note that the defaults provided in this file should be changed according to the
# installation environment. Copy this file to the /local/conf/alcatel-sam/ directory and
# make installation-specific changes there.

ASA_Config::ASA-Config
{

# EMS instance description block(s), add one block per EMS instance
# Each block contain the following parameters, where the order of
# the parameters is important:
# - EMS IporURL (where to find it -- must be an IP)
# - EMS port (which HTTP port to use)
# - EMS account (EMS Login account)
# - EMS password (EMS Login password)

EmsInstance = {
{
"10.93.20.1",
"8080",
"admin",
"c36b885125105c462d34774140eec076"
}
}

# AltEmsInstance = {
# {
# "10.69.20.1",
# "8080",
# "admin",
# "c36b885125105c462d34774140eec076"
# }
# }

# AM server name
AMServerName = "INCHARGE-AM-PM"

# MPLS server name
MPLSServerName = "INCHARGE-MPLS"

# OI server name
OIServerName= "INCHARGE-OI"

# BGP server name
BGPServerName = ""

# OSPF server name
OSPFServerName = "INCHARGE-OSPF"

# Adapter server name
ASAServerName = "ALCATEL-SAM"

# MCAST server name
MCASTServerName = "INCHARGE-MCAST"

ChassisMapping = {
{
"2",
"7750-SR12"
},
{
"3",
"7750-SR24"
},
{
"4",
"7750-SR4"
},
{
"5",
"7750-SR1"
},
{
"6",
"7750-SR7"
},
{
"7",
"7450-ESS12"
},
{
"8",
"7450-ESS24"
},
{
"9",
"7450-ESS4"
},
{
"10",
"7450-ESS1"
},
{
"11",
"7450-ESS7"
},
{
"12",
"7710 SR-12c"
},
{
"101",
"t4Router"
},
{
"102",
"t5Router"
},
{
"105",
"t5c_48TRouter"
},
{
"106",
"t5c_24GTRouter"
},
{
"107",
"t5c_24TRouter"
},
{
"120",
"T5 Compact 24G"
},
{
"121",
"T5 Compact 24F"
},
{
"130",
"7250-SAS"
},
{
"sr_shelf_12Slot",
"7750-SR12"
},
{
"sr_shelf_24Slot",
"7750-SR24"
},
{
"sr_shelf_4Slot",
"7750-SR4"
},
{
"sr_shelf_1Slot",
"7750-SR1"
},
{
"sr_shelf_7Slot",
"7750-SR7"
},
{
"ess_shelf_12Slot",
"7450-ESS12"
},
{
"ess_shelf_24Slot",
"7450-ESS24"
},
{
"ess_shelf_4Slot",
"7450-ESS4"
},
{
"ess_shelf_1Slot",
"7450-ESS1"
},
{
"ess_shelf_7Slot",
"7450-ESS7"
},
{
"sr_shelf_7710_12c",
"7710 SR-12c"
},
{
"t4Router",
"t4Router"
},
{
"t5Router",
"t5Router"
},
{
"t5c_48TRouter",
"t5c_48TRouter"
},
{
"t5c_24GTRouter",
"t5c_24GTRouter"
},
{
"t5c_24GRouter",
"t5c_24GRouter"
},
{
"t5c_24FRouter",
"t5c_24FRouter"
},
{
"SAS_Router",
"7250-SAS"
},
{
"t5c_24TRouter",
"t5c_24TRouter"
}
}

# Control for level of logging output (currently a simple int)
# valid numbers are 1-7. 1 means log only the most severe; 7 means log
# the lowest level (debug) and all higher priority messages
# Level 1 - Error
# Level 2 - Warning
# Level 3 - Information
# others are debug levels

LogLevel = 1

# JMS connectivity to Alcatel SAM server (in SmAsAlarmEmsInterface)
JmsPort = "10.93.20.1:8080/xmlapi"

# JMS connectivity to Alcatel SAM server (in SmAsAlarmEmsInterface)
# empty string means no standby
AltJmsPort = ""

# ClientId - identifier Adapter should use when making XML requests.
# Alcatel recommends format like smarts@12345@138.45.32.12
# where the IP is where InCharge is running and 12345 is any unique integer.
ClientId = "smarts@12345@10.93.20.1"

# JMS UniqueId - empty string will indicate non-durable subscriber
# Alcatel recommends format like smarts@67891@138.45.32.12
# where the IP is where InCharge is running and 67891 is any unique integer.
JmsUniqueId = "smarts@31416@10.93.20.1"

# JMS User
JmsUser = "smarts"

# JMS Password
JmsPassword = "SmartsSmarts2007"

# Should Router Down alarm force all Interfaces Down and do a complete
# Status inventory on clear?
RouterDownProcessing = FALSE

# Should an alarm be automatically cleared when it is deleted
ClearAlarmOnDelete = TRUE

# ObjectDeletionEvent on Alarm should archive notification in oi
ArchiveOnDelete = TRUE

# specify whether discovery to Alcatel SAM should start immediately
DiscoveryOnStartup = TRUE

# Should SAM-O discovery be initiated automatically when JMS Events missed
# or when 5620Sam server switches
DiscoveryOnJmsLoss = TRUE

# The Adapter should create Service Access Point objects for VPLS services
CreateVPLSSAPs = TRUE

# If non-negative, MulticastQTag will look for VPLSs between 7750 and
# 7450 with this Outer encapsulation value and create PIMInterfaces over
# the interfaces. Use 0 (zero) with caution!
# Turn off with -1
MulticastQTag = -1

# When using MulticastQTag, this configuration will determine if the
# Multicast IES port on the 7750 is the one before (FALSE) or after
# (TRUE) the VPLS port.
IESAfterVPLS = TRUE

# Determines the timeout (in minutes) for OSPF configuration error alarms.
# Set this value to 0 to disable this feature and make the adapter
# wait on 5620Sam to clear.
OSPFConfigurationErrorAlarmTimeout = 30
}



Please find the ALCATEL-SAM.log file:

Creating GA_StringDictionary::PortTypeMappings
ICF-N-LICENSEDFEATURE-Enabling the following licensed feature(s):
Feature-ICALCSAMADAPTER
Initializing JVM interface...
JVM Interface initialization complete.

Finding EMS entries for this server...
Done creating EMS entries.
GA_StringDictionary::PortTypeMappings created
ICF-N-SUBSCRIBERSTART-Starting internal subscription adapter
[23-Feb-2007 11:27:03+187ms CET] t@15 InCharge Framework
ASL-E-ERROR_NO_PROFILE-Profile 'PROFILE-default' does not exist

[23-Feb-2007 11:27:03+193ms CET]
RSRV-N-DMSTARTED-Domain Manager ALCATEL-SAM started on TESTHYP1:37866
V1.1 RP15(66988), 23-Oct-2006 17:11:03 - Build 15
Feb 23, 2007 11:27:03 AM com.smarts.asac.SmAsAdapterLog debug
FINEST: Logger set to level FINEST
Feb 23, 2007 11:27:03 AM com.smarts.asac.SmAsAdapterLog info
INFO:
Alcatel 5620Sam Adapter: V1.1 RP5, 19-Oct-2006 12:00:00

Feb 23, 2007 11:27:03 AM com.smarts.asac.SmAsAdapterLog info
INFO: SmAdapterSettings ready.
Feb 23, 2007 11:27:06 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: Exception Type:java.lang.NullPointerException null
com.smarts.asac.SmConfigurationSettings.getAltEmsIP(SmConfigurationSettings.java:136)
com.smarts.asac.SmAsAlarmEmsInterface.initialize(SmAsAlarmEmsInterface.java:101)
com.smarts.asac.AlcatelSAMAdapter.initialize(AlcatelSAMAdapter.java:411)
com.smarts.asac.AlcatelSAMAdapter.realConstructor(AlcatelSAMAdapter.java:197)
com.smarts.asac.AlcatelSAMAdapter$1.run(AlcatelSAMAdapter.java:120)

java.lang.NullPointerException
at com.smarts.net.JI_FlowTCP$SenderThread.run(JI_FlowTCP.java:424)
Feb 23, 2007 11:28:10 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: Attach to broker got:com.smarts.remote.SmRemoteException: Remote server is not a Domain Manager
Feb 23, 2007 11:28:35 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
java.io.IOException: Broken pipe
at java.net.PlainSocketImpl.socketSendUrgentData(Native Method)
at java.net.PlainSocketImpl.sendUrgentData(PlainSocketImpl.java:509)
at java.net.Socket.sendUrgentData(Socket.java:855)
at com.smarts.net.JI_FlowTCP$SenderThread.run(JI_FlowTCP.java:424)
Feb 23, 2007 11:30:00 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:31:25 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:32:50 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:34:15 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:35:40 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:37:05 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:38:30 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:39:55 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:41:20 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:42:45 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
Feb 23, 2007 11:44:10 AM com.smarts.asac.SmAsAdapterLog error
SEVERE: SmAsAdapter.startMonitor() JNDI API lookup failed: Receive timed out
env:{java.naming.provider.url=jnp://10.93.20.1:8080/xmlapi/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
No Responses!
No Events found!

Top