LMS 3.2: WISM not reachable

Hey Pros.
When I try to add WISM cards to the LMS they are not managable. Neither inventories nor configs can be collected. It's telling me "device not reachable". The community strings are correct and by trying "Management Station to Device" it says "ok" to SNMP but SSH is not successful, nevertheless they are accessible via SSH from the LMS server.
Any idea how I could fix this?
Device updates are all installed.
CS 3.3.0
CM 5.2.1
RME 4.3.1
Thanks in advance!
cheers
Marc

Perform a new inventory collection job for this device, then look at the IC_Server.log. What is the error you see there?

Similar Messages

Master/Slave Server is not reachable

We have standalone server install, but then I go to System->object finder and try to search something: i got the following error:
"Master/Slave Server is not reachable"

This typically indicates a problem with the System Identity User. Go to Common Services > Server > Security > System Identity Setup. Re-enter the username and password, and make sure the username points to an account with full access to all LMS applications and tasks.

Private iTunes U site is not reachable

The LaGuardia CC private iTunes U site is not reachable using the administrative credentials originally provided by Apple. Attempts to reach the site using Woolamaloo as well as the Vanderbilt building block for Blackboard LMS have failed. This behavior began shortly after Apple provisioned a public site for the college at which time the original credentials of the private site might have bee re-provisioned, touched or in some way made invalid.

Jetmir-
Your site appears to be functioning as expected from our end. We would recommend you log into the site with your Primary Apple ID account and check the transfer script information for accuracy and then trying to access the site again with Woolamaloo.
Specific to the Bb access issue - Losing access to an iTunes U site via an existing transfer script typically occurse when the time stamp for the system generating the transfer script has drifted beyond the 90 second window within which a transfer script is valid. Ensuring the server time is correct will most likely address the issue. You should also be able utulize the debug suffix to test the validity of the transfer script <http://deimos.apple.com/rsrc/doc/iTunesUAdministrationGuide/DebuggingSiteAccessa ndIntegration/chapter_19_section_1.html>
-Regards

IOS Remote Desktop App resolves hostname but throws Host is not reachable error.

Hello,
I am trying to use the Remote Desktop app on my iPad running iOS 7.0.2 to connect to a server through our Juniper VPN. When I type the hostname or IP address I get an error that say "Host is not reachable". If I connect through my Mac I have no
problem when on the same VPN. I have looked through all of the setting in Junos Pulse and it is setup to route all traffic through the VPN, and I do not know of anything that would be blocking it on the network end.
Edit: I am connecting to a Windows Server 2008 R2 box with RDP turned on with all types of connections.
Here is the log data for my latest attempt.
[2013-Nov-19 11:23:42] RDP (0): *** Application lauched ***
[2013-Nov-19 11:23:43] RDP (0): Application became foreground application
[2013-Nov-19 11:24:30] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2013-Nov-19 11:24:30] RDP (0): client version: 8.0.24094 on iPad3,4 (iPhone OS 7.0.3)
[2013-Nov-19 11:24:30] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2013-Nov-19 11:24:30] RDP (0): Showing credentials dialog
[2013-Nov-19 11:24:49] RDP (0): Final rdp configuration used: {
    activeUsername = "DOMAIN\\UserName";
    arcTimeout = 1800;
    cacheId = BEBD1725D63BB841;
    configurationVersion = 8;
    console = 0;
    host = "server.mysite.com";
    label = "Server";
    mouseMode = "-1";
    port = 3389;
    soundMode = 1;
    swapMouseButtons = 0;
    type = rdp;
    utilityBar = "-1";
    kCFProxyTypeKey = kCFProxyTypeNone;
[2013-Nov-19 11:24:49] RDP (0): --- BEGIN INTERFACE LIST ---
[2013-Nov-19 11:24:49] RDP (0): lo0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2013-Nov-19 11:24:49] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2013-Nov-19 11:24:49] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): en0 af=30 (AF_INET6) addr=fe80::66:9d3c:3d77:5cce%en0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en0 af=2 (AF_INET) addr=192.168.114.44 netmask=255.255.252.0
[2013-Nov-19 11:24:49] RDP (0): awdl0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): awdl0 af=30 (AF_INET6) addr=fe80::3c11:d7ff:feb2:7a82%awdl0 netmask=ffff:ffff:ffff:ffff::
[2013-Nov-19 11:24:49] RDP (0): en2 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): utun0 af=18 addr= netmask=
[2013-Nov-19 11:24:49] RDP (0): utun0 af=2 (AF_INET) addr=10.100.01.01 netmask=255.255.255.255
[2013-Nov-19 11:24:49] RDP (0): --- END INTERFACE LIST ---
[2013-Nov-19 11:24:49] RDP (0): Not using any proxy
[2013-Nov-19 11:24:49] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2013-Nov-19 11:24:49] RDP (0): Resolved 'server.mysite.com' to '10.100.01.01' using NameResolveMethod_Unknown(0)
[2013-Nov-19 11:25:09] RDP (0): Exception caught: Exception in file '/Users/build/jenkins/workspace/rc-ios-develop/protocols/RDP/cftcpendpoint.cpp' at line 242
    User Message : Host is not reachable
