PTP (Precision Time Protocol) configuration

Question

Hi,
Is there anyone has configured PTP on IE-3000 switches? I have some problems with the configuration and operation. Below is the summary of what I've done and the porblems.
There are two IE-3000 switches with ip services 15.0 (2) SE4 IOS. One has configured in the boundary mode to become master clock and the other one has left in the e2etransparent mode. There are two inter-connection links (via Cat6 ethernet cable) on Gi1/1 and Gi1/2 interfaces on both switches. All inter-connect ports are up and running. Both switches have same IOS, same hardware almost identical except IP configuration etc. Main problem is SW2 is not able to sync with SW1 as master clock (this is my understanding), and also it seems PTP on SW1 has wrong reading of local clock time. But in fact I have NTP server in the network and NTP is syncd. I've included some of the configuration and output here, if someone has experience in configuring and running PTP I would be thankful to give me some help here.
Regards,
Tohid
Configuration on SW1:
ptp mode boundary
ptp priority1 10
ptp priority2 128
ptp time-property persist 300
SW1#show ptp clock
PTP CLOCK INFO
  PTP Device Type: Boundary clock
  Clock Identity: 0x8:CC:68:FF:FE:7F:73:80
  Clock Domain: 0
  Number of PTP ports: 10
  Priority1: 10
  Priority2: 128
  Clock Quality:
        Class: 248
        Accuracy: Unknown
        Offset (log variance): N/A
  Offset From Master: 0
  Mean Path Delay: 0
  Steps Removed: 0
  Local clock time: 00:30:30 UTC Mar 1 1993
SW1#sh clock
16:18:10.856 UTC Thu Feb 27 2014
SW1#sh ntp status
Clock is synchronized, stratum 3, reference is 10.1.1.1
nominal freq is 119.2092 Hz, actual freq is 119.2091 Hz, precision is 2**17
reference time is D6B9E25E.3EAA5D0E (16:12:14.244 UTC Thu Feb 27 2014)
clock offset is 45.5794 msec, root delay is 1.42 msec
root dispersion is 57.46 msec, peer dispersion is 5.25 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000000985 s/s
system poll interval is 64, last update was 423 sec ago.
SW2#sh ptp clock
PTP CLOCK INFO
  PTP Device Type: End to End transparent clock
  Clock Identity: 0x3C:E:23:FF:FE:44:92:80
  Clock Domain: 0
  Number of PTP ports: 10
  Delay Mechanism: End to End
  Local clock time: 01:08:13 UTC Mar 4 1993
SW2#sh ptp port gi 1/1
PTP PORT DATASET: GigabitEthernet1/1
  Port identity: clock identity: 0x3C:E:23:FF:FE:44:92:80
  Port identity: port number: 9
  PTP version: 2
Port state FAULTY: FALSE
SW1#sh ptp port gi 1/1
PTP PORT DATASET: GigabitEthernet1/1
  Port identity: clock identity: 0x8:CC:68:FF:FE:7F:73:80
  Port identity: port number: 9
  PTP version: 2
  Port state: MASTER
  Delay request interval(log mean): 5
  Announce receipt time out: 3
  Peer mean path delay: 0
  Announce interval(log mean): 1
  Sync interval(log mean): 0
  Delay Mechanism: End to End
  Peer delay request interval(log mean): 0
  Sync fault limit: 5000000004271-NET-001#sh ptp port gi 1/1
PTP PORT DATASET: GigabitEthernet1/1
  Port identity: clock identity: 0x8:CC:68:FF:FE:7F:73:80
  Port identity: port number: 9
  PTP version: 2
  Port state: MASTER
  Delay request interval(log mean): 5
  Announce receipt time out: 3
  Peer mean path delay: 0
  Announce interval(log mean): 1
  Sync interval(log mean): 0
  Delay Mechanism: End to End
  Peer delay request interval(log mean): 0
  Sync fault limit: 500000000

Answer 1

So if I have a L2 network consisting of severall access switches connected via trunks to a distribution, with PTP clients in differing VLAN's, as long as each VLAN has a connection to the PTP source then the client will receive the PTP timestamp allthough subject to switching delays?