Receiving route

Hello,
I am trying to understand the following. I have a PE(7200-SF02) router peering with 10 other PE routers and one E-BGP, all these routers are sending a default route to each other, but this router only shows 2 learned routes in the RIB-IN:
7200-SF02#show ip bgp v v vrfData 0.0.0.0
BGP routing table entry for 100:3:0.0.0.0/0, version 1007
Paths: (3 available, best #2, table vrfData)
Advertised to peer-groups:
mbgp-ut mbgp-sf
P1 P2, imported path from 100:1:0.0.0.0/0
10.0.0.3 (metric 2) from 10.0.0.3 (10.0.0.3)
Origin IGP, metric 0, localpref 100, valid, internal
Extended Community: RT:100:1,
mpls labels in/out 142/98
26749 3356
69.x.x.x from 69.x.x.x (x.x.x.x)
Origin IGP, localpref 100, valid, external, best
Extended Community: RT:100:1,
mpls labels in/out 142/nolabel
P1 P2, (received-only)
x.x.x.x from x.x.x.x (x.x.x.x)
Origin IGP, localpref 100, valid, external,
mpls labels in/out 142/nolabel
On another router which has the same peerings and route targets I show:
7200-SF04#show ip bgp v v vrfData 0.0.0.0
BGP routing table entry for 100:1:0.0.0.0/0, version 333461
Paths: (12 available, best #11, table vrfData)
Advertised to peer-groups:
mbgp-ut mbgp-sf
P1 P2, imported path from 100:3:0.0.0.0/0
10.0.0.2 (metric 2) from 10.0.0.2 (10.0.0.2)
Origin IGP, metric 0, localpref 100, valid, internal
Community: no-export
Extended Community: RT:100:1,
mpls labels in/out 212/142
P1 P2
10.0.0.4 (metric 2) from 10.0.0.4 (10.0.0.4)
Origin IGP, metric 0, localpref 100, valid, internal
Community: no-export
Extended Community: RT:100:1,
mpls labels in/out 212/206
P1 2828
10.0.0.5 (metric 5) from 10.0.0.5 (10.0.0.5)
Origin IGP, metric 0, localpref 100, valid, internal
Extended Community: RT:100:1,
mpls labels in/out 212/66
P1 2828
10.0.0.6 (metric 5) from 10.0.0.6 (10.0.0.6)
Origin IGP, metric 0, localpref 100, valid, internal
Extended Community: RT:100:1,
mpls labels in/out 212/254
P1 2828
10.0.0.10 (metric 4) from 10.0.0.10 (10.0.0.10)
Origin IGP, metric 0, localpref 100, valid, internal
Extended Community: RT:100:1,
mpls labels in/out 212/123
P1 2828
10.0.0.1 (metric 4) from 10.0.0.1 (10.0.0.1)
Origin IGP, metric 0, localpref 100, valid, internal
Extended Community: RT:100:1,
mpls labels in/out 212/121
P1 P2
CUT OUTPUT DUE TO LIMIT
I see the other routers sending this:
200-SF04#show ip bgp v a neighbors 10.0.0.2(SF02) advertised-routes
BGP table version is 333779, local router ID is 10.0.0.7
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 100:1 (default for vrf vrfData)
*> 0.0.0.0 xxxxxx 0 P1 P2 i
The only difference is that they have a different route distinguisher, but don't know how the RD is relevant since the route targets are the same and the RD are only locally significant.
This routers are running the same version.
TIA

No filtering going on.
show ip bgp v a summ
BGP router identifier 10.0.0.2, local AS number 65520
BGP table version is 1522, main routing table version 1522
788 network entries using 95348 bytes of memory
926 path entries using 59264 bytes of memory
157 BGP path attribute entries using 9420 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
1 BGP community entries using 24 bytes of memory
100 BGP extended community entries using 3888 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 167992 total bytes of memory
1 received paths for inbound soft reconfiguration
BGP activity 903/115 prefixes, 1104/178 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.0.0.1 4 65520 1707 1810 1522 0 0 1d04h 7
10.0.0.3 4 65520 1706 1836 1522 0 0 1d04h 3
10.0.0.4 4 65520 1780 1836 1522 0 0 1d04h 117
10.0.0.5 4 65520 1783 1810 1522 0 0 1d04h 92
10.0.0.6 4 65520 1745 1810 1522 0 0 1d04h 99
10.0.0.7 4 65520 1789 1836 1522 0 0 1d04h 81
10.0.0.8 4 65520 1761 1836 1522 0 0 1d04h 98
10.0.0.9 4 65520 1706 1836 1522 0 0 1d04h 3
10.0.0.10 4 65520 1707 1810 1522 0 0 1d04h 7
10.0.0.11 4 65520 1735 1836 1522 0 0 1d04h 23
x.x.x.x.7 4 xxxx 1705 1778 1522 0 0 1d04h 1
Which part of the config. is relevant?
Only difference is that the RD on that particular vrf is different.
router bgp 65520
no synchronization
bgp log-neighbor-changes
neighbor mbgp-ut peer-group
neighbor mbgp-ut remote-as 65520
neighbor mbgp-ut update-source Loopback0
neighbor mbgp-ut soft-reconfiguration inbound
neighbor mbgp-sf peer-group
neighbor mbgp-sf remote-as 65520
neighbor mbgp-sf update-source Loopback0
neighbor mbgp-sf soft-reconfiguration inbound
neighbor 10.0.0.1 peer-group mbgp-ut
neighbor 10.0.0.3 peer-group mbgp-sf
neighbor 10.0.0.4 peer-group mbgp-sf
neighbor 10.0.0.5 peer-group mbgp-ut
neighbor 10.0.0.6 peer-group mbgp-ut
neighbor 10.0.0.7 peer-group mbgp-sf
neighbor 10.0.0.8 peer-group mbgp-sf
neighbor 10.0.0.9 peer-group mbgp-sf
neighbor 10.0.0.10 peer-group mbgp-ut
neighbor 10.0.0.11 peer-group mbgp-sf
no auto-summary
address-family vpnv4
neighbor mbgp-ut send-community both
neighbor mbgp-sf send-community both
neighbor mbgp-sf route-map noexport out
neighbor 10.0.0.1 activate
neighbor 10.0.0.3 activate
neighbor 10.0.0.4 activate
neighbor 10.0.0.5 activate
neighbor 10.0.0.6 activate
neighbor 10.0.0.7 activate
neighbor 10.0.0.8 activate
neighbor 10.0.0.9 activate
neighbor 10.0.0.10 activate
neighbor 10.0.0.11 activate
exit-address-family
address-family ipv4 vrf vrfData
redistribute static
redistribute ospf 101 match internal external 1 external 2 route-map igp2bgp
neighbor x.x.x.7 remote-as xxxxx
neighbor x.x.x.7 activate
neighbor x.x.x.7 soft-reconfiguration inbound
neighbor x.x.x.7 route-map metric out
no auto-summary
no synchronization
exit-address-family
All of my neighbors are sending a default, but I am only receiving the one from 10.0.0.3 and the peer on vrfData

Similar Messages

Reassigning IPv6 temporary address when it receives router advertisements

Hi everybody.
I've just met a problem with IPv6 connectivity.
*My environment*
I list my environment that I tested as follows.
1. MacBook Pro (A)
OS Version: 10.6.4
Card Type: AirPort Extreme (0x14E4, 0x93)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.131.16.1)
IPv6 temporary address setting: net.inet6.ip6.use_tempaddr=1
2. AP+Router
TimeCapsule
N.B., I experienced same problem under other sets of router and access point (Cisco's ones). So, let me skip to write the detail of this.
3. MacBook Pro (B) (No problem with this Laptop)
OS Version: 10.6.4
Card Type: AirPort Extreme (0x168C, 0x87)
Firmware Version: Atheros 5416: 2.0.19.10
IPv6 temporary address setting: net.inet6.ip6.use_tempaddr=1
N.B., All user data and settings are transferred to MacBook Pro (A). I think the difference between these two MacBooks is about hardwares.
*The problem*
1. Connect the MacBook Pro (A) to AP+Router.
2. Receive IPv6 router advertisement from the router. (router lifetime=1800, valid lifetime=2592000, preferred lifetime=604800)
3. Assign both IPv6 EUI-64 address and temporary address.
4. Receive IPv6 router advertisement from the router again, 70 sec after previous one.
5. Both the EUI-64 and temporary addresses are removed, and then same EUI-64 address and _new_ temporary address are assigned.
The problem here is that MacBook Pro (A) configures _new_ temporary address, or it removes old temporary address. This causes additional issues on TCP connections because TCP sessions become no longer available after the temporary address has changed.
This problem is not experienced my old MacBook Pro (B); i.e., it keeps the temporary address even after receiving router advertisements.
All the data and setting in MacBook Pro (A) are transferred from MacBook Pro (B).
Therefore, I think the problem is due to hardwares.
I prefer to use IPv6 because I'm in a networking group and also prefer to use temporary addresses.
Do you experience same problem or any suggestions to me?
If you need additional environment description, please ask me.
Thank you in advance, and sorry for my poor English.
Message was edited by: scyphus

This bug has been stealthily fixed in the update http://support.apple.com/kb/HT4250 today, though I have received no reply from Apple bug reporter site.

Information on Receiving Routing types

Hello all,
I am working on Purchase order receipts and internal requisitions receipt.
There is a field named 'Routing Receipt type' at the PO Line level. (Its there at several levels like Organization, Item, PO level)
It is 3 Types
1. Standard Receipt
supplier ----------> sub inventory
2. Direct delivery
supplier---->recieving area(stagging area)------>sub inventory
3. Inspection Required
supplier----> recieving area------->inspection(done)---->sub inventory.
but if we create receipt for Standard , Inspection types -- its creating 1 transaction with DELIVER line in rcv_transactions table And onhand quantity is not incrementing.
If we create receipt for Direct delivery -- its creating 2 trxs with DELIVER and RECEIVE lines in rcv_transactions table and onhand qty is incrementing.
Can you tell me when the Inv qty wil be incremented for Standard, Inspection Routing types. Do we need to run any other programs or anything to do inorder to increment th inv qty.
Thanks inadvance,
Amarnadh js

Hi Amarnadh,
I think you have the options a bit jumbled, so I have changed to what is the functionality depending on routing option. I have put in the the source or location and in ( ) the operation that is moving the goods. Once the DELIVER bit is executed the Inv wty is increased. DELIVER is done manually with the routing options Standard, Inspection Required.
1. Standard Receipt
supplier (Receipt) receiving area (Deliver) sub inventory
2. Direct delivery
supplier (Receipt and Deliver) sub inventory
3. Inspection Required
supplier (Receipt) to be inspected (inspection) Inspected/Receiving Area (Deliver) sub inventory.
/Niels LM

Sh bgp: received & advertised routes

Dear all:
In reference at the commands:
- sh bgp neighbor A.B.C.D
- sh bgp neighbor A.B.C.D received routes
- sh bgp neighbor A.B.C.D advertised-routes
For example:
ROUTER#sh bgp neighbor A.B.C.D
Policy for incoming advertisements is PEERING-IN
Policy for outgoing advertisements is PEERING-OUT
1 accepted prefixes, 0 are bestpaths
Cumulative no. of prefixes denied: 8974070.
No policy: 0, Failed RT match: 0
By ORF policy: 0, By policy: 8974070
Prefix advertised 77, suppressed 0, withdrawn 2
In output this command we have # Prefixes:
1 accepted & 0 are bestpaths (after policy)
advertised 77, suppressed 0, withdrawn 2 (after policy)
8974070 prefix are deny
But, when you execute the next command:
ROUTER#sh bgp neighbor A.B.C.D received routes
Processed 503233 prefixes, 503233 paths
In output this command we have# Prefixes = 503233
And when you execute the next command:
ROUTER#sh bgp neighbor A.B.C.D advertised-routes
Processed 73 prefixes, 73 paths
In output this command we have:
73 prefixes advertised at peer
The question is:
What's the different between counter 8974070 and 503233 (prefix received before apply policy)?
What's the different between counter 77 (or 75 = 77 - 2 withdrawn) and 73 (prefix advertised before apply policy)?
Exist only one command that help at see total prefix received/advertised (different a sh bgp neighbor A.B.C.D received routes) ?
Thanks.

Not really because OSPF does not advertise routes it sends LSAs to it's peers.
So you need to look at the OSPF database ie. -
"sh ip ospf database"
which will show you all the LSAs the router is aware of.
In terms of all the LSAs the router has received it will show all of those but it will also show you LSAs that were generated by the router itself although the advertising router IP will point to that being the case.
In terms of all the LSAs the router advertises again it depends on the area and how that has been configured.
So for example an ABR might well have external LSAs (which aren't tied to any area in the OSPF database) but that doesn't necessarily mean it is advertising them to peers within an area as it could have been configured not to.
So it gives you a good idea but you need to also work out a few things for yourself as well.
Jon

ESYU: R11.5.10/R12 - ROI를 이용하여 Receiving Transaction을 Correct 하는 방법1

Purpose
Oracle Inventory Management - Version: 11.5.10 to 12.0
11.5.10/11i.SCM_PF.J/11i.PRC_PF.J (and higher)에서 ROI가 지원하는 새로운
functionality를 알아본다.
-. CORRECT to DELIVER to Inventory transactions
ROI를 이용하여 Standard Purchase Order에 대한 Receiving Transaction을
Correct 할 수 있는 방법은?
Solution
아래 예제 script는 Destination Type이 'inventory'인 Purchase Order의
Devlier to Inventory Transaction을 Receiving Open Interface(ROI)를 이용하여
Correct 하는 방법을 위한 것이다.
각 script는 가장 포괄적인 사용을 위해 Lot와 Serial을 control 하는 item을 가지고
test 되었다.
각 script는 한 record 만 RCV_TRANSACTIONS_INTERFACE,
MTL_TRANSACTION_LOTS_INTERFACE, MTL_SERIAL_NUMBERS_INTERFACE
tables에 insert 할 것이다.
Following SAMPLE scripts are intended
만일 item이 단지 standard item(non lot, serial control) 이라면, record는 단지
RCV_TRANSACTIONS_INTERFACE table에만 insert 된다.
Note: 11.5.10 (or 11i.SCM_PF.J)로 upgrade 하였거나 11.5.10을 install 한 후
Enhanced Receiving Validation을 위해 Note 367396.1에 설명되어져 있는
Recommended Patches list가 적용되어져 있는지 확인해야 한다.
1) Standard Purchase Order number # 6752 생성
Inventory Item = Lot-Serial-Controlled-1
Shipment Receiving Routing = Standard Receipt
Destination Type Code = Inventory
2) Item Lot-Serial-Controlled-1은 lot/serial control item
SQL> Select mp.organization_id Org_Id, mp.organization_code Org_Code,
msi.inventory_item_id, msi.segment1, decode(to_char(msi.lot_control_code),
'2','Y',
'1','N') LOT_CONTROL,
decode(to_char(msi.serial_number_control_code),
'1','None',
'2','Predefined',
'5','Dynamic at INV receipt',
'6','Dynamic at SO issue') SERIAL_CONTROL
from mtl_system_items_b msi,mtl_parameters mp
where msi.segment1 like '&item' and msi.organization_id=mp.organization_id;
위 select 결과:
LOT_CONTROL='Y' and SERIAL_CONTROL='Dynamic at INV receipt'
inventory_item_id=169845 for item=Lot-Serial-Controlled-1
3) 수량=10에 대해 Receipt number # 7746 생성(Receive and Deliver Transactions)
item=Lot-Serial-Controlled-1
Lot Number=S246
Serial Number from SN0001 to SN0010
4) RCV_TRANSACTIONS_INTERFACE table에 insert 할 필요한 정보를 찾기 위해
아래 script를 실행한다.
SQL> Select RSH.RECEIPT_NUM ,
PH.SEGMENT1 PO_NUMBER,
RT.TRANSACTION_ID ,
RT.TRANSACTION_TYPE ,
RT.TRANSACTION_DATE ,
RT.QUANTITY ,
RT.UNIT_OF_MEASURE ,
RT.SHIPMENT_HEADER_ID ,
RT.SHIPMENT_LINE_ID ,
RT.SOURCE_DOCUMENT_CODE ,
RT.DESTINATION_TYPE_CODE ,
RT.EMPLOYEE_ID ,
RT.PARENT_TRANSACTION_ID ,
RT.PO_HEADER_ID ,
RT.PO_LINE_ID ,
PL.LINE_NUM ,
PL.ITEM_ID ,
PL.ITEM_DESCRIPTION ,
PL.UNIT_PRICE ,
RT.PO_LINE_LOCATION_ID ,
RT.PO_DISTRIBUTION_ID ,
RT.ROUTING_HEADER_ID,
RT.ROUTING_STEP_ID ,
RT.DELIVER_TO_PERSON_ID ,
RT.DELIVER_TO_LOCATION_ID ,
RT.VENDOR_ID ,
RT.VENDOR_SITE_ID ,
RT.ORGANIZATION_ID ,
RT.SUBINVENTORY ,
RT.LOCATOR_ID ,
RT.LOCATION_ID,
RSH.SHIP_TO_ORG_ID
From
RCV_TRANSACTIONS RT,
RCV_SHIPMENT_HEADERS RSH,
PO_HEADERS_ALL PH,
PO_LINES_ALL PL
Where
RSH.RECEIPT_NUM = '&RECEIPT_NUMBER'
AND PH.SEGMENT1 like '&PO_NUMBER'
AND PH.PO_HEADER_ID = PL.PO_HEADER_ID
AND RT.PO_HEADER_ID = PH.PO_HEADER_ID
AND RT.SHIPMENT_HEADER_ID = RSH.SHIPMENT_HEADER_ID;
이 script는 RECEIPT_NUM=7746, PO_NUMBER=6752에 대해 아래의 두 개
records를 return 한다.
For TRANSACTION_TYPE=RECEIVE
TRANSACTION_ID=302978
DESTINATION_TYPE_CODE=RECEIVING
PARENT_TRANSACTION_ID=-1
QUANTITY=10
UNIT_OF_MEASURE=Each
SHIPMENT_HEADER_ID=250536
SHIPMENT_LINE_ID=261490
SOURCE_DOCUMENT_CODE=PO
EMPLOYEE_ID=13706
PO_HEADER_ID=36665
PO_LINE_ID=42138
ITEM_ID=169845
PO_LINE_LOCATION_ID=76782
DELIVER_TO_PERSON_ID=null
DELIVER_TO_LOCATION_ID=null
VENDOR_ID=7927
VENDOR_SITE_ID=4724
ORG_ID=204
SUBINVENTORY=null
LOCATOR_ID=null
LOCATION_ID=204
SHIP_TO_ORG_ID=204
For TRANSACTION_TYPE=DELIVER
TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
QUANTITY=10
UNIT_OF_MEASURE=Each
SHIPMENT_HEADER_ID=250536
SHIPMENT_LINE_ID=261490
SOURCE_DOCUMENT_CODE=PO
EMPLOYEE_ID=13706
PARENT_TRANSACTION_ID=302978
PO_HEADER_ID=36665
PO_LINE_ID=42138
ITEM_ID=169845
PO_LINE_LOCATION_ID=76782
DELIVER_TO_PERSON_ID=13706
DELIVER_TO_LOCATION_ID=204
VENDOR_ID=7927
VENDOR_SITE_ID=4724
ORG_ID=204
SUBINVENTORY=Stores
LOCATOR_ID=null
LOCATION_ID=204
SHIP_TO_ORG_ID=204
5) Delivery transaction RCV_TRANSACTIONS.TRANSACTION_ID=302979 와
관련된 Lot/Serial 정보를 확인하기 위해 아래 script를 실행한다.ACTION_ID=302979
SQL> Select LOT_TRANSACTION_TYPE,LOT_NUM,QUANTITY
from RCV_LOT_TRANSACTIONS
where source_transaction_id=&RTtransaction_id;
SQL> Select SERIAL_TRANSACTION_TYPE,SERIAL_NUM,SHIPMENT_LINE_ID,TRANSACTION_ID,
LOT_NUM
from RCV_SERIAL_TRANSACTIONS
where source_transaction_id=&RTtransaction_id;
Script 결과로 10 records가 보여지는데 각각은 SN0001 and SN0010 사이의 serianl no를
갖는다.
예를 들어,
SERIAL_NUM=SN0005 and SERIAL_NUM=SN0006
SERIAL_TRANSACTION_TYPE=TRANSACTION
SHIPMENT_LINE_ID=261490
SOURCE_TRANSACTION_ID=302979
TRANSACTION_ID=302979
LOT_NUM=S246
CORRECT to DELIVER to INVENTORY Transaction for PURCHASE ORDER Example
1) DELIVER to INVENTORY Transaction에 대한 CORRECT record를 ROI를 이용해
insert 한다.(RCV_TRANSACTIONS.TRANSACTION_ID=302979)
Delivered 된 수량을 10에서 8로 correct, SERIAL_NUM=SN0005 and SERIAL_NUM=SN0006
와 LOT_NUM=S246를 correct 한다.
Insert:
-. RCV_TRANSACTIONS_INTERFACE, MTL_TRANSACTION_LOTS_INTERFACE,
MTL_SERIAL_NUMBERS_INTERFACE tables에 1 record 씩 insert
SQL> INSERT INTO RCV_TRANSACTIONS_INTERFACE
(INTERFACE_TRANSACTION_ID,
GROUP_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
TRANSACTION_TYPE,
TRANSACTION_DATE,
PROCESSING_STATUS_CODE,
PROCESSING_MODE_CODE,
TRANSACTION_STATUS_CODE,
QUANTITY,
UNIT_OF_MEASURE,
ITEM_ID,
EMPLOYEE_ID,
SHIPMENT_HEADER_ID,
SHIPMENT_LINE_ID,
RECEIPT_SOURCE_CODE,
VENDOR_ID,
FROM_ORGANIZATION_ID,
FROM_SUBINVENTORY,
FROM_LOCATOR_ID,
SOURCE_DOCUMENT_CODE,
PARENT_TRANSACTION_ID,
PO_HEADER_ID,
PO_LINE_ID,
PO_LINE_LOCATION_ID,
PO_DISTRIBUTION_ID,
DESTINATION_TYPE_CODE,
DELIVER_TO_PERSON_ID,
LOCATION_ID,
DELIVER_TO_LOCATION_ID,
VALIDATION_FLAG
VALUES
(rcv_transactions_interface_s.nextval, --INTERFACE_TRANSACTION_ID
rcv_interface_groups_s.nextval, --GROUP_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATE_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'CORRECT', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
-2, --QUANTITY
'Each', --UNIT_OF_MEASURE
169845, --ITEM_ID
13706, --EMPLOYEE_ID
250536, --SHIPMENT_HEADER_ID
261490, --SHIPMENT_LINE_ID
'VENDOR', --RECEIPT_SOURCE_CODE
7927, --VENDOR_ID
204, --FROM_ORGANIZATION_ID
'Stores', --FROM_SUBINVENTORY
null, --FROM_LOCATOR_ID
'PO', --SOURCE_DOCUMENT_CODE
302979, --PARENT_TRANSACTION_ID
36665, --PO_HEADER_ID
42138, --PO_LINE_ID
76782, --PO_LINE_LOCATION_ID
78674, --PO_DISTRIBUTION_ID
'INVENTORY', --DESTINATION_TYPE_CODE
13706, --DELIVER_TO_PERSON_ID
204, --LOCATION_ID
204, --DELIVER_TO_LOCATION_ID
'Y' --Validation_flag
INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
LOT_NUMBER,
TRANSACTION_QUANTITY,
PRIMARY_QUANTITY,
SERIAL_TRANSACTION_TEMP_ID,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID
VALUES
( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'S246', --LOT_NUMBER
2, --TRANSACTION_QUANTITY
2, --PRIMARY_QUANTITY
MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --SERIAL_TRANSACTION_TEMP_ID
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --PRODUCT_TRANSACTION_ID
INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
FM_SERIAL_NUMBER,
TO_SERIAL_NUMBER,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID)
VALUES
(MTL_MATERIAL_TRANSACTIONS_S.CURRVAL,--TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'SN0005', --FM_SERIAL_NUMBER
'SN0006', --TO_SERIAL_NUMBER
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --PRODUCT_TRANSACTION_ID
Commit;
2) Data가 제대로 insert 되었는지 확인을 위해 아래 scripts를 실행한다.
SQL> Select * from RCV_TRANSACTIONS_INTERFACE where PO_HEADER_ID=36665
INTERFACE_TRANSACTION_ID=232850
GROUP_ID=25057
TRANSACTION_TYPE=CORRECT
QUANTITY=-2
PARENT_TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
RECEIPT_SOURCE_CODE=VENDOR
SOURCE_DOCUMENT_CODE=PO
SQL> Select * from MTL_TRANSACTION_LOTS_INTERFACE
where PRODUCT_TRANSACTION_ID=&interface_txn_id;
TRANSACTION_INTERFACE_ID=11300777
LOT_NUMBER=S246
TRANSACTION_QUANTITY=2
NoteIMARY_QUANTITY=2
SERIAL_TRANSACTION_TEMP_ID=11300777
NoteODUCT_TRANSACTION_ID=232850
SQL> Select * from MTL_SERIAL_NUMBERS_INTERFACE
where PRODUCT_TRANSACTION_ID=&interface_txn_id;
TRANSACTION_INTERFACE_ID=11300777
NoteODUCT_TRANSACTION_ID=232850
FM_SERIAL_NUMBER=SN0005
TO_SERIAL_NUMBER=SN0006
3) Purchasing Responsibility에서 특정 Group ID(GROUP_ID=25057)에 대해
'Receiving Transaction Processor'를 실행한다.
4) Navigate to Receiving / Receiving Transactions Summary
PO 6752에 대해 Receipt Number 7746 가 Receive, Delivery, Correct to Inventory
transactions이 발생했는지 확인한다.
SQL> Select * from RCV_TRANSACTIONS where PO_HEADER_ID=36665
It returns 3 records
For TRANSACTION_TYPE=RECEIVE
TRANSACTION_ID=302978
DESTINATION_TYPE_CODE=RECEIVING
PARENT_TRANSACTION_ID=-1
QUANTITY=10
For TRANSACTION_TYPE=DELIVER
TRANSACTION_ID=302979
DESTINATION_TYPE_CODE=INVENTORY
PARENT_TRANSACTION_ID=302978
QUANTITY=10
For TRANSACTION_TYPE=CORRECT
TRANSACTION_ID=302982
DESTINATION_TYPE_CODE=INVENTORY
PARENT_TRANSACTION_ID=302979
QUANTITY=-2
FROM_SUBINVENTORY=Stores
5) Navigate to Purchase Orders/Purchase Orders Summary
Shipment, Distribution level에서 PO Number 6752에 대해 아래 수량을
확인한다.
Quantity Received=10
Quantity Delivered=8
Reference
Note 335699.1

