Configuring Frequency Synchronization

Next generation networks must provide the ability to distribute precision frequency around the network. Thisis known as frequency synchronization. Precision frequency is required for applications such as circuitemulation and cell tower frequency referring. To achieve compliance to ITU specifications for TDM, differentialmethod circuit emulation must be used, which requires a known, common precision frequency reference ateach end of the emulated circuit

For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide:

Configuring fsync

Configuring fsync

POST http://<mgmt0_IP>/api/mo/sys/fm.json

{
  "fmEntity": {
    "children": [
      {
        "fmFsyncMgr": {
          "attributes": {
            "adminSt": "enabled"
}}}]}}

{
    imdata:[]
}

<System>
  <fm-items>
    <fsyncmgr-items>
      <adminSt>enabled</adminSt>
    </fsyncmgr-items>
  </fm-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

feature frequency-synchronization

Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MO	DN
fmEntity	sys/fm
fmFsyncMgr	sys/fm/fsyncmgr

fmFsyncMgr Properties

The following table contains information about the fmFsyncMgr properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property Name	Data Type	Description	Values
adminSt	fm:AdminState (scalar:Enum8)	Admin status	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting fsync

Deleting fsync

POST http://<mgmt0_IP>/api/mo/sys/fm.json

{
  "fmEntity": {
    "children": [
      {
        "fmFsyncMgr": {
          "attributes": {
            "adminSt": "disabled"
}}}]}}

{
    imdata:[]
}

<System>
  <fm-items>
    <fsyncmgr-items>
      <adminSt>disabled</adminSt>
    </fsyncmgr-items>
  </fm-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

no feature frequency-synchronization

Verifying a DME Configuration

MO	DN
fmEntity	sys/fm
fmFsyncMgr	sys/fm/fsyncmgr

fmFsyncMgr Properties

Property Name	Data Type	Description	Values
adminSt	fm:AdminState (scalar:Enum8)	Admin status	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring ITU-T QL Option 2 Generation

Configuring ITU-T QL Option 2 Generation

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "qloption": "op2g1"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <qloption>op2g1</qloption>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

fsync quality itu-t option 2 generation 1

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

The following table contains information about the fsyncMgrSynceEntity properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property Name	Data Type	Description	Values
qloption	fsyncMgr:gqloptype (scalar:Enum8)	QL option type global	SELECTION: 1 - op1 2 - op2g1 3 - op2g2 DEFAULT: op1

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring ITU-T QL Option 2 Generation

Configuring ITU-T QL Option 2 Generation

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "qloption": "op2g2"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <qloption>op2g2</qloption>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

fsync quality itu-t option 2 generation 2

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

Property Name	Data Type	Description	Values
qloption	fsyncMgr:gqloptype (scalar:Enum8)	QL option type global	SELECTION: 1 - op1 2 - op2g1 3 - op2g2 DEFAULT: op1

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Clock Identity

Configuring Clock Identity

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "clockid": "D8:B1:90:71:E9:03"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <clockid>D8:B1:90:71:E9:03</clockid>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

fsync clock-identity d8b1.9071.e903

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

Property Name	Data Type	Description	Values
clockid	address:MAC	SyncE clock-identity MAC Address	Value must match MM:MM:MM:SS:SS:SS format

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Clock Identity

Deleting Clock Identity

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "clockid": "00:00:00:00:00:00"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <clockid>00:00:00:00:00:00</clockid>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

no fsync clock-identity d8b1.9071.e903

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

Property Name	Data Type	Description	Values
clockid	address:MAC	SyncE clock-identity MAC Address	Value must match MM:MM:MM:SS:SS:SS format

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Receive Timer During Update

Configuring Receive Timer During Update

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "peerrcvtimeout": "467"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <peerrcvtimeout>467</peerrcvtimeout>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

fsync esmc peer receive timeout 467

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

Property Name	Data Type	Description	Values
peerrcvtimeout	fsyncMgr:peerrcvtimeout (scalar:Uint16)	fsync esmc peer receive timeout in seconds, (120-600) default: 0	RANGE: [0 , 600] DEFAULT: 120

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Receive Timer During Update

Deleting Receive Timer During Update

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "fsyncMgrSynceEntity": {
          "attributes": {
            "peerrcvtimeout": "120"
}}}]}}

{
    imdata:[]
}

<System>
  <fsyncmgr-items>
    <peerrcvtimeout>120</peerrcvtimeout>
  </fsyncmgr-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

no fsync esmc peer receive timeout 467

Verifying a DME Configuration

MO	DN
topSystem	sys
fsyncMgrSynceEntity	sys/fsyncmgr

fsyncMgrSynceEntity Properties

Property Name	Data Type	Description	Values
peerrcvtimeout	fsyncMgr:peerrcvtimeout (scalar:Uint16)	fsync esmc peer receive timeout in seconds, (120-600) default: 0	RANGE: [0 , 600] DEFAULT: 120

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html