PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000349PacketFence 1.71.7.2public2008-07-18 14:522008-07-21 11:51
Reporterrbalzard 
Assigned Torbalzard 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Versionmonotone 
Summary0000349: Add a resetVlanNetwork fonction to pfcmd_vlan in case of major PacketFence failure
DescriptionIf PacketFence fails and VLAN Isolation is used, we need to have a way to reset all ports on all switches to their default VLAN so network is not down.
TagsNo tags attached.
fixed in mtn revision
Attached Files

- Relationships
related to 0000351closed PacketFence enhance resetVlanNetwork 

-  Notes
(0000757)
rbalzard (administrator)
2008-07-18 15:07

In the first version of this function, the intelligence is going to be very basic:

check if any PF service is running ("pfcmd control pf status")
  if yes
    tell the user to do "service PacketFence stop"
    quit
  end if

for each switch in production mode
  read defaultVLAN (new parameter in switches.conf for every switch)
  
  for each non uplink port
     - setVlan to defaultVLAN
     - shut the port
     - no shut the port (this way, computer renew is IP)
  end for
end for
(0000759)
rbalzard (administrator)
2008-07-18 15:21

In the next version:

if there is a connection to database
  for each non uplink port
    if a MAC is connected:
       determine in which VLAN should be the port based on the MAC status
       if port is already in this VLAN
         do nothing
       else
         set port to VLAN
         shut the port
         no shut the port
       end if
    else
      setport to defaultVLAN
    end if
  end for
else
...
(0000763)
user4
2008-07-21 11:50

First version availalbe in mtn revision a773c6035eae542ae495c7ff4c0185139bfe06f5
(0000764)
user4
2008-07-21 11:50

The more elaborate version will go into PF 1.8
(0000765)
user4
2008-07-21 11:51

a773c6035eae542ae495c7ff4c0185139bfe06f5

- Issue History
Date Modified Username Field Change
2008-07-18 14:52 rbalzard New Issue
2008-07-18 14:53 rbalzard Status new => assigned
2008-07-18 14:53 rbalzard Assigned To => rbalzard
2008-07-18 14:54 rbalzard Category => 1.7.2
2008-07-18 15:07 rbalzard Note Added: 0000757
2008-07-18 15:21 rbalzard Note Added: 0000759
2008-07-21 11:50 user4 Note Added: 0000763
2008-07-21 11:50 user4 Note Added: 0000764
2008-07-21 11:51 user4 Status assigned => closed
2008-07-21 11:51 user4 Note Added: 0000765
2008-07-21 11:51 user4 Resolution open => fixed
2008-07-21 11:51 user4 Fixed in Version => monotone
2008-07-21 11:52 user4 Relationship added related to 0000351


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker