Cisco DCNM Media Controller Deployment: AMQP Notifications

Available Languages

Download Options

  • PDF     (1.9 MB)
    View with Adobe Reader on a variety of devices
Updated:April 6, 2021

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

AMQP Notifications for Cisco DCNM Media Controller Deployment

First Published: January 22, 2019

Revised and Published: December 22, 2020

 

Contents

Contents. 2

Host Alias Notifications. 3

Hosts Notifications. 7

Host Policy Notifications. 9

Flow Notifications. 15

Flow Alias. 16

Flow Policy Notifications. 20

PTP. 25

RTP. 26

Realtime Faults. 28

Realtime Notifications. 31

VRF. 33

General Notifications. 70

Static Receivers. 74

Link Bandwidth.. 78

Flow Bandwidth.. 82

Obtaining Documentation and Submitting a Service Request. 83

Legal Information.. 84

Cisco Trademark (all documentation) 84

Cisco Copyright (all documentation) 84


 

Host Alias Notifications

Create Host Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.hostalias

Redelivered

○

Properties

message_id:

7000

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Success

Event:

Host Alias with alias name h1 successfully created by admin

Sent At:

2018-05-01, 08:59:18

Severity:

Information

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"h1",
                  "ipAddress":"10.2.3.4" ,
                  "message":"Host Alias with alias name h1 successfully created by admin"}

 

Update Host Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.hostalias

Redelivered

○

Properties

message_id:

7001

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Success

Event:

Host Alias with original name and IP address h1, (10.2.3.4) updated to h1, (10.2.3.9) by admin

Sent At:

2018-05-01, 09:02:13

Severity:

Information

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"h1",
                  "ipAddress":"10.2.3.9",
                  "message":"Host Alias with original name and IP address h1, (10.2.3.4) updated to h1, (10.2.3.9) by admin"

}

 

Delete Host Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.hostalias

Redelivered

○

Properties

message_id:

7002

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Success

Event:

Host Alias with name host3 deleted by admin

Sent At:

2018-05-01, 09:04:26

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

{

               "name":"host3",
              "ipAddress":"3.3.3.3",
              "message":"Host alias with name host3 deleted by admin",

}

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.hostalias

Redelivered

○

Properties

message_id:

7004

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Success

Event:

Host Alias was successfully deleted by admin with 1 Hosts

Sent At:

2018-05-01, 09:04:26

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "successCount":1,
                  "message":"Host Alias deletion done successfully by admin with 1 Hosts",
                  "failureCount":0

}

 

Create Host Alias - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.hostalias

Redelivered

○

Properties

message_id:

7100

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Failure

Event:

Failed to create Host Alias with alias name abcaaaaaaaaaaaaaabcaaaaaaaaaaaaaabcaaaaaa by admin

Sent At:

2018-05-01, 09:27:24

Severity:

Error

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

{

                  "name":"Hostname_1",

                  "ipAddress":"1.2.3.4 ,”

                  "message":"Failed to create Host Alias with alias name Hostname_1 by admin"

}

 

Update Host Alias- Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.hostalias

Redelivered

○

Properties

message_id:

7101

delivery_mode:

2

headers:

Type:

HostAlias

User:

admin

Operation Status:

Failure

Event:

Failed to update Host Alias with original name and IP address h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2, (10.2.3.5) to 2h22h2h2h2h2h2h2h2h2h2h2h2, (10.2.3.5) by admin

Sent At:

2018-05-01, 09:29:42

Severity:

Error

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              “message":"Failed to update Host Alias with original name and IP address h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2, (10.2.3.5) to h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2h2, (10.2.3.5) by admin"

}

Delete Host Alias - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.hostalias

Redelivered

○

Properties

message_id:

7102

delivery_mode:

2

headers:

Type:

Host

User:

admin

Operation Status:

Delete

Event:

Host alias deletion failed for name HostTesting by admin

Severity:

Error

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"HostTesting",

              "ipAddress":"18.1.1.1"

              "message":" Host alias deletion failed for name HostTesting by admin",

 }

Hosts Notifications

Host Discovered

DCNM will periodically go through the End Points List provided by the switch through telemetry and determine if there are any new hosts discovered. DCNM will generate a notification for all the new hosts discovered. The host will be either local or remote (PIM router case).

 

Exchange

DCNMExchange

Routing Key

info.com.cisco.dcnm.event.pmn.discover.host

Redelivered

○

Properties

message_id:

1005

delivery_mode:

2

headers:

Type:

Host

User:

admin

Operation Status:

Success

Event:

Host with the name: Host-11.11.11.11 discovered on switch 172.23.244.113 and interface Ethernet1/2

Severity:

Information

Operation:

Discover

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "role":"Sender",

              "Switch time":"Sun, Mar 24 2019 07:25:27 (PDT)",

              "ipAddress":"20.2.1.2",

              "discoverd by":"",

              "source":"20.2.1.2",

              "message":"Host:20.2.1.2 Discovered Source:20.2.1.2  group:228.0.0.18",

              "interface":"Vlan21",

              "mac":"",

              "switch":"pmn-109-leaf",

              "external":"NO",

              "fault reason":"NONE",

              "name":"Host-20.2.1.2","group":"228.0.0.18"

}

Host Deleted

DCNM will periodically go through the End Points List provided by the switch through telemetry and determine if there are any hosts got deleted. DCNM will generate a notification for all the deleted hosts.

 

Exchange

DCNMExchange

Routing Key

info.com.cisco.dcnm.event.pmn.delete.host

Redelivered

○

Properties

message_id:

1005

delivery_mode:

2

headers:

Type:

Host

User:

admin

Operation Status:

Success

Event:

Host with the name: Host-11.11.11.11 deleted on switch 172.23.244.113 and interface Ethernet1/2

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "role":"Sender",

              "Switch time":"Sun, Mar 24 2019 07:25:27 (PDT)",

              "ipAddress":"20.2.1.2",

              "discoverd by":"",

              "source":"20.2.1.2",

              "message":"Host:20.2.1.2 Deleted Source:20.2.1.2  group:228.0.0.10",

              "interface":"Vlan21","mac":"",

              "switch":"pmn-109-leaf",

              "external":"NO",

              "fault reason":"NONE",

              "name":"Host-20.2.1.2",

              "group":"228.0.0.10"

 }

Host Policy Notifications

Create Host Policy

·       “hostRole” can be Sender or Receiver-Local or Receiver-External.

·       senderName or receiverName field based on the host role

·       receiverIp is not shown in case the role is the sender

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.hostpolicy

Redelivered

○

Properties

message_id:

2000

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

Host policy test successfully saved by admin

Sent At:

2018-05-01, 09:43:33

Severity:

Information

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

{

                  "sequenceNumber":5,

                  "policyName":"test",

                  "permit":true,

                  "link":"https://172.23.244.229/rest/pmn/hostpolicies/test",                   "hostRole":"Sender",

                  "message":"Host policy  test successfully saved by admin",

                  "multicast":"*","senderIp":"1.3.4.7","mask":32

}

Create Host Policy – Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.hostpolicy

Redelivered

○

Properties

message_id:

2100

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Failure

Event:

Policy with name 'HostPolicyAA' already exists.

Sent At:

2019-03-25, 23:38:33

Severity:

Error

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

{

                  "permit":false,

                  "message":"Policy with name 'HostPolicyAA' already exists.",

                  "mask":0}

}

Update Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.hostpolicy

Redelivered

○

Properties

message_id:

2001

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

Host Policy with policy name Test1 successfully updated by admin

Severity:

Information

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

{

                  “policyName": "Test1",

                  "receiverName": "H1",

                  "receiverIp": "1.1.1.1",

                  "senderIp": "2.2.2.2",

                  "permit": true,

                   "link": "https://172.23.244.150/rest/pmn/hostpolicies/Test1",

                  "hostRole": "Receiver-Local",

                  "message": "Host Policy with policy name Test1 successfully updated by admin",

                  "multicast": "237.7.6.7"

}

