PTP Transport mode

Hi All,
I'm trying to configure the PTP on the ASR9001 and I'd like to use the transport mode ETHERNET instead of IPv4.
From the RP/0/RSP0/CPU0:ASR9001-2#show ptp interfaces it look likes that the Ethernet capability is not supported:
TenGigE0/0/1/1 is in Master state
PTP port number: 1
IPv4 transport: IPv4 address 10.85.52.5
Linestate: Up
Mechanism: Two-step delay-request-response
Sync rate: every second
Announce rate: every 2 seconds, timeout 3 intervals
Min Delay-Request rate: every second
CoS: General 6, Event 6, DSCP: General 46, Event 46
Platform capabilities:
    Supported:     One-step, Two-step, IPv4, Unicast, Master, Slave
    Not-supported: Ethernet, Multicast, IPv6, Source IP
    Max-Sync-rate: 128 per second
Master state only
0 Unicast peers
Can you please support me?
thanks in advance.
BR// Saverio

Here is a good doc on that:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080901caa.shtml

Similar Messages

Can't get Transport Mode to Work

Just messing around in a lab with a few routers. Trying to bring up transport mode first on an IPSEC tunnel. All seems correct, but it constantly comes up in Tunnel Mode. I can't see why?
Can anyone see anything obvious?
Enclosed are configs and a WireShark capture of the output - as you can see it's Tunnel Mode - and not Transport.
The output of "show crypto ipsec sa" demonstrates the fact that its Tunnel mode.

Thanks for the reply Rick.
The access list is a catch-all :-
access-list 100 permit ip any any
It's a strange one to grasp really.
"traffic to be protected has the same IP addresses as the IPSec peers "
My routers are peers - 192.168.1.1 & 192.168.1.2
If i ping from .1 to .2, or .2 to .1, in my mind this represented "the same IP addresses as the IPSEC peers". Other than the ping, i don't know how i can simulate peer traffic that would come up in transport mode. Do you?
Once the IPSEC link is built, and it's a tunnel link, i don't think it will ever divert away from this and create a separate transport mode link, so all traffic will ride across it.
It's not a big deal i suppose. Router to router connections don't seem to support transport mode.
I know how the packets would look like, which is the most important thing really. The headers are just in different positions.
Thanks again for taking the time to answer Rick.

LAyer 3 to Layer 3 LWAPP Transport mode

Has anyone moved from layer 2 to Layer 3 transport mode?
I want to see if it is easy as changing the transport mode on the 4124 controller and assigning an IP address to the AP.
Thanks!

Pretty much it's that easy. You will also have a new interface on the controller after it reboots. The interface will be an AP-Manager. You need to assign this interface an address in the same subnet as the Management interface. After that, you will also need to either set an IP address on the AP's and specify the system name of the primary controller, or setup a DHCP scope for them, and specify the Option 43/60 so the AP can find the controller.
Here is the link to the Upgrade guide that references the option 43 information.
http://www.cisco.com/en/US/partner/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp125304
Also, the document is a bit lacking, it does not tell you what the VCI strings should be for all of the AP's, so here they are.
Airespace/Cisco 1200/1000
Airespace.AP1200
Cisco 1200/1230
Cisco AP c1200
Cisco 1240
Cisco AP c1240
Cisco 1130
Cisco AP c1130
Let us know if you need any more assitance.
Here is another document, that is a little more tuned towards an IOS DHCP server, and it does have the VCI for all the AP's.
http://www.cisco.com/en/US/products/ps6548/products_installation_guide_chapter09186a00807158ec.html

Importing content: transport modes 'all', 'data'

I try to import *.epa file and get error for evere entity in package:
PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.
It seems the thing is in transport mode. How to change it?

Hi Denis,
I am facing same problem whiile importing BP for ESS & MSS (ERP 2005NW04s) into EP NW04(6.0 sp14).
Either i can modify all .properties files as suggested by you or we can upgrade EP to 04s (7.0).
Did you face any problem after modifying all 'data' to 'all'; is it working fine?
Subhash

IPSec (transport mode) load balancing via CSM

Suppouse that there is two servers providing service for remote aplications. Those aplications using IPSEC in transport mode. I would like to put at front CSM to load-balance beetwen both of them (persist via SRC IP is ok for me).
Have you any expirience with transort mode? IMHO it is not possible becouse of ip header changes? (I have no exact informatin that resign from AH transforms are possible)
What when changing to tunnel mode. Have you ever seen that configuraion working?

I think you can for the transport mode. I have not had any luck with the Tunnel mode.

Transportation mode from Sea to Air(AFS route determination)?

Dear Gurus,
1. PO is created and the ex-factory date in PO is 19th Dec 2010 and
2. Delivery date in PO is 27th Jan 2011 and now, the transportation mode is by default coming as ZS(Sea) through AFS route determination process.Now, user is trying to change the transportation mode(ME22N txn) from ZS(Sea) to ZA(Air), it does not change always and if it does some time,
3. then the transportation mode will again restores back to ZS but the
4. planed delivery time changes to ZA value thereby causing Inconsistency between transportation mode and its value.
Please help to solve this issue ASAP.

thanks...

IPSEC ESP SECURITY PROTOCOL IN TUNNEL & TRANSPORT MODE

My query is that who much IP Pachet is
added/expanded in following two case.
1. ESP IN TRANSPORT MODE.
2. ESP IN TUNNEL MODE

Transport mode: 37 bytes 3DES or 63 bytes AES
Tunnel mode 57 bytes 3 DES or 83 bytes AES
M.
Hope that helps, rate if it does

WLC Guidelines L3 Transport Mode and functionality

Hi,
I'm implementing a LWAPP Solution and I would like to have some confirmation about LWAPP solution
If I understand right all the traffic from the WLAN client have to pass through the dynamic interface of the controller and there are no
opportunity to configure it in another way...
Best Practises suggest that LWAPP AP should be placed in a different VLAN (IP Subnet) from the LWAPP WLAN client and to use LWAPP L3 Transport Mode...
Which are the drawback if I put the LWAPP APs on the same VLAN(IP Subnet) as the LWAPP APs? If I implement the solution in this way I can still configure
LWAPP L3 transport Mode or it isn't working???
Thanks for sharing your opinion

Actually, Layer 2 LWAPP mode is considered depreciated by Cisco. Also, only 4400 controllers support Layer-2 LWAPP discovery. 2000 series WLCs doesn't.
The reason why Layer-3 LWAPP is preferable than Layer-2 LWAPP is "Layer-3 LWAPP discovery involves a series of steps in its algorithm and finds the candidate list of controller in different ways like DHCP option43, OTAP, DNA etc..,
Layer-2 LWAPP discovery just uses one method of controller discovery that is by using layer-2 broadcast in a LWAPP frame. Since, layer-3 lwapp uses a series of controller discovery methods, it is more secured and reliabel than layer-2 LWAPP mode.

IPsec transport mode with IPv6?

I am trying to set up IPsec in a IPv6 environment. However, when I configure "crypto map" I wasn't able to "set peer" to a IPv6 peer address. Why is that?
I used Virtual Tunnel Interface instead of Crypto Map and it worked. But I need to IPsec in transport mode instead of tunnel mode.

I think here is no support for mixed mode which is ipv6 traffic through ipv4 tunnel and vice versa in VTI . Better solution is Gre tunnel.

IPSec Transport Mode

Hi,
I am trying to setup an IPSec transport mode policy from my test server in the office to a VM in Azure in order to replicate data to a RODC.
Both servers sit behind a NAT firewall and have private IP addresses.
I have created a security policy at each end which specifies both the private address of the server and the public address of the cloud service (Azure) and firewall (On Prem)
I have opened firewall ports on both sides to allow both 500/udp and 4500/udp
Using the Network Monitor tool, I can see some IKE transmissions but I can't ping/rdp either way.
Any ideas?
Thanks
Dave