No Receiver agreement found for Sender

Hello,
I have a scenario like this : sending an IDoc from R/3 4.6c to R/3 4.7 through XI 3.0.
I am struck up with the follwoing Error in SXMB_MONI
"outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04"
The Complete TRACE is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPR46</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = F0EAB201EEA5F74A814EF22C32394FD0</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0009</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO____0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XI3</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SMART01</Trace>
<Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="1" type="T">outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
I have made neccesary Configurations for the Receiver agreement in the Configuration Directory...
Anybody could please help me out...
Regards,
Romit Arun Shankar

Hi Frank,
Many Thanks for your reply.The problem got sorted out and the IDoc(ORDERS04) which i send in SAP 4.6c gets into SAP 4.7 AS ORDERS04 but i have a new problem now....
I didnt use any mappings until now...but now i have to have the segment E1EDK14 filled up for Sales organisation, Distribution Channel, Division details as well as the material number. These segments will not be filled up when a PO is sent from the source system.These segments has to be filled only in the XI system...Is it ? or is there any other solution for it....
Now how we can have this segment E1EDK14 which can occur any number of times with constant values for SORG,DV,DC in the mapping process....
Waiting for ur replies....
Bye,
Romit Shankar Arun.
For this

IP routing utilizing Verizon private network (GRE tunnel) with remote cellular gateways

Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details). Time for some advice. My usual trade is controls engineering which generally require only basic knowledge of networking principals. However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system. I decided to use cellular technology to connect these remote sites back to the main SCADA system. Well the infrastructure is now in and it’s time to get these things talking. Basic topology description is as follows: Each remote site has an Airlink LS300 gateway. Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system. The Airlinks are provisioned by Verizon utilizing a private network with static IP's. This private networks address is 192.168.1.0/24. Back at the central office the SCADA computer is sitting behind a Cisco 2911. The LAN address of the central office is 192.168.11.0/24. The 2911 is utilizing GRE tunnels that terminate with Verizon. The original turn up was done with another contractor that did a basic config of the router which you will find below. As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks. I think I understand just about every part of the config below and think it is just missing a few items to be complete. I would greatly appreciate anyone’s help in getting this set up correctly. I also have a few questions about the set up that still don’t make sense to me, you will find them below the config. Thanks in advance.
no aaa new-model
ip cef
ip dhcp excluded-address 10.10.10.1
ip dhcp pool ccp-pool
import all
network 10.10.10.0 255.255.255.248
default-router 10.10.10.1
lease 0 2
ip domain name yourdomain.com
no ipv6 cef
multilink bundle-name authenticated
username cisco privilege 15 one-time secret
redundancy
crypto isakmp policy 1
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp key AbCdEf01294 address 99.101.15.99
crypto isakmp key AbCdEf01294 address 99.100.14.88
crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac
mode transport
crypto map VZW_VPNTUNNEL 1 ipsec-isakmp
description Verizon Wireless Tunnel
set peer 99.101.15.99
set peer 99.100.14.88
set transform-set VZW_TSET
match address VZW_VPN
interface Tunnel1
description GRE Tunnel to Verizon Wireless
ip address 172.16.200.2 255.255.255.252
tunnel source 22.20.19.18
tunnel destination 99.101.15.99
interface Tunnel2
description GRE Tunnel 2 to Verizon Wireless
ip address 172.16.200.6 255.255.255.252
tunnel source 22.20.19.18
tunnel destination 99.100.14.88
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
ip address 10.10.10.1 255.255.255.248
shutdown
duplex auto
speed auto
interface GigabitEthernet0/1
ip address 192.168.11.1 255.255.255.0
duplex auto
speed auto
interface GigabitEthernet0/2
ip address 22.20.19.18 255.255.255.0
duplex full
speed 100
crypto map VZW_VPNTUNNEL
router bgp 65505
bgp log-neighbor-changes
network 0.0.0.0
network 192.168.11.0
neighbor 172.16.200.1 remote-as 6167
neighbor 172.16.200.5 remote-as 6167
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip route 0.0.0.0 0.0.0.0 22.20.19.19
ip access-list extended VZW_VPN
permit gre host 99.101.15.99 host 22.20.19.18
permit icmp host 99.101.15.99 host 22.20.19.18
permit esp host 99.101.15.99 host 22.20.19.18
permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
permit gre host 22.20.19.18 host 99.101.15.99
permit gre host 22.20.19.18 host 99.100.14.88
access-list 23 permit 10.10.10.0 0.0.0.7
control-plane
end
So after spending countless hours analyzing every portion of this, I think that adding one line to this will get it going (or at least closer).
ip route 192.168.1.0 255.255.0.0 22.20.19.19
That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
Now for a couple of questions for those that are still actually hanging around.
#1 what is the purpose of the Ethernet address assigned to each tunnel? I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?). Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
#2 is the config above correct in pointing the default route to the physical Ethernet address? Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)? If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
#3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP. Or is TCP implicit in some way with the GRE permit?
I actually have alot more questions, but I will keep reading for now.
I really appreciate the time you all took to trudge through this. Also please feel free to point anything else out that I may have missed or that can be improved. Have a great day!

