I have too much QOS on the brain and misunderstood tagging in that I was thinking of DSCP tagging, not VLAN tagging. VLAN tagging makes more sense now so I added all of the VLAN tags that I would need. The results are the same though when I have all of the vlans added.
<Earlier you mentioned that you wanted a trunk interface configured. This implies that you are going to tag. However, you probably expected that we would allow all VLANs but we do not. If its a problem for you we can look into it.> Not a problem. snmpwalk -v 2c -c 192.168.10.228 1.3.6.1.4.1.9.9.46.1.6.1.1.13 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10001 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10002 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10003 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10004 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10005 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10006 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10007 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10008 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10009 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10010 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10011 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10012 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10013 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10014 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10015 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10016 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10017 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10018 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10019 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10020 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10021 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10022 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10023 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10024 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10101 = INTEGER: 4 SNMPv2-SMI::enterprises.9.9.46.1.6.1.1.13.10102 = INTEGER: 4 FYI: Ports 1 and 4 trunks are not trunks because of PF because they are not being managed by PF. The floating device is currently plugged into port 17. Thanks Olivier.. -----Original Message----- From: Olivier Bilodeau [mailto:[email protected]] Sent: Thursday, February 03, 2011 1:50 PM To: [email protected] Subject: Re: [Packetfence-users] Floating Network Device port not configuring correctly Hi Kurtis, First, I know floating devices were not developed in a VoIP context so don't be surprised if your Voice VLAN or maximum 2 statements disappear from your port config after a floating device passed. > > <Here is the log. It appears that the problem first of all was that > I did not have any 'tagged vlans' defined because I don't want to tag any > traffic from this device.> > Earlier you mentioned that you wanted a trunk interface configured. This implies that you are going to tag. However, you probably expected that we would allow all VLANs but we do not. If its a problem for you we can look into it. > <So I added VLAN 200 as a tagged vlan, reset the port config and tried again > and tried again.> > > Feb 03 09:13:28 pfsetvlan(17) INFO: secureMacAddrViolation trap received on > 192.168.10.228 ifIndex 10015 for ac:67:06:15:30:30 (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(17) INFO: The floating network device > ac:67:06:15:30:30 has just plugged into 192.168.10.228 port 10015. Enabling > floating network device configuration on the port. (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(17) INFO: Disabling port-security on port 10015 > (pf::floatingdevice::enablePortConfig) > Feb 03 09:13:28 pfsetvlan(17) DEBUG: opening SNMP v2c write connection to > 192.168.10.228 (pf::SNMP::connectWrite) > Feb 03 09:13:28 pfsetvlan(17) INFO: Setting port 10015 as trunk. > (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk) > Feb 03 09:13:28 pfsetvlan(17) ERROR: An error occured while enabling port > 10015 as multi-vlan (trunk) > (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk) > Feb 03 09:13:28 pfsetvlan(17) INFO: An error occured while enabling floating > network device configuration on port 10015. It may not work! > (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(17) INFO: finished (main::cleanupAfterThread) > Feb 03 09:13:28 pfsetvlan(17) DEBUG: closing SNMP v2c read connection to > 192.168.10.228 (pf::SNMP::disconnectRead) > Feb 03 09:13:28 pfsetvlan(17) DEBUG: closing SNMP v2c write connection to > 192.168.10.228 (pf::SNMP::disconnectWrite) > Feb 03 09:13:28 pfsetvlan(18) INFO: nb of items in queue: 1; nb of threads > running: 0 (main::startTrapHandlers) > Feb 03 09:13:28 pfsetvlan(18) DEBUG: opening SNMP v2c read connection to > 192.168.10.228 (pf::SNMP::connectRead) > Feb 03 09:13:28 pfsetvlan(18) INFO: secureMacAddrViolation trap received on > 192.168.10.228 ifIndex 10015 for ac:67:06:15:30:30 (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(18) INFO: The floating network device > ac:67:06:15:30:30 has just plugged into 192.168.10.228 port 10015. Enabling > floating network device configuration on the port. (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(18) INFO: Disabling port-security on port 10015 > (pf::floatingdevice::enablePortConfig) > Feb 03 09:13:28 pfsetvlan(18) DEBUG: opening SNMP v2c write connection to > 192.168.10.228 (pf::SNMP::connectWrite) > Feb 03 09:13:28 pfsetvlan(18) INFO: Setting port 10015 as trunk. > (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk) > Feb 03 09:13:28 pfsetvlan(18) ERROR: An error occured while enabling port > 10015 as multi-vlan (trunk) > (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk) > Feb 03 09:13:28 pfsetvlan(18) INFO: An error occured while enabling floating > network device configuration on port 10015. It may not work! > (main::handleTrap) > Feb 03 09:13:28 pfsetvlan(18) INFO: finished (main::cleanupAfterThread) > Feb 03 09:13:28 pfsetvlan(18) DEBUG: closing SNMP v2c read connection to > 192.168.10.228 (pf::SNMP::disconnectRead) > Feb 03 09:13:28 pfsetvlan(18) DEBUG: closing SNMP v2c write connection to > 192.168.10.228 (pf::SNMP::disconnectWrite) > Thanks for the output! Now can you try running: snmpwalk -v 2c -c <your read community string> 192.168.10.228 1.3.6.1.4.1.9.9.46.1.6.1.1.13 (all on one line) and show me what you get. You need the net-snmp-utils package installed. Thanks! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