Update Host Policy – Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.hostpolicy

Redelivered

○

Properties

message_id:

2101

delivery_mode:

2

headers:

Type:

HostPolicy

User:

Internal

Operation Status:

Failure

Event:

Host Policy with policy name Anyname failed to be updated by admin. Error: Policy does not exist. Nothing to update.

Severity:

Error

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

{

                  "permit":false,

                  "message":"Host Policy with policy name Anyname failed to updated by admin.

                  Error: Policy does not exist. Nothing to update.",

                  "mask":0}

}

Delete Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.hostpolicy

Redelivered

○

Properties

message_id:

2002

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

Host Policy with policy name Test101 successfully deleted by admin

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "policyName": "Test101",

                  "receiverName": "H1",

                  "receiverIp": "1.1.1.1",

                  "senderIp": "2.2.2.2", 

                  "permit": false,

                   "hostRole": "Receiver-Local",

                  "message": "Host Policy with policy name Test101 successfully deleted by admin",
                  "multicast": "231.71.42.72"
}

Delete Host Policy – Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.hostpolicy

Redelivered

○

Properties

message_id:

2102

delivery_mode:

2

headers:

Type:

HostPolicy

User:

Internal

Operation Status:

Failure

Event:

Host Policy with policy name Anyname failed to be deleted by admin. Error: Policy does not exist. Nothing to delete.

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

Host Policy Application

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.apply.hostpolicy

Redelivered

○

Properties

message_id:

2005

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

Host Policy with policy name P2

successfully applied on the switch: 172.23.244.58

Severity:

Information

Operation:

Apply

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
            "switchIP": "172.23.244.58",
            "policyName": "P2",
            "senderName": "Host-1.4.1.6",
            "senderIp": "2.2.2.2",
            "permit": true,
             "link": "https://172.23.244.150/rest/pmn/hostpolicies/P2",
            "hostRole": "Sender",
            "message": " Host Policy with policy name P2 successfully applied on switch: 172.23.244.58",
            "multicast": "232.3.5.3"
}

Host Policy Deployment

Exchange

DCNMExchange

 

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.hostpolicy

 

Redelivered

○

 

Properties

message_id:

2006

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

Host Policy with policy name P2

successfully deployed on the switch: 172.23.244.58

Severity:

Information

Operation:

Deploy

content_encoding:

UTF-8

content_type:

application/json

 

Payload

 
{
            "switchIP": "172.23.244.58",
            "policyName": "P2",
            "senderName": "Host-1.4.1.6",
            "senderIp": "2.2.2.2",
            "permit": true,
             "link": "https://172.23.244.150/rest/pmn/hostpolicies/P2",
            "hostRole": "Sender",
            "message": " Host Policy with policy name P2 successfully deployed on switch: 172.23.244.58",
            "multicast": "232.3.5.3"
}
 
 

Host Policy Deployment - Failure

Exchange

DCNMExchange

 

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.hostpolicy

 

Redelivered

○

 

Properties

message_id:

2106

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Failure

Event:

Switch: 172.22.31.104 is in 'Unmanaged' state

Severity:

Error

Operation:

Deploy

content_encoding:

UTF-8

content_type:

application/json

 

Payload

 
{
            "Deployed data":"[Policy3, Policy5, Policy6, Policy8, Policy9, SunPolicy, MondayPolicy, NewPolicy]",
            "deployment type":"HostPolicy",
            "switch-ip":"172.22.31.104"}
}
 
 

 

Host Policy Un-deployment

Exchange

DCNMExchange

 

Routing Key

information.com.cisco.dcnm.event.pmn.undeploy.hostpolicy

 

Redelivered

○

 

Properties

message_id:

2006

delivery_mode:

2

headers:

Type:

HostPolicy

User:

admin

Operation Status:

Success

Event:

HostPolicy [] Undeployment on switch: 172.22.31.109

Severity:

Information

Operation:

Undeploy

content_encoding:

UTF-8

content_type:

application/json

 

Payload

 
{
            "Deployed data":"[]",
            "deployment type":"HostPolicy",
            "switch-ip":"172.22.31.109"
}
 
 

Flow Notifications

Flow Established

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.establish.flow

Redelivered

○

Properties

message_id:

5000

delivery_mode:

2

headers:

Type:

Flow

User:

admin

Operation Status:

Success

Event:

SUCCESS_FLOW_STITCHED - Established a new flow from Sender IP: 1.1.1.1 to Receiver IP: 2.4.1.8 for Multicast IP: 236.71.6.7.

Severity:

Information

Operation:

Establish

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "multicast-IP": "236.71.6.7",
                  "link": "https://172.23.244.150/rest/pmn/flow/236.71.6.7/1.1.1.1/2.4.1.8",
                  "receiver-IP": "2.4.1.8",
                  "receiver-host-interface": "Ethernet1/8",
                  "sender-leaf": "172.23.244.58",
                  "message": "SUCCESS_FLOW_STITCHED - Establised a new flow from Sender IP: 1.1.1.1 to Receiver IP: 2.4.1.8 for Multicast IP: 236.71.6.7",
                  "sender-host-interface": "Ethernet1/12",
                  "sender-IP": "1.1.1.1",
                  "receiver-leaf": "172.23.244.68",
                  "applied-flow-policy": "Default",
                  "local-flow": "No"
}

Flow Deleted

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flow

Redelivered

○

Properties

message_id:

5003

delivery_mode:

2

headers:

Type:

Flow

User:

admin

Operation Status:

Success

Event:

Flow-Deleted – Sender-IP: 192.168.10.108, Receiver-IP: 192.168.20.105, Multicast-IP:228.1.1.1

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "multicast-IP": "228.1.1.1",
                  "sender-IP": "192.168.10.108",
                  "receiver-IP": "192.168.20.105",
                  "sender-leaf": "172.23.244.68",
                  "sender-host-interface": "ethernet1/1",
                  "receiver-leaf": "172.23.244.58",
                  "receiver-host-interface": "ethernet1/38",
                  "message": “Flow-Deleted – Sender-IP: 192.168.10.108, Receiver-IP: 192.168.20.105, Multicast-IP:228.1.1.1“
}

Flow Alias

Create Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flowalias

Redelivered

○

Properties

message_id:

4000

delivery_mode:

2

headers:

Type:

FlowAlias

User:

Internal

Operation Status:

Success

Event:

Flow Alias with alias name FlowA successfully created by admin

Severity:

Information

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"FlowA",
                  "link":"https://172.23.244.195/rest/pmn/flowalias/FlowA",
                  "description":"dd",
                  "message":"Flow Alias with alias name FlowA successfully created by admin",
                  "multicastIp":"224.3.2.5"
}

Create Flow Alias - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.flowalias

Redelivered

○

Properties

message_id:

4100

delivery_mode:

2

headers:

Type:

FlowAlias

User:

admin

Operation Status:

Failure

Event:

Flow Alias with alias name FlowAA failed to be created by admin

Severity:

Error

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  {"name":"FlowAA",
                  "description":"FlowAA Description",
                  "message":"Flow Alias with alias name FlowAA failed to be created by admin",
                  "multicastIp":"1.1.1.1"
}

Update Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.flowalias

Redelivered

○

Properties

message_id:

4001

delivery_mode:

2

headers:

Type:

FlowAlias

User:

Internal

Operation Status:

Success

Event:

Flow Alias updated with alias name FlowA by admin

Severity:

Information

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"FlowA",
                  "link":"https://172.23.244.195/rest/pmn/flowalias/FlowA",
                  "description":"dd",
                  "message":"Flow Alias updated with alias name FlowA by admin",
                  "multicastIp":"224.1.2.2"
}

Update Flow Alias - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.flowalias

Redelivered

○

Properties

message_id:

4101

delivery_mode:

2

headers:

Type:

FlowAlias

User:

Internal

Operation Status:

Failure

Event:

Flow Alias with alias name FlowB failed to be updated by admin

Severity:

Error

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"FlowB",
                  "link":"https://172.23.244.195/rest/pmn/flowalias/12460",
                  "description":"Des",
                  "message":"Flow Alias with alias name FlowB failed to be updated by admin",
                  "multicastIp":"22.1.2.23"
}

Delete Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flowalias

Redelivered

○

Properties

message_id:

4002

delivery_mode:

2

headers:

Type:

FlowAlias

User:

admin

Operation Status:

Success

Event:

Flow Alias with alias name FlowAA successfully deleted by admin

Severity:

Information

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "name":"FlowAA",
                  "description":"FlowAA Description",
                  "message":"Flow Alias with alias name FlowAA successfully deleted by admin",
                  "multicastIp":"224.1.1.1"
}

Delete Flow Alias – Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.flowalias

Redelivered

○

Properties

message_id:

4102

delivery_mode:

2

headers:

Type:

FlowAlias

User:

Internal

Operation Status:

Failure

Event:

Flow Alias with alias id or name anyone failed to be deleted by admin

Severity:

Error

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "link":"https://172.23.244.195/rest/pmn/flowalias/anyone",
                  "message":"Flow Alias with alias id or name anyone failed to be deleted by admin"
}

Flow Policy Notifications

Create Flow Policy

 " multicastIpRange" – may have a start and end IP (e.g. 224.10.10.10 – 224.10.10.30) or maybe a single multicast IP.

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flowpolicy

Redelivered

○

Properties

message_id:

3000

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Success

Event:

Flow Policy with policy name P3 successfully created by admin

Severity:

Information

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS1",
                  "policyName": "P3",
                  "bandwidth": "3gbps",
                   "link": "https://172.23.244.150/rest/pmn/flowpolicies/P3",
                  "message": "Flow Policy with policy name P3 successfully created by admin",
                  " multicastIpRange ": "233.4.3.4"
}

Update Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.flowpolicy

Redelivered

○

Properties

message_id:

3001

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Success

Event:

Flow Policy with policy name P11 successfully updated by admin

Severity:

Information

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS4",
                  "policyName": "P11",
                  "bandwidth": "1.4gbps",
                   "link": "https://172.23.244.150/rest/pmn/flowpolicies/P11",
                  "message": "Flow Policy with policy name P11 successfully updated by admin",
                  " multicastIpRange ": "233.33.33.33"
}

Delete Flow Policy

 Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flowpolicy

Redelivered

○

Properties

message_id:

3002

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Success

Event:

Flow Policy with policy name P3 successfully deleted by admin

Severity:

Information

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS1",
                  "policyName": "P3",
                  "bandwidth": "3gbps",
                   "message": "Flow Policy with policy name P3 successfully deleted by admin",
                  "multicastIpRange": "233.4.3.4"
}

 

Flow Policy Deployment

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.flowpolicy

Redelivered

○

Properties

message_id:

3006

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Success

Event:

Flow Policy with policy name P2

successfully deployed on the switch: 172.23.244.58

Severity:

Information

Operation:

Deploy

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
            "dscp": "CS1",
            "policyName": "P3",
            "bandwidth": "3gbps",
            "multicastIpRange": "233.4.3.4"
            "message": " Flow Policy with policy name P2 successfully deployed on the switch: 172.23.244.58
}

Flow Policy Un-deployment

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.undeploy.flowpolicy

Redelivered

○

Properties

message_id:

3006

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

Internal

Operation Status:

Success

Event:

FlowPolicy [] Undeployment on switch: 172.22.31.109

Severity:

Information

Operation:

Undeploy

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
            "Deployed data":"[]",
            "deployment type":"FlowPolicy",
            "switch-ip":"172.22.31.109"
 
}

Create Flow Policy - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.flowpolicy

Redelivered

○

Properties

message_id:

3100

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Failure

Event:

Flow Policy with policy name P40 failed to be created by admin. Error: Invalid bandwidth units

Severity:

Error

Operation:

Create

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS3",
                  "policyName": "P40",
                  "bandwidth": "8ibps",
                   "message": "Flow Policy with policy name P40 failed to be created by admin. Error: Invalid bandwidth units",
                  "multicastIpRange": "237.71.17.17"
}

Update Flow Policy - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.flowpolicy

Redelivered

○

Properties

message_id:

3101

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Failure

Event:

Flow Policy with policy name P40 failed to be updated by the admin. Error: Invalid DSCP: '249'

Severity:

Error

Operation:

Update

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS3",
                  "policyName": "P40",
                  "bandwidth": "8mbps",
                   "link": "https://172.23.244.150/rest/pmn/flowpolicies/P40",
                  "message": "Flow Policy with policy name P40 failed to be updated by admin. Error: Invalid DSCP: '249'",
                  "multicastIpRange": "237.71.17.17"
}

Delete Flow Policy - Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.flowpolicy

Redelivered

○

Properties

message_id:

3102

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Failure

Event:

Flow Policy with policy name P401 failed to be deleted by admin. Error: Policy does not exist. Nothing to delete.

Severity:

Error

Operation:

Delete

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                   "message": "Flow Policy with policy name P401 failed to be deleted by admin. Error: Policy does not exist. Nothing to delete."
}

Flow Policy Deployment – Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.flowpolicy

Redelivered

○

Properties

message_id:

3105

delivery_mode:

2

headers:

Type:

FlowPolicy

User:

admin

Operation Status:

Failure

Event:

Flow Policy with policy name P1 failed to be deployed on the switch: 172.23.244.58

Severity:

Error

Operation:

Deploy

content_encoding:

UTF-8

content_type:

application/json

Payload

 
{
                  "dscp": "CS1",
                  "policyName": "P1",
                  "bandwidth": "3gbps",
                   "link": "https://172.23.244.150/rest/pmn/flowpolicies/P1",
                  "message": "Flow Policy with policy name P1 failed to be deployed on switch: 172.23.244.58”,
                  " multicastIpRange ": "233.4.3.4"
}

PTP

Whenever we detect PTP correction exceeds the threshold configure on the PTP Management page, a AMQP notification will be sent to report it.

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.ptpcorrection

Redelivered

○

Properties

message_id:

5300

delivery_mode:

2

headers:

Event:

Time correction is created for Switch spine-1 and Interface Eth1/35

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-12, 23:08:04

Severity:

Information

Type:

PTPCorrection

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

 

Payload

{

"date":"2019-Jun-12 09:49:49",

"sup-time":"Wed Jun 12 09:49:49 2019 890705",

"mean-path-delay":164,

"interface":"Eth1/35",

"micro-seconds":890705,

"correction-value":288,

"switch":"spine-1"

}

RTP

Packet Drop Occurs

Whenever a new packet drop occurs, the next pulling cycle will detect it and a AMQP notification will be sent to inform this new packet drop.

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flowerror

Redelivered

●

Properties

message_id:

5200

delivery_mode:

2

headers:

Event:

Flow Error created for Source:1.1.1.1:319, Receiver:233.1.0.1:319

Operation:

Create

Operation Status:

Success

Sent At:

2019-05-30, 15:00:12

Severity:

Information

Type:

FlowError

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload323 bytes Encoding: string

{"source-port":319,"bit-rate":169053000,"packet-loss":"736416795","start-time":"13:10:59 UTC Mar 25 2019","pod":"","loss-start":"13:25:07 UTC Mar 25 2019","vrf":"","interface":"Ethernet1/1","destination-ip":"233.1.0.1","switch":"pmn-105-leaf","protocol":17,"destination-port":319,"packet-count":11764,"source-ip":"1.1.1.1"}

Packet Drop Cleared

Whenever a packet drop goes to packet drop history, the next pulling cycle will detect it and a AMQP notification will be sent to inform the packet drop is clear.

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flowerror

Redelivered

●

Properties

message_id:

5203

delivery_mode:

2

headers:

Event:

Flow Error deleted for Source:1.1.1.1:319, Receiver:233.1.0.1:319