Hi Dave,
We've not heard from you yet. I assume the information provided by me has helped. I am marking my reply as answered now.
In case the information did not help, please feel free to unmark the answer and come back to us with your comments.
Best regards.
Steven Lee
TechNet Community Support

IPSEC transport mode and GET VPN

All,
I am about to implement GET VPN while read the following from Cisco's website:
IPsec transport mode suffers from fragmentation and reassembly limitations and must not be used in
deployments where encrypted or clear packets might require fragmentation.
I just do not understand why transport mode will suffer fragmentation and reassembly while it had less overhead than tunnel mode.

One thing to understand about Tran sport mode vs Tunnel mode (ipsec) is thst Transport is used between acyual source and destination of the ip protocol
Tunnel mode actually not only authenticates but also encrypts at the higher layers of the pckt
Pix
VPN
IP layers
Tunnel actual source and destination is encrypted at the upper layers and therefor when the packet gets to the IP Layer, it really doesnt know about or care about the iCV signature already withinh the upper PIX layer.
Also from a security standpoint because of the fact that tunnel mode encrpyts and authenticated the ip infoemation whereas transport only authenticates packets

Additional Transportation mode on Traval Request form

Hi all,
Can we add more transportation modes (in request transportation/accommodation) on travel request form on SAP R/3!
i.e. Employee can request for company pool car but currently flight, train, rental car options are available on travel request form.
Awaiting for responses!

Hi Raynard Coscolluela,
Thanks for your response.
but where i have to activate additional services on travel request form..
if it is in schema (t-code FITVFELD) there which node i have to activate ?
Thanks in advance for your time!

[TP Transport Mode] Set to 'data_and_acl' by default

Hi,
Is this possible to change the standard customizing that makes 'data' as the default entry for the Transport Mode of newly created Transport Packages ?
Why is this 'data' by default? I don't see much interest for this or am I missing something ??
Thanks in advance for your answer.
Best regards,
Guillaume

Hi Guillaume,
In previous version there was only one option ( so i guess backwards compatible).
If you really would like to adjust this, find out which portal application takes control for transport. Download it, adjust the default setting (probably in the portalapp.xml) and upload it.
But I would strongly suggest: just click the data_and_acl option. Changing these minor this is not recommended!
Another option is to create a 'template transport package'. If you need a new transport, copy the template, change name / description and add the appropriate objects to it.
Cheers,
Noël Hendrikx

Trying to import tables from datapump file which done using transportable mode

Hi using impdp on oracle 11.2.0.3 and have a dumpfile which contains export of tables which done using transportable tablespace mode.
Want to import 3 of the tables just form file cobncerned into another database using impd but not working
Error
ORA-39002: invalid operation
ORA-39061: import mode FULL conflicts with export mode TRANSPORTABLE
{code}
userid=archive/MDbip25
DIRECTORY=TERMSPRD_EXTRACTS
DUMPFILE=archiveexppre.964.dmp
LOGFILE=por_200813.log
PARALLEL=16
TABLES=ZPX_RTRN_CDN_STG_BAK,ZPX_RTRN_STG_BAK,ZPX_STRN_STG_BAK
REMAP_TABLESPACE=BI_ARCHIVE_DATA:BI_ARCHIVE_LARGE_DATA
REMAP_TABLESPACE=BI_ARCHIVE_IDX:BI_ARCHIVE_LARGE_IDX
{code}
Any ideas

Hi,
Export command
{code}
procedure export_old_partitions_to_disk (pi_SEQ_num NUMBER)
is
h1 number; -- Datapump handle
dir_name    CONSTANT    ALL_directories.DIRECTORY_NAME%type :='DATA_EXPORTS_DIR'; -- Directory Name
v_file_name varchar2(100);
v_log_name varchar2(100);
v_job_status ku$_Status;          -- The status object returned by get_status
    v_job_state VARCHAR2(4000);
    v_status ku$_Status1010;
    v_logs ku$_LogEntry1010;
    v_row PLS_INTEGER;
    v_current_sequence_number archive_audit.aa_etl_run_num_seq%type;
    v_jobState                user_datapump_jobs.state%TYPE;
