- Community Home
- >
- Networking
- >
- Legacy
- >
- Switching and Routing
- >
- Re: Strange VLAN Behavior
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2021 10:49 AM - last edited on 09-08-2021 11:02 AM by support_s
08-24-2021 10:49 AM - last edited on 09-08-2021 11:02 AM by support_s
I have some Aruba switches that I'm trying to configure a VLAN on, and am running into some strange issues.
My MDF switch(5406r) has an ip address of 10.2.7.254
Edge switch 1 has an ip address 10.2.7.242
Edge switch 2 has an ip address 10.2.7.243
Edge switch 1 is connected to the MDF switch's port d1
Edge switch 2 is connected to the MDF switch's port d2
The VLAN ID I'm using for this is 60. Ports d1 and d2 are tagged VLAN 60, as well as the uplink ports on both switches. The edge switches both have an untagged port with a camera connected to it.
I can ping the camera one edge switch 1 with no issues from anywhere on the LAN. However, the camera on edge switch 2 can't be pinged from any device other than the MDF switch, not even the edge switch itself. Both edge switch configs appear to be identical. Any ideas what could be going on here? I've done this a ton of times before and never had this issue.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2021 11:51 AM
08-24-2021 11:51 AM
Re: Strange VLAN Behavior
Hello @strict_bishop ,
Have you tried to change camera port on edge switch 2?
Have you tried to swap the camera from edge switch 2 to 1 or vice versa?
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2021 11:58 AM
08-24-2021 11:58 AM
Re: Strange VLAN Behavior
I have tried changing the port, but I haven't been able to swap the cameras themselves(they're screwed onto walls).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2021 10:29 PM
08-24-2021 10:29 PM
Re: Strange VLAN Behavior
Hello @strict_bishop ,
Is it possible to share below outputs:
show logbuffer -r
show power-over-ethernet
show power-over-ethernet <camera 2 port on edges switch > Status/ Counters
As a part of troubleshooting, can you try to connect host/LAPTOP to that or other port and give the same subnet IP and check the reachability?
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2021 11:03 AM
08-25-2021 11:03 AM
Re: Strange VLAN Behavior
@akg7 wrote:Hello @strict_bishop ,
Is it possible to share below outputs:
show logbuffer -r
show power-over-ethernet
show power-over-ethernet <camera 2 port on edges switch > Status/ Counters
As a part of troubleshooting, can you try to connect host/LAPTOP to that or other port and give the same subnet IP and check the reachability?
Thanks!
@akg7 wrote:Hello @strict_bishop ,
Is it possible to share below outputs:
show logbuffer -r
show power-over-ethernet
show power-over-ethernet <camera 2 port on edges switch > Status/ Counters
As a part of troubleshooting, can you try to connect host/LAPTOP to that or other port and give the same subnet IP and check the reachability?
Thanks!
Keys: W=Warning I=Information
M=Major D=Debug E=Error
---- Reverse event Log listing: Events Since Boot ----
I 08/12/21 15:21:31 04753 system: Event log buffer has wrapped; older logs will
be overwritten.
W 08/12/21 13:33:03 03443 system: The event log buffer is 80% full.
---- Top of Log : Events Listed = 2 ----
Operational Status : On
Usage Threshold (%) : 80Chassis power-over-ethernet:
Total Available Power : 195 W
Total Power Drawn : 22 W +/- 6W
Total Power Reserved : 22 W
Total Remaining Power : 173 W
Operational Status : On
Usage Threshold (%) : 80Chassis power-over-ethernet:
Total Available Power : 195 W
Total Power Drawn : 22 W +/- 6W
Total Power Reserved : 22 W
Total Remaining Power : 173 W
I was able to connect with that same port using my laptop on the same subnet. What's really strange is that the MDF switch is able to ping the camera, but nothing else is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2021 09:45 PM
08-25-2021 09:45 PM
SolutionHello @strict_bishop ,
When you connect your laptop to same port then able to ping everything or not?
If yes then issue is with camera and if not then need to dig more in swtich.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2021 08:30 AM
08-26-2021 08:30 AM
Re: Strange VLAN Behavior
Well I feel like an idiot now. After checking the camera's settings for the second or third time, I found a typo in the default gateway >.<
It's working correctly now with the proper default gateway set.
Thanks for the help!