Network Segmentation Manager
This chapter describes how to identify and resolve problems with Network Segmentation Manager (NSM).
Information About Network Segmentation Manager
See the Cisco Nexus 1000V for KVM Virtual Network Configuration Guide, Release 5.x for more information.
Problems with Network Segmentation Manager
The following are symptoms and possible causes for problems with virtual networking.
|
|
OpenStack Neutron operations fails if the VSM is not reachable. |
Verify that the VSM and the controller node are connected and resolve connectivity issues, if any. |
Creation of networks/subnets/ports fails if it exceeds the quota set in configuration file, neutron.conf |
Verify that the quota set in /etc/neutron/neutron.conf is not exceeded. If quota is exceeded, adjust the quota and restart neutron-server on all nodes. |
If the VEM port count exceeds 990, vEth ports cannot be created, and this condition impacts data traffic. |
Verify whether the number of VEM ports do not exceed 900 virtual ports. Remove some ports, if required. |
Neutron agent-list and Nova service-list fails when executing commands. |
Verify whether the Neutron and Nova services are correctly configured. Resolve configuration issues, see Red Hat Enterprise Linux OpenStack Platform 7 Director Installation and Usage. |
For more information about problems occurring with NSM, see Problems with Port Profiles.
Network Segmentation Manager Troubleshooting Commands
You can use the commands in this section to troubleshoot problems related to the NSM.
|
|
show nsm ip pool template name name |
Displays the IP pool template information. |
show nsm ip pool template usage network segment |
Displays the network segment using an IP pool template. |
show nsm logical network name |
Displays the NSM logical network name. |
show nsm network segment brief |
Displays brief information about the network segment information. |
show nsm network segment filter network segment pool name |
Displays the filtered information for a network segment pool. |
show nsm network segment filter vlan vlan_ID |
Displays the network segment VLAN information. |
show nsm network segment name name |
Displays network segment information. |
show nsm network segment pool name |
Displays network segment pool information. |
show nsm network uplink brief |
Displays brief information about the network segment uplink. |
show nsm network uplink filter import Ethernet Port-Profile name |
Displays network segment uplink information filtered by Ethernet policy port profile. |
show dynamic-port-profile |
Displays dynamic port profile information. |
show dynamic-port-profile name |
Displays dynamic port profile information for the specified port profile. |
show dynamic-port-profile inherit name |
Displays dynamic port profiles with inherited vEthernet policy profiles. |
show dynamic-port-profile network segment name |
Displays dynamic port profile network segment information. |
For detailed information about show command output, see the Cisco Nexus 1000V for KVM Command Reference, Release 5.x.
Virtual Networking Troubleshooting Steps
Use the following steps to help you troubleshoot your virtual network:
1. Check the IP address associated with the router.
# ip netns exec router_namespace_id
2. Verify that the internal port and external port are connected to br-int.
# ovs-vsctl show
3. Check that the router namespace can ping the router gateway floating IP and fixed IP addresses associated with each instance.
# ip netns exec router_namespace_id ping [ router_gateway_floating_IP ]
4. Check that you can ping the floating IP and fixed IP addresses that are associated with the instance.
# ip netns exec router_namespace_id ping router_gw_IP address
5. Check up to which port the ping is reachable.
# tcpdump -i eth1 | grep ICMP
6. Check that all internal ports have VLANs configured in the cisco-network-profile-create command.
# vemcmd show port vlans
# neutron router-list
# neutron router-port-list router
7. Verify that the router port is in the VEM and is in the forwarding state.
# vemcmd show port
8. Verify which network node the router is hosted.
# neutron l3-agent-list-hosting-router
# neutron router-list-on-l3-agent