Operation:

Delete

Operation Status:

Success

Sent At:

2019-05-31, 14:17:06

Severity:

Information

Type:

FlowError

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{"source-port":319,"bit-rate":169053000,"packet-loss":"736416795","start-time":"13:10:59 UTC Mar 25 2019","pod":"","loss-start":"13:25:07 UTC Mar 25 2019","vrf":"","interface":"Ethernet1/1","destination-ip":"233.1.0.1","switch":"pmn-105-leaf","protocol":17,"destination-port":319,"packet-count":11764,"source-ip":"1.1.1.1"}

 

Realtime Faults

Fault Create  

 

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.realtime.switch

Redelivered

○

Properties

message_id:

21005

delivery_mode:

2

headers:

Event:

Fabric: Default_LAN Switch: anna-pmn-archer Fault: sys/nbm/show/faults/dom-default/faults-[sys/nbm/show/endpoints/dom-default/h-[15.2.1.2]-if-0/g-[228.10.1.16]] created

Operation:

Real Time Notification

Operation Status:

Failure

Sent At:

2020-06-04, 07:55:45 PDT

Severity:

Error

Type:

Switch

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

"faultReason":"No Bandwidth",

"faultResolution":"Please consult documentation",

"Switch":"anna-pmn-archer",

"dn":"sys/nbm/show/faults/dom-default/faults-[sys/nbm/show/endpoints/dom-default/h-[15.2.1.2]-if-0/g-[228.10.1.16]]",

"TimestampReceived":1591282545383,

"Timestamp":1588691553014,

"Fabric":"Default_LAN",

"status":"created"

}

 

Different faultReason:

 

·       "No Bandwidth"

·       "No Bandwidth (Ext)"

·       "Sender Denied"

·       "Sender Denied (Ext)"

·       "No Flow Policy"

·       "No Policer Avail"

·       "No Policer Avail (Ext)"

·       "No Unicast Route"

·       "No Flow Slot Avail"

·       "No Flow Slot Avail(Ext)"

·       "No Profile Avail"

·       "No Profile Avail (Ext)"

·       "Flow in Pending Delete"

·       "No TCAM Carved (Ext)"

·       "No TCAM Carved"

·       "Unknown"

 

Fault Delete 

 

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.realtime.switch

Redelivered

○

Properties

message_id:

21005

delivery_mode:

2

headers:

Event:

Fabric: Default_LAN Switch: anna-pmn-archer Fault: sys/nbm/show/faults/dom-default/faults-[sys/nbm/show/endpoints/dom-default/h-[15.2.1.2]-if-0/g-[228.10.1.16]] deleted

Operation:

Real Time Notification

Operation Status:

Failure

Sent At:

2020-06-04, 07:55:45 PDT

Severity:

Information

Type:

Switch

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

"Switch":"anna-pmn-archer",

"dn":"sys/nbm/show/faults/dom-default/faults-[sys/nbm/show/endpoints/dom-default/h-[15.2.1.2]-if-0/g-[228.10.1.16]]",

"TimestampReceived":1591282545327,

"Timestamp":1588691553005,

"Fabric":"Default_LAN",

"status":"deleted"

}

 

 

Realtime Notifications

Flow Established

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.realtime.switch

Redelivered

●

Properties

message_id:

21005

delivery_mode:

2

headers:

Event:

Fabric: Default_LAN Switch: pmn-n93-leaf2 DN: sys/nbm/show/notify/dom-default/event-[FLOW:s-[11.3.1.2]-g-[227.50.1.1]/oif-[Eth1/25]]created

Operation:

Real Time Notification

Operation Status:

Information

Sent At:

2020-10-20, 11:57:42 PDT

Severity:

Information

Type:

Switch

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

"identifier":"FLOW:s-[11.3.1.2]-g-[227.50.1.1]/oif-[Eth1/25]",

"reason":"FLOW Provisioned Successfully","

Switch":"pmn-n93-leaf2","dn":"sys/nbm/show/notify/dom-default/event-[FLOW:s-[11.3.1.2]-g-[227.50.1.1]/oif-[Eth1/25]]",

"TimestampReceived":1603220262137,"Timestamp":1603220262189,

"Fabric":"Default_LAN",

"status":"created"

}

Flow Deleted

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.realtime.switch

Redelivered

●

Properties

message_id:

21005

delivery_mode:

2

headers:

Event:

Fabric: Default_LAN Switch: pmn-n93-leaf1 DN: sys/nbm/show/notify/dom-default/event-[FLOW:s-[0.0.0.0]-g-[228.50.1.1]/oif-[Eth1/27]]deleted

Operation:

Real Time Notification

Operation Status:

Information

Sent At:

2020-11-16, 11:30:12 PST

Severity:

Information

Type:

Switch

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

             "Switch":"pmn-n93-leaf1",

"dn":"sys/nbm/show/notify/dom-default/event-[FLOW:s-[0.0.0.0]-g-[228.50.1.1]/oif-[Eth1/27]]",

             "TimestampReceived":1605555012672,"Timestamp":1605555012618,

             "Fabric":"Default_LAN",

             "status":"deleted

}

 

VRF

For VRF support, we will need to add VRF field for all the notifications we support so far. VRF info will be added in Event header and in the payload name value pair as well as in payload link.

The followings are examples we captured:

Create Host Alias

 

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.hostalias

Redelivered

●

Properties

message_id:

7000

delivery_mode:

2

headers:

Event:

Host Alias with alias name 'HostAlias7-8' in VRF 'default' in Fabric 'Default_LAN' successfully created by admin

Operation:

Create

Operation Status:

Success

Sent At:

2019-07-08, 15:12:55

Severity:

Information

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload
209 bytes

{

              "fabric":"Default_LAN",

              "name":"HostAlias7-8",

              "ipAddress":"3.3.3.3",

              "vrf":"default",

              "message":"Host Alias with alias name 'HostAlias7-8' in VRF 'default' in Fabric 'Default_LAN' successfully created by admin"

}

Update Host Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.hostalias

Redelivered

●

Properties

message_id:

7001

delivery_mode:

2

headers:

Event:

Host Alias with original name and IP address HostAlias7-8, (3.3.3.3) updated to HostAlias7-8, (3.3.3.1) in VRF 'default' in Fabric 'Default_LAN' by admin

Operation:

Update

Operation Status:

Success

Sent At:

2019-07-08, 15:14:06

Severity:

Information

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "fabric":"Default_LAN",

              "name":"HostAlias7-8",

              "ipAddress":"3.3.3.1",

              "vrf":"default",

              "message":"Host Alias with original name and IP address HostAlias7-8, (3.3.3.3)               updated to HostAlias7-8, (3.3.3.1) in VRF 'default' in Fabric 'Default_LAN' by admin"

}

Delete Host Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.hostalias

Redelivered

●

Properties

message_id:

7002

delivery_mode:

2

headers:

Event:

Host Alias with name 'HostAlias7-8' in VRF 'default' in Fabric 'Default_LAN' in Fabric 'Default_LAN' deleted by admin

Operation:

Delete

Operation Status:

Success

Sent At:

2019-07-08, 15:14:33

Severity:

Information

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "fabric":"Default_LAN",

              "name":"HostAlias7-8",

              "ipAddress":"3.3.3.1",

              "vrf":"default",

              "message":"Host Alias with name 'HostAlias7-8'  in VRF 'default' in Fabric 'De              fault_LAN' in Fabric 'Default_LAN' deleted by admin"

}

 

Discovered Host

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.discover.host

Redelivered

○

Properties

message_id:

1005

delivery_mode:

2

headers:

Event:

Host:20.2.1.20 Discovered Source:20.2.1.20 group:228.20.0.48 in VRF coke

Operation:

Discover

Operation Status:

Success

Sent At:

2019-06-14, 23:41:21

Severity:

Information

Type:

Host

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "role":"Sender",

              "Switch time":"Fri, Jun 14 2019 23:40:31 (PDT)",

              "ipAddress":"20.2.1.20",

              "discoverd by":"",

              "vrf":"coke",

              "source":"20.2.1.20",

              "message":"Host:20.2.1.20 Discovered Source:20.2.1.20

              group:228.20.0.48 in VRF coke",

              "interface":"Vlan21",

              "mac":"",

              "switch":"pmn-109-leaf",

              "external":"NO",

              "fault reason":"NONE",

              "name":"Host-20.2.1.20",

              "group":"228.20.0.48"

}

Deleted Host

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.host

Redelivered

●

Properties

message_id:

1002

delivery_mode:

2

headers:

Event:

Host:10.2.1.20 Deleted Source:0.0.0.0 group:228.20.0.8 in VRF coke

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-15, 12:14:47

Severity:

Information

Type:

Host

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "role":"Dynamic Receiver",

              "Switch time":"Sat, Jun 15 2019 11:10:16 (PDT)",

              "ipAddress":"10.2.1.20",

              "discoverd by":"IGMP",

              "vrf":"coke",

              "source":"0.0.0.0",

              "message":"Host:10.2.1.20 Deleted Source:0.0.0.0

              group:228.20.0.8 in VRF coke",

              "interface":"Vlan11",

              "mac":"",

              "switch":"pmn-109-leaf",

              "external":"NO",

              "fault reason":"NONE",

              "name":"Host-10.2.1.20",

              "group":"228.20.0.8"

}

Create Host Alias Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.hostalias

Redelivered

○

Properties

message_id:

7100

delivery_mode:

2

headers:

Event:

Failed to create Host Alias with alias name HostAlias in VRF default by admin (Error:Host Alias 'HostAlias' in VRF default already exists.)

Operation:

Create

Operation Status:

Failure

Sent At:

2019-06-08, 23:34:06

Severity:

Error

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

210 bytesEncoding: string

{

              "name":"HostAlias",

              "ipAddress":"1.1.1.2",

              "vrf":"default",

              "message":"Failed to create Host Alias with alias name HostAlias in VRF default               by admin (Error:Host Alias 'HostAlias' in VRF default already exists.)"

}

 

Update Host Alias Failure

 

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.hostalias

Redelivered

○

Properties

message_id:

7101

delivery_mode:

2

headers:

Event:

Failed to update Host Alias with original name and IP address Jun3, (2.2.2.2) to June3, (2.2.2.2) in VRF default by admin

Operation:

Update

Operation Status:

Failure

Sent At:

2019-06-04, 12:52:26

Severity:

Error

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "message":"Failed to update Host Alias with original name and IP address Jun3,               (2.2.2.2) to June3, (2.2.2.2) in VRF default by admin"

}

Delete Host Alias Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.hostalias

Redelivered

○

Properties

message_id:

7102

delivery_mode:

2

headers:

Event:

Host Alias deletion failed. 'Anyname' in VRF default does not exist.

Operation:

Delete

Operation Status:

Failure

Sent At:

2019-06-04, 13:01:25

Severity:

Error

Type:

HostAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "message":"Host Alias deletion failed. 'Anyname' in VRF default does               not exist."

}

 

Create Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.hostpolicy

Redelivered

○

Properties

message_id:

2000

delivery_mode:

2

headers:

Event:

Host policy JunePolicy in VRF default successfully saved by admin

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-04, 16:14:28

Severity:

Information

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sequenceNumber":5,

              "policyName":"JunePolicy",

              "permit":true,

              "link":"https://172.23.244.98/rest/pmn/hostpolicies/JunePolicy",

              "hostRole":"Sender",

              "vrf":"default",

              "message":"Host policy  JunePolicy in VRF default successfully saved by admin",

              "multicast":"*",

              "senderIp":"3.3.3.3",

              "mask":0,

              "receiverIp":""

}

Update Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.hostpolicy

Redelivered

○

Properties

message_id:

2001

delivery_mode:

2

headers:

Event:

Host policy JunePolicy in VRF default successfully saved by admin

Operation:

Update

Operation Status:

Success

Sent At:

2019-06-04, 16:19:17

Severity:

Information

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sequenceNumber":5,

              "policyName":"JunePolicy",

              "permit":true,

              "link":"https://172.23.244.98/rest/pmn/hostpolicies/JunePolicy",

              "hostRole":"Sender",

              "vrf":"default",

              "message":"Host policy  JunePolicy in VRF default successfully saved by admin",

              "multicast":"*",

              "senderIp":"3.3.3.3",

              "mask":4,

              "receiverIp":""

}

Delete Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.hostpolicy

Redelivered

○

Properties

message_id:

2002

delivery_mode:

2

headers:

Event:

Host policy JunePolicy in VRF default deleted by admin

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-04, 16:22:57

Severity:

Information

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

290 bytesEncoding: string

{

              "sequenceNumber":5,

              "policyName":"JunePolicy",

              "permit":true,

              "link":"https://172.23.244.98/rest/pmn/hostpolicies/JunePolicy",

              "hostRole":"Sender",

              "vrf":"default",

              "message":"Host policy  JunePolicy in VRF default deleted by admin",

              "multicast":"*",

              "senderIp":"3.3.3.3",

              "mask":0,"receiverIp":""

}

Deploy Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.hostpolicy

Redelivered

○

Properties

message_id:

2006

delivery_mode:

2

headers:

Event:

HostPolicy [June20] Deployment in VRF: default on switch: 10.23.234.152

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-06-19, 12:02:04

Severity:

Information

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[June20]",

              "deployment type":"HostPolicy",

              "vrf":"default",

              "switch-ip":"10.23.234.152"

}

Un-Deploy Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.undeploy.hostpolicy

Redelivered

○

Properties

message_id:

2006

delivery_mode:

2

headers:

Event:

HostPolicy [June20] Undeployment in VRF: default on switch: 172.22.31.109

Operation:

UNDEPLOY

Operation Status:

Success

Sent At:

2019-06-19, 12:53:46

Severity:

Information

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[June20]",

              "deployment type":"HostPolicy",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Applied Host Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.hostpolicy

Redelivered

○

Properties

message_id:

2005

delivery_mode:

2

headers:

Event:

Policy Default-Receiver-Local Applied on Switch:pmn-109-leaf Interface:ALL in VRF default

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-18, 10:49:03

Severity:

Information

Type:

HostPolicy

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "switchIP":"172.22.31.109",

              "Action":"created",

              "role":"RECEIVER",

              "Switch time":"2019-06-18, 10:47:12",

              "policyName":"Default-Receiver-Local",

              "permit":"true",

              "vrf":"default",

              "message":"Policy Default-Receiver-Local Applied on Switch:pmn-109-leaf Interface:ALL in VRF default",

              "interface":"IfIndex:0 Ifname not available"

}

Create Host Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.hostpolicy

Redelivered

○

Properties

message_id:

2100

delivery_mode:

2

headers:

Event:

Policy with name June4Policy in VRF default already exists.

Operation:

Create

Operation Status:

Failure

Sent At:

2019-06-06, 18:01:22

Severity:

Error

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "permit":false,

              "vrf":"default",

              "message":"Policy with name June4Policy in VRF default already exists.",

              "mask":0

}

Update Host Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.hostpolicy

Redelivered

●

Properties

message_id:

2101

delivery_mode:

2

headers:

Event:

Host Policy with policy name Somename in VRF default failed to updated by admin. Error: Policy does not exist. Nothing to update.

Operation:

Update

Operation Status:

Failure

Sent At:

2019-06-04, 16:41:16

Severity:

Error

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "permit":false,

              "vrf":"default",

              "message":"Host Policy with policy name Somename in VRF default failed to updated by admin. Error: Policy does not exist. Nothing to update.",

              "mask":0

}

Delete Host Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.hostpolicy

Redelivered

○

Properties

message_id:

2102

delivery_mode:

2

headers:

Event:

Host Policy with policy name Somein VRF default failed to be deleted by admin. Error: Policy does not exist. Nothing to delete.