[2013-Nov-19 11:25:09] RDP (0): Error message: Host is not reachable(phase: 0, type: 0, reason: 0, systemCode: -1, systemMessage: )
[2013-Nov-19 11:25:09] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
[2013-Nov-19 11:25:09] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2013-Nov-19 11:25:09] RDP (0): ------ END ACTIVE CONNECTION ------
Cameron

Hi,
According to the log, your iPad tried to connect the remote server with IP address 10.100.01.01/32. Please check if it is the correct IP address of the server.
Also, please make sure that your iPad can connect to your VPN network successfully and get a valid IP address so that it can remote your internal server.
Thanks.
Jeremy Wu
TechNet Community Support

The system is not reachable, the login data could not be considered

Hello
I'm trying to connect via Hana Studio to a Hana One instance I have configured in AWS, following the guides & videos in the Hana Academy.
When adding the system in Hana studio, I get an error message after inputting the SYSTEM password:
The system is not reachable, the login data could not be considered
I've seen another post in the forum where the user solved the issue by resetting the SYSTEM password to a password without special characters, but mine is already "special character" free.
Are there others who have had difficulties when adding a new system?
Regards
Yann

Hi Swapan,
Thank you for your attention and message.
I downloaded the SAP HANA Studio from "Get your own SAP HANA, developer edition on Amazon Web Services (http://scn.sap.com/docs/DOC-28294)", specifically at SAP HANA Studio, developer edition and SAP HANA Client, developer edition, for Windows XP 32-bit. Is this HANA One? How to know the version of HANA server? How to make my Internet or firewall allow me to go out to the JDBC port? I am just learning to deal with these computer-science issues.
Regards,
Beiwei
Date: Wed, 4 Sep 2013 20:52:41 -0700
From: [email protected]
To: [email protected]
Subject: Re: - The system is not reachable, the login data could not be considered
                                                                                SAP HANA
    The system is not reachable, the login data could not be considered
    created by Swapan Saha in SAP HANA One Platform on AWS - View the full discussion
Hi Beiwei,
I suppose you are using HANA One (which you can only launch today from AWS Marketplace and HANA costs 99 cents/hr). If it is HANA One, which version of HANA One you are using? Please make sure you are using the same version of HANA Studio with HANA Server? Instance number in HANA One is 00.
If you HANA One, by default, it will open all the necessary ports. Please make sure you are Internet or your firewall allow you to go out to the JDBC port. If not, you cannot connect your studio behind your firewall with HANA server in the cloud.
Thanks,
Swapan
     Reply to this message by replying to this email -or- go to the message on SAP HANA
     Start a new discussion in SAP HANA One Platform on AWS by email or at SAP HANA

Officejet Pro X476dw MFP not reachable

