Ask Your Question
0

(Mitaka) Network validation failed in fuel 9

asked 2016-09-13 06:24:20 -0500

anonymous user

Anonymous

updated 2016-09-13 06:26:15 -0500

I am deploying openstack Mitaka with 3 Compute + Ceph and 1 Controller using Fuel 9. Nodes are discovered . but when i do network validation check it gives error.

mcollective call failed in agent 'net_probe', xxxx reason: listener did not reported status.

We are using neutron with VXLAN. we have already enabled jumbo frames in private, public and management VLAN.

Anyone faced such issue before?

edit retag flag offensive close merge delete

Comments

check your port configurations and ensure your vlans are tagged properly, and your interfaces on the machines are configured as well

bcollins gravatar imagebcollins ( 2016-09-13 10:20:43 -0500 )edit

All the switch ports connected to respective vlans Switch Vlan2(management, storage)-> port 1-8 (mode access) Switch Vlan3(public)-> port 9-16 (mode access) Switch Vlan4(private)-> port 17-22 (mode access)

Configured 9000 mtu in switch

Do i need to make private vlan (vlan 4) ports as trunk

tsheth gravatar imagetsheth ( 2016-09-14 22:15:41 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2016-09-15 22:12:02 -0500

tsheth gravatar image

The issue is resolved. It was the switch configuration. I have changed switch port configuration to hybrid (auto detect).

Access port was not allowing management and storage tags.

edit flag offensive delete link more

Comments

good find. i knew it had to be physical :)

bcollins gravatar imagebcollins ( 2016-09-15 23:55:04 -0500 )edit
0

answered 2017-07-19 04:53:10 -0500

Prathamesh gravatar image

Hello ,

I am getting same error in my environment :

Verification failed. Method verify_networks. 9dafeea3-1a4b-4d00-9a35-cb8adc7bee87: MCollective call failed in agent 'net_probe', method 'start_frame_listeners', failed nodes: ID: 1 - Reason: Listener did not reported status ID: 4 - Reason: Listener did not reported status ID: 3 - Reason: Listener did not reported status ID: 2 - Reason: Listener did not reported status .

Inspect Astute logs for the details

In my environment, trunk port is already configured.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-09-13 06:24:20 -0500

Seen: 685 times

Last updated: Sep 15 '16