Keeping your database environment tuned, optimized and high-performance is key to achieving business goals. If your database goes down, so does your business. Percona experts have a long history of helping enterprises ensure their databases are running smoothly.
Course Of The Month
10 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
How to change listening Vlan for management on Dell 2848
Posted on 2012-12-20
Hi, we do not use Vlan1 for internal network anymore. On the Dell 5548 we can change in the IPAdressing Interface setting the VLAN ID for listening for the internal web openmanage page. I can't find it on the older switch 2848.
Any suggestion? In CLI ?
Any suggestion? In CLI ?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4 Comments
Active today
If you can't find it, you can leave an old laptop plugged into a port with pvid1 and use that. Sorry I don't have a better solution. Did you try newer firmware?
Active 5 days ago
Hello,
If you can connect through CLI, try this:
switch(config)> interface vlan XX
switch(config-if)> ip address 192.168.XX.10 255.255.255.0 default-gateway 192.168.XX.10
In case interface vlan command works only for VLAN 1, there is one trick you can use by bridging VLANs:
- configure one port in VLAN1 (for example port 1)
- configure one port in VLAN you are using for management (for example port 2)
- put management IP on VLAN1 as described in example above
- use crossover cable to connect configured VLAN1 port with management VLAN port (connect ports 1 and 2 with crossover cable)
As both ports are access ports, there is no tagging, so there should be no problem.
Regards!
If you can connect through CLI, try this:
switch(config)> interface vlan XX
switch(config-if)> ip address 192.168.XX.10 255.255.255.0 default-gateway 192.168.XX.10
In case interface vlan command works only for VLAN 1, there is one trick you can use by bridging VLANs:
- configure one port in VLAN1 (for example port 1)
- configure one port in VLAN you are using for management (for example port 2)
- put management IP on VLAN1 as described in example above
- use crossover cable to connect configured VLAN1 port with management VLAN port (connect ports 1 and 2 with crossover cable)
As both ports are access ports, there is no tagging, so there should be no problem.
Regards!
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
Arrow Electronics was searching for a KVM (Keyboard/Video/Mouse) switch that could display on one single monitor the current status of all units being tested on the rack.
- Networking Hardware-Other
- Switches / Hubs
- Components
- ATEN Technology
- Hardware
- *Kernel-based Virtual Machine (KVM)
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month10 days, 15 hours left to enroll
Earn Certification
Cisco CCNA R&S: ICND2 v3
$197.00$177.30
Earn Certification
Cisco CCNP Security: SIMOS
$197.00$177.30
628 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.