Operation:

Delete

Operation Status:

Failure

Sent At:

2019-06-04, 16:44:43

Severity:

Error

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

Deploy Host Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.hostpolicy

Redelivered

○

Properties

message_id:

2106

delivery_mode:

2

headers:

Event:

HostPolicy [HostPolicy25] Deployment failed in VRF: default on switch: 172.22.31.104, Reason: configured object ((Dn0)) not found Dn0=sys/nbm/conf/hostpolicytable/dom-default,

Operation:

Deploy

Operation Status:

Failure

Sent At:

2019-06-24, 23:57:46

Severity:

Error

Type:

HostPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[HostPolicy25]",

              "deployment type":"HostPolicy",

              "vrf":"default",

              "switch-ip":"172.22.31.104"

}

Create Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flowalias

Redelivered

○

Properties

message_id:

4000

delivery_mode:

2

headers:

Event:

Flow Alias with alias name FlowAlias8 in VFF default successfully created by admin

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-08, 08:53:59

Severity:

Information

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"FlowAlias8",

              "link":"https://172.23.244.98/rest/pmn/flowalias/FlowAlias8",

              "description":"Flow Alias 8",

              "vrf":"default",

              "message":"Flow Alias with alias name FlowAlias8 in VFF default successfully created by admin",

              "multicastIp":"224.1.1.1"}

Update Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.flowalias

Redelivered

○

Properties

message_id:

4001

delivery_mode:

2

headers:

Event:

Flow Alias updated with alias name FlowAlias8 in VRF default by admin

Operation:

Update

Operation Status:

Success

Sent At:

2019-06-08, 08:56:53

Severity:

Information

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"FlowAlias8",

              "link":"https://172.23.244.98/rest/pmn/flowalias/FlowAlias8",

              "description":"Flow Alias 8",

              "vrf":"default",

              "message":"Flow Alias updated with alias name FlowAlias8 in VRF default by admin",

              "multicastIp":"224.2.2.2"

}

Delete Flow Alias

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flowalias

Redelivered

○

Properties

message_id:

4002

delivery_mode:

2

headers:

Event:

Flow Alias with alias name FlowAlias8 in VRF default successfully deleted by admin

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-08, 09:01:25

Severity:

Information

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"FlowAlias8",

              "description":"Flow Alias 8",

              "vrf":"default",

              "message":"Flow Alias with alias name FlowAlias8 in VRF default successfully deleted by admin",

              "multicastIp":"224.2.2.2"

}

Create Flow

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flow

Redelivered

○

Properties

message_id:

5000

delivery_mode:

2

headers:

Event:

Flow created for Source:20.2.1.20, Receiver:10.2.1.20 group:228.20.0.5 in VRF coke

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-18, 12:16:24

Severity:

Information

Type:

Flow

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Sender Switch time":"172.22.31.109: 2019-06-18, 12:15:37",

              "sender-IP":"20.2.1.20",

              "Receiver Switch time":"172.22.31.109: 2019-06-18, 12:15:37",

              "receiver-IP":"10.2.1.20",

              "receiver-host-interface":"Vlan11",

              "vrf":"coke",

              "sender-leaf":"172.22.31.109",

              "receiver-leaf":"172.22.31.109",

              "group":"228.20.0.5",

              "sender-host-interface":"Vlan21",

              "policy":"Default"

}

Delete Flow

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flow

Redelivered

●

Properties

message_id:

5003

delivery_mode:

2

headers:

Event:

Flow deleted for Source:20.2.1.20, Receiver:10.2.1.20 group:228.20.0.5 in VRF coke

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-18, 12:24:25

Severity:

Information

Type:

Flow

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Sender Switch time":"172.22.31.109: 2019-06-18, 12:15:37",

              "sender-IP":"20.2.1.20",

              "Receiver Switch time":"172.22.31.109: 2019-06-18, 12:15:37",

              "receiver-IP":"10.2.1.20",

              "receiver-host-interface":"Vlan11",

              "vrf":"coke",

              "sender-leaf":"172.22.31.109",

              "receiver-leaf":"172.22.31.109",

              "group":"228.20.0.5",

              "sender-host-interface":"Vlan21",

              "policy":"Default"

}

Create Flow Alias Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.flowalias

Redelivered

○

Properties

message_id:

4100

delivery_mode:

2

headers:

Event:

Flow Alias with alias name FlowAlias in VRF default failed to be created by admin

Operation:

Create

Operation Status:

Failure

Sent At:

2019-06-08, 09:31:41

Severity:

Error

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"FlowAlias",

              "description":"Flow Alias",

              "vrf":"default",

              "message":"Flow Alias with alias name FlowAlias in VRF default failed to be created by admin",

              "multicastIp":"254.1.2.1"

}

Update Flow Alias Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.flowalias

Redelivered

○

Properties

message_id:

4101

delivery_mode:

2

headers:

Event:

Flow Alias with alias name FlowAlias8 in VRF default failed to be updated by admin

Operation:

Update

Operation Status:

Failure

Sent At:

2019-06-08, 09:33:05

Severity:

Error

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "name":"FlowAlias8",

              "link":"https://172.23.244.98/rest/pmn/flowalias/7050",

              "description":"Flow Alias 8",

              "vrf":"default",

              "message":"Flow Alias with alias name FlowAlias8 in VRF default failed to be updated by admin",

              "multicastIp":"244.1.1.1"

}

Delete Flow Alias Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.flowalias

Redelivered

○

Properties

message_id:

4102

delivery_mode:

2

headers:

Event:

Flow Alias with alias name SomeFlowAlias in VRF default failed to be deleted by admin

Operation:

Delete

Operation Status:

Failure

Sent At:

2019-06-08, 09:53:36

Severity:

Error

Type:

FlowAlias

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "link":"https://172.23.244.98/rest/pmn/flowalias/flowalias/SomeFlowAlias",

              "message":"Flow Alias with alias name SomeFlowAlias in VRF default failed to be deleted by admin"

}

Create Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.flowpolicy

Redelivered

●

Properties

message_id:

3000

delivery_mode:

2

headers:

Event:

Flow Policy with policy name FlowPolicy in VRF default successfully created by admin

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-08, 23:37:30

Severity:

Information

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "policer":"Enabled",

              "dscp":"Best Effort",

              "policyName":"FlowPolicy",

              "bandwidth":"3gbps",

              "link":"https://172.23.244.98/rest/pmn/flowpolicies/FlowPolicy",

              "vrf":"default",

              "message":"Flow Policy with policy name FlowPolicy in VRF default successfully created by admin",

              "multicastRangeList":[{"endIP":"224.2.2.8","deleted":false,"beginIP":"224.2.2.2"}]

}

Update Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.update.flowpolicy

Redelivered

○

Properties

message_id:

3001

delivery_mode:

2

headers:

Event:

Flow Policy with policy name FlowPolicy in VRF default successfully updated by admin

Operation:

Update

Operation Status:

Success

Sent At:

2019-06-08, 23:48:31

Severity:

Information

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "policer":"Enabled",

              "policyName":"FlowPolicy",

              "bandwidth":"3mbps",

              "link":"https://172.23.244.98/rest/pmn/flowpolicies/FlowPolicy",

              "vrf":"default",

              "message":"Flow Policy with policy name FlowPolicy in VRF default successfully updated by admin",

              "multicastRangeList":[{"endIP":"224.2.2.8","deleted":false,"beginIP":"224.2.2.2"}]

}

Delete Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.flowpolicy

Redelivered

○

Properties

message_id:

3002

delivery_mode:

2

headers:

Event:

Flow Policy with policy name FlowPolicy in VRF default successfully deleted by admin

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-08, 23:50:19

Severity:

Information

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "policer":"Enabled",

              "policyName":"FlowPolicy",

              "bandwidth":"3mbps",

              "vrf":"default",

              "message":"Flow Policy with policy name FlowPolicy in VRF default successfully deleted by admin",

              "multicastRangeList":[{"endIP":"224.2.2.8","deleted":false,

              "beginIP":"224.2.2.2"}]

}