This post is a duplicate of this thread
https://supportforums.cisco.com/discussion/12275476/proper-routing-lan-through-verizon-private-network-gre-airlink-gateways
which has a response. I suggest that all discussion of this question be done through the other thread.
HTH
Rick

IDOC Receiver determines no receiving service

Hi,
I have send an R/3 IDOC successfully to XI and find the messag with status OK in the monitor, even the receiving service and the receiving interface is empty.
I have configured a message interface and the receiver has an appropriate communication channel using SOAP. In the repository there is a defined receiver and even in the SXI_cache I can see the receiver.
Has anyone an idea?
Thanks
Juergen

Hi Volker,
the cache is OK, here is the data form the monitor:
Date          Time                              sender     Namespace sender               Sender Interface          Receiver     Rceiver Interface
17.03.2006     05:42:53     SAPR3     urn:sap-com:document:sap:idoc:messages     REQOTE.PORDCR04.YFUTURA
and here is the SOAP header of the message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Trace level="1" type="T">User: RUGE</Trace>
<Trace level="1" type="T">Language: D</Trace>
<Trace level="1" type="T">XML-Conversion for all IDocs </Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling </Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling </Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag </Trace>
<Trace level="1" type="T">Queueid </Trace>
<Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPI01</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types </Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc </Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object </Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB </Trace>
<Trace level="1" type="T">COMMIT is expected by application ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="1" type="T">system-ID = TXI</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = D</Trace>
<Trace level="1" type="T">user = RUGE</Trace>
<Trace level="1" type="Timestamp">2006-03-17T04:42:53Z CET </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = 3B4CA10CF867924D9F60B752E345F378</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0005</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0005</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
I dont know how to increase the trace level, so ists still 1.
Thanks
Juergen

