|
Unable to
import a cable plan from Cisco Prime DCNM to a device.
|
-
The
switch does not have the feature
cable-management command enabled.
-
Cisco
Prime DCNM is unable to make a Secure Shell (SSH) connection to the device.
-
The
cable plan is not correctly formatted for the switch.
|
-
Check
log files:
/usr/local/
cisco/dcm/fm/logs/fmserver*.log*
for
indication of the error condition.
-
Use
the
show accounting
log command on the switch to review the following:
|
|
The switch
already has an XML file with the same name.
|
-
Manually delete the existing XML file.
-
Import
the file again.
|
|
The
following error is displayed when you attempt to import a cable plan:
Failed to import cable plan or Remove copy failure
|
The switch
was previously registered with a different Cisco Prime DCNM instance.
|
-
Open
an SSH terminal session.
-
Clear
the SSH key on the switch on which you want to deploy the cable plan.
For
example:
n6k-leaf-2017#
clear ssh hosts
|
|
A cable or
tier mismatch error is expected but did not occur.
|
The DFA
switch poll is not updated.
|
-
Open
an SSH terminal session.
-
Use
the
show fabric conn
neighbor command to identify the state of cable or tier links.
-
Review
the output of the
show fabric conn
neighbor command for cable/tier mismatches.
-
If the
show fabric conn
neighbor command output displayed the proper connections, DFA
should show those same connections. However, the updated state might take up to
5 minutes.
| Note
|
DFA
polls the switches every 5 minutes to learn the error state information.
|
|
|
The
following system message error is displayed when you attempt to import the
cable plan:
errDisabled
|
In the
cable plan XML file, sourceChassis and destChassis were not specified in a
hostname.domainname fully qualified domain name (FQDN) format.
|
Specify
the sourceChassis and destChassis in a hostname.domainname format.
| Note
| When
you enter the
ip domain-name
command, the Link Layer Discovery Protocol (LLDP) sends the chassis
type-length-value (TLV) in an FQDN format.
|
For
example:
switch # config terminal
switch (config) # ip domain-name cisco.com
<<<<cableplan.xml snip>>>>
<CHASSIS_INFO sourceChassis="spine1.cisco.com"
type-"n6k">
<LINK_INFO sourcePort="Eth2/1"
destChassis="leaf1.cisco.com" destPort="Eth2/1"/>
|
|
No
neighbors are detected.
|
LLDP is
not running on the interface and cannot transport information.
|
Check to
ensure that the LLDP is enabled on the interface. Use the
feature lldp
command to enable LLDP on the switch and the
lldp {receive |
transmit} command to enable the
reception or transmission of LLDP packets on an interface.
|
|
Problems
occur with neighbor detection.
|
Neighbor
connections are stale.
|
-
Use
the
feature
cable-management command to enable the cable management feature.
-
Use
the
clear fabric connectivity
neighbors stale
command to clear neighbor cache information for
stale or purged neighbors.
|
|
When cable-plan is not enforced, the following status is
displayed for links when you issue
show fabric connectivity cable-plan
— "ErrC, S”.
|
Actual link errors or faulty cable plan is causing the
errors. After the errors are seen, disabling the cable-plan enforcement.
|
-
Open an SSH terminal session.
-
Actual link or cable errors could have caused the ErrC
status displayed via the
show fabric connectivity
cable-plan command. Since cable-plan enforcement is disabled
after the errors are seen via the
show fabric connectivity
cable-plan command, there is no automated way to clear those
entries. You can either ignore the show command output or use the
clear fabric connectivity
cable-plan command to clear the entries.
To fix the actual link errors and enable cable-plan,
perform the following steps.
-
Use the
clear fabric connectivity
cable-plan command to clear the error/stale entries.
-
Verify/re-generate cable-plan to be imported.
-
Import and enforce cable-plan.
-
Use the
show fabric connectivity
cable-plan to identify the status of the links.
-
If the connections are OK, the output of
show fabric connectivity
neighbors command should list the cable plan information. If not,
check the connections, cable-plan, and cabling.
|
|
The entry for cable plan in the output of
show fabric connectivity neighbors
command is 'unknown'.
|
Cable-plan is not enforced.
|
-
Open an SSH terminal session.
-
To verify if the cable plan enforcement is disabled via
the
show fabric connectivity
neighbors command output, check if the output reads the following
message "Cable-Plan Enforce: Disabled" and the cable-plan column displays
“unknown".
-
In order to generate/import/enforce cable-plan, use the
fabric connectivity
cable-plan.. command.
-
Once a cable-plan is successfully enforced, the output
of
show fabric connectivity
neighbors will list the appropriate cable-plan entry.
|
Feedback