Deploy Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.flowpolicy

Redelivered

○

Properties

message_id:

3006

delivery_mode:

2

headers:

Event:

FlowPolicy [FlowPolicy] Deployment in VRF: default on switch: 172.22.31.109

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-06-19, 12:11:12

Severity:

Information

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[FlowPolicy]",

              "deployment type":"FlowPolicy",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Un-Deploy Flow Policy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.undeploy.flowpolicy

Redelivered

○

Properties

message_id:

3006

delivery_mode:

2

headers:

Event:

FlowPolicy [FlowPolicy] Undeployment in VRF: default on switch: 10.23.234.152

Operation:

UNDEPLOY

Operation Status:

Success

Sent At:

2019-06-19, 13:02:21

Severity:

Information

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[FlowPolicy]",

              "deployment type":"FlowPolicy",

              "vrf":"default",

              "switch-ip":"10.23.234.152"

}

Create Flow Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.flowpolicy

Redelivered

○

Properties

message_id:

3100

delivery_mode:

2

headers:

Event:

Flow Policy with policy name FlowPolicy in VRF default failed to be created by admin. Error: Multicast IP Range (224.1.1.1 - 224.1.1.6) of this policy conflicts with another existing Multicast IP Range (224.1.1.1 - 224.1.1.9)

Operation:

Create

Operation Status:

Failure

Sent At:

2019-06-08, 23:53:03

Severity:

Error

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "message":"Flow Policy with policy name FlowPolicy in VRF default failed to be created by admin. Error: Multicast IP Range (224.1.1.1 - 224.1.1.6) of this policy conflicts with another existing Multicast IP Range (224.1.1.1 - 224.1.1.9)"

}

Update Flow Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.update.flowpolicy

Redelivered

○

Properties

message_id:

3101

delivery_mode:

2

headers:

Event:

Flow Policy with policy name SomeFlowPolicy in VRF default failed to be updated by admin. Error: Invalid bandwidth units

Operation:

Update

Operation Status:

Failure

Sent At:

2019-06-09, 00:01:33

Severity:

Error

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "message":"Flow Policy with policy name SomeFlowPolicy in VRF default failed to be updated by admin. Error: Invalid bandwidth units"

}

Delete Flow Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.flowpolicy

Redelivered

○

Properties

message_id:

3102

delivery_mode:

2

headers:

Event:

Flow Policy with policy name SomeFlowPolicy in VRF default failed to be deleted by admin. Error: Policy does not exist. Nothing to delete.

Operation:

Delete

Operation Status:

Failure

Sent At:

2019-06-08, 23:59:15

Severity:

Error

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "message":"Flow Policy with policy name SomeFlowPolicy in VRF default failed to be deleted by admin. Error: Policy does not exist. Nothing to delete."

}

Deploy Flow Policy Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.flowpolicy

Redelivered

○

Properties

message_id:

3106

delivery_mode:

2

headers:

Event:

FlowPolicy [FlowPolicy25] Deployment failed in VRF: default on switch: 172.22.31.104, Reason: unknown attribute 'policer' in element 'nbmFlowPolicy'

Operation:

Deploy

Operation Status:

Failure

Sent At:

2019-06-25, 00:09:44

Severity:

Error

Type:

FlowPolicy

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[FlowPolicy25]",

              "deployment type":"FlowPolicy",

              "vrf":"default",

              "switch-ip":"172.22.31.104"

}

Deploy Unicast BW

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.unicast_bw

Redelivered

○

Properties

message_id:

8000

delivery_mode:

2

headers:

Event:

unicast_bw [unicast_bw] Deployment in VRF: default on switch: 172.22.31.109

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-08, 17:02:04

Severity:

Information

Type:

unicast_bw

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[unicast_bw]",

              "deployment type":"unicast_bw",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Un-Deploy Unicast BW

(To do: key and message id should be different than deploy)

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.unicast_bw

Redelivered

○

Properties

message_id:

8000

delivery_mode:

2

headers:

Event:

unicast_bw [unicast_bw] Deployment in VRF: default on switch: 172.22.31.109

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-08, 21:38:04

Severity:

Information

Type:

unicast_bw

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[unicast_bw]",

              "deployment type":"unicast_bw",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Deploy Unicast BW Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.unicast_bw

Redelivered

○

Properties

message_id:

8100

delivery_mode:

2

headers:

Event:

unicast_bw [unicast_bw] Deployment failed in VRF: default on switch: 172.22.31.105, Reason: Invalid request. dn 'sys/nbm/conf/global/dom-default' does not match naming properties specified 'sys/nbm/conf/global/dom-default/global'

Operation:

Deploy

Operation Status:

Failure

Sent At:

2019-07-07, 09:43:50

Severity:

Error

Type:

unicast_bw

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[unicast_bw]",

              "deployment type":"unicast_bw",

              "vrf":"default",

              "switch-ip":"172.22.31.105"

}

Deploy ASM

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.asm

Redelivered

○

Properties

message_id:

8001

delivery_mode:

2

headers:

Event:

asm [nbmGroupRangeDom] Deployment in VRF: default on switch: 172.22.31.109

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-08, 17:02:09

Severity:

Information

Type:

asm

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[nbmGroupRangeDom]",

              "deployment type":"asm",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Un-Deploy ASM

To do: key wrong, message id should be different than deploy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.asm

Redelivered

○

Properties

message_id:

8001

delivery_mode:

2

headers:

Event:

asm [nbmGroupRangeDom] Deployment in VRF: default on switch: 172.22.31.105

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-06, 17:51:48

Severity:

Information

Type:

asm

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[nbmGroupRangeDom]",

              "deployment type":"asm",

              "vrf":"default",

              "switch-ip":"172.22.31.105"

}

Deploy ASM Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.asm

Redelivered

○

Properties

message_id:

8101

delivery_mode:

2

headers:

Event:

asm [nbmGroupRangeDom] Deployment failed in VRF: default on switch: 172.22.31.105, Reason: configured object ((Dn0)) not found Dn0=sys/nbm/conf/grouprangelist/dom-default,

Operation:

Deploy

Operation Status:

Failure

Sent At:

2019-07-07, 09:48:16

Severity:

Error

Type:

asm

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[nbmGroupRangeDom]",

              "deployment type":"asm",

              "vrf":"default",

              "switch-ip":"172.22.31.105"

}

Deploy WAN Link

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.wan_links

Redelivered

○

Properties

message_id:

8002

delivery_mode:

2

headers:

Event:

wan_links [wan_links] Deployment in VRF: default on switch: 172.22.31.109

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-08, 17:06:05

Severity:

Information

Type:

wan_links

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[wan_links]",

              "deployment type":"wan_links",

              "vrf":"default",

              "switch-ip":"172.22.31.109"

}

Un-Deploy WAN Link

To do: key wrong, message id should be different than deploy

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.wan_links

Redelivered

○

Properties

message_id:

8002

delivery_mode:

2

headers:

Event:

wan_links [wan_links] Deployment in VRF: default on switch: 172.22.31.105

Operation:

Deploy

Operation Status:

Success

Sent At:

2019-07-06, 18:06:31

Severity:

Information

Type:

wan_links

User:

Internal

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[wan_links]",

              "deployment type":"wan_links",

              "vrf":"default",

              "switch-ip":"172.22.31.105"

}

Deploy WAN Link Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.deploy.wan_links

Redelivered

○

Properties

message_id:

8102

delivery_mode:

2

headers:

Event:

wan_links [wan_links] Deployment failed in VRF: default on switch: 172.22.31.105, Reason: configured object ((Dn0)) not found Dn0=sys/nbm/conf/interfaces/dom-default,

Operation:

Deploy

Operation Status:

Failure

Sent At:

2019-07-07, 09:51:24

Severity:

Error

Type:

