I have a fairly simple configuration - two Nexus 3048 ( A and B ), both enterprise licensed. One 10G port on switch A is the start of a fibre ring around a number of HP switches, the ring is closed on the same port on switch B. One 10G port is to route to a different building - this one isn't my problem ( yet ) (the remaining 10G pair are my peer links).   I have the vPC peer links and keep alive configured and working fine. I've configured a number of ways using either VRRP or HSRP. In both cases I can ping the VLAN IP address's and the 'virtual' IP from within the switches themselves. I cannot ping or reach the IP's from outside the switch regardless of the port mode (trunk or access), all vlans allowed or specific.   Ultimately I want eth1/1 on each switch to form an LACP pair with a HyperV host array but testing this is a pain in the butt without the host since the Cisco's refuse to bring the ports up unless LACP is seen - which most laptops can't do. I did have this 'sort of' functional but then started to diagnose a DHCP issue - discover received, offer made but that's where the exchange ended. The DHCP discover broadcasts came in, the offer was made but the request and ack were never triggered but the offer was present at the device.   I am not so familiar with these newer techniques on the Nexus boxes - not touched a switch in years. Can somebody have a scan of the config below, also can somebody offer a source of knowledge that is up to date that goes into how to pull all this together because much of what I've found seems to be out of date. The Cisco docs are OK if you're digging into individual topics but pulling everything together isn't a document that I have found yet. Everything I've read says this should work - but it doesn't - the ring of switches aren't cisco (they're Aruba 2930's with an SFP+ module) there is broadcast traffic appearing, the Aruba's also know the 3K's are there (they show the switch name as the neighbour). I'm trying to expand the knowledge whilst the opportunity presents.   My server dhcp / dns server is currently on eth1/1 in the config below (this will be one side of the hyperV).   I do have peer-gateway and also layer3 peer-router set on the vpc domain. The configs below leave out the peer link stuff and are HSRP but I've tried VRRP too.   I have port states showing no operational member which isn't true, cables are connected appropriately. eth1/50 shows connected to vlan 9 but the associated port channel (po9) shows noOperMem. eth1/1 shows connected 'trunk' but po10 shows noOperMem .... I can get them 'connected' if I don't use active mode and use the default of 'on' but it makes no difference.   NEXUS-3048-A config vl 9 name device-net int vl 9 no shut description **HSRP** ip address 10.9.1.252/24 hsrp 9 preempt delay minimum 300 priority 130 ip 10.9.1.254 int eth1/50 description **Aruba Link** channel-group 9 mode active no shut int port-channel 9 description **Aruba Circuit** switchport mode trunk no shut int eth1/1 channel-group 10 mode active int port-channel 10 switchport mode trunk # I have tried this as 'Access' / 'Trunk', specific VLAN, all VLAN no shut router eigrp 1 log-adjacency-changes int eth1/52 description **Routed Link A** channel-group 1003 mode active no shut vl 1003 int port-channel 1003 no switchport ip router eigrp 1   NEXUS-3048-B config vl 9 name device-net int vl 9 no shut description **HSRP** ip address 10.9.1.253/24 hsrp 9 preempt delay minimum 300 priority 110 ip 10.9.1.254 int eth1/50 description **Aruba Link** channel-group 9 mode active no shut int port-channel 9 description **Aruba Circuit** switchport mode trunk no shut int eth1/1 channel-group 10 mode active int port-channel 10 switchport mode trunk no shut router eigrp 1 log-adjacency-changes int eth1/52 description **Routed Link B** channel-group 1003 mode active no shut vl 1003 int port-channel 1003 no switchport ip router eigrp 1   ... View more

How do I configure an RV320 to link two sites via a BT VPN channel (always up) - I thought these RV320's were supposed to be easy - I find IOS easier !!. Site 1 is 192.168.8.0/24, with a gateway IP (in BT box) of 192.168.8.254 Site 2 is 192.168.10.0/24, with a gateway IP (in BT box) of 192.168.10.254 I've tried enabled RIPv2, tried transparent bridging, and static IP on WAN1 using the BT IP address as the gateway, tried both gateway and router modes, both site subnets are in the subnet table, I don't need or want to use a VPN - since the traffic is passing through a VPN already between the BT boxes. If somebody on Site 1 needs to inspect Site 2 they enter an appropriate IP and ... nothing .... The RV320 sounded like the ideal box but it refuses to 'route' anything in either router or gateway mode. I can't use DHCP on either site due to existing DHCP servers. Anyone have any ideas ? ... View more

Architecture : 3 x 3560 switches, ipservicesk9 image, linked by fibre trunks running EIGRP ... Normal DHCP works - 4 VLANS, 1 uses fixed IP - the Server VLAN, 4 use DHCP. Normal DHCP from VLans 3 to 5 works, I've configured in two ways, in both cases I can get DHCP to work correctly. DHCP in IOS with DNS on MS Server (2008 R2) DHCP and DNS on MS Server (2008 R2) DNS server is 10.10.2.253, PXE Server is 10.10.2.251, these are my helper-address's .... So all VLAN's can get an IP address from a server in the same VLAN as the PXE boot server - BUT - try PXE booting anything and it fails - the switches will not pass / forward the PXE boot 'DHCP discover' packets no matter what. I know the problems in the routing side of the switch, a packet trace proves it, I've  done a packet trace in a flat network (the server VLAN) in which PXE boot works fine (so I know for sure my PXE server is OK), trying   from another VLAN on the SAME switch (done as a test to eliminate the trunks) and all the initial PXE device 'DHCP discover' fails  - the 'DHCP Discover' packets initiated under PXE boot are not routed or forwarded, they can be seen on the non server VLAN but they never appear in the server VLAN, hence not received and so the PXE boot  process never starts. I know I've asked this before but it went nowhere, why the hell would normal DHCP work and PXE boot not ????????? It's getting frustrating - seriously so, I'm getting to the point where something is going to get launched ... ... View more

I have a routed DHCP from 4 VLAN's and it works fine except in certain cases - those cases are where a remote PLC tries to call back as a PXEClient. No DHCP discover packets are forwarded by the 'routing' process if the packet contains option 60 = "PXEClient : Arch ......" - leastways that's how it looks. The routed trunks both have "ip dhcp relay information option enable"  set, yes the VLAN's do have 'ip helper-address =' settings one for both  the primary DHCP box and another for the PXE server. I've played with portfast and vaious other options, nothing has helped. If I connect the PXE Server (OK so its a laptop) into the same VLAN as the PLC the PXE boot process works fine so I know that this is related to the routing / relay agent. I have verified on the server switch and VLAN that the issued 'PXE' discover message is never received, I have verified of course that it is sent. In any case normal DHCP and DNS operations function correctly each VLAN device gets an appropriate IP address from the appropriate scope and a suitable DNS entry - but anything that tries with option 60 set to "PXEClient : *******" fails - or is it option 252 - Private/Proxy autodiscovery ? Switches are 3560's using EIGRP routing via fibre trunks. This has to be something simple that I've missed, I've read an encyclopedia worth of posts on here re PXE issues nothing has so far solved. Is there any way to log what the routed interface is doing with DHCP /  Bootp traffic? (DHCP and DNS are provided by Microsoft Server 2008 R2) ... View more