Netflow on CRS (MPLS problem)
Hi all,
I have configured netflow on CRS platfom, but it seems it doesn't capture/export any mpls information(traffic) on mpls enabled interfaces. My configuration is:
flow monitor-map xxxxxxx
record mpls ipv4-fields
exporter xxxxxxx
cache entries 10000
cache timeout active 30
cache timeout inactive 15
sampler-map xxxxxxx
random 1 out-of 1500
flow exporter-map xxxxxxx
version v9
options interface-table timeout 60
options sampler-table timeout 60
template timeout 60
template data timeout 60
template options timeout 60
transport udp 9950
source Loopback0
destination xxxxxxx
interface Bundle-Etherx.xx
description test
mtu 9200
ipv4 mtu 9000
ipv4 address x.x.x.x
ipv6 mtu 9000
ipv6 address x6.x6.x6.x6
flow ipv6 monitor x6monitor sampler x ingress
flow mpls monitor MPLSmonitor sampler x ingress
dot1q vlan x
This is show command for that interface:
RP/0/RP0/CPU0:CN-Srce-00-RO#show flow monitor MPLSmonitor cache match interface ingress eq bundle-ether 1.155 location 0/7/CPU0
Fri Aug 29 13:09:57.352 MET
Cache summary for Flow Monitor CN-NetFlow-MPLSmonitor:
Cache size: 10000
Current entries: 0
High Watermark: 9500
Flows added: 3335609
Flows not added: 0
Ager Polls: 27241668
- Active timeout 65946
- Inactive timeout 3244005
- TCP FIN flag 25658
- Watermark aged 0
- Emergency aged 0
- Counter wrap aged 0
- Total 3335609
Periodic export:
- Counter wrap 0
- TCP FIN flag 0
Flows exported 3335609
Matching entries: 0
I have also configured ipv4 and ipv6 monitor maps on few other interfaces and I can see netflow info of that type of traffic.
Tnx for your help.
Best regards,
RJ.
Hi Marcin,
Unfortunately, if you try to sample an MPLS+IPv4 packet and only send the IPv4 part in the records, it's not possible with IOS-XR,
Best Regards,
N.
Similar Messages
-
Hi
We are implementing DDoS solution in our network and the netflow protocol is lunch on core routers - the CRS-3
I've got the folloing monitor-map:
flow monitor-map arbor-ddos-mpls
record mpls ipv4-fields
exporter arbor-ddos
cache timeout active 30
cache timeout inactive 15
The point is that CRS-3 is sending netflow record to DDoS system ( arbor) with the records from MPLS VPN service.
I would like to filter force CRS-3 to not to send this MPLS VPN netflow information.
is there any chance to do it ? I was thinking about :
record mpls ipv4-fields labels 1
but is it only for labels to be used for hashing
I would be appreciated for any help
Kind Regards
MarcinHi Marcin,
Unfortunately, if you try to sample an MPLS+IPv4 packet and only send the IPv4 part in the records, it's not possible with IOS-XR,
Best Regards,
N. -
Crs installation problem in oracle 10g rac with NAS storage
Hi,
for my practice i am trying to install oracle 10gR2 on RHEL5-64bit OS in my laptop.
during my crs installation i have struckup with the below error while i am executing root.sh in node1.
Error:
+++++
Setting the permissions on OCR backup directory
Setting up NS directories
PROT-1: Failed to initialize ocrconfig
Failed to upgrade Oracle Cluster Registry configuration
ocrconfig.log ;
++++++++++++
NFS file system /u01 mounted with incorrect options
[ OCROSD][4265610768]WARNING:Expected NFS mount options: wsize>=32768,rsize>=32768,hard,(noac | actimeo=0 | acregmin=0,acregmax=0,acdirmin=0,acdirmax=0
[ OCROSD][4265610768]utopen:6m'': OCR location [share/storage/ocr] configured is not a valid storage type. Rturn code [37].
As per metalink i have find that this problem is fixed with Patch:4679769
# Patch Installation Instructions:
# To apply the patch, unzip the PSE container file:
# p4679769_10201_LINUX.zip
# Set your current directory to the directory where the patch
# is located:
# % cd 4679769
# Copy the clsfmt.bin binary to the $ORACLE_HOME/bin directory where
# clsfmt is being run:
# % cp $ORACLE_HOME/bin/clsfmt.bin $ORACLE_HOME/bin/clsfmt.bin.bak
# % cp clsfmt.bin $ORACLE_HOME/bin/clsfmt.bin
# Ensure permissions on the clsfmt.bin binary are correct:
# % chmod 755 $ORACLE_HOME/bin/clsfmt.bin
3. Run the root.sh script and proceed with the installation.
**My question is still i am not install Database ..only i ma trying to install crs but in this readme .txt we need to replace the clsfmt.bin file in ORACLE_HOME/bin.**
**but i have not bin directory under in ORACLE_HOME.please clear my doupt to apply this patch...**
Regards,
MugunthAlso you clusterware installation installs to an ORACLE_HOME.
Oracle does only make a differentiation, if it has to be clear, that you got a clusterware home and a database home.
Normally if a patch is referring to $ORACLE_HOME (and the patch can be used for clusterware & database), it just means the installation directory of the oracle software installed.
Sebastian -
CRS Installation problem - node out of sync?
Hi at all
I have some installation problems with 10gR2 Rac and CRS on RHEL 4.0 (kernel 2.6.9) and Vmware Workastion 5.0. . Also I have applied suggestion in the vmware KB available at this link
http://kb.vmware.com/vmtnkb/search.do?cmd=displayKC&docType=kc&externalId=1420&sliceId=SAL_Public
due some synchronization problems .
Also, I have configured ntpd daemon for sync my virtual machine.
The error message from installActions2006-12-18_01-10-58AM.log is:
INFO: Exclude file list /tmp/OraInstall2006-12-18_01-10-58AM/installExcludeFile.lst does not exist or is empty. The file is ignored.
WARNING: Error while copying directory /app/oracle/product/10.2.0/crs with exclude file list 'null' to nodes 'oracle002'. [PRKC-1002 : All the submitted commands did not execute successfully]
oracle002:
/bin/tar: ./bin/ocrcheck: time stamp 2006-12-18 01:15:27 is 34 s in the future
/bin/tar: ./bin/crs_register: time stamp 2006-12-18 01:15:28 is 35 s in the future
/bin/tar: ./bin/cemutls: time stamp 2006-12-18 01:15:28 is 34 s in the future
/bin/tar: ./bin/usrvip: time stamp 2006-12-18 01:15:28 is 34 s in the future
/bin/tar: ./bin/cluvfy: time stamp 2006-12-18 01:15:28 is 32 s in the future
/bin/tar: ./bin/racgons: time stamp 2006-12-18 01:15:28 is 30 s in the future
/bin/tar: ./bin/cluutil: time stamp 2006-12-18 01:15:28 is 29 s in the future
/bin/tar: ./bin/crs_profile: time stamp 2006-12-18 01:15:28 is 29 s in the future
/bin/tar: ./bin/vipca: time stamp 2006-12-18 01:15:47 is 48 s in the future
/bin/tar: ./bin/clscfg: time stamp 2006-12-18 01:15:27 is 25 s in the future
/bin/tar: ./bin/clsid: time stamp 2006-12-18 01:15:27 is 25 s in the future
/bin/tar: ./bin/crs_start: time stamp 2006-12-18 01:15:28 is 26 s in the future
/bin/tar: ./bin/crsctl: time stamp 2006-12-18 01:15:27 is 24 s in the future
/bin/tar: ./bin/evmsort: time stamp 2006-12-18 01:15:28 is 24 s in the future
/bin/tar: ./bin/evmmkbin: time stamp 2006-12-18 01:15:28 is 24 s in the future
but if I check clock sync between two nodes....:
[oracle@oracle001 ~]$ date;ssh oracle002 date;
Mon Dec 18 01:39:33 CET 2006
Mon Dec 18 01:39:33 CET 2006
and from the first node
[root@oracle001 crs]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
oracle002-priv 10.0.0.1 3 u 30 64 37 0.264 8.075 2003.55
and from the second node:
[root@oracle002 crs]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
10.0.0.1 193.204.114.232 2 u 17 64 377 0.652 -30.302 16212.0
[root@oracle002 crs]#
Please, someone can Help me?
Thanks
Adriano Capruzzi
Message was edited by:
adriano.baYour 4MEM error code is indeed reporting to you that some of your RAM is not working properly (MEM = memory, i.e. RAM).
The fix for this (replacing the RAM) is normally covered under warranty for a computer as new as yours is. To get the free warranty repair I believe that you do need to bring your computer to an Apple-certified repair center, however. If you order the RAM and do it yourself, you will need to pay for the RAM and also go through the trouble of opening your computer to access the RAM, which is not that hard to do for some people, others prefer to have a technician do that.
I'd suggest that you have Apple do the RAM fix, if only so that the replacement RAM is covered as well going forward ... -
CRS starting problem "CSSCLNT][1]clsssInitNative: connect failed, rc 9"
We have one 2 node HP-UX 10.2.0.4 cluster. Due to power problems we shutdowned the nodes and started the nodes after a week.
The CRS is not coming. I check the priv NICs, OCR/VOTE disks and their permissions, etc,...... Everything is fine.
In the log directory $CRS_HOME/log/<node_name>/client , there were thousands of css*.log files.
All the file contains same word
Oracle Database 10g CRS Release 10.2.0.4.0 Production Copyright 1996, 2008 Oracle. All rights reserved.
2009-04-13 19:50:08.877: [ CSSCLNT][1]clsssInitNative: connect failed, rc 9
How to solve this issue ?delete all the files inside .oracle directoery in /var/tmp or /tmp.
-
I'm installing RAC on two nodes. I have installed Clusterware, and I've ran successfully root.sh script on first node.
I've also tried to run script on second node, but it hangs:
slesred:/home/oracle # /u01/oracle/product/10.2.0/crs/root.sh
WARNING: directory '/u01/oracle/product/10.2.0' is not owned by root
WARNING: directory '/u01/oracle/product' is not owned by root
WARNING: directory '/u01/oracle' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/u01/oracle/product/10.2.0' is not owned by root
WARNING: directory '/u01/oracle/product' is not owned by root
WARNING: directory '/u01/oracle' is not owned by root
WARNING: directory '/u01' is not owned by root
clscfg: EXISTING configuration version 3 detected.
clscfg: version 3 is 10G Release 2.
assigning default hostname slesorange for node 1.
assigning default hostname slesred for node 2.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: slesorange slesorange-priv slesorange
node 2: slesred slesred-priv slesred
clscfg: Arguments check out successfully.
NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 90 seconds.I've stopped it, and now when I'm trying to run it again I get:
slesred:/u01/oracle/product/10.2.0/crs/bin # /u01/oracle/product/10.2.0/crs/root.sh
WARNING: directory '/u01/oracle/product/10.2.0' is not owned by root
WARNING: directory '/u01/oracle/product' is not owned by root
WARNING: directory '/u01/oracle' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
Oracle CRS stack is already configured and will be running under init(1M)
slesred:/u01/oracle/product/10.2.0/crs/bin #What can I do now? On first node Notification Server Configuration Assistant status is failed now...
Any suggestions will be appreciated.Ok, it was about SSH communication. I've removed passwords from my id_rsa.pub/id_dsa.pub and it goes ok. After setting $ORA_CRS_HOME/bin/oifcfg setif global eth0/subnet:public and $ORA_CRS_HOME/bin/oifcfg setif global eth1/subnet:cluster_interconnect I'm able to run vipca, but:
1. I can only see one network interface in vipca (eth0)
2. After putting virtual addresses into vipca I've got CRS-0184: Cannot communicate with the CRS daemon
Any suggestions?
UPDATE:
I can run $ORA_CRS_HOME/bin/crs_start -all without CRS-0184 (there is no communication problem), it is only thrown by vipca... Is it possible that error shows due to root account? (vipca is running from root, crs_start from oracle)
Edited by: Łukasz Mastalerz on Oct 26, 2008 12:57 PM -
Hi,
Anybody knows how to configure mpls netflow egress for a cisco router running 12.2(25)S service provider image ?
The following link says there is a restriction for it:
http://www.cisco.com/en/US/partner/products/ps6350/products_configuration_guide_chapter09186a00805e1253.html#wp1043334
The MPLS Egress NetFlow Accounting feature is not supported in Cisco IOS Release 12.2(25)S and later. Use the Egress NetFlow Accounting feature, which captures either IP or MPLS packets as they leave the router.
I haven't found out how to exactly configure this feature because the ip flow egress work is not working.
Anybody care to shed some light ?
Thanks in advance,
Luis RuedaNetflow was in ingress technology, in which the flows that were captured were flows that entered the interface. Flows leaving the interface were not captured. Also, it was an IP technology, hence non IP traffic were not captured.
With the introduction of MPLS VPN, traffic from remote PEs were recieved on the egress PE as labelled traffic. Hence, they were not captured by Netflow (Without MPLS, enabling netflow on the WAN interface of the egress PE would have allowed the traffic be captured).
MPLS Egress Netflow Accounting patched the situation above by allowing Netflow to capture the flow, when the mpls packet was untagged. This feature was introduced in 12.0(20)S. see
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_white_paper09186a00800b3d18.shtml
It is configured with the command mpls netflow egress
To make things better, they bettered the netflow technology and allowed it to captured egress traffic. With it capturing outgoing traffic, the mpls egress netflow feature was not needed again. Or to put it in another way, Egress Netflow Accounting, replaced MPLS Egress Netflow. See
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00802d41ea.html
This is configured with the command
ip flow egress
For using these features, check your IOS properly and see which one it supports. I have succesfully used the MPLS Netflow Egress. -
I have followed all of the configuration steps given for egress accounting with netflow on a MPLS VPN link. However, it is only showing flows coming into the router. I need to be able to account both ways- any recommendations? Config below:
interface Multilink12
mtu 1580
ip address XX.XX.XX.XX 255.255.255.252
no ip redirects
no ip unreachables
ip pim sparse-mode
ip route-cache flow
mpls netflow egress
mpls label protocol ldp
mpls ip
ppp multilink
ppp multilink group 12
ip flow-export source FastEthernet0/0/0.10
ip flow-export version 5
ip flow-export destination XX.XX.XX.XX 9996
IP packet size distribution (10730093 total packets):
1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480
.000 .098 .645 .011 .016 .012 .009 .010 .000 .001 .000 .001 .000 .000 .000
512 544 576 1024 1536 2048 2560 3072 3584 4096 4608
.000 .000 .000 .002 .185 .000 .000 .000 .000 .000 .000
IP Flow Switching Cache, 4456704 bytes
4 active, 65532 inactive, 464700 added
6109192 ager polls, 0 flow alloc failures
Active flows timeout in 1 minutes
Inactive flows timeout in 15 seconds
IP Sub Flow Cache, 336520 bytes
0 active, 16384 inactive, 20706 added, 20706 added to flow
0 alloc failures, 0 force free
1 chunk, 1 chunk added
last clearing of statistics never
Protocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)
-------- Flows /Sec /Flow /Pkt /Sec /Flow /Flow
TCP-Telnet 7 0.0 20 233 0.0 7.0 11.3
TCP-FTP 3 0.0 1 40 0.0 0.4 1.6
TCP-WWW 5757 0.0 6 389 0.0 1.1 3.0
TCP-SMTP 7 0.0 1 40 0.0 0.7 1.6
TCP-X 244 0.0 1 54 0.0 0.0 1.5
TCP-other 304762 0.2 7 346 1.6 2.2 4.8
UDP-DNS 346 0.0 1 127 0.0 0.0 15.4
UDP-NTP 3323 0.0 1 80 0.0 0.0 15.4
UDP-other 131041 0.0 62 341 5.4 17.6 13.2
ICMP 64291 0.0 1 79 0.0 0.0 15.4
Total: 509781 0.3 21 341 7.1 5.9 8.3
SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP Pkts
Mu12 10.50.66.218 Null 10.105.0.1 11 0675 00A1 84
Mu12 10.50.66.218 Null 10.105.19.10 11 0675 00A1 2
Mu12 10.50.66.218 Null 10.105.19.3 11 0675 00A1 4
Mu12 10.50.66.42 Null 10.105.19.10 06 0B3C 01BD 12Update on this- Im now receiving all traffic incoming into the interface, but am tracking only about 10% of the outgoing traffic- revised config below:
ip flow-cache timeout active 1
ip flow-cache mpls label-positions 1 2 3
ipv6 flow-cache mpls label-positions 1 2 3
interface Multilink12
mtu 1580
ip address XX.XX.XX.XX 255.255.255.252
no ip redirects
no ip unreachables
ip flow ingress
ip flow egress
ip pim sparse-mode
ip route-cache flow
mpls netflow egress
mpls label protocol ldp
mpls ip
ppp multilink
ppp multilink group 12
service-policy output cbwfq-voice20per
ip flow-export source FastEthernet0/0/0.10
ip flow-export version 9 origin-as
ip flow-export destination XX.XX.XX.XX 9996 -
CRS does not appear to be healthy
Hi all,
i'm using oracle database 10g with RAC (02 nodes).
Before we had database name named abdwh, and our co dba has removed this and changed it to abdatawh and unregister the service from crs by using the command: crs_unregister ora.abdwh.abdwh1.inst. But after this command our cRS had problem and not working, when i do the command crsctl check crs i got the following error:
CSS appears healthy
CRS does not appear to be healthy
EVM appears healthy
when i do crs_stat command i got also an error like this:
CRS-0210: Could not find resource 'ora.abdwh.abdwh1.inst'.
Does anyboby can help me how i can solve this problem. How to remove the resource ora.abdwh.abdwh1.inst from CRS because we don't use it now, it was our old database instance.
Thanks and regards
raitsarevo.Our platform is Oracle 10g (10.2.0.3) on HPUX RAC
I tried the command you give but in vain:
oracle@ab-dwh1:/home/oracle$ srvctl remove service -d abdwh -i abdwh2
PRKO-2001 : Invalid command line syntax
oracle@ab-dwh1:/home/oracle$
oracle@ab-dwh1:/home/oracle$
oracle@ab-dwh1:/home/oracle$ srvctl remove instance -d abdwh -i abdwh2 -f
CRS-0184: Cannot communicate with the CRS daemon.
PRKR-1056 : invalid registry entry ora.abdwh.db found; should be of form ab-dwh2
oracle@ab-dwh1:/home/oracle$ srvctl remove service -d abdwh -i abdwh2
PRKO-2001 : Invalid command line syntax
oracle@ab-dwh1:/home/oracle$ srvctl remove service -d abdwh -s 'ora.abdwh.abdwh2.inst -i abdwh2
oracle@ab-dwh1:/home/oracle$ srvctl remove service -d abdwh -s ora.abdwh.abdwh2.inst -i abdwh2
PRKO-2007 : Invalid instance name: abdwh2
oracle@ab-dwh1:/home/oracle$ srvctl remove service -d abdwh -s abdwh -i abdwh2
PRKO-2120 : The internal database service abdwh cannot be managed with srvctl.
Thanks for the help
raistaervo -
Install ASM on Solaris RAC 10g
Hello,
I installed CRS and database software on two nodes RAC 10.2.0.4 Solaris x86-64 5.10, latest updates for Solaris. I have no error with crs.
Problems description:
1) When I run DBCA to create ASM it fails to create it on the nodes, with error ORA-03135: connection lost contact.
2) I see ORA-29702 into the logs (error occurred in Cluster Group Service operation
Cause: An unexpected error occurred while performing a CGS operation.
Action: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors.)
Question:
Do you think that the problem is that interface 10.0.0.21 node1-priv-fail2 is started? (see bellow bdump/alert_+ASM1.log).
This interface 10.0.0.21 node1-priv-fail2 is the one that frozens the prompt when I try ssh oracle@node1-priv-fail2 from node2?
Possible solution: I saw Metalink 283684.1 but don't know if/what to change in my interfaces.
Details:
I think is something with the interfaces, but I don't know what.
- One thing I noticed is that is not possible to ssh from node1 to node2-priv-fail2 (this I wad told is the private standby loopback insterface). The same is from node2 to node1-priv-fail2, it gives a frozen prompt.
- in /etc/hosts on both nodes I have:
+127.0.0.1 localhost+
+172.17.1.17 node1+
+172.17.1.18 node1-fail1+
+172.17.1.19 node1-fail2+
+172.17.1.20 node1-vip+
+172.17.1.29 node2 loghost+
+172.17.1.30 node2-fail1+
+172.17.1.31 node2-fail2+
+172.17.1.32 node2-vip+
+10.0.0.1 node1-priv+
+10.0.0.11 node1-priv-fail1+
+10.0.0.21 node1-priv-fail2+
+10.0.0.2 node2-priv+
+10.0.0.12 node2-priv-fail1+
+10.0.0.22 node2-priv-fail2+
Do you think that the problem is that interface 10.0.0.21 node1-priv-fail2 is started (see bdump/alert_+ASM1.log).
This interface 10.0.0.21 node1-priv-fail2 is the one that frozens the prompt when I try ssh oracle@node1-priv-fail2 from node2?
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 e1000g2 10.0.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 e1000g3 10.0.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 e1000g0 172.17.0.0 configured from OCR for use as a public interface
Interface type 1 e1000g1 172.17.0.0 configured from OCR for use as a public interface
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
large_pool_size = 12582912
instance_type = asm
cluster_database = TRUE
instance_number = 1
remote_login_passwordfile= EXCLUSIVE
++background_dump_dest = /opt/app/oracle/db/admin/+ASM/bdump++
++user_dump_dest = /opt/app/oracle/db/admin/+ASM/udump++
++core_dump_dest = /opt/app/oracle/db/admin/+ASM/cdump++
Cluster communication is configured to use the following interface(s) for this instance
+10.0.0.1+
+10.0.0.21+
node1:oracle$ oifcfg getif
e1000g0 172.17.0.0 global public
e1000g1 172.17.0.0 global public
e1000g2 10.0.0.0 global cluster_interconnect
e1000g3 10.0.0.0 global cluster_interconnect
node1:oracle$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.17.1.17 netmask ffff0000 broadcast 172.17.255.255
groupname orapub
e1000g0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
inet 172.17.1.18 netmask ffff0000 broadcast 172.17.255.255
e1000g0:2: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 2
inet 172.17.1.20 netmask ffff0000 broadcast 172.17.255.255
e1000g1: flags=39040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED,STANDBY> mtu 1500 index 3
inet 172.17.1.19 netmask ffff0000 broadcast 172.17.255.255
groupname orapub
e1000g2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 10.0.0.1 netmask ff000000 broadcast 10.255.255.255
groupname oracle_interconnect
e1000g2:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
inet 10.0.0.11 netmask ff000000 broadcast 10.255.255.255
e1000g3: flags=39040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED,STANDBY> mtu 1500 index 5
inet 10.0.0.21 netmask ff000000 broadcast 10.255.255.255
groupname oracle_interconnectHi,
for a 10g RAC you need:
- a host-IP for every node
- a private IP for every node
- a virtual IP for every node
Host-IP and Private IP must be assigned to both hosts and conenction between the hosts using either the host-IP or the private IP must be possible.
Is is possible to build the RAC and ASM only with the private IP without the public and the virtual IP, if yes how?The term "private" and "public" does not refer to public IPs. It refers to the fact "private" is only for communication between the nodes and public for communication between the client and database.
For a successful installation you need at least these three IPs on each system.
So for instance your public IPs reside in the network 192.168.1.0/255.255.255.0 and your private interconnect network can be 192.168.2.0/255.255.255.0. Both networks consists of private (i.e. non-routeable) IPs. -
Endeca initialize_services give encoding exception
HI I am in process of creating a new Endeca Product catalog Integration app. I was successfully able to deploy and see the sample Discover-data ref app but this does not seem to create record store in CAS. So I followed the same deployment steps for "discover-data-catalog-integration". I was able to create and deploy app using deployment template in ToolsAndFrameworks but when i initialize the app I get exception mentioned below:
What could possibly be wrong? which file it is trying to parse that is not right?
I found "\n" after D: in <app>/test_data\baseline\rs_baseline_data.xml. I removed it but to no avail. It still gives the same exception. Is it a bug?
Version for CAS and ToolsAndFrameworks is 3.1.1.
Setting EAC provisioning and performing initial setup...
[03.22.13 16:13:34] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[03.22.13 16:13:35] INFO: Setting definition for application 'CRS'.
[03.22.13 16:13:36] INFO: Setting definition for host 'AuthoringMDEXHost'.
[03.22.13 16:13:36] INFO: Setting definition for host 'LiveMDEXHostA'.
[03.22.13 16:13:36] INFO: Setting definition for host 'ReportGenerationHost'.
[03.22.13 16:13:36] INFO: Setting definition for host 'WorkbenchHost'.
[03.22.13 16:13:36] INFO: Setting definition for host 'ITLHost'.
[03.22.13 16:13:37] INFO: Setting definition for component 'AuthoringDgraph'.
[03.22.13 16:13:37] INFO: Setting definition for component 'DgraphA1'.
[03.22.13 16:13:38] INFO: Setting definition for script 'PromoteAuthoringToLive'.
[03.22.13 16:13:38] INFO: Setting definition for custom component 'WorkbenchManager'.
[03.22.13 16:13:38] INFO: Updating provisioning for host 'ITLHost'.
[03.22.13 16:13:38] INFO: Updating definition for host 'ITLHost'.
[03.22.13 16:13:38] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[03.22.13 16:13:40] INFO: Setting definition for custom component 'IFCR'.
[03.22.13 16:13:40] INFO: Updating provisioning for host 'ITLHost'.
[03.22.13 16:13:40] INFO: Updating definition for host 'ITLHost'.
[03.22.13 16:13:40] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[03.22.13 16:13:42] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[03.22.13 16:13:44] INFO: Setting definition for component 'LogServer'.
[03.22.13 16:13:44] INFO: Setting definition for script 'DaySoFarReports'.
[03.22.13 16:13:44] INFO: Setting definition for script 'DailyReports'.
[03.22.13 16:13:45] INFO: Setting definition for script 'WeeklyReports'.
[03.22.13 16:13:45] INFO: Setting definition for script 'DaySoFarHtmlReports'.
[03.22.13 16:13:45] INFO: Setting definition for script 'DailyHtmlReports'.
[03.22.13 16:13:45] INFO: Setting definition for script 'WeeklyHtmlReports'.
[03.22.13 16:13:45] INFO: Setting definition for component 'WeeklyReportGenerator'.
[03.22.13 16:13:46] INFO: Setting definition for component 'DailyReportGenerator'.
[03.22.13 16:13:46] INFO: Setting definition for component 'DaySoFarReportGenerator'.
[03.22.13 16:13:47] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.
[03.22.13 16:13:48] INFO: Setting definition for component 'DailyHtmlReportGenerator'.
[03.22.13 16:13:48] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'.
[03.22.13 16:13:49] INFO: Setting definition for script 'BaselineUpdate'.
[03.22.13 16:13:49] INFO: Setting definition for script 'PartialUpdate'.
[03.22.13 16:13:49] INFO: Setting definition for component 'ConfigurationGeneratorForge'.
Exception:
java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.components.encoding.UTF8Encoder.writeEncoded(UTF8Encoder.java:81)
at org.apache.axis.encoding.SerializationContext.writeSafeString(SerializationContext.java:1289)
at org.apache.axis.encoding.ser.SimpleSerializer.serialize(SimpleSerializer.java:104)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.ArraySerializer.serialize(ArraySerializer.java:414)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Exception:
java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.io.IOException: java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
{http://xml.apache.org/axis/}hostname:nodswl0129
java.io.IOException: java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:317)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Caused by: java.io.IOException: java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
... 21 more
Exception:
java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.components.encoding.UTF8Encoder.writeEncoded(UTF8Encoder.java:81)
at org.apache.axis.encoding.SerializationContext.writeSafeString(SerializationContext.java:1289)
at org.apache.axis.encoding.ser.SimpleSerializer.serialize(SimpleSerializer.java:104)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.ArraySerializer.serialize(ArraySerializer.java:414)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.SOAPPart.getContentLength(SOAPPart.java:229)
at org.apache.axis.Message.getContentLength(Message.java:510)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:371)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
Exception:
java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at org.apache.axis.SOAPPart.getContentLength(SOAPPart.java:229)
at org.apache.axis.Message.getContentLength(Message.java:510)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:371)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.endeca.eac.client.ProvisioningPortSOAPBindingStub.addComponent(ProvisioningPortSOAPBindingStub.java:1068)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:838)
at com.endeca.soleng.eac.toolkit.component.Component.setDefinition(Component.java:815)
at com.endeca.soleng.eac.toolkit.Controller.provision(Controller.java:691)
at com.endeca.soleng.eac.toolkit.Controller.execute(Controller.java:235)
at com.endeca.soleng.eac.toolkit.Controller.main(Controller.java:134)
[03.22.13 16:13:50] SEVERE: Caught an exception while checking provisioning.
Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
com.endeca.soleng.eac.toolkit.component.Component setDefinition - Caught exception while setting component definition.
Caused by org.apache.axis.AxisFault
org.apache.axis.AxisFault makeFault - ; nested exception is:
java.io.IOException: java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
Caused by java.io.IOException
org.apache.axis.encoding.ser.BeanSerializer serialize - java.io.IOException: java.lang.IllegalArgumentException: The char '0xc' after 'D:' is not a valid XML character.
Failed to setup EAC application.
D:\folders\installations\endeca\apps\CRS\control>Problem is with AppConfig.xml file, check ConfigurationGeneratorForge component configuration. Path defined might be wrong.
Please provide the configuration here to provide more help.
If you are asking questions about Guided Search, you might have better luck if you ask questions in Technical Questions
-Srikanth -
Link errors when tag-switching enabled
I have 4 6506 with SUP720-3BXL connected via 100Mb ethernet links as below. (you may have to copy the diagram to look at it using a fixed font)
r3---utp---r4
|.........|
media......|
converter..|
|.........|
fibre....Telstra 2Mb Ethernet service
|.........|
media......|
converter..|
|.........|
r1--fibre--r2
On the link between r1 and r3 I am getting CRC errors and runts for about 5% of packets.
When I turn off tag-switching on that link I get no errors so it doesn't appear to be a physical link problem.
No other links are showing these symptoms.
Any ideas as to what could be causing this?
Michaelrepeat after me (as many time as necessary)
a layer 1 problem is not an mpls problem
a layer 1 problem is not an mpls problem
a layer 1 problem is not an mpls problem
a layer 1 problem is not an mpls problem
Switch interface is set for 100Mb full-duplex
Media converter is set for 100Mb full-duplex also, but this media converter also has a DIP switch labelled 'force'
I changed this DIP switch and everthing runs perfectly.
I hate media converters. -
A Chairde,
Am having problems setting up MPLS between a AS5350 and 7609 , I have used commands stated in this link, enable MPLS incrementally on a network.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/switch_c/xcprt4/xcdtagc.pdf
The commands below are added to each router, and some troubleshooting.
7609
ip cef distributed
interface Loopback0
ip address 192.168.254.1 255.255.255.255
tag-switching advertise-tags
interface GigabitEthernet3/12
ip address 192.168.230.162 255.255.255.248
mpls label protocol tdp
tag-switching ip
AS5350
ip cef
mpls label protocol tdp
tag-switching advertise-tags
interface Loopback0
ip address 192.168.254.2 255.255.255.255
interface FastEthernet0/0
ip address 192.168.230.161 255.255.255.248
duplex auto
speed auto
mpls ip
h323-gateway voip interface
h323-gateway voip id cnibhco111 ipaddr 192.168.230.129 1719
h323-gateway voip h323-id cnibhco112
h323-gateway voip tech-prefix 71401
h323-gateway voip tech-prefix 0030
h323-gateway voip bind srcaddr 192.168.230.161
ip rsvp bandwidth 64 64
cnibhco112#sh tag-switching tdp neighbor
Peer TDP Ident: 192.168.254.1:0; Local TDP Ident 192.168.230.161:0
TCP connection: 192.168.254.1.49842 - 192.168.230.161.711
State: Oper; PIEs sent/rcvd: 18/23; Downstream
Up time: 00:12:54
TDP discovery sources:
FastEthernet0/0, Src IP addr: 192.168.230.162
Addresses bound to peer TDP Ident:
192.168.100.17 192.168.100.25 159.107.212.49 172.16.8.81
192.168.230.130 192.168.230.77 192.168.230.81 192.168.254.1
192.168.210.6 192.168.127.6 192.168.210.106 192.168.127.66
192.168.127.138 192.168.210.146 192.168.210.142 192.168.210.122
192.168.210.17 192.168.230.140 192.168.230.26 192.168.230.74
192.168.230.10 192.168.230.14 192.168.127.130 192.168.127.142
192.168.230.6 192.168.230.70 192.168.230.34 192.168.210.178
192.168.200.25 192.168.210.126 192.168.232.1 192.168.231.1
192.168.200.17 192.168.210.102 190.168.200.245 190.168.200.225
190.168.201.241 192.168.230.98 192.168.210.14 190.168.201.201
190.168.201.209 192.168.210.162 192.168.210.210 190.168.201.205
192.168.230.38 190.168.200.249 190.168.200.217 190.168.200.253
192.168.230.162
cnibhco112#
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
cnibhco112#traceroute 192.168.254.1
Type escape sequence to abort.
Tracing the route to 192.168.254.1
1 192.168.230.162 0 msec 0 msec *
cnibhco112#traceroute 192.168.230.162
Type escape sequence to abort.
Tracing the route to 192.168.230.162
1 192.168.230.162 0 msec 0 msec *
cnibhco112#Ro,
Thanks for the respone, have been playin, with MPLS for last few hours.
The routing between the loopbacks is now working, can PING 7609 Loopback from AS5350 ,and vice versa. (used static routes).
Having problem with TDP / LDP on routers,
mpls label protocol ldp / tdp command works correctly on both routers, but the
tag-switching tdp router-id Loopback0 force
command works on the 7609, but when I add it onto the AS5350 , the command "mpls ldp router-id Loopback0 force" appears on the startup script.
The opposite is true for the 7609 , you add MPLS LDP command, and TAG-SWITCHING command appears instead.
Any Ideas, as different configs of this leave me with forwarding table with both tags added, but not been able to ping the loopbacks !!!
When I can ping bot loopbacks, the OUTGOING TAG , disapears.....
Problem is LOOPBACK Commands on bot routers default to LDP (AS5350) , or TDP (7609). Any Ideas ...
mpls label protocol tdp
tag-switching tdp router-id Loopback0 force
mpls label protocol tdp
mpls ldp router-id Loopback0 force
cnibhco100#sh tag-switching forwarding-table 192.168.254.2 detail
Local Outgoing Prefix Bytes tag Outgoing Next Ho
tag tag or VC or Tunnel Id switched interface
18 17 192.168.254.0/24 0 Gi3/12 192.168.2
MAC/Encaps=14/18, MRU=1500, Tag Stack{17}
00097CA3293000127FCDBA808847 00011000
No output feature configured
Per-packet load-sharing
cnibhco100#traceroute 192.168.254.2
Type escape sequence to abort.
Tracing the route to 192.168.254.2
1 192.168.230.161 [MPLS: Label 17 Exp 0] 0 msec 0 msec 0 msec
2 192.168.230.162 0 msec 0 msec 0 msec
But no PINGING 192.168.254.2
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
17 18 192.168.254.0/24 1915668 Fa0/0 192.168.230.162
MAC/Encaps=14/18, MRU=1500, Tag Stack{18}
00127FCDBA8000097CA329308847 00012000
No output feature configured
Per-packet load-sharing
cnibhco100#sh tag-switching forwarding-table 192.168.254.2 detail
Local Outgoing Prefix Bytes tag Outgoing Next Ho
tag tag or VC or Tunnel Id switched interface
18 17 192.168.254.0/24 752551 Gi3/12 192.168.2
MAC/Encaps=14/18, MRU=1500, Tag Stack{17}
00097CA3293000127FCDBA808847 00011000
No output feature configured
Per-packet load-sharing
WHEN BOTH LOCAL AND OUTGOING TAG, CANNOT PING EITHER WAY !!!
HAVE LABEL PROTOCOL AND LOOPBACK FORCE on AS5350
HAVE LABEL PROTOCOL ON 7609
WHEN ADD LOOPBACK FORCE on 7609 , CAN PING BOTH LOOPBACKS,
BUT OUTGOING TAG DISAPEARS
cnibhco112#PING 192.168.254.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.254.2, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
cnibhco112#sh tag-switching forwarding-table 192.168.254.1 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
17 Untagged 192.168.254.0/24 598678 Fa0/0 192.168.230.162
MAC/Encaps=0/0, MRU=1504, Tag Stack{}
No output feature configured
Per-packet load-sharing
cnibhco112#
mpls label protocol tdp
tag-switching tdp router-id Loopback0 force -
Problem with "call redirect" in CRS script
Hi all,
I have just started to get myself familiar with scripting in Cisco CRS (version 5.0(2) but have run in
to a problem which I do not understand.
I have created four applications and three queues. One application is just a menu script, that
when the appropriate key is pressed, redirects callers with the "call redirect" function to the
trigger entry number of one of the other three applications which is assigned to a queue.
When a call goes directly to the trigger, not through the menu script, the call is correctly added
to the historical reporting database. When the call is redirected by the menu script, it will not
show up in historical reporting.
scenario:
external number1 --> Menu --> choice 1 --> call redirect(external number2)
--> choice 2 --> call redirect(external number3)
--> choice 3 --> call redirect(external number4)
external number2 --> queue1
external number3 --> queue2
external number4 --> queue3
Thank you for your help.
kind regards
AndreasHello Jonathan,
for instance in the Contact Service Queue Activity Report (by CSQ) the calls, redirected by the menu
script, do not show up in the total/handled or abandoned calls count. In realtime reporting an active call
coming from the menu script is shown as reserved.
thank you
kind regards
Andreas -
HTTPS certificate problem on MPLS
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Tableau Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Hi everyone,
We are currently migrating our network from IP to MPLS and we encounter an issue with a only one application using security certificat through HTTPS. All other services are OK such as HTTP, FTP, Mailing, etc.
Network description :
The network architecture is composed by 4 core routers (which play the role of P and PE at the same time) and 2 borders routers (B1 and B2) linked to Internet via STM1 - POS interfaces.
Each borders are both connected to two core routers (C1 and C2) by GigabitEthernet links.
Please also note that there is a DPI (Deep Packet Inspector, model Arbor 100) between each border and core.
Core routers C1,C2, C3 and C4 are connected to each other by GigabitEthernet links.
B1 and B2 are linked to Internet by STM1 (POS) using eBGP.
OSPF is used as the infrastructures routing protocol between all equipments.
(cf the network diagram attached)
Configuration :
When migrating to MPLS, we fixed interfaces MTU at 9216 and the MPLS MTU at 1512 on all concerned interfaces from Core to Border routers.
Below is a sample configuration.
mpls ip
mpls label protocol ldp
mpls ldp router-id loopback0
interface GigabitEthernet1/1
mtu 9216
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 XXXXXXXXXXX
ip ospf network point-to-point
ip ospf cost 1
ip ospf hello-interval 1
mpls mtu 1512
mpls ip
Problem :
The service application uses a server on the local network (linked via CE router) which send https requests and files to a server located in the Internet.
When MPLS is activated only on the Core-To-Core interfaces (C1, C2, C3 and C4) the application is working properly.
But when the MPLS is expanded on Core-To-Border / Border-To-Core interfaces, this specific application fails as it appears that the certificate server sees a corrupted frame, some bits have been added to the normal frame. But all other services (HTTP, FTP, everything,)
Below are major differences between Border and Core routers connection schemes:
A DPI equipment between Core and Border,
GibabitEthernet are used for links Border-To-Core and Core-To-Core, STM1(POS) is used for links Border-To-Internet (IP)
The MTU size on STM1 interface is fixed at 4470, MTU size of 9216 is assigned to GE interfaces (Border-To-Core, Core-To-Core)
Regards.Hi,
Would it be possible to disable the functionality of the DPI (passthrough mode?) and test again?
MPLS labels or not on the packet should not make a difference wrt HTTPS only (in theory).
Since you mention corrupted frames, taking a packet capture should show you if this is true or not.
Thanks,
Luc
Maybe you are looking for
-
When is Apple coming with an update to fix Snow Leopard???
I can't tell you how LONG I've waited to upgrade to Snow Leopard from Tiger! I bought it THE DAY it came out, manually backed up everything I had to my External Drives (OVER 6TB worth of data!) and to my surprise installing Snow Leopard was just like
-
I imported different trips to different catalogs on different external hard drives. Later renamed external HDs. I want to combine catalogs and have my source (NEF) files all together on one drive. I'm not really sure how to get those source files
-
Dreamweaver CC impossible to use on MacBook Pro 13" ?
Hi, I have a 13" MacBook Pro 2012 (classic, not retina). I installed Dreamweaver CC yesterday to continue working on a site I'm developing (I had it on my Mac desktop but needed to work while away from home). I found the workspace layout of Dreamweav
-
Today I bought a Cinema Display with a Mini DVI connector. Unfortunately I did not realise that my MacPro only got normal DVI. Is there by chance a connector and where can I by it?
-
firefox currently always opens a new url in the taB THAT IS CURRENTLY OPEN. i WANT IT TO OPEN IN A TAB NEXT TO THE ON THAT IS CURRENTLY OPEN. hOW DO i DO THAT?