Errors about 'No receiver could be determined'

Hi all:
I am setting up one scenario about ' IDOC to file '.
When I send IDOC from one R3 system to XI , I meet with the following errors.
No receiver could be determined
The SOAP Error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The trace is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: KEN</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0012</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Could anybody give me some clue to debug this problem ?

Hi Jianhong,
Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.
Configure your receiver file adapter according to this:
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm
Do ask if you require further information.
Regards,
Chandra

3845 router failing to look up routes from routing table correctly!

Hi all,
Got a really strange issue which I am wondering if someone can point me in the right direction for. Facts of the issue:
- Some customers, all with a specific ISP, cannot access a hosted service we host internally
- External user can reach service but never gets a response - hence focussing on reachability of their public IP
- Cisco 3845 router used, peers with service provider over BGP - receives full internet routing tables
- All affected customers receive dynamic IP addresses within the same /10 public IP range
I received an example IP address and when doing "show ip route x.x.x.x" for this IP, the router responds "Subnet not in table". When trying to traceroute to the IP, the router doesnt even go to the next hop. However, the subnet is definitely in the routing table with the correct next hop (and, for complete information, is also within the BGP updates). Before anyone asks the question :) - yes I have definitely verified that the hosts are within this subnet.
If I put a static /32 route in for this specific IP address, everything works fine - then fails again once its taken out.
I literally cannot understand why the router is not correctly performing the lookup for the hosts within this subnet. I can understand a lot of potential reasons why the BGP received route wouldnt be placed in the routing table, but that is not the case here.
Some other factors (if applicable):
- Nothing showing in the logs
- Plenty memory available (despite the high number of routes)
- Plenty CPU resource available
- No default route is ran
I am going to restart the router and really expect this to resolve the issue (would log a TAC but this one is a bit time precious) - but it is frankly doing my head in and I assume I am missing something!
Any help or guidance would be appreciated!

