Cisco Nexus 1000V, Руководство по устранению неисправностей, Страница: 230 / 280

22-12
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 22 System
VEM Log Commands
show l2 <bd-number> Show the L2 table for a given BD/VLAN
show l2 all Show the L2 table
show port [priv|vsm] Show the port table
show pc Show the port channel table
show portmac Show the port table MAC entries
show trunk [priv|vsm] Show the trunk ports in the port table
show stats Show port stats
VEM Log Commands
Use the following commands to control the vemlog:
• vemlog stop – stops the log
•
vemlog clear – clear s the log
• vemlog start number-of-entries – starts the log and stops it after the specified number of entries
•
vemlog stop number-of-entries – stops the log after the next specified number of entries
• vemlog resume – starts the log, but does not clear the stop value
Error Messages
On the vSphere Client, you can see error messages under the recent tasks tab. You can find detailed
description of the error under the Tasks and Events tab. The same messages are also propagated to the
VSM.
Table 22-1 lists error messages that you might see on the VSM.
Table 22-1 Error Messages on the VSM
Error Description
ERROR: [VMWARE-VIM] Extension key was
not registered before its use This error indicates that VSM extension key is not
registered.
ERROR: [VMWARE-VIM] A DVS switch with
spec.name as switch already exists, cannot create
DVS switch. A specified parameter was not
correct. spec.name. This error is displayed after you enter the first
connect command, and indicates that a DVS
already exists with the same name.
ERROR: [VMWARE-VIM] A DVS switch with
spec.extensionKey as
Cisco_Nexus_1000V_2055343757 already
exists, cannot create DVS new-switch. A
specified parameter was not correct.
spec.extensionKey This error is displayed when the VSM tries to
create a different DVS after changing the switch
name.