Hi,
out of the blue my Officejet Pro X476dw MFP turned 'not reachable' from my MacBook. Device is still connected to my Wifi network, no changes there since last use. I can print ok from my iPhone. I turned the device off and on again - no success. I turned the MacBook off and on again - same. I reconfiguered Wifi connection at device - same. I deleted printer from MacBook and tried to re-add but installation program couldn't find device. I tried to connect manually using IP address that was shown on device - 'device not reachable'.
I am running out of ideas, appreciate any help!
Thank you!
Maik.

@weirdharrell
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Photosmart C4385 "Device Not Reachable"

I know this has been addressed in other threads, but none of the solutions have worked for me and my configuration is a little different. So here goes:
I'm running OS 10.6 Snow Leopard with my C4385. My computer is connected to a wireless network via an extender. I don't know anything about the router other than it's probably a Cisco since that's in the network name. The router and extender are both in my landlord's house, so I don't have access to them to reboot, check settings, or anything. Until this morning my printer was associated with the main network, which worked fine, but the signal is very weak and I would rather have it associated with the extender network. I went through the HP Setup Assistant and now all I get is the "Device Not Reachable" error message, whether I use the extender or main network.
I printed a Network Configuration Page and typed the printer's IP into my browser, and it shows up just fine, saying it's connected to the main network. Print & Fax under System Preferences disagrees and I can't print at all anymore (except with the USB cable). The only thing I changed recently is switching to a manual IP address for my laptop since I had lots of connectivity issues with automatic IPs, but after that everything worked until this morning when I ran Setup Assistant.
Sorry for writing a novel. I wish I had more information about the hardware but my landlord's not very helpful with these sorts of things. Any advice would be great! I've tried scrubbing software and reinstalling it and resetting the printing system, with no luck.

I see a couple of potential problems, here.
First, adding the printer by IP is dicey. If the router changes the printer's IP (actually WHEN it does, because eventually it will), then your Mac may lose track of it. Plus, adding by IP usually only enables printing, not scanning.
Second, HP printers don't seem to play well with wifi extenders. Is there a way to move your printer so that it is connected to the main router, not the extender?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

CUE Website not reachable

Hello,
we've configured a UC560 with Cisco Standards. So the CUE has the IP-adress 10.1.10.1 (Gateway .2).
The CUE successfully answer a ping ! The CCA CUE diagnostics ended successful.
I also can connect to CUE through CLI of the UC560.
BUT : The Webinterface of the CUE does not answer. The webiste ist not reachable.
Here the http config of the UC560 :
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip http path flash:/GUI
telephony-service
video
fxo hook-flash
max-ephones 138
max-dn 600
ip source-address 10.1.1.1 port 2000
auto assign 1 to 1 type bri
calling-number initiator
service phone videoCapability 1
service phone ehookenable 1
service dnis overlay
service dnis dir-lookup
service dss
timeouts interdigit 5
system message Cisco Small Business
url services
http://10.1.10.1/voiceview/common/login.do
url authentication
http://10.1.10.1/voiceview/authentication/authenticate.do
cnf-file location flash:
cnf-file perphone
user-locale U4 load CME-locale-de_DE-German-8.1.2.2.tar
network-locale U4
load 7941 SCCP41.9-1-1SR1S
load 7941GE SCCP41.9-1-1SR1S
load 7961 SCCP41.9-1-1SR1S
load 7961GE SCCP41.9-1-1SR1S
load 521G-524G cp524g-8-1-17
time-zone 23
time-format 24
date-format dd-mm-yy
dialplan-pattern 1 5909.. extension-length 2
keepalive 30 auxiliary 4
voicemail 39
max-conferences 8 gain -6
call-forward pattern .T
call-forward system redirecting-expanded
moh flash:/media/music-on-hold.au
multicast moh 239.10.16.16 port 2000
web admin system name cisco secret 5 $1$xdzm$dQ00q0.IUYeRDA4lTuNIl1
dn-webedit
time-webedit
transfer-system full-consult dss
transfer-pattern .T
transfer-pattern 0.T
transfer-pattern 6.. blind
secondary-dialtone 0
and the telephony part :
telephony-service
video
fxo hook-flash
max-ephones 138
max-dn 600
ip source-address 10.1.1.1 port 2000
auto assign 1 to 1 type bri
calling-number initiator
service phone videoCapability 1
service phone ehookenable 1
service dnis overlay
service dnis dir-lookup
service dss
timeouts interdigit 5
system message Cisco Small Business
url services http://10.1.10.1/voiceview/common/login.do
url authentication http://10.1.10.1/voiceview/authentication/authenticate.do
cnf-file location flash:
cnf-file perphone
user-locale U4 load CME-locale-de_DE-German-8.1.2.2.tar
network-locale U4
load 7941 SCCP41.9-1-1SR1S
load 7941GE SCCP41.9-1-1SR1S
load 7961 SCCP41.9-1-1SR1S
load 7961GE SCCP41.9-1-1SR1S
load 521G-524G cp524g-8-1-17
time-zone 23
time-format 24
date-format dd-mm-yy
dialplan-pattern 1 5909.. extension-length 2
keepalive 30 auxiliary 4
voicemail 39
max-conferences 8 gain -6
call-forward pattern .T
call-forward system redirecting-expanded
moh flash:/media/music-on-hold.au
multicast moh 239.10.16.16 port 2000
web admin system name cisco secret 5 $1$xdzm$dQ00q0.IUYeRDA4lTuNIl1
dn-webedit
time-webedit
transfer-system full-consult dss
transfer-pattern .T
transfer-pattern 0.T
transfer-pattern 6.. blind
secondary-dialtone 0
Can the problem be based on corrupt http CUE files or the wrong version ? Which files are required ?
May the Firewall ACLs block this traffic ? But ping works !
Please help !
Greets
Huck

That usually happens when your PC is using a default gatway that doesn't know about CUE address subnet.
So you have to fix your routing.

ISE NODE NOT REACHABLE when building distributed deployment

I am trying to build a distributed deployment with the following personas:
2 policy admin nodes
2 monitoring nodes
4 policy service nodes
This was a project that was partially implemented but never in production. It was in a distributed deployment, but half the nodes were no longer working (http errors or devices weren't reachable or could not sync). I decided to start from scratch. All nodes were:
-de-registered
-application was reset to factory defaults on all nodes
-upgraded all 8 nodes to 1.1.4.218 patch 1
-installed all new certs and joined all nodes to the domain
-added to DNS forward and reverse lookup zones
When I make 1 admin node primary and register the other nodes (secondary admin, monitoring, policy services) the nodes successfully register and show up in the deployment window of the primary; however, all the nodes show as NODE NOT REACHABLE. After registration, I've noticed that the registered nodes are still showing as STANDALONE if I access the GUI. I've tried rebooting them manually after registration and they are still unreachable. I have also tried resetting the database user password from the CLI on both admin nodes and the results are always the same.

Originally I had added them all at the same time. I thought that maybe I just wasn't waiting long enough for the sync. I waited an entire day and all the nodes were still unreachable. At this point, I've de-registered all the nodes, rebooted all the nodes, converted the primary back to standalone (the remaining nodes never converted from standalone to distributed even when I rebooted them after registering despite a message that they were successfully registered), converted one node back to primary and tried to register just the secondary admin node giving it plenty of time to sync; this node is still not reachable from the primary.
I've quadruple checked the certificates on all the nodes, these certs were all added on the same day (just last week) and the default self-signed certs were removed.
I had restored from a backup on the primary so I might just rest the config on that node and try joining the other nodes before I restore again.

ISE 1.1.3.124 secondary node not reachable after registration

G'day All,
I'm constantly seeing that the sync and replication status for my secondary admin/monitor node in the primary node as node not reachable. The secondary still thinks it is in standalone mode. When I run the ISE diag tool connectivity tests I am able successfully ping the devices from each other using both hostname and ip and the nslookup also works fine between both nodes. Ping and nslookups also work from different networks within the environment. The two nodes are in the same vlan on a 6500 vss pair but on different switches of the pair. I'm new to ISE so any help is greatly appreciated.
Thanks All.
JS
Sent from Cisco Technical Support iPhone App

Hi Saurav,
Thanks for your prompt repsonse...
I have worked through that section of the document. The registration completes successfully, I've got NTP sync on both nodes and the system time on both nodes is identical.
I am only using the self signed certificates, but following the user guide instructions I have imported the secondary's cert into the primary node.
Just as of about 30 minutes ago, I saw an alarm on the Secondary ISE node stating that a Slow or Stuck Replication has been detected...
As I said in the original post, I can ping the fqdn's from each other so it appears that the DNS requirements have been satisfied.
I've changed the admin account password, I am certain that the ISE DB passwords are correct and the same on both nodes and the timezones for both nodes is the same also....
It looks to me that registration is fine, but the first full replication isn't completing successfully
Thanks,
JS

Ora 12543 tns destination host not reachable

Dear All,
OS: RHEL 5
DB VERSION:-11.2.0
I am facing problem related to ora 12543 tns destination host not reachable
The problem here is little bit different what exactly other face:-
i have 2 servers with name abc.localdomain & xyz.localdomain.
Db name on abc.localdomain is abc
Db name on xyz.localdomain is xyz
When i try to ping with below mentioned command abc and xyz from abc.localdomain i am successful
ping abc
ping xyz
But when the same thing i am trying to do from xyz.localdomain i am able to ping the db running on xyz.localdomain. but getting the above mentioned error duringg pinging of abc database located on abc.localdomain server
I am able to ping both the server's from their ip's and hostname but not by abc db name and also checked firewall on both servers are disabled.
Here are my tnsnames.ora and listener.ora files for both machines
xyz.localdomain tnsnames.ora file:-
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
LISTENER1 =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xyz.localdomain)(PORT = 12001))
xyz =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = xyz.localdomain)(PORT = 12001))
    (CONNECT_DATA =
      (SERVICE_NAME = xyz)
abc =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = abc.localdomain)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = abc)
xyz.localdomain listener.ora:-
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER1 =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xyz.localdomain)(PORT = 12001))
SID_LIST_LISTENER1 =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = xyz)
      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1)
      (SID_NAME = xyz)
