Hi, If you are a vendor (or experimenter in later specifications), you will have a vendor ID, which identifies you. Typically you will want to have multiple vendor features and so use multiple message types under your vendor ID, so you will have to use another type system (called sub-type) that identifies the various messages you want to send to the switch.
In OF 1.0 and 1.1 the experimenter body is "uninterpreted", meaning you can invent your own of sub-typing system for your messages. In OF 1.2 and later there is a mandated way to do sub-typing of exptensions. Look for "exp_type" fields for details. So the answer your question is that when a switch receives a vendor message, if the vendor ID is not recognized, it returns OFPBRC_BAD_VENDOR, but if the vendor ID is known to the switch, but the vendor specific sub-type is not, the switch returns the OFPBRC_BAD_SUBTYPE code. Regards, Zoltan. ________________________________________ From: [email protected] [[email protected]] on behalf of pragyan dash [[email protected]] Sent: Wednesday, 19 December 2012 6:45 AM To: openflow-discuss Subject: Re: [openflow-discuss] "Vendor Subtype not supported" Error Code in Open Flow spec 1.0 Gentle Reminder.... On Mon, Dec 17, 2012 at 8:34 PM, pragyan dash <[email protected]<mailto:[email protected]>> wrote: Hi, Under what circumstances, Open Flow 1.0 Switch will generate the following error - Error Type - OFPET_BAD_REQUEST (Request was not understood) Error Code - OFPBRC_BAD_SUBTYPE (Vendor Subtype not supported) Regards, Pragyan _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