begin
-- Set to read only to make transportable
execute immediate ('alter tablespace ARCHIVED_PARTITIONS read only');
-- Get last etl_run_num_seq by querying public synonym ARCHIVE_ETL_RUN_NUM_SEQ
-- Need check no caching on etl_run_num_seq
select last_number - 1
into v_current_sequence_number
from ALL_SEQUENCES A
WHERE A.SEQUENCE_NAME = 'ETL_RUN_NUM_SEQ';
v_file_name := 'archiveexppre.'||PI_SEQ_NUM||'.dmp';--v_current_sequence_number;
v_log_name := 'archiveexpprelog.'||PI_SEQ_NUM||'.log';--v_current_sequence_number;
dbms_output.put_line(v_file_name);
dbms_output.put_line(v_log_name);
-- Create a (user-named) Data Pump job to do a schema export.
-- dir_name := 'DATA_EXPORTS_DIR';
h1 := dbms_datapump.open(operation =>'EXPORT',
job_mode =>'TRANSPORTABLE',
remote_link => NULL,
job_name    => 'ARCHIVE_OLD_PARTITIONS_'||PI_SEQ_NUM);
dbms_datapump.add_file(handle =>h1,
                         filename => v_file_name,
                         directory => dir_name,
                         filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE,
                         reusefile => 1); -- value of 1 instructs to overwrite existing file
dbms_datapump.add_file(handle =>h1,
                         filename => v_log_name,
                         directory => dir_name,
                         filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE,
                         reusefile => 1); -- value of 1 instructs to overwrite existing file
