Hi,
I need to use this switch for OEM project where I have minimum of 4 servers.
In each implementation I would like the switch to allocate the same IP address per port , for example , SRV1 that connected in port x will always get 10.10.10.1
SRV2 connected in port y will always get 10.10.10.2
Can this be done by this switch?
If yes, how should I do that?
Tnx a lot!
Tzach
We bought a new PowerConnect 2824 with a corresponding SFP module to replace an older 2724 and SFP module.
After configuring the switch and installing it, we were unable to get a connection on our fiber uplink.
The SFP light lights up and blinks occasionally, and the switch properly detects that SFP module is inserted and the fiber is plugged in. We can see the SFP insertion being detected and the switch changing to fiber mode by watching the console output, and the web administration port status page lists the port as "ComboF" when the SFP module is inserted and the fiber is connected.
However, the switch always reports that the port status is down. (The port is not administratively disabled.)
The old switch works fine with the old SFP module. The new switch does not work with either the old or the new SFP module. We've tried both SFP combo ports. We have also verified that the fiber itself is fine. We cannot get the new switch to show the combo port status as up when using the SFP module. We've tried completely resetting the new switch by deleting the config file via the boot menu over the serial connection and running the initial setup wizard again, but the port will still not come up.
Any ideas?
Hi Experts,
I am new in powerconnect world and learning, currently having a scenario and need experts help
A company is having 5 departments and one server/network room, who is providing the internet and email, etc. to all the department, the company is having 192.168.1.x IP scheme, all departments are communicating to each other and ping replying is receiving between the all departments.
The requirement is department A should access and ping to B, C, D & E department and should have access rest of the network e.g. internet, email, etc., but the department B, C, D and E shouldn’t be pinged or access to any department but they should access the internet, email etc.
Please share the steps and commands for configuration in PowerConnect 5524 switch
Thanks....
Hello Gurus,
I have two VLANS. 1 and 20. I just need simple config to make this work. How do i have routes between them and make then vbisible to each other.? appreciate any inputs and recommendations.
f10#show vlan
NUM Status Description Q Ports
1 Active U Po1(Gi 0/3,Gi 1/2-3)
U Po2(Gi 0/4,Gi 1/4,Gi 2/4)
U Po3(Gi 0/5,Gi 1/5)
U Gi 0/1,6-41,43-45,47-48
U Gi 1/1,6-48
U Gi 2/1-3,5-48
U Gi 3/2-48
20 Active SSLVPN U Gi 0/42,46
f10#show ip route
Gateway of last resort is 10.1.10.1 to network 0.0.0.0
Destination Gateway Dist/Metric Last Change
----------- ------- ----------- -----------
*S 0.0.0.0/0 via 10.1.10.1, Vl 1 1/0 21w1d
C 10.1.10.0/24 Direct, Vl 1 0/0 21w1d
C 10.3.10.0/24 Direct, Vl 20 0/0 1d2h
interface Vlan 1
ip address 10.1.10.4/24
untagged GigabitEthernet 0/1,6-41,43-45,47-48
untagged GigabitEthernet 1/1,6-48
untagged GigabitEthernet 2/1-3,5-48
untagged GigabitEthernet 3/2-48
untagged Port-channel 1-3
no shutdown
interface Vlan 20
description SSLVPN
ip address 10.3.10.4/24
untagged GigabitEthernet 0/42,46
no shutdown
I'm having a lot of troubles implementing VLANs on these switches.
From what I've gathered:
T: VLAN member, packets are tagged. Trunk.
U: VLAN Member, however packets are untagged.
F: Denied VLAN membership
Blank: Not a VLAN member
I have 2 switches an a router in my scenario.
Switch2: has an access point broadcasting 3 VLANs (IDs 2-4), attached to interface1. Interface16 is the uplink to switch1.
Switch1: has Switch2 attached to interface1
Switch1 had interface1 blank, previously, and the VLANs were working. I switched it to T and it stopped working. Clients would try to get a DHCP address and it would stop there. Assigning addresses statically provided no network access beyond connecting to the access point. Switching this interface back to blank does not resolve the issue, the issue persists.
Am I missing something here? Wouldn't I want all the paths that these VLANs should follow to receive the VLAN IDs?
To summarize:
1. VLAN IDs 2,3, and 4 are broadcasted on wifi. A user joins one of these VLANs based on the SSID they connect to
2. 1 Access Point is connected to interface1 on switch2, which uplinks to switch1 via interface16
3. interface1 on switch1 receives the traffic from interface16 on switch2
4. switch2 sends the traffic to my sonicwall via interface22
What settings do I need on each switch to accomplish this?
This is switch 2: http://puu.sh/eid5Z/345baaf3d4.png, the settings are the same for VLANs 2 through 4.
Same story for switch1: http://puu.sh/eidlX/c24ea6e948.png
the 6224P constantly to restart like this:
Boot Menu 3.3.12.1
Select an option. If no selection in 10 seconds then
operational code will start.
1 - Start operational code.
2 - Start Boot Menu.
Select (1, 2):
Operational Code Date: Fri Nov 7 10:36:26 2014
Uncompressing.....
There was an error during decompression... resetting the switch
select 2 i can get in BOOT MENU，and functions in the boot menu are OK，for example i can Load new operational code using XMODEM,Reset the system,Restore to factory defaults and so on... and i have flashed the latest rom by XMODEM,but the problem still exists.
if shutdown the 6224P for a day or more ,it will get OK for some minutes.
Here are some messages before it constantly to restart :
<187> JUN 13 18:26:34 192.168.70.132-1 LLDP[213756864]: lldp_util.c(2471) 309 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
<187> JUN 13 18:27:04 192.168.70.132-1 LLDP[213756864]: lldp_util.c(2471) 310 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
<187> JUN 13 18:27:34 192.168.70.132-1 LLDP[213756864]: lldp_util.c(2471) 311 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
<187> JUN 13 18:28:04 192.168.70.132-1 LLDP[213756864]: lldp_util.c(2471) 312 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
<187> JUN 13 18:30:30 192.168.70.132-1 LLDP[213756896]: lldp_util.c(2471) 326 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
<187> JUN 13 18:31:00 192.168.70.132-1 LLDP[213756896]: lldp_util.c(2471) 327 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
Exception: taskID = e6109b0, vectNum = 700, pEsf = 0xe611b88
saving crash record in crashdump.1
NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
poe_monito Error 1 decompressing devshell symbols while refilling
hpcPwrdsineP e6109b0 255 READY 0x82ffa4 e6106f0 0 0
stack: base 0xe6109b0 end 0xe6089b0 size 32768 high 1264 margin 31504
options: 0x1009001
vector: 0x700
Stack Trace:
<187> JUN 13 18:31:30 192.168.70.132-1 LLDP[213756896]: lldp_util.c(2471) 330 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
0x82ffa4: poe_device_read (0x82fcec) + 0x2b8
0x830374: poe_device_read (0x82fcec) + 0x688
0x7651740 (dot1s_timer_task): task 0x7651740 has had a failure and has been stop
ped.
0x7651740 (dot1s_timer_task): fatal kernel task-level exception!
<187> JUN 13 18:32:00 192.168.70.132-1 LLDP[213756896]: lldp_util.c(2471) 331 %%
lldpTimerProcess(): LLDPDU Transmit Failed! Unable to reserve network buffer fo
r transmission
0x831e80: hpcPwrdsinePoeMsgChannelPrioritySet (0x8318d8) + 0x5a8
0x836eac: hpcPwrdsinePoeChannelToPhysicalPortMap (0x833d3c) + 0x3170
0xd8bbe10 (isdpTask): task 0xd8bbe10 has had a failure and has been stopped.
0xd8bbe10 (isdpTask): fatal kernel task-level exception!
0x1dbcd20: vxTaskEntry (0x1dbccc4) + 0x5c
r0 = 0 sp = e6106f0 r02 = 0 r03 = e610820
r04 = 45 r05 = 0 r06 = 64 r07 = 3e8
r08 = 0 r09 = e610820 r10 = e610821 r11 = 35
r12 = 989680 r13 = 0 r14 = 0 r15 = 0
r16 = 0 r17 = 0 r18 = 0 r19 = 0
r20 = 0 r21 = 0 r22 = 0 r23 = 0
r24 = 0 r25 = 0 r26 = 0 r27 = e610904
r28 = e610903 r29 = e6108c0 r30 = 836c9c r31 = e6106f0
msr = 2029200 lr = 830400 ctr = 1e6a91c pc = 82ffa4
cr = 40000048 xer = 0
Dear All,
I have a query. Sorry in advance if this is not the right place to ask. I couldn't find any other relevant forum.
I am working with M1000E Chassis and using MXL switches. I want to know how an MXL pair can provide High Availabilty. At the fabric level they are connected to two separate ports (p2p1 and p2p2) of each blade. If one MXL goes down, where is this decision made to use the other MXL?
Thanking you in anticipation.
Hi,
Im currently testing MLAG with two N4032F to a server and failover and load balancing works. One problem I face is that the MLAG interface doesnt go up until both switches are up and running. Can I somehow force the MLAG interface so go up with only one switch running? Lets say after a power failure where only on switch boots up.
//Cest
Hello
I installed a Powerconnect 6248 (Ver.3.3.12.1 Nov14) to change my old 3Com Switch.
When I plug the fiber on the SFP module, the light on port don't turn on.
The SFP Port is configured on Full Duplex and Auto negotiation is disabled.
Hi there,
I'm a little new to the MLAG of the N3000, but not the VLT of the Force10, but somehow, something is not behaving the same way, or I am missing something.
I have 2 switchs, connected together by a Port-channel in trunk mode and MLAG
Eventhough the MLAG is up and running, and the Port-Channel linking both peers is in trunk mode for all VLANs, I cannot connect to a device on the same vlan that is connected to the other switch. But If i connect a PC to a partner switch, I can connect to any device connected to either one or the other peer switch.
Any ideas why the peer link is behaving that way?
Thanks for your help!
sHello,
We have replaced on our old powerconnect 62xx with a new stack of N3000 switches. With previous hardware there was no isolated management interface. As a result we were able to administrate the switch from our LAN subnet .
If I set OOB interface in our LAN subnet then I cannot allocate IP to VLAN . ... .
How to be able to administrate our N3000 switch via web gui from our LAN subnet.
I have tried to setup ip address for vlan1 in the hope I would be able to web gui for management ...but no ...
console>enable
console#configure
console(config)#interface vlan 1
console(config-if)#ip address 192.168.0.250 255.255.255.0
Can you please help ?
Thanks for reading my post.
Gmiga.
New to Dell switching. In Cisco port configuration I could do a "no" command to remove settings on a port. What is Dells command to remove settings from a port?
hi!
we have a problem with a MS cluster, where hosts are connected to a PC5548 switches. there are two stacked PC5548 with VLANs for LiveMigration, Cluster communication and LAN. recently we had several major crashes.
on the switch the logs shows:
6 2147478624 13~Jan~2015 20:48:19 Notice %STCK SYSL-N-UNITMSG: UNIT ID 2,Msg:%SYSLOG-N-LOGGING: Logging started.
7 2147478625 13~Jan~2015 20:48:12 Warning %STP-W-PORTSTATUS: gi2/0/37: STP status Forwarding
8 2147478626 13~Jan~2015 20:48:11 Warning %STP-W-PORTSTATUS: gi2/0/48: STP status Forwarding
9 2147478627 13~Jan~2015 20:48:11 Warning %STP-W-PORTSTATUS: gi2/0/47: STP status Forwarding
10 2147478628 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/46: STP status Forwarding
11 2147478629 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/45: STP status Forwarding
12 2147478630 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/44: STP status Forwarding
13 2147478631 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/43: STP status Forwarding
14 2147478632 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/41: STP status Forwarding
15 2147478633 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/36: STP status Forwarding
16 2147478634 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/35: STP status Forwarding
17 2147478635 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/34: STP status Forwarding
18 2147478636 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/33: STP status Forwarding
19 2147478637 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/32: STP status Forwarding
20 2147478638 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/31: STP status Forwarding
21 2147478639 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/29: STP status Forwarding
22 2147478640 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/22: STP status Forwarding
23 2147478641 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/24: STP status Forwarding
24 2147478642 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/23: STP status Forwarding
25 2147478643 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/40: STP status Forwarding
26 2147478644 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/39: STP status Forwarding
27 2147478645 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/38: STP status Forwarding
28 2147478646 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/21: STP status Forwarding
29 2147478647 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/20: STP status Forwarding
30 2147478648 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/19: STP status Forwarding
31 2147478649 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/18: STP status Forwarding
32 2147478650 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/13: STP status Forwarding
33 2147478651 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/12: STP status Forwarding
34 2147478652 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/11: STP status Forwarding
35 2147478653 13~Jan~2015 20:48:10 Warning %STP-W-PORTSTATUS: gi2/0/10: STP status Forwarding
36 2147478654 13~Jan~2015 20:48:09 Warning %STP-W-PORTSTATUS: gi2/0/9: STP status Forwarding
37 2147478655 13~Jan~2015 20:48:09 Warning %STP-W-PORTSTATUS: gi2/0/8: STP status Forwarding
38 2147478656 13~Jan~2015 20:48:09 Warning %STP-W-PORTSTATUS: gi2/0/4: STP status Forwarding
39 2147478657 13~Jan~2015 20:47:42 Info %LINK-I-Up: gi2/0/37
40 2147478658 13~Jan~2015 20:47:41 Info %LINK-I-Up: gi2/0/48
41 2147478659 13~Jan~2015 20:47:41 Info %LINK-I-Up: gi2/0/47
42 2147478660 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/46
43 2147478661 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/45
44 2147478662 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/44
45 2147478663 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/43
46 2147478664 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/41
47 2147478665 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/36
48 2147478666 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/35
49 2147478667 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/34
50 2147478668 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/33
51 2147478669 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/32
52 2147478670 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/31
53 2147478671 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/29
54 2147478672 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/22
55 2147478673 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/24
56 2147478674 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/40
57 2147478675 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/39
58 2147478676 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/23
59 2147478677 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/38
60 2147478678 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/21
61 2147478679 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/20
62 2147478680 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/19
63 2147478681 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/18
64 2147478682 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/13
65 2147478683 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/12
66 2147478684 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/11
67 2147478685 13~Jan~2015 20:47:40 Info %LINK-I-Up: gi2/0/10
68 2147478686 13~Jan~2015 20:47:39 Warning %LINK-W-Down: te2/0/2
69 2147478687 13~Jan~2015 20:47:39 Info %LINK-I-Up: gi2/0/9
70 2147478688 13~Jan~2015 20:47:39 Info %LINK-I-Up: gi2/0/8
71 2147478689 13~Jan~2015 20:47:39 Info %LINK-I-Up: gi2/0/4
72 2147478690 13~Jan~2015 20:47:38 Warning %LINK-W-Down: te2/0/1
73 2147478691 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/48
74 2147478692 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/47
75 2147478693 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/46
76 2147478694 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/45
77 2147478695 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/44
78 2147478696 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/43
79 2147478697 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/42
80 2147478698 13~Jan~2015 20:47:37 Warning %LINK-W-Down: gi2/0/41
81 2147478699 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/40
82 2147478700 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/39
83 2147478701 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/38
84 2147478702 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/37
85 2147478703 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/36
86 2147478704 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/35
87 2147478705 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/34
88 2147478706 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/33
89 2147478707 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/32
90 2147478708 13~Jan~2015 20:47:36 Warning %LINK-W-Down: gi2/0/31
91 2147478709 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/30
92 2147478710 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/29
93 2147478711 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/28
94 2147478712 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/27
95 2147478713 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/26
96 2147478714 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/25
97 2147478715 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/24
98 2147478716 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/23
99 2147478717 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/22
100 2147478718 13~Jan~2015 20:47:35 Warning %LINK-W-Down: gi2/0/21
101 2147478719 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/20
102 2147478720 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/19
103 2147478721 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/18
104 2147478722 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/17
105 2147478723 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/16
106 2147478724 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/15
107 2147478725 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/14
108 2147478726 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/13
109 2147478727 13~Jan~2015 20:47:34 Warning %LINK-W-Down: gi2/0/12
110 2147478728 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/11
111 2147478729 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/10
112 2147478730 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/9
113 2147478731 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/8
114 2147478732 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/7
115 2147478733 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/6
116 2147478734 13~Jan~2015 20:47:33 Warning %LINK-W-Down: gi2/0/5
117 2147478735 13~Jan~2015 20:47:32 Warning %LINK-W-Down: gi2/0/4
118 2147478736 13~Jan~2015 20:47:32 Warning %LINK-W-Down: gi2/0/3
119 2147478737 13~Jan~2015 20:47:32 Info %DSYNCH-I-SYNCH_SUCCEEDED: Synchronization with unit 2 is finished successfully
120 2147478738 13~Jan~2015 20:47:32 Warning %LINK-W-Down: gi2/0/2
121 2147478739 13~Jan~2015 20:47:32 Warning %LINK-W-Down: gi2/0/1
122 2147478740 13~Jan~2015 20:47:29 Info %Entity-I-SEND-ENT-CONF-CHANGE-TRAP: entity configuration change trap.
123 2147478741 13~Jan~2015 20:47:29 Info %Stack-I-STACK-LINK-CHNG: Stack cable connected : link 1 on unit-2
124 2147478742 13~Jan~2015 20:47:29 Info %Stack-I-STACK-LINK-CHNG: Stack cable connected : link 0 on unit-1
125 2147478743 13~Jan~2015 20:47:25 Info %STCK SYSL-I-UNITMSG: UNIT ID 2,Msg:%MLDP-I-CONNECT: Connection to Unit 1 is established.
126 2147478744 13~Jan~2015 20:47:25 Info %STCK SYSL-I-UNITMSG: UNIT ID 2,Msg:%MLDP-I-SLAVE: Switching to the Slave Mode.
127 2147478745 13~Jan~2015 20:47:25 Info %STCK SYSL-I-UNITMSG: UNIT ID 2,Msg:%Stack-I-LINK UP: link 1 on unit-2
128 2147478746 13~Jan~2015 20:47:25 Info %STCK SYSL-I-UNITMSG: UNIT ID 2,Msg:%INIT-I-InitCompleted: Initialization task is completed
129 2147478747 13~Jan~2015 20:47:25 Info %MLDP-I-CONNECT: Connection to Unit 2 is established.
130 2147478748 13~Jan~2015 20:47:08 Info %Stack-I-LINK UP: link 0 on unit-1
131 2147478749 13~Jan~2015 20:47:03 Warning %Stack-W-LINK DOWN: link 0 on unit-1
132 2147478750 13~Jan~2015 20:47:02 Info %Stack-I-LINK UP: link 0 on unit-1
133 2147478751 13~Jan~2015 20:46:34 Info %Entity-I-SEND-ENT-CONF-CHANGE-TRAP: entity configuration change trap.
134 2147478752 13~Jan~2015 20:46:34 Info %Stack-I-STACK-LINK-CHNG: Stack cable removed : link 1 on unit-2
135 2147478753 13~Jan~2015 20:46:34 Info %Stack-I-STACK-LINK-CHNG: Stack cable removed : link 0 on unit-1
136 2147478754 13~Jan~2015 20:46:34 Info %Stack-I-STCK-BCKUP-REM: Backup master unit 2 was removed from the stack.
137 2147478755 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: te2/0/2
138 2147478756 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: te2/0/1
139 2147478757 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/48
140 2147478758 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/47
141 2147478759 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/46
142 2147478760 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/45
143 2147478761 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/44
144 2147478762 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/43
145 2147478763 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/42
146 2147478764 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/41
147 2147478765 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/40
148 2147478766 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/39
149 2147478767 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/38
150 2147478768 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/37
151 2147478769 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/36
152 2147478770 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/35
153 2147478771 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/34
154 2147478772 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/33
155 2147478773 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/32
156 2147478774 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/31
157 2147478775 13~Jan~2015 20:46:34 Warning %LINK-W-Not Present: gi2/0/30
there is no rule for the 3o-48 ports - some of them are is default VLAN, some are in tagged VLAN for cluster communication...
thx!
So I need to connect our PC6248 to the ISP's Router. We are going to use Link networks between the devices to access MPLS networks.
The ISP router will have our internal network (172.16.112.0 /20) in it's routing table and the GW will be the link network address (192.168.0.2)
I want to subnet our 172.16.112.0 /20 into several smaller networks (/24). My question is can I go ahead and add my vlans with subnetted addresses right away on the PC6248 or do I first need a vlan with the 172.16.112.0 /20 address and the creating my subnetted adresses?
Network
172.16.112.0 /20 -----ISP-Router--192.168.0.1 /24--------------------192.168.0.2 /24--PC6248-----172.16.112.0 /20 or 172.16.112.0 /24
A client purchased 3 used 5524 switches and added them to an existing controlled 5524 with a static IP assigned. Evidently the 3 were not reset to factory defaults and the stack control was taken over by used controlling 5524 of the three. The original 5524 was absorbed into the bogus stack as #4.
I have no access to any stack member either through the console port or via http as the IP addressing is not in our range. I have searched come LAN IP ranges without joy. I have searched for an external reset to factory defaults for the 5524 without any joy. I am aware that console access is only available on devices 1 & 2 in the stack. The unfortunate fact is that even booted without the stack members connected, each device remembers its configuration so there is no access.
Any help would be greatly appreciated.
My network has always been Cisco. I just bought my first Dell switch and need some help. I currently use VTP on my cisco switches. I know that Dell does not talk VTP. So I manually add my VLANS to my Dell switch, and trunk the port both on the Dell and the Cisco, shouldnt everything work? Any new VLANS crated via VTP on the cisco network will still have to be manually added to the Dell, but as long as the Dell switch has the VLAN added everything should talk?
العملاق مركز صيانة ايديال ايليت الاول فى مصر : خبراء وتقنييون ومهندسون وماهرون
يرحب بعملاء ايديال ايليت القاهرة الكبرى
35699066//35710008//01112124913 //01220261030
01095999314
صيانة ايديال ايليت صيانة ايديال ايليت صيانة ايديال ايليت صيانة ايديال ايليت صيانة ايديال ايليت صيانة ايديال ايليت
العملاق مركز صيانة ماجيك شيف الاول فى مصر : خبراء وتقنييون ومهندسون وماهرون
يرحب بعملاء ماجيك شيف القاهرة الكبرى
35699066//35710008//01112124913 //01220261030
01095999314
صيانة ماجيك شيف صيانة ماجيك شيف صيانة ماجيك شيف صيانة ماجيك شيف صيانة ماجيك شي
I have a 7048P connected to a Meraki MR34 Wireless Access Point on gi3/0/33. The MR34 needs 19W to run all features but is not receiving it from the 7048P. On the 7048P, that port is configured as follows:
7048P#show running-config interface gigabitethernet 3/0/33
description "Meraki MR34 AP"
switchport mode general
switchport general allowed vlan add 5,10,40,50,60,250 tagged
lldp med confignotification
lldp med transmit-tlv ex-pse
power inline high-power
power inline limit user-defined 31200
power inline priority critical
7048P#show lldp med interface gigabitethernet 3/0/33
TLV Codes: 0- Capabilities, 1- Network Policy
2- Extended PSE, 3- Extended Pd
Interface Link configMED operMED ConfigNotify TLVsTx
--------- ------ --------- -------- ------------ -----------
Gi3/0/33 Up Enabled Disabled Enabled 0,1,2
7048P#show lldp med local-device detail gigabitethernet 3/0/33
LLDP MED Local Device Detail
Interface: Gi3/0/33
Network Policies
Extended PoE
Device Type: PSE
Extended PoE PSE
Available: 3120.00 Watts
Source: Primary
Priority: Critical
7048P#show lldp med remote-device detail gigabitethernet 3/0/33
LLDP MED Remote Device Detail
Local Interface: Gi3/0/33
Remote Identifier: 40735
Capabilities
MED Capabilities Supported:
MED Capabilities Enabled:
Network Policies
I have used Wireshark to look at the LLDP conversation.
MR34 says:
IEEE 802.3 - Power via MDI IEEE 802.3 subtype: Power via MDI (0x02)
MDI Power support: 0x00 Port class: PD PSE MDI Power: Not supported PSE MDI Power: Disabled PSE pairs control Ability: No PSE Power pair: 1 Power class: 5 Power Type: Type 2 PD Device (1) Power source: 1 PSE Power priority: unknown (0) PD Requested Power value: 19.0. watt PSE Allocated Power value: 0.0. watt
7048P says:
IEEE 802.3 - Power via MDI
IEEE 802.3 subtype: Power Via MDI (0x02)
MDI Power support: 0x07
Port class: PSE
PSE MDI Power: supported
PSE MDI Power: Enabled
PSE pairs control Ability: No
PSE Power pair: 1
Power class: 5
Power Type: Type 2 PSE Device (0)
Power source: 1 primary Power source
Power priority: critical (1)
PD Requested Power value: 13.0. watt
PSE Allocated Power value: 13.0. watt
Meraki support say that the 7048P side is misconfigured.
Can anyone point me in the right direction of what is wrong with my 7048P config?
Hi,
Can you stack non-PoE & PoE models ?
For Example:
6224 (non-PoE) & 6224P (PoE)
or
6248 (non-PoE) & 6248P (PoE)
Thanks,
Paul