> > Hi, > > I have a question of how fcoemon/fcoeadm handles vlan id change in the > switch. > > When I change vlan_id in the switch, I expected the fcoeadm/fcoemon to > handle the CVL by calling fcoe_destroy, followed by vlan discovery and > call fcoe_create with the new vlan_id that was discovered. However, I > didnt observe this behavior when I tested this. > > Once the vlan_id is changed, the targets disappeared after dev_loss_tmo. > I had to manually call fcoeadm -d followed by -c to rediscover the > targets. > > Is it currently implemented this way, or did I miss something? > > Thanks, > Bhanu
AFAIK, the current implementation should work. Do you have AUTO_VLAN set to "yes" in your corresponding fcoe cfg? As I recall, that will allow fcoemon to automatically create vlan interface for the vid from the VLAN descriptor of the newly received VLAN notification. Also, I think we are doing lport reset only in libfcoe, can't say for sure if we are doing -d or not on a vlan that's gone... yi > > > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