dbms_datapump.metadata_filter(
      handle => h1,
      name   => 'TABLESPACE_EXPR',
     VALUE    => 'IN(''ARCHIVED_PARTITIONS'')'
dbms_datapump.metadata_filter(handle =>h1,
                         name => 'TABLE_FILTER',
                         value => 'BATCH_AUDIT');
--dbms_datapump.set_parameter(h1, 'TRANSPORTABLE', 'ALWAYS');
-- Start the datapump_job
dbms_datapump.start_job(h1);
begin
      NULL;
     --dbms_datapump.detach(handle => h1);
end;
dbms_output.put_line('Job has completed');
dbms_datapump.wait_for_job(h1,v_jobState);
dbms_output.put_line('Status '||v_jobState);
   dbms_output.put_line('Job has completed');
execute immediate ('alter tablespace ARCHIVED_PARTITIONS read write');
exception
    when others then
      dbms_datapump.get_status(handle => h1,
                             mask => dbms_datapump.KU$_STATUS_WIP,
                             timeout=> 0,
                            job_state => v_job_state,
                            status => v_job_status);
               dbms_output.put_line(v_job_state);
        MISC_ROUTINES.record_error;
         raise;
      -- RAISE_APPLICATION_ERROR(-20010, DBMS_UTILITY.FORMAT_ERROR_BACKTRACE||' '||v_debug_table_name);
    -- RAISE_APPLICATION_ERROR(-20010,DBMS_UTILITY.format_error_backtrace);
end export_old_partitions_to_disk;
{code}

IpSec in transport mode not completeing phase 2 quick mode

I am trying to connect Solaris 10 to a non Solaris box over IPsec. I know this box has worked with a windows machine running ipsec.
My configuration of ipsec and ike looks to be correct but I must be missing something.
If I turn the ikeadm traces I see that I get through the phase 1 main mode but can not establish quick mode.
I have to use 3des for encryption and sha1 for authentic ion. I have followed the steps in the Solaris 10 ipsec and ike manual but I don't know where to turn now.
This are the ikeadm traces
Wed 20 Jul 2005 12:05:21 BST: in.iked: Quick Mode negotiation failed: code 14 (No proposal chosen).
Wed 20 Jul 2005 12:05:21 BST: in.iked: local_ip = 172.18.10.1, remote_ip = 192.168.25.22,
Wed 20 Jul 2005 12:05:21 BST: in.iked: local_i_id = ipv4(tcp:0,[0..3]=192.168.25.22), local_r_id = No Id,
Wed 20 Jul 2005 12:05:21 BST: in.iked: remote_i_id = ipv4(tcp:2126,[0..3]=172.18.10.1), remote_r_id = No Id,
Wed 20 Jul 2005 12:05:21 BST: in.iked: spsi: ike_send_packet -1
Wed 20 Jul 2005 12:05:21 BST: in.iked: In ssh_policy_phase_ii_sa_freed.
Wed 20 Jul 2005 12:05:21 BST: in.iked: local_ip = 172.18.10.1, remote_ip = 192.168.25.22,
Wed 20 Jul 2005 12:05:21 BST: in.iked: spsi: ike_udp_callback_common -1
Wed 20 Jul 2005 12:05:21 BST: in.iked: In ssh_policy_new_connection_phase_qm (pm_info = 0x85938).
Wed 20 Jul 2005 12:05:21 BST: in.iked: In ssh_policy_qm_select_sa (pm_info = 0x85938).
Wed 20 Jul 2005 12:05:21 BST: in.iked: Number of sas is 1.
Wed 20 Jul 2005 12:05:21 BST: in.iked: pfkey_request: queueing seq 598 type 12/X_INVERSE_ACQUIRE satype 0/UNSPEC
Wed 20 Jul 2005 12:05:21 BST: in.iked: tx_req: posting seq 598 type 12/X_INVERSE_ACQUIRE satype 0/UNSPEC
Wed 20 Jul 2005 12:05:21 BST: in.iked: pf_key_handler: got pid 1242 seq 598 type
6/ACQUIRE sa 0/UNSPEC errno 0 diag 0/No diagnostic len 109
Wed 20 Jul 2005 12:05:21 BST: in.iked: handle_reply: got seq 598 type 6/ACQUIREsatype 0/UNSPEC
Wed 20 Jul 2005 12:05:21 BST: in.iked: SA #0.
Wed 20 Jul 2005 12:05:21 BST: in.iked: Number of proposals = 1.
Wed 20 Jul 2005 12:05:21 BST: in.iked: Proposal 0.
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 0 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 1 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 2 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 3 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 4 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 5 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 6 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 7 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 8 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: ecomb 9 lost
Wed 20 Jul 2005 12:05:21 BST: in.iked: no matching ecomb
Wed 20 Jul 2005 12:05:21 BST: in.iked: No winner.
Wed 20 Jul 2005 12:05:21 BST: in.iked: finish_qm_select_sa: invoked for 85018
Wed 20 Jul 2005 12:05:21 BST: in.iked: Quick Mode negotiation failed: code 14 (No proposal chosen).
Wed 20 Jul 2005 12:05:21 BST: in.iked: local_ip = 172.18.10.1, remote_ip = 192.1
My config file
# more config
local_id_type IP
p1_lifetime_secs 28800
p1_nonce_len 20
p1_xform {auth_method preshared oakley_group 2 auth_alg sha1 encr_alg 3des}
p2_pfs 0
p2_lifetime_secs 10800
label "cmts1"
local_addr 172.18.10.1
remote_addr 192.168.25.22
I have also set up the ike.preshared file with my preshared key
When I do a ikeadm dump preshared I see the correct key
Any suggestions
penright

Eeesh. I wish I'd signed up for SDN earlier.
I know I'm a year late in replying, but the peer is proposing something in Quick Mode
(Phase 2) that your Solaris box doesn't think is available. Given the combinations
you had (0-9), I'd be interested to know what the peer proposed that didn't match.
You don't mention what ipsecconf(1m) input is, nor what the peer is configured to
do. You say 3des + sha1 - so that should be one of the choices.
One common mistake is to use "auth_algs" in ipsecconf(1m) (which is AH) instead
of "encr_auth_algs" (which is ESP's hash).

PTP Transport mode

Similar Messages

Maybe you are looking for