Cisco Nexus 1000V Troubleshooting Guide, Release 4.0
Table Of ContentsTroubleshooting the Installation
Isolating Installation Problems
Ensuring vSphere 4.0 Supports Nexus 1000V
Refreshing the vCenter Server Connection
Recreating the Installation
Cleaning Up the vCenter Server
Improving Performance
Verifying the Configuration of Nexus 1000V Domain Parameters
Verifying the Correct Assignment of Port Groups to VSM VM Virtual Interfaces
Verifying Connectivity Between VSM and vCenter Server
Troubleshooting Connection Issues to a vCenter Server
Recovering the Network Administrator Password
Using the CLI with Network-Admin Privileges
Power Cycling the Device
Resolving a Plug-In Conflict
Viewing the Extension Keys
Finding the Extension Key Tied to a Specific DVS
Removing the Extension Key from a Specific DVS
Troubleshooting the Installation
This chapter describes how to identify and resolve problems that might occur during the installation of the Cisco Nexus 1000V.
This chapter includes the following sections:
•Isolating Installation Problems
•Improving Performance
•Verifying the Configuration of Nexus 1000V Domain Parameters
•Verifying the Correct Assignment of Port Groups to VSM VM Virtual Interfaces
•Verifying Connectivity Between VSM and vCenter Server
•Troubleshooting Connection Issues to a vCenter Server
•Recovering the Network Administrator Password
•Resolving a Plug-In Conflict
•Resolving a Plug-In Conflict
•Viewing the Extension Keys
Isolating Installation Problems
Use this flow chart to isolate a problem with the installation.
Flow Chart: Isolating Installation Problems
[attach]8754[/attach]
Ensuring vSphere 4.0 Supports Nexus 1000V
Before you begin troubleshooting any installation issue, make sure that you have the required VMware license.The Cisco Nexus 1000V requires an Enterprise Plus license for VMware ESX 4.0 servers. Without the Enterprise Plus license, hosts in a data center do not appear in the Add Host to Distributed Virtual Switch dialog box. See Figure 3-1.
Figure 3-1 Add Host to Distributed Virtual Switch Dialog Box
[attach]8755[/attach]
If this situation occurs, you need to upgrade the VMware ESX 4.0 servers to an Enterprise Plus license.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•Log in to the vSphere Client and the Nexus 1000V.
To view the current license of a particular host, follow these steps:
Step 1 Select the host.
Step 2 Click the Configuration tab.
Step 3 Select Licensed Features.
Cisco Nexus 1000V requires the Distributed Virtual Switch product feature that is included as part of the Enterprise Plus license. Figure 3-2 shows the correct output for the ESX Server License.
Figure 3-2 ESX Server License Showing Distributed Virtual Switch Feature
[attach]8756[/attach]
Refreshing the vCenter Server Connection
Use this procedure to refresh the connection between the Nexus 1000V and vCenter Server.
Step 1 From the Nexus 1000V Connection Configuration mode on the VSM, enter the following command sequence:
Example:
n1000v# config t
n1000v(config)# svs connection s1
n1000v(config-svs-conn)# no connect
n1000v(config-svs-conn)# connect
Step 2 You have completed this procedure.
Recreating the Installation
Use this section to recreate the complete configuration in the event of a persistent problem that cannot be resolved using any other workaround.
BEFORE YOU BEGIN
Before beginning these procedures, you must know or do the following:
•Review the flow chart and steps involved and ensure you have the appropriate information needed for this procedure.
[attach]8763[/attach]
[font=Arial, Helvetica, sans-serif][size=13px]Cleaning Up the vCenter Server[align=left][font=Arial, Helvetica, sans-serif][size=12px]Use this procedure to remove the hosts from the Cisco Nexus 1000V DVS and remove the Cisco Nexus 1000V DVS from vCenter Server.[/size][/font][/align]
BEFORE YOU BEGIN[align=left][font=Arial, Helvetica, sans-serif][size=12px]Before beginning this procedure, you must know or do the following:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]You are logged in to the vSphere Client and the Nexus 1000V.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 1 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]From the vSphere Client, choose
[b]Inventory
[/b][font=Wingdings][b]‡[/b][/font][b]
Networking[/b].[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 2 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Select the Nexus 1000V DVS and select the
[b]Hosts[/b]
tab.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 3 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Right-click each host, and choose
[b]Remove from Distributed Virtual Switch[/b].[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 4 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]On the VSM, enter the[b]
show vmware vc extension-key
[/b]command to verify the extension key.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 5 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Delete the extension key that is present on vCenter Server using the Managed Object Browser (MOB) Unregister Extension API, as follows:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]a. [/b][img=10,2]http://netemu.cn/i/templates/blank.gif[/img]Go to the extension manager [https://<vc-ip>/mob/?moid=ExtensionManager][/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]b. [/b][img=10,2]http://netemu.cn/i/templates/blank.gif[/img]Click
[b]Unregister Extension[/b]
[https://<vc-ip>/mob/?moid=ExtensionManager&method=unregisterExtension][/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]c. [/b][img=10,2]http://netemu.cn/i/templates/blank.gif[/img]Paste Cisco_Nexus_1000V_495736846 (your extension key attached to the DVS) and click
[b]Invoke Method[/b].[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 6 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]From the Nexus 1000V Connection Configuration mode, remove the DVS from the vCenter Server as follows:.[/size][/font][/align]
[size=11px]n1000v# [b]conf t[/b][/size]
[size=11px]n1000v(config)# [b]svs connection VC[/b][/size]
[size=11px]n1000v(config-svs-conn)# [b]no vmware dvs[/b][/size]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]The DVS is removed from the vCenter Server.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 7 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]You have completed this procedure.
Return to
[url=http://netemu.cn/bbs/post.php?action=edit&fid=469&tid=11551&pid=117794&page=1&extra=page%3D1#wp1213749]FlowChart: Recreating the Installation[/url].[/size][/font][/align]
Improving Performance[align=left][font=Arial, Helvetica, sans-serif][size=12px]Use the following pointers to improve performance on the ESX host and the VMs.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Install VMware Tools on the vCenter Server VM, with Hardware Acceleration enabled to the full.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Use the command line interface in the VMs instead of the graphical interface where possible.[/size][/font][/align]
Verifying the Configuration of Nexus 1000V Domain Parameters[align=left][font=Arial, Helvetica, sans-serif][size=12px]The Nexus 1000V Virtual Supervisor Module (VSM) and Virtual Ethernet Module (VEM) are separated within a Layer 2 domain. To allow VSM-VEM pairs to communicate within the same Layer 2 domain, each pair must have a unique identifier. The Nexus 1000V domain ID serves as the unique identifier that allows multiple VSM-VEM pairs communicate inside the same Layer 2 domain.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]Following the installation of the Cisco Nexus 1000V, make certain that you configure a domain ID. Without a domain ID, the VSM will not be able to connect to the vCenter Server. Follow these guidelines:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]The Nexus 1000V domain ID should be a value within the range of 1 to 4095.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]All the control traffic between the VSM and the VEM is carried over the configured control VLAN.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]All the data traffic between the VSM and the VEM is carried over the configured packet VLAN.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Make sure the control VLAN and the packet VLAN are allowed on the port in the upstream switch to which the physical NIC of the host hosting the VSM and VEM VM are connected.[/size][/font][/align]
Verifying the Correct Assignment of Port Groups to VSM VM Virtual Interfaces[align=left][font=Arial, Helvetica, sans-serif][size=12px]Verify if two port groups are created on the ESX Host hosting the VSM VM through the vCenter Server. The following port groups (PG) should be created:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Control PG (Vlan = Control VLAN)[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Packet PG (Vlan = Packet VLAN)[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Management PG (Vlan = Management VLAN)[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]Make sure the port groups are assigned to the three virtual interfaces of the VSM VM in the following order:
[/size][/font][/align]
[align=left][table=80%][tr][td][align=left][font=Arial, Helvetica, sans-serif][size=13px][b]Virtual Interface Number[/b][/size][/font][/align]
[/td][td][align=left][font=Arial, Helvetica, sans-serif][size=13px][b]Port Group[/b][/size][/font][/align]
[/td][/tr][tr][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]Network Adapter 1[/size][/font][/align]
[/td][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]Control PG[/size][/font][/align]
[/td][/tr][tr][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]Network Adapter 2[/size][/font][/align]
[/td][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]MGMT PG[/size][/font][/align]
[/td][/tr][tr][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]Network Adapter 3[/size][/font][/align]
[/td][td][align=left][font=Arial, Helvetica, sans-serif][size=12px]Packet PG[/size][/font][/align]
[/td][/tr][/table][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]To verify if the VSM VM network adapter 1, network adapter 2, and network adapter 3 are carrying the control VLAN, management VLAN, and the packet VLAN, follow these steps:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 1 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Enter the
[b]show mac address table dynamic interface vlan[/b]
[i]control-vlan[/i]
command on the upstream switch.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]Expected Output: the network adapter1 MAC address of the VSM VM.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 2 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Enter the
[b]show mac address table dynamic interface vlan[/b]
[i]mgmt-vlan[/i]
command on the upstream switch.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]Expected Output: the network adapter2 MAC address of the VSM VM.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 3 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Enter the
[b]show mac address table dynamic interface vlan[/b]
[i]packet-vlan[/i]
command on the upstream switch.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]Expected Output: the network adapter3 MAC address of the VSM VM.[/size][/font][/align]
Verifying Connectivity Between VSM and vCenter Server[align=left][font=Arial, Helvetica, sans-serif][size=12px]When troubleshooting connectivity issues between the VSM and vCenter Server, follow these guidelines:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Ensure that Nexus 1000V domain parameters are configured correctly.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Make sure the Windows VM machine hosting the vCenter Server has the following ports open.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]–[img=17,2]http://netemu.cn/i/templates/blank.gif[/img]Port 80[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]–[img=17,2]http://netemu.cn/i/templates/blank.gif[/img]Port 443[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Try reloading the VSM if after verifying the preceding steps, the connect still fails.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Check if the VSM extension is created by the vCenter Server by pointing your web browser to https://your-virtual-center/mob/, and then clicking Content > Extension Manager.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]To troubleshoot connectivity issues between a VSM and a vCenter Server, follow these steps:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 1 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Ensure that Nexus N1000V VSM VM network adapters are configured properly.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 2 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Make sure the Windows VM machine hosting the vCenter Server has the following ports open.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Port 80[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]Port 443[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 3 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Ping the vCenter Server from the Nexus 1000V VSM.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 4 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Ensure the VMware VirtualCenter Server service is running.[/size][/font][/align]
Troubleshooting Connection Issues to a vCenter Server[align=left][font=Arial, Helvetica, sans-serif][size=12px]To troubleshoot connection problems between a Cisco Nexus 1000V VSM and a vCenter Server, follow these steps:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 1 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]In a web browser, enter the path: http://<VSM-IP>[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 2 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Download the cisco_nexus_1000v_extension.xml file to your desktop.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 3 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]From the vCenter Server menu, choose
[b]Plugins
[/b][font=Wingdings][b]‡[/b][/font][b]
Manage Plugins.[/b]
Right click an empty area and select the plugin in Step2 as the New Extension.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]If these steps fail, then you may be using an out-of-date .xml file.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]To confirm that the extension is available, follow these steps:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 1 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]In a web browser, enter the path: http://<vCenter-Server-IP>/mob.[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 2 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Click
[b]Content[/b].[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 3 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]Click
[b]extensionManager[/b].[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Step 4 [/b][img=5,2]http://netemu.cn/i/templates/blank.gif[/img]If extensionList[Cisco_Nexus_1000v_584325821] is displayed in the value column, then proceed to connect to the VSM.[/size][/font][/align]
[align=left][img]http://netemu.cn/i/templates/note.gif[/img][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px][b]Note [/b][img=1,2]http://netemu.cn/i/templates/blank.gif[/img]The actual value of "Cisco_Nexus_1000V_584325821" will vary. It should match the extension key from the cisco_nexus_1000v_extension.xml file.[/size][/font][/align]
Recovering the Network Administrator Password[align=left][font=Arial, Helvetica, sans-serif][size=12px]You can recover the network administrator password using one of two methods:[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]From the CLI with a username that has network-admin privileges[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]•[img=19,2]http://netemu.cn/i/templates/blank.gif[/img]By power cycling the device[/size][/font][/align]
[align=left][font=Arial, Helvetica, sans-serif][size=12px]This section includes the following topics:[/size][/font][/align]
[/size][/font]
Using the CLI with Network-Admin Privileges
•Power Cycling the Device
Using the CLI with Network-Admin Privileges
If you are logged in to the device, or can log in to it with a username that has network-admin privileges, follow these steps:
Step 1 Verify that your username has network-admin privileges.
n1000V# show user-account
user:admin
this user account has no expiry date
roles:network-admin
user:dbgusr
this user account has no expiry date
roles:network-admin network-operator
Step 2 Assign a new network administrator password if your username has network-admin privileges, .
n1000V# configure terminal
n1000V(config)# username admin password <new password>
n1000V(config)# exit
n1000V#
Step 3 Save the configuration.
n1000V# copy running-config startup-config
Power Cycling the Device
If you cannot start a session on the device that has network-admin privileges, you must recover the network administrator password by power cycling the device.
Caution This procedure disrupts all traffic on the device. All connections to the device will be lost for two to three minutes.
Note You cannot recover the administrator password from a Telnet or SSH session. You must have access to the local console connection.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•Boot the VSM from the CD and ensure that you have the VSM ISO file in the datastore.
•Power on the VSM and select the Install Nexus 1000v and go to vsh option during the VSM bootup process.
To recover the network administrator password by power cycling the device, follow these steps:
Step 1 Establish a terminal session on the console port of the active supervisor module.
Step 2 Power cycle the device.
Step 3 Press the Ctrl-] key sequence from the console port session when the device begins the Cisco NX-OS software boot sequence to enter the switch(boot)# prompt mode.
Ctrl-]
n1000V(boot)#
Step 4 Reset the network administrator password.
n1000V(boot)# configure terminal
n1000V(boot-config)# admin-password <new password>
n1000V(boot-config)# exit
n1000V(boot)#
Step 5 Display the bootflash: contents to locate the Cisco NX-OS software image file.
n1000V(boot)# dir bootflash:
Step 6 Load the Cisco NX-OS system software image.
In the following example, the system image filename is nx-os.bin:
n1000V(boot) # load bootflash:nx-os.bin
Step 7 Log in to the device using the new administrator password.
switch login: admin
Password: <new password>
Step 8 Reset the new password to ensure that is it is also the SNMP password.
n1000V# configure terminal
n1000V(config)# username admin password <new password>
n1000V(config)# exit
n1000V#
Step 9 Insert the previously removed standby supervisor module into the chassis, if necessary.
Step 10 Boot the Cisco NX-OS kickstart image on the standby supervisor module, if necessary.
In the following example, the image filename is nx-os_kickstart.bin:
loader# boot bootflash:nx-os_kickstart.bin
Step 11 Load the Cisco NX-OS system software on the standby supervisor module, if necessary.
In the following example, the image filename is nx-os.bin:
n1000V(boot)# load bootflash:nx-os.bin
Step 12 Save the configuration.
n1000V# copy running-config startup-config
Resolving a Plug-In Conflict
If you see the error, "The specified parameter was not correct," when Creating a Nexus 1000V Plug-In on the vCenter Server, then you have tried to register a plugin that is already registered.
Use the following procedure to resolve this problem.
Step 1 Make sure that you are using the correct cisco_nexus1000v_extension.xml file.
Step 2 Make sure that you have refreshed your browser since it caches this file and unless refreshed it might cache obsolete content with the same file name.
Step 3 Follow the steps described in the "Viewing the Extension Keys" section to compare the extension key installed on the VSM with the plug-in installed on the vCenter Server.
Viewing the Extension Keys
Use this procedure to compare the extension key installed on the VSM with the plug-in installed on the vCenter Server for verification purposes.
Step 1 To view the extension key on the VSM, from the Nexus 1000V, enter the following command:
show vmware vc extension-key
Example:
n1000v# show vmware vc extension-key
Extension ID: Cisco_Nexus_1000V_1935882621
n1000v#
Step 2 To view the extension key on the vCenter Server, open an Internet browser such as Internet Explorer and go to the vCenter Server address.
http://<VC_IP_ADDRESS>/mob.
An authentication dialog box opens.
Figure 3-3 Authenticating with the vCenter Server[attach]8764[/attach]
Step 3 Add your username and password, and click OK.
The Managed Object Browser (MOB) opens to the Service Instance page.
Figure 4 Verifying Plug-In—Managed Object: Service Instance[attach]8765[/attach]
页:
[1]