Route Map Interface Binding Only lists default VLAN

Hi @erfritts,

What model switch are you having issue with? What is the current firmware version? Could you give us a better view of the mentioned issue, it is still not selectable. Maybe screenshots. Could you provide us your switch VLAN and Route Map configuration.

I believe the version is 6.3.3.10. The switch is an N3048. There isn't anything wrong with the switch just the operator. I am a newby. I am using the Open Manage interface and I have created the following VLANs:

32

172

So I have 3 VLANs including the default. I created a map called Policy172 with a sequence number 172 and a permit action. It will send traffic to the firewall. Everything works fine up to this point until I go to the page to bind the map to the VLAN. the drop down menu doesn't show my configured VLANs. I read in the forum that the VLAN needs to be active and to make it active I just need to plug a client into one of the VLAN access ports. I did that and the drop down still only shows the default VLAN.

Erfritts,

I would suggest starting with updating the firmware to current. You may also want to look on page 1554 here for rules to creating maps. 

I don't have the option of updating the firmware as I am not the manager of the data center. Thanks for the link it was an interesting read. Even though the port I plugged into is assigned to my VLAN and shows a status of being up my VLAN does not have an active status and therefore the switch will not let me select it as a bindable interface for the route map I created. I just don't know why the VLAN I created is not active. How do I make it active?

Hi @erfritts,

It might be related to your VLAN configuration, I'm unsure. Could you do a show VLAN 32 and 172 to check the status of the VLANs. Also, could you provide a screenshot of the stated error that you mentioned about binding the route map and it's showing VLAN not active. It also might be related to the switch firmware and OpenManage version. What is the OpenManage version? Oh, and are you referring OpenManage to OpenManage Network Manager?

There was never an error. It was simply not selectable in the dropdown menu. I read somewhere in your forum that it had to be active to be selectable so I started trying to find out why it wasn't. I gave 172 it's own ip and it became selectable. So I guess in order to route a VLAN it needs its own IP address?

Erfritts,

That is correct, the VLAN would need its own IP address.