PacketFence - BTS - PacketFence |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000845 | PacketFence | configuration | public | 2009-11-10 17:38 | 2010-11-19 14:35 |
|
| Reporter | steven1545 | |
| Assigned To | obilodeau | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | |
| Platform | | OS | | OS Version | |
| Product Version | 1.8.5 | |
| Target Version | | Fixed in Version | | |
| fixed in git revision | |
| fixed in mtn revision | |
|
| Summary | 0000845: system not getting proper vlan |
| Description | I am very new to PF and I have been able to install it and access the web GUI. I am not sure where I went wrong, but when a system is plugged into the switch it automatically assigns it to the normalVlan, but in the nodes section of the web gui it labels that mac address as unreg. I think that it might have something to do with my snmptraps my cisco 3500XL switch says that it sends the LINKUP and DOWN traps to my server, but my snmptrapd.log file is empty. If I manually add a port of the switch to vlan 2 or 3, then I get an address and can access the registration page. Any help would be appreciated. Thanks |
| Steps To Reproduce | |
| Additional Information | Server OS = CentOS 5.4
Switch = Cisco 3500XL
I have attached all my configurations |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  configs.tar.gz (2,198) 2009-11-10 17:38
https://www.packetfence.org/bugs/file_download.php?file_id=45&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-11-10 17:38 | steven1545 | New Issue | |
| 2009-11-10 17:38 | steven1545 | File Added: configs.tar.gz | |
| 2009-11-11 09:52 | obilodeau | Note Added: 0001395 | |
| 2009-11-11 09:52 | obilodeau | Status | new => assigned |
| 2009-11-11 09:52 | obilodeau | Assigned To | => obilodeau |
| 2009-11-11 09:54 | obilodeau | Note Added: 0001396 | |
| 2009-11-30 14:02 | obilodeau | Note Added: 0001414 | |
| 2009-11-30 14:02 | obilodeau | Severity | major => minor |
| 2009-11-30 14:02 | obilodeau | Status | assigned => feedback |
| 2010-05-05 13:33 | obilodeau | Category | 1.8.5 => 1.8.x |
| 2010-05-05 13:33 | obilodeau | Product Version | trunk => 1.8.5 |
| 2010-11-19 14:35 | obilodeau | Note Added: 0001768 | |
| 2010-11-19 14:35 | obilodeau | Status | feedback => closed |
| 2010-11-19 14:35 | obilodeau | Resolution | open => unable to reproduce |
| 2010-11-19 14:35 | obilodeau | Category | 1.8.x => configuration |
|
Notes |
|
|
|
You should definitely be getting snmp traps on the packetfence system.
Verify that snmptrapd is properly started:
# ps -ef | grep snmptrapd
root 6560 1 0 09:40 ? 00:00:00 /usr/sbin/snmptrapd -n -c /usr/local/pf/conf/snmptrapd.conf -C -A -Lf /usr/local/pf/logs/snmptrapd.log -p /usr/local/pf/var/snmptrapd.pid -On
port udp 162 is in listen:
# netstat -an | grep 162
udp 0 0 0.0.0.0:162 0.0.0.0:*
and verify your firewall config that access to port udp 162 is allowed (in /etc/sysconfig/iptables) |
|
|
|
|
|
If the above doesn't help, check your logs/packetfence.log for any hint on why snmptrapd doesn't start. |
|
|
|
|
|
waiting for feedback (and reduced priority) |
|
|
|
|
|
closing for lack of feedback |
|