Hi all,
Got a really strange issue which I am wondering if someone can point me in the right direction for. Facts of the issue:
- Some customers, all with a specific ISP, cannot access a hosted service we host internally
- External user can reach service but never gets a response - hence focussing on reachability of their public IP
- Cisco 3845 router used, peers with service provider over BGP - receives full internet routing tables
- All affected customers receive dynamic IP addresses within the same /10 public IP range
I received an example IP address and when doing "show ip route x.x.x.x" for this IP, the router responds "Subnet not in table". When trying to traceroute to the IP, the router doesnt even go to the next hop. However, the subnet is definitely in the routing table with the correct next hop (and, for complete information, is also within the BGP updates). Before anyone asks the question :) - yes I have definitely verified that the hosts are within this subnet.
If I put a static /32 route in for this specific IP address, everything works fine - then fails again once its taken out.
I literally cannot understand why the router is not correctly performing the lookup for the hosts within this subnet. I can understand a lot of potential reasons why the BGP received route wouldnt be placed in the routing table, but that is not the case here.
Some other factors (if applicable):
- Nothing showing in the logs
- Plenty memory available (despite the high number of routes)
- Plenty CPU resource available
- No default route is ran
I am going to restart the router and really expect this to resolve the issue (would log a TAC but this one is a bit time precious) - but it is frankly doing my head in and I assume I am missing something!
Any help or guidance would be appreciated!

BGP Advertised Routes two Peering

Dear all
I have issue with BGP behaviour. I have two BGP peering; from both I receive default route, but one of them,
AS 65472 is primary so I setup local preference in 200; it is because I want to use AS 65472 as internet
provider. The another one, AS 65472 is used as secundary internet access, but for internal network (private) is
used as primary. The issue is when try ping from LAN, can not reach internal network, seems to be that
becuase Local preference is setup within AS65472 and the packet try to go thru AS 65472 because local prefeence 200,
but I need that internal network go thru AS 65471.
I am sure that I am advertising network as I expect, but when is running BGP for both peering, it fails.
Here are go output for this situation:
7204VXR-SCT#sh ip bgp neighbors 172.16.40.37 received-routes
   Network          Next Hop            Metric LocPrf Weight Path
* i0.0.0.0          172.16.40.37             0    100      0 i
Total number of prefixes 1
7204VXR-SCT#sh ip bgp neighbors 172.16.40.37 advertised-routes
   Network          Next Hop            Metric LocPrf Weight Path
*> 10.10.200.0/30   0.0.0.0                  0         32768 i
*> 10.30.24.0/21    172.16.40.4              0         32768 i
*> 172.16.17.0/24   172.16.40.5              0         32768 i
*> 172.16.211.0/24 0.0.0.0                  0         32768 i
*> 172.18.56.16/29 0.0.0.0                  0         32768 i
*> 172.30.100.18/32 0.0.0.0                  0         32768 i
*> 172.31.0.20/30   0.0.0.0                  0         32768 i
7204VXR-SCT#sh ip bgp neighbors 190.97.254.241 received-routes
   Network          Next Hop            Metric LocPrf Weight Path
* 0.0.0.0          190.97.254.241                         0 65472 i
Total number of prefixes 1
   Network          Next Hop            Metric LocPrf Weight Path
*> 190.153.116.0/22 172.16.40.4              0         32768 i
*> 190.153.120.0/22 172.16.40.4              0         32768 i
*> 190.153.124.0/24 172.16.40.37            10         32768 i
router bgp 65471
bgp log-neighbor-changes
neighbor externalBGP peer-group
neighbor externalBGP remote-as 65472
neighbor externalBGP version 4
neighbor internalBGP-SCT peer-group
neighbor internalBGP-SCT remote-as 65471
neighbor internalBGP-SCT version 4
neighbor 172.16.40.37 peer-group internalBGP-SCT
neighbor 190.97.254.241 peer-group viginet
address-family ipv4
neighbor externalBGPsoft-reconfiguration inbound
neighbor externalBGProute-map viginet-in in
neighbor externalBGProute-map viginet-out out
neighbor internalBGP-SCT soft-reconfiguration inbound
neighbor internalBGP-SCT route-map internalBGP-SCT-out out
neighbor 172.16.40.37 activate
neighbor 190.97.254.241 activate
no auto-summary
no synchronization
network 10.10.200.0 mask 255.255.255.252
network 10.30.24.0 mask 255.255.248.0
network 172.16.17.0 mask 255.255.255.0
network 172.16.40.0 mask 255.255.255.0
network 172.16.211.0 mask 255.255.255.0
network 172.18.56.16 mask 255.255.255.248
network 172.30.100.18 mask 255.255.255.255
network 172.31.0.20 mask 255.255.255.252
network 190.153.116.0 mask 255.255.252.0
network 190.153.120.0 mask 255.255.252.0
network 190.153.124.0 mask 255.255.255.0
exit-address-family
ip route 172.16.40.36 255.255.255.252 Null0 250
ip route 190.153.116.0 255.255.252.0 172.16.40.4
ip route 190.153.120.0 255.255.252.0 172.16.40.4
ip prefix-list invalidas seq 10 permit 172.16.40.0/24
ip prefix-list invalidas seq 15 permit 10.30.24.0/21
ip prefix-list invalidas seq 20 permit 172.16.211.0/24
ip prefix-list invalidas seq 25 permit 172.18.56.16/29
ip prefix-list invalidas seq 30 permit 172.30.100.18/32
ip prefix-list invalidas seq 35 permit 10.10.200.0/30
ip prefix-list invalidas seq 40 permit 172.16.17.0/24
ip prefix-list invalidas seq 45 permit 172.31.0.20/30
ip access-list standard viginet-100
permit 190.153.116.0 0.0.3.255
permit 190.153.120.0 0.0.3.255
permit 190.153.124.0 0.0.0.255
route-map externalBGP-out permit 10
match ip address viginet-100
route-map externalBGP-in permit 10
set local-preference 200
route-map internalBGP-SCT-out permit 10
match ip address prefix-list invalidas

Hello.
If you want your internal network to go through peer 65471 (to 0.0.0.0/0), then why do you need AS 65472?
Could you please provide "show ip bgp 0.0.0.0/0"?

BGP received-only Question