wan_links

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[wan_links]",

              "deployment type":"wan_links",

              "vrf":"default",

              "switch-ip":"172.22.31.105"

}

Create Static Receiver

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.create.sreceiver

Redelivered

●

Properties

message_id:

9001

delivery_mode:

2

headers:

Event:

Succcess in accepting static receiver creation in VRF default with switchIp:172.22.31.109

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-17, 11:14:30

Severity:

Information

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sourceId":"8.8.5.5",

              "pod":"Default_LAN",

              "ticket":"1WCyaB-1",

              "multiCastIpAddress":"233.1.1.1",

              "create":true,

              "hostId":"1.1.1.1",

              "vrf":"default",

              "message":"Succcess in accepting static receiver creation in VRF default with switchIp:172.22.31.109",

              "hostInterface":""

}

Delete Static Receiver

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.delete.sreceiver

Redelivered

○

Properties

message_id:

9003

delivery_mode:

2

headers:

Event:

Success in accepting static receiver deletion request in VRF default with switchIp:172.22.31.109

Operation:

Delete

Operation Status:

Success

Sent At:

2019-06-17, 11:52:49

Severity:

Information

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sourceId":"8.8.5.5",

              "pod":"Default_LAN",

              "ticket":"1YaZbM-1",

              "multiCastIpAddress":"233.1.1.1",

              "create":true,

              "hostId":"1.1.1.1",

              "vrf":"default",

              "message":"Success in accepting static receiver deletion request in VRF default with switchIp:172.22.31.109",

              "hostInterface":""

}

Create Bulk Static Receiver

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.bulk.sreceiver

Redelivered

○

Properties

message_id:

9005

delivery_mode:

2

headers:

Event:

Success in accepting bulk static receiver request with switchIp:172.22.31.108

Operation:

Bulk

Operation Status:

Success

Sent At:

2019-06-24, 23:35:37

Severity:

Information

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "input":[{"sourceId":"8.9.8.9","pod":"Default_LAN","multiCastIpAddress":"233.2.2.2","create":true,"hostId":"5.6.5.6","vrf":"default","hostInterface":""}],

              "ticket":"3RkXUO-b-1",

              "message":"Success in accepting bulk static receiver request with switchIp:172.22.31.108"

}

Deploy Static Receiver

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.deploy.sreceiver

Redelivered

●

Properties

message_id:

9007

delivery_mode:

2

headers:

Event:

Success in static receiver Create operation for switch:172.22.31.109

Operation:

Create

Operation Status:

Success

Sent At:

2019-06-25, 16:08:14

Severity:

Information

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Deployed data":"[(ticket:4vDTFQ-1:1,pod:Default_LAN,host:9.9.9.9,source:19.19.19.19,vrf:default,operation:CREATE,seq:4vDTFQ-1:1,group:233.9.9.9)]",

              "deployment type":"SReceiver",

              "vrf":"default",

              "message":"Success in static receiver Create operation for switch:172.22.31.109",

              "switch-ip":"172.22.31.109"

}

Create Static Receiver Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.create.sreceiver

Redelivered

●

Properties

message_id:

9002

delivery_mode:

2

headers:

Event:

{"error":{"code":"ProcessingError","detail":"An error is encoutered during request processing with error

Caught exception in create static receiver: <<PMNStaticReceiverController>> error in adding static receiver:com.cisco.dcbu.vinci.pmn.models.StaticReceiver@26b01d5[hostId=1.1.1.1,source=8.8.5.5,

multicastIp=233.1.1.1,deviceIp=172.22.31.109,interfaceName=NA,deployStatus=1W1FUn-1,vrf=default,pod=Default_LAN,deployedSwitchStatus=<null>,creationTime=<null>,modifiedTime=<null>]

with exception:ERROR: column \"pod\" of relation \"pmn_static_receivers\" does not exist
Position: 108"}}

Operation:

Create

Operation Status:

Failure

Sent At:

2019-06-17, 10:59:52

Severity:

Error

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sourceId":"8.8.5.5",

              "pod":"Default_LAN",

              "ticket":"1W1FUn-1",

              "multiCastIpAddress":"233.1.1.1",

              "create":true,"hostId":"1.1.1.1",

              "vrf":"default",

              "message":"{\"error\":{\"code\":\"ProcessingError\",\"detail\":\"An error is encoutered during request processing with error 

Caught exception in create static receiver:  <<PMNStaticReceiverController>>  error in adding static receiver:com.cisco.dcbu.vinci.pmn.models.

StaticReceiver@26b01d5[hostId=1.1.1.1,source=8.8.5.5,multicastIp=233.1.1.1,deviceIp=172.22.31.109,interfaceName=NA,

deployStatus=1W1FUn-1,vrf=default,pod=Default_LAN,deployedSwitchStatus=<null>,creationTime=<null>,modifiedTime=<null>]

with exception:ERROR: column \\\"pod\\\" of relation \\\"pmn_static_receivers\\\" does not exist\n  Position: 108\"}}",

              "hostInterface":"",

              "failure-reason":" Caught exception in create static receiver:  <<PMNStaticReceiverController>>  error in adding static receiver:com.cisco.dcbu.vinci.pmn.models.StaticReceiver@26b01d5[hostId=1.1.1.1,source=8.8.5.5,multicastIp=233.1.1.1,

deviceIp=172.22.31.109,interfaceName=NA,deployStatus=1W1FUn-1,vrf=default,pod=Default_LAN,deployedSwitchStatus=<null>,

creationTime=<null>,modifiedTime=<null>] with exception:ERROR: column \\\"pod\\\" of relation \\\"pmn_static_receivers\\\"

does not exist\n  Position: 108"

}

Delete Static Receiver Failure

Exchange

DCNMExchange

Routing Key

error.com.cisco.dcnm.event.pmn.delete.sreceiver

Redelivered

●

Properties

message_id:

9004

delivery_mode:

2

headers:

Event:

switch Ip address is not known/managed by DCNM

Operation:

Delete

Operation Status:

Failure

Sent At:

2019-06-17, 11:58:09

Severity:

Error

Type:

SReceiver

User:

admin

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "sourceId":"8.8.5.5",

              "pod":"Default_LAN",

              "ticket":"1Yopt1-1",

              "multiCastIpAddress":"233.2.2.2",

              "create":true,

              "hostId":"1.1.1.1",

              "vrf":"default",

              "message":"switch Ip address is not known/managed by DCNM",

              "hostInterface":"",

              "failure-reason":"switch Ip address is not known/managed by DCNM"

}

Start DCNM

(no VRF needed):

Exchange

DCNMExchange

Routing Key

information.com.cisco.dcnm.event.pmn.dcnm.server

Redelivered

○

Properties

message_id:

10000

delivery_mode:

2

headers:

Bulk:

false

Event:

DCNM server (172.23.244.98) is Started

Operation:

DCNM

Operation Status:

SUCCESS

Severity:

Information

Type:

Server

User:

Unknown

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "date":"Mon Jun 17 15:57:38 PDT 2019",

              "dcnm-ip":"172.23.244.98",

              "message":"DCNM server (172.23.244.98) is Started",

              "status":"Started"

}

Reload Switch

(no VRF needed):

Exchange

DCNMExchange

Routing Key

com.cisco.dcbu.sm.server.model.DCManager

Redelivered

●

Properties

message_id:

11003

delivery_mode:

2

headers:

Bulk:

false

Event:

Device is shutting down: Reset Requested by CLI command reload

Operation:

undefined

Operation Status:

SUCCESS

Severity:

Information

Type:

LAN_DISCOVERY

User:

Unknown

content_encoding:

UTF-8

content_type:

application/json

Payload

{

              "Status":"Failure",

              "Message":"Device is shutting down: Reset Requested by CLI command reload",

              "DBID":1090,

              "Switch IP":"172.22.31.106",

              "UUID":"DCNM-UUID-1100",

              "Date":"Sat Jun 29 22:04:40 PDT 2019",