Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Problem with DHCP and a Cisco nexus 5020 10GB siwtch Not gettings ip addresses.

    Scheduled Pinned Locked Moved DHCP and DNS
    31 Posts 3 Posters 2.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JKnottJ
      JKnott
      last edited by

      Well, start with the basics.  Do the computers have an address via DHCP from elsewhere?  Can you ping if you manually configure an IP address in the same range as the DHCP server?  Does Packet Capture show any DHCP activity?  Are the computers on a VLAN?  Is pfSense configured for that VLAN?

      PfSense running on Qotom mini PC
      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
      UniFi AC-Lite access point

      I haven't lost my mind. It's around here...somewhere...

      1 Reply Last reply Reply Quote 0
      • R
        redbaron28
        last edited by

        For the switch i cant ping the router. Monitoring shows a little of outpass traffic from opt1 but i couldnt find the dhcp tab. I did att vlan 2 to pfsense vlan tab with no change.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          You have to add the VLAN to the physical interface then assign that interface use the VLAN in Interfaces > Assignments. That will make pfSense send/expect traffic tagged on that VLAN for that pfSense interface.

          ![Screen Shot 2018-02-10 at 10.29.16 PM.png](/public/imported_attachments/1/Screen Shot 2018-02-10 at 10.29.16 PM.png)
          ![Screen Shot 2018-02-10 at 10.29.16 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2018-02-10 at 10.29.16 PM.png_thumb)

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • R
            redbaron28
            last edited by

            @Derelict:

            You have to add the VLAN to the physical interface then assign that interface use the VLAN in Interfaces > Assignments. That will make pfSense send/expect traffic tagged on that VLAN for that pfSense interface.

            On pfsense i have a physical port going to the switch. I dont think i need a vlan on pfsense. On my switch my config looks like this.

            vrf context management
              ip route 0.0.0.0/0 192.168.2.1
            vlan 1
            vlan 2
              name vmware2
            port-profile default max-ports 512

            interface Ethernet1/1

            interface Ethernet1/2

            interface Ethernet1/3

            interface Ethernet1/4

            interface Ethernet1/5

            interface Ethernet1/6

            interface Ethernet1/7

            interface Ethernet1/8

            interface Ethernet1/9

            interface Ethernet1/10
              switchport access vlan 2

            interface Ethernet1/11
              switchport access vlan 2

            interface Ethernet1/12
              switchport access vlan 2

            interface Ethernet1/13
              switchport access vlan 2

            interface Ethernet1/14
              switchport access vlan 2

            interface Ethernet1/15
              switchport access vlan 2

            interface Ethernet1/16
              switchport access vlan 2

            interface Ethernet1/17
              switchport access vlan 2

            interface Ethernet1/18
              switchport access vlan 2

            interface Ethernet1/19

            interface Ethernet1/20

            interface Ethernet1/21

            interface Ethernet1/22

            interface Ethernet1/23

            interface Ethernet1/24

            interface Ethernet1/25

            interface Ethernet1/26

            interface Ethernet1/27

            interface Ethernet1/28

            interface Ethernet1/29

            interface Ethernet1/30

            interface Ethernet1/31

            interface Ethernet1/32

            interface Ethernet1/33

            interface Ethernet1/34

            interface Ethernet1/35

            interface Ethernet1/36

            interface Ethernet1/37

            interface Ethernet1/38

            interface Ethernet1/39

            interface Ethernet1/40
              switchport mode trunk
              switchport trunk allowed vlan 1-2

            interface Ethernet2/1

            interface Ethernet2/2

            interface Ethernet2/3

            interface Ethernet2/4

            interface Ethernet2/5

            interface Ethernet2/6

            interface Ethernet3/1

            interface Ethernet3/2

            interface Ethernet3/3

            interface Ethernet3/4

            interface Ethernet3/5

            interface Ethernet3/6

            interface mgmt0
              ip address 192.168.2.220/24
            line console
            line vty
            boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.9a.bin
            boot system bootflash:/n5000-uk9.5.2.1.N1.9a.bin

            I have now even reset the interfaces and just make a trunk port on interface 1/40 and i still cant ping pfsense.

            Thanks for the help.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              If pfSense is connected to Ethernet 1/40 you have to assign the pfSense interface to VLAN 2. Is this ESXi or what? Where is pfSense? Physical or virtual?

              What is the exact physical layout? What is connected to what?

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • R
                redbaron28
                last edited by

                @Derelict:

                If pfSense is connected to Ethernet 1/40 you have to assign the pfSense interface to VLAN 2. Is this ESXi or what? Where is pfSense? Physical or virtual?

                What is the exact physical layout? What is connected to what?

                Pfsense is in its dedicated server. how my network is set up

                Modem-> pfsense -> lan to 192.168.1.x->switch-> internet side of vmware esxi
                                          |
                                            -> OPT1 to 192.168.2.x ->cisco 5020 switch-> storage network side for vmware hosts

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  If you want OPT1 to talk VLAN 2 to a Cisco trunk port, the OPT1 interface needs to be assigned to VLAN 2 on ethX on pfSense. With ethX being whatever that physical interface is.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • R
                    redbaron28
                    last edited by

                    I did that and re worked my switches config and i still cant ping the router. The attachment is my pfsense lan's page.

                    vrf context management
                      ip route 0.0.0.0/0 192.168.2.1
                    vlan 1
                    vlan 10
                      name vmware10
                    port-profile default max-ports 512

                    interface Ethernet1/1

                    interface Ethernet1/2

                    interface Ethernet1/3

                    interface Ethernet1/4

                    interface Ethernet1/5

                    interface Ethernet1/6

                    interface Ethernet1/7

                    interface Ethernet1/8

                    interface Ethernet1/9
                      switchport access vlan 10

                    interface Ethernet1/10
                      switchport access vlan 10

                    interface Ethernet1/11
                      switchport access vlan 10

                    interface Ethernet1/12
                      switchport access vlan 10

                    interface Ethernet1/13
                      switchport access vlan 10

                    interface Ethernet1/14
                      switchport access vlan 10

                    interface Ethernet1/15
                      switchport access vlan 10

                    interface Ethernet1/16
                      switchport access vlan 10

                    interface Ethernet1/17
                      switchport access vlan 10

                    interface Ethernet1/18
                      switchport access vlan 10

                    interface Ethernet1/19

                    interface Ethernet1/20

                    interface Ethernet1/21

                    interface Ethernet1/22

                    interface Ethernet1/23

                    interface Ethernet1/24

                    interface Ethernet1/25

                    interface Ethernet1/26

                    interface Ethernet1/27

                    interface Ethernet1/28

                    interface Ethernet1/29

                    interface Ethernet1/30

                    interface Ethernet1/31

                    interface Ethernet1/32

                    interface Ethernet1/33

                    interface Ethernet1/34

                    interface Ethernet1/35

                    interface Ethernet1/36

                    interface Ethernet1/37

                    interface Ethernet1/38

                    interface Ethernet1/39

                    interface Ethernet1/40
                      switchport mode trunk
                      switchport trunk native vlan 10
                      switchport trunk allowed vlan 1-10

                    interface Ethernet2/1

                    interface Ethernet2/2

                    interface Ethernet2/3

                    interface Ethernet2/4

                    interface Ethernet2/5

                    interface Ethernet2/6

                    interface Ethernet3/1

                    interface Ethernet3/2

                    interface Ethernet3/3

                    interface Ethernet3/4

                    interface Ethernet3/5

                    interface Ethernet3/6

                    interface mgmt0
                      ip address 192.168.3.25/24
                    line console
                    line vty
                    boot kickstart bootflash:/n5000-uk9-kickstart.5.2.1.N1.9a.bin
                    boot system bootflash:/n5000-uk9.5.2.1.N1.9a.bin

                    This the the updated config.

                    Thanks

                    ![pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg)
                    ![pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg_thumb](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg_thumb)

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      That is still not tagging LAN with VLAN ID 2.

                      Create VLAN 2 on interface igb1

                      Change the Network port for LAN to VLAN 2 on igb1

                      Patch igb1 to a trunk port with VLAN 2 tagged on it.

                      Be sure the firewall rules on LAN pass the desired traffic that will be inbound to it.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • R
                        redbaron28
                        last edited by

                        @Derelict:

                        That is still not tagging LAN with VLAN ID 2.

                        Create VLAN 2 on interface igb1

                        Change the Network port for LAN to VLAN 2 on igb1

                        Patch igb1 to a trunk port with VLAN 2 tagged on it.

                        Be sure the firewall rules on LAN pass the desired traffic that will be inbound to it.

                        I re made the vlan to vlan10 on the switch and in pfsense.

                        I dont think i'm understanding. The opt1 port is on 192.168.2.1 and thats the network i need to give ip's to the switch to my hosts.

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          Please describe EXACTLY what interface you are talking about and please post the screen shots of Interfaces > Assignments and the switch port you are connecting to pfSense.

                          Setting the PVID (native) here says you want the traffic UNTAGGED on that port:

                          interface Ethernet1/40
                            switchport mode trunk
                            switchport trunk native vlan 10
                            switchport trunk allowed vlan 1-10

                          If it is tagged on one interface it has to be tagged on the other.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          1 Reply Last reply Reply Quote 0
                          • R
                            redbaron28
                            last edited by

                            @Derelict:

                            Please describe EXACTLY what interface you are talking about and please post the screen shots of Interfaces > Assignments and the switch port you are connecting to pfSense.

                            Setting the PVID (native) here says you want the traffic UNTAGGED on that port:

                            interface Ethernet1/40
                              switchport mode trunk
                              switchport trunk native vlan 10
                              switchport trunk allowed vlan 1-10

                            If it is tagged on one interface it has to be tagged on the other.

                            I re configured ethernet 1/40 and removed trunk native line.

                            I will attach pictures of the tabs and a diagram of how things look.

                            Thanks

                            ![pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg)
                            ![pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg_thumb](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ Interface Assignments-1.jpg_thumb)
                            ![pfSense.localdomain - Interfaces_ VLANs-1.jpg](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ VLANs-1.jpg)
                            ![pfSense.localdomain - Interfaces_ VLANs-1.jpg_thumb](/public/imported_attachments/1/pfSense.localdomain - Interfaces_ VLANs-1.jpg_thumb)
                            ![pfSense.localdomain - Status_ Dashboard-1.jpg](/public/imported_attachments/1/pfSense.localdomain - Status_ Dashboard-1.jpg)
                            ![pfSense.localdomain - Status_ Dashboard-1.jpg_thumb](/public/imported_attachments/1/pfSense.localdomain - Status_ Dashboard-1.jpg_thumb)
                            20180211_224254.jpg
                            20180211_224254.jpg_thumb

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              How is the switchport connnected to cxgb0 currently configured?

                              What, specifically, isn't working.

                              You are going to have to be very specific to overcome this language barrier.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

                              1 Reply Last reply Reply Quote 0
                              • R
                                redbaron28
                                last edited by

                                @Derelict:

                                How is the switchport connnected to cxgb0 currently configured?

                                What, specifically, isn't working.

                                You are going to have to be very specific to overcome this language barrier.

                                The csgb0 port is connect to the trunk port on the switch ethernet 1/40.

                                Whats not working is i cant ping the router from the switch and the switch is not getting a ip address from pfsense.

                                Now i just did a test about hardware problem. The 10gb nic i have is a Chelsio T320-CO-SR.
                                If i'm correct if i connect cxgb0 directly into one of my hosts that port should get a ip address from pfsense.
                                I did that and i got no ip address.
                                I tried the same thing and igb2 which is opt2 on my router and connected it into my host and i got a ip address.

                                Could this because of a hardware fault?

                                1 Reply Last reply Reply Quote 0
                                • DerelictD
                                  Derelict LAYER 8 Netgate
                                  last edited by

                                  It could be a hardware fault but there is really no way to know with the information being provided.

                                  Chattanooga, Tennessee, USA
                                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                  1 Reply Last reply Reply Quote 0
                                  • R
                                    redbaron28
                                    last edited by

                                    @Derelict:

                                    It could be a hardware fault but there is really no way to know with the information being provided.

                                    What could i post to help this out?

                                    I'm i correct on how dchp should work when directly connecting a end device?

                                    1 Reply Last reply Reply Quote 0
                                    • DerelictD
                                      Derelict LAYER 8 Netgate
                                      last edited by

                                      I will ask one question at a time so we don't get lost…

                                      What pfSense interface are you talking about? LAN, OPT1, or OPT2?

                                      Chattanooga, Tennessee, USA
                                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                      1 Reply Last reply Reply Quote 0
                                      • R
                                        redbaron28
                                        last edited by

                                        Opt1 is the interface I'm having problems with.@Derelict:

                                        I will ask one question at a time so we don't get lost…

                                        What pfSense interface are you talking about? LAN, OPT1, or OPT2?

                                        1 Reply Last reply Reply Quote 0
                                        • DerelictD
                                          Derelict LAYER 8 Netgate
                                          last edited by

                                          Please post a current screenshot of Interfaces > Assignments

                                          Chattanooga, Tennessee, USA
                                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                          1 Reply Last reply Reply Quote 0
                                          • R
                                            redbaron28
                                            last edited by

                                            @Derelict:

                                            Please post a current screenshot of Interfaces > Assignments

                                            20180212_104550.jpg
                                            20180212_104550.jpg_thumb

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.