Hi
From what I understand in the show ip bgp x.x.x.x/x output the received-only would be present when soft-reconfiguration inbound is configured and the route has been rejected by a policy i.e. a route map
What i have also found is that on many outputs i can see the exact same route in the output twice, one which has the received-only keyword and one doesn't.
Now for a specified neighbor we have a route map configured inbound which will change the weight based on the community value. It seems as though when a route map is configured and an attribute is changed that route appears in the output twice, one being modified and one which is unchanged. But this contradicts what is said on the Cisco website its states 'the received-only keyword will only show up if the route is denied by a policy', but its not.. it's just changed.
Has anyone had this discussion before? I would like to hear people's thoughts on the matter.
Thanks
Andre
corerouter#show ip bgp | b 10.141.54.0
* 10.141.54.0/23 10.199.10.18 0 64000 34406 65502 ?
*> 10.199.10.18 0 64000 34406 65502 ?
corerouter#sho ip bgp 10.141.54.0/23
BGP routing table entry for 10.141.54.0/23, version 1219279
Paths: (4 available, best #3, table Default-IP-Routing-Table)
Advertised to update-groups:
2 3 4 5 6 7
34406 65502
10.199.10.18 from 10.199.10.20 (82.196.60.60)
Origin incomplete, metric 0, localpref 100, weight 64000, valid, external
Community: 10199111
34406 65502, (received-only)
10.199.10.18 from 10.199.10.20 (82.196.60.60)
Origin incomplete, metric 0, localpref 100, valid, external
Community: 10199111
34406 65502
10.199.10.18 from 10.199.10.19 (82.196.60.1)
Origin incomplete, metric 0, localpref 100, weight 64000, valid, external, best
Community: 10199111
34406 65502, (received-only)
10.199.10.18 from 10.199.10.19 (82.196.60.1)
Origin incomplete, metric 0, localpref 100, valid, external
Community: 10199111

show ip bgp neighbor x.x.x.x received-routes
show ip bgp neighbor x.x.x.x routes
sho ip bgp a.b.c.d
If you found this page, like I did, while searching for "received-only" - that means that the route has only been received, but not entered in the routing table. This is good if you meant to block that route. But if that route is actually also installed in the routing table and you meant to block it, check your route-map, specifically your prefix-lists and you will likely find that you have an error with wither the IP address or the CIDR mask, resulting in a non-match condition. The inverse is also true if you intend to allow a route but you only see the "received-only" route, you probably have a typo in your route-map or prefix list. Below are some examples that might help.
Here are some BGP with route-map and prefix-list examples, although the data is not meaningful.
router bgp 1234
neighbor CARRIER1 peer-group
neighbor CARRIER1 route-map PROVIDER1-IN in
neighbor 6.7.8.9 peer group CARRIER1
route-map PROVIDER1-IN deny 5
match ip address prefix-list MyIPs
route-map PROVIDER1-IN permit 10
match ip address prefix-list GOOG APPL
ip prefix-list GOOG seq 5 permit 8.8.8.0/24 le 32
ip prefix-list GOOG seq 10 permit 8.8.4.4/32
ip prefix-list APPL seq 5 per 17.142.160.59/32
ip prefix-list APPL seq 10 per 17.178.96.0/24 le 32
ip prefix-list MyIPs seq 5 per 1.2.0.0/16 le 24
ip prefix-list MyIPs seq 10 per 2.3.4.0/24 le 32
ip prefix-list MyIPs seq 15 per 4.5.6.7/32

BGP advertised routes

Hi All,
Is it possible to find since how long a route being advertised to BGP neighbor?
To elaborate, if EBGP neighbors are up since 24 hours and among 10 routes advertised, at receiving router, 5 routes show the uptime as 12 hours, whereas other 5 routes show the uptime as 24 hours.
All 10 routes were present in advertising router's routing table for more than 24 hours.
Regards,
Nagabhushan

Hi,
when you issue on the advertising router
sh ip route x.x.x.x
for one particular prefix among those showing the uptime as 12 hours on the other router, do you see any " Last update from ... xxx ago"?
That should show you the last time the routing was changed on the advertising router (and BGP should have advertised the change that time).
Best regards,
Milan

BGP Router high process

What do we need to do if BGP Router contribute high process in CPU?
CPU utilization for five seconds: 97%/43%; one minute: 99%; five minutes: 92%
PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
44    36270732 35464661       1022 25.03% 15.21% 14.43%   0 BGP Router
325   7703860203228294256          0 10.47% 5.58% 5.24%   0 IP Input
455     7596596 28244228        268 5.59% 1.60% 0.82%   0 BGP I/O
543    13576608   8569950       1584 3.83% 18.94% 9.57%   0 BGP Task
   9   152474380 15201602      10030 2.07% 0.27% 0.57%   0 Check heaps
376    16372652   7777145       2105 1.83% 13.93% 13.76%   0 IP RIB Update
358    56785192 14452691       3929 0.95% 0.44% 0.52%   0 CEF: IPv4 proces
23    55656604 116191071        479 0.71% 0.51% 0.50%   0 ARP Input
348     5736736   7812055        734 0.63% 4.19% 5.03%   0 XDR mcast
546    36531108 132425650        275 0.63% 0.37% 0.28%   0 Port manager per
35    56337684 306101724        184 0.23% 0.42% 0.30%   0 IPC Seat Manager
330   287962916 871459868        330 0.23% 0.39% 1.61%   0 SNMP ENGINE
286      7682841067821917          0 0.15% 0.07% 0.07%   0 Ethernet Msec Ti
626      354112    825565        428 0.15% 0.11% 0.09%   0 IPv6 Input
   3      754316 523105917          1 0.15% 0.10% 0.09%   0 HSRP Common
385     2182508 14151135        154 0.15% 0.10% 0.14%   0 L3 Manager
317    44655884 658073408         67 0.07% 0.04% 0.21%   0 PDU DISPATCHER
395     4363480   4661440        936 0.07% 0.04% 0.05%   0 HIDDEN VLAN Proc
323     1161648 134374319          8 0.07% 0.04% 0.05%   0 VRRS Main thread
56     2269676   9230664        245 0.07% 0.08% 0.07%   0 Per-Second Jobs
240     1449416   1870109        775 0.07% 0.04% 0.05%   0 Compute load avg
243   1488814081309230003        113 0.07% 0.13% 0.76%   0 IP SNMP
CPU utilization for five seconds: 97%/43%; one minute: 99%; five minutes: 92%
PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
44    36270732 35464661       1022 25.03% 15.21% 14.43%   0 BGP Router
325   7703860203228294256          0 10.47% 5.58% 5.24%   0 IP Input
455     7596596 28244228        268 5.59% 1.60% 0.82%   0 BGP I/O
543    13576608   8569950       1584 3.83% 18.94% 9.57%   0 BGP Task
   9   152474380 15201602      10030 2.07% 0.27% 0.57%   0 Check heaps
376    16372652   7777145       2105 1.83% 13.93% 13.76%   0 IP RIB Update
358    56785192 14452691       3929 0.95% 0.44% 0.52%   0 CEF: IPv4 proces
23    55656604 116191071        479 0.71% 0.51% 0.50%   0 ARP Input
348     5736736   7812055        734 0.63% 4.19% 5.03%   0 XDR mcast
546    36531108 132425650        275 0.63% 0.37% 0.28%   0 Port manager per
35    56337684 306101724        184 0.23% 0.42% 0.30%   0 IPC Seat Manager
330   287962916 871459868        330 0.23% 0.39% 1.61%   0 SNMP ENGINE
286      7682841067821917          0 0.15% 0.07% 0.07%   0 Ethernet Msec Ti
626      354112    825565        428 0.15% 0.11% 0.09%   0 IPv6 Input
   3      754316 523105917          1 0.15% 0.10% 0.09%   0 HSRP Common
385     2182508 14151135        154 0.15% 0.10% 0.14%   0 L3 Manager
317    44655884 658073408         67 0.07% 0.04% 0.21%   0 PDU DISPATCHER
395     4363480   4661440        936 0.07% 0.04% 0.05%   0 HIDDEN VLAN Proc
323     1161648 134374319          8 0.07% 0.04% 0.05%   0 VRRS Main thread
56     2269676   9230664        245 0.07% 0.08% 0.07%   0 Per-Second Jobs
240     1449416   1870109        775 0.07% 0.04% 0.05%   0 Compute load avg
243   1488814081309230003        113 0.07% 0.13% 0.76%   0 IP SNMP

Hi,
BGP Router process is in charge to determine the best path and processes any route "churn". It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
(http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html)
So I suggest to check what make this process working hard. Depending on that you can choose what to do: bgp dampening (if you have many changes in advertisement received form a neighbor), tuning timer (if neighbor is flapping), using peer-group / update-groups to reduce the amount of job your BGP process has to do to process updates etc...
Have a look here: https://supportforums.cisco.com/discussion/11604471/high-cpu-usage-bgp-router-process
Bye,
enrico
PS please rate if useful

Proper routing for lan through verizon private network (GRE) to airlink gateways

Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details). Time for some advice. My usual trade is controls engineering which generally require only basic knowledge of networking principals. However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system. I decided to use cellular technology to connect these remote sites back to the main SCADA system. Well the infrastructure is now in and it’s time to get these things talking. Basic topology description is as follows: Each remote site has an Airlink LS300 gateway. Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system. The Airlinks are provisioned by Verizon utilizing a private network with static IP's. This private networks address is 192.168.1.0/24. Back at the central office the SCADA computer is sitting behind a Cisco 2911. The LAN address of the central office is 192.168.11.0/24. The 2911 is utilizing GRE tunnels that terminate with Verizon. The original turn up was done with another contractor that did a basic config of the router which you will find below. As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks. I think I understand just about every part of the config below and think it is just missing a few items to be complete. I would greatly appreciate anyone’s help in getting this set up correctly. I also have a few questions about the set up that still don’t make sense to me, you will find them below the config. Thanks in advance.
no aaa new-model
ip cef
ip dhcp excluded-address 10.10.10.1
ip dhcp pool ccp-pool
import all
network 10.10.10.0 255.255.255.248
default-router 10.10.10.1
lease 0 2
ip domain name yourdomain.com
no ipv6 cef
multilink bundle-name authenticated
username cisco privilege 15 one-time secret
redundancy
crypto isakmp policy 1
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp key AbCdEf01294 address 99.101.15.99
crypto isakmp key AbCdEf01294 address 99.100.14.88
crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac
mode transport
crypto map VZW_VPNTUNNEL 1 ipsec-isakmp
description Verizon Wireless Tunnel
set peer 99.101.15.99
set peer 99.100.14.88
set transform-set VZW_TSET
match address VZW_VPN
interface Tunnel1
description GRE Tunnel to Verizon Wireless
ip address 172.16.200.2 255.255.255.252
tunnel source 22.20.19.18
tunnel destination 99.101.15.99
interface Tunnel2
description GRE Tunnel 2 to Verizon Wireless
ip address 172.16.200.6 255.255.255.252
tunnel source 22.20.19.18
tunnel destination 99.100.14.88
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
ip address 10.10.10.1 255.255.255.248
shutdown
duplex auto
speed auto
interface GigabitEthernet0/1
ip address 192.168.11.1 255.255.255.0
duplex auto
speed auto
interface GigabitEthernet0/2
ip address 22.20.19.18 255.255.255.0
duplex full
speed 100
crypto map VZW_VPNTUNNEL
router bgp 65505
bgp log-neighbor-changes
network 0.0.0.0
network 192.168.11.0
neighbor 172.16.200.1 remote-as 6167
neighbor 172.16.200.5 remote-as 6167
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip route 0.0.0.0 0.0.0.0 22.20.19.19
ip access-list extended VZW_VPN
permit gre host 99.101.15.99 host 22.20.19.18
permit icmp host 99.101.15.99 host 22.20.19.18
permit esp host 99.101.15.99 host 22.20.19.18
permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
permit gre host 22.20.19.18 host 99.101.15.99
permit gre host 22.20.19.18 host 99.100.14.88
access-list 23 permit 10.10.10.0 0.0.0.7
control-plane
end
So after spending countless hours analyzing every portion of this, I think that adding one line to this will get it going (or at least closer).
ip route 192.168.1.0 255.255.0.0 22.20.19.19
That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
Now for a couple of questions for those that are still actually hanging around.
#1 what is the purpose of the Ethernet address assigned to each tunnel? I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?). Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
#2 is the config above correct in pointing the default route to the physical Ethernet address? Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)? If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
#3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP. Or is TCP implicit in some way with the GRE permit?
I actually have alot more questions, but I will keep reading for now.
I really appreciate the time you all took to trudge through this. Also please feel free to point anything else out that I may have missed or that can be improved. Have a great day!