ADR_BASE_LISTENER1 = /u01/app/oracle
abc.localdomain machine:-
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = abc)
      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/grid)
      (SID_NAME = abc)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = abc.localdomain)(PORT = 1521))
ADR_BASE_LISTENER = /u01/app/oracle
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER = ON
tnsnames.ora:-
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
xyz =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = xyz.localdomain)(PORT = 12001))
    (CONNECT_DATA =
      (SERVICE_NAME = xyz)
abc =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = abc.localdomain)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = abc)
So kindly advice over the same if anyone of you face the same problem.

Hi,
Before actually looking up on this issue. I would suggest you to read the below posts to get true knowledge of what these utility do (i.e Listener, tnsping) and what are there purpose.
Help! I can't connect to my database...; | Ed Stevens, DBA
Help! I can't connect to my database (part duex) | Ed Stevens, DBA
tnsping what it is, what it isn't | Ed Stevens, DBA

MAC OS 10.9 Scan with 476DW after 2 scan computer not reachable

Hello,
I was very happy about the new multi printer 476 dw, but the most I need it for is scanning. After 1-2 documents the computer MAC 0s 10.9 is not reachable anymore. Also Mac Book same problems, it is getting on our nerves now.
Scanning over the network is not possible. Turning on and off is not the solution, we are a company and we need a professionel solution.
I hope somebody can help.
Best wishes
Frank

To get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at Commercial Forums.
I hope this helps!
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Uc560 - CUE Webinterface not reachable

Hello,
i have a problem with my UC560. Especially with the CUE Webinterface. After config my UC560 everthings working fine.
But the webinterface of the CUE is not reachable. I can ping the integtr. Service. Engine with IP 10.1.10.1. from my network.
A service-module integr.S.E. status reports -> everything OK. A seesion on CLI also connects and works.
Is there any idea ? help !!!
here some configs :
interface Integrated-Service-Engine0/0
description Interface used to manage integrated application modulecue is initialized with default IMAP group
ip unnumbered Vlan90
ip nat inside
ip virtual-reassembly in
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
interface GigabitEthernet0/1/3
description Interface used to communicate with integrated service module
switchport access vlan 90
no ip address
service-module ip address 10.1.10.1 255.255.255.252
service-module ip default-gateway 10.1.10.2
interface Vlan90
description $FW_INSIDE$
ip address 10.1.10.2 255.255.255.252
ip access-group 103 in
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip http path flash:/gui
ip dns server
ip nat inside source list 1 interface GigabitEthernet0/0 overload
ip route 10.1.10.1 255.255.255.255 Vlan90

Hello,
I have a similar issue. I know that there are many threads like this but this is the newest I found
I've wiped the preloaded configuration and now using the uc560 like a standard ISR. I've made a lot of tests and changes, using G0/0 and an IP for connecting to the LAN, or g0/1/0 as trunk/access port connecting to the LAN. I've ended up with the configuration I'm attaching. There is no way to have connectivity with the CUE. I've tried with and without VLANs (the file attached is with VLANs). NAT is irrelevant in my case since there is not anything to translate it's all a private routed network. I still cannot ping the ISE inf from inside the uc560 localy or the gateway address from inside the CUE.
This G0/1/3 seems to need some special configuration to be done in order to work. Do you know what is it?
It's also not possible to make the CUE to factory default. No initial setup wizard starts... nothing. No wizard needed for the initial setup like all the other CUE products?
Here is the config:
! interface GigabitEthernet0/0 no ip address duplex auto speed auto h323-gateway voip interface!interface Integrated-Service-Engine0/0 description Loopback interface used to manage integrated application module ip unnumbered Vlan2 service-module ip address 192.168.2.254 255.255.255.0 service-module ip default-gateway 192.168.2.2!interface GigabitEthernet0/1/0 switchport access vlan 2 no ip address!interface GigabitEthernet0/1/1 no ip address!interface GigabitEthernet0/1/2 no ip address!interface GigabitEthernet0/1/3 description Interface used to communicate with integrated service modue switchport access vlan 2 no ip address service-module ip address 192.168.2.254 255.255.255.0 service-module ip default-gateway 192.168.2.2!interface BRI0/1/0 no ip address isdn switch-type basic-net3 isdn point-to-point-setup trunk-group isdn 5!interface BRI0/1/1 no ip address isdn switch-type basic-net3 isdn point-to-point-setup trunk-group isdn 6!interface BRI0/2/0 no ip address isdn switch-type basic-net3 isdn point-to-point-setup! interface BRI0/2/1 no ip address isdn switch-type basic-net3 isdn point-to-point-setup!interface Vlan1 no ip address!interface Vlan2 ip address 192.168.2.2 255.255.255.0!ip forward-protocol ndip http serverno ip http secure-serverip http path flash:/gui!ip route 0.0.0.0 0.0.0.0 192.168.2.1ip route 192.168.2.254 255.255.255.255 Integrated-Service-Engine0/0!!!telephony-service no auto-reg-ephone max-ephones 15 max-dn 15 ip source-address 192.168.2.2 port 2000 secondary 192.168.2.3 rehome 15 time-zone 28 time-format 24 max-conferences 4 gain -6 moh flash:/media/music-on-hold.au multicast moh 239.0.0.1 port 16384 route 192.168.2.2 web admin system name admin password cisco time-webedit transfer-system full-consult create cnf-files version-stamp 7960 Mar 06 2013 15:02:09!
Thanks in advance!

Some sites are not reachable in FF however they were before.(In other browser they work). Why?

Some sites are not reachable in FF however they were before.(In other browser they work). Why
It is like some sites are blocked but FF says :
"The connection was reset
The connection to server was reset while the page download..."
== URL of affected sites ==
http://www.profession.hu http://www.hirkereso.hu

See "Error_loading_some_websites": http://kb.mozillazine.org/Error_loading_websites

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

LMS 3.2: WISM not reachable

Similar Messages

Maybe you are looking for