My first comment is that you have two posts in this forum and as far as I can tell they are exact duplicates, other than changing the title of the posts. It is better to figure what you want to ask and then to ask once.
My second comment is that you have given us information about your central site. At some point we may also need some information about what is at the remote and how that is set up. But for now we will deal with what we know about your site.
Before I deal with your specific questions I will comment that if you are able to access the remote airlinks that it is a pretty good indicator that the tunnels are probably working. But to understand the significance of this it would help if you clarify for us what address is on the local computer when you change the subnet to 255.255.0.0.
Also what you have shown us allows us to see that BGP is configured but provides no insight into whether BGP is working or now. It would provide helpful information if you would post the output of show ip bgp sum.
So to address your specific questions:
You suggest that adding a static route for 192.168.1.0 might be part of the solution. But we have no information about what that network is or its significance. So we have no way to know whether the static route would help or not. But my guess (based on very scant information and therefore based mostly on assumptions) is that if BGP is working correctly that the static route is not needed.
1) asks about an Ethernet address on the tunnel. I assume that you really meant to ask about the IP address assigned to the tunnel. The reason that the tunnel needs it own IP address is that we want a unique subnet assigned to the tunnel. If we used the address from the physical interface as you suggest then both tunnels would have the same address and that implies that they both connect to the same place, and that assumption is not correct.
2) Yes it is correct to point the default route to the IP address that is the next hop from the Ethernet interface. You might want to have a route pointing at the tunnel address for remote subnets reached via the tunnel. But in looking at the config and trying to understand what was intended it is pretty obvious that running BGP over the tunnel is intended to learn the remote addresses over the tunnel and therefore there is no need for static routes for the remote resources.
3) You should not need an additional permit for TCP 402. The TCP packet will be carried through the tunnel and the access list you are referring to will see the packet will modbus polling as GRE traffic and not as TCP traffic.
HTH
Rick

Receiving route

Similar Messages

Maybe you are looking for