Quantcast
Channel: PowerConnect Forum - Recent Threads
Viewing all 2954 articles
Browse latest View live
↧

Reset Password on DELL Switch N3024

January 13, 2017, 2:46 am
$
0
0

Hi All,

Actually I forget the username/password on my DELL N3024 Switch.

How to reset the username/password but still have the switch configuration?

Please kindly need your help. 

↧
Search

PowerConnect 7048 no enable password issue

January 13, 2017, 2:18 am
$
0
0

Hi,

I'm facing an issue with PowerConnect 7048.

I'm trying to add it in my rancid, so, i would like to disable the enable password, i tried the following:

conf t
username "rancid" password 1b430c5c9deb13487f016d09e7c66fce privilege 15 encrypted
no enable password


After that, if i try a new session and type "en", i have this error:

SAASPC7048>en

Authentication failed.

SAASPC7048>

I did it on a 1524 and it works perfectly.

So, do somebody can help me to solve this cause it's driving me crazy ...

Many thanks for your help

↧
↧

Advantage of PowerConnect Switches with Dell Servers

January 13, 2017, 7:53 am
$
0
0

Basic question, I need to get a switch to manage a few previous generation Dell PowerEdge servers.  What if any are the advantages of staying with the same vendor and using a Dell PowerEdge switch versus another brand of a managed switches?  Are there network monitoring software advantages to sticking with the same vendor?

Thanks for any thoughts.

↧

DHCP packet issues on N2/3/4000 switches

January 13, 2017, 8:04 am
$
0
0

Information post rather than a question/ problem.

We had suffered for some time with poor DHCP service at remote site when we lose Internet connection to our main site and all traffic fails over to the remote link.

It does appear to be fixed by FW upgrade to (in our case) 6.2.7.2

It was always difficult to keep up with FW releases especially on the smaller site with a single core in constant use.

The release notes do hint at some DHCP issues and in this case only seemed to be apparent when taking the load from both sites.

Just wanted to share as it caught us out at the times when we needed the switch to justify its cost.

↧

PowerConnect 2848 - Creating VLANS for other organization in the same office

January 14, 2017, 12:04 am
$
0
0

Hi,

I need to separate two VLANS so that the two organisation would not have access to each other computer and files, but still able to share the internet access. How should I setup using the Powerconnect console?

Port 1-9 - Our PC clients (VLAN 2)

Port 10 - Other office switch (VLAN 3)

Port 45 - to other switch

Port 46 - to router (internet)

I have been trying to setup using the console but no success.

Please help, thank you.

↧
↧

Setting VLAN via SNMP on Dell Network N1548

January 14, 2017, 12:32 pm
$
0
0

I'm back after six years, with the same issue but now on a new switch... I bought 60 of these switches under the premise that they worked the same as the old PowerConnect 5548 and while they seem to do just that, I'm having an issue setting VLANs over SNMP.


As a refresher, here's my original post:

When I attempt the same method as before, it seems to accept it but nothing happens. See the "1" on the third position of the Hex-STRING. I'm trying to set it to 0; the string gets returned with no errors, yet it's still a "1" when I read it again.

[root@tms n1548]# snmpget -c public -v2c switchca-ib .1.3.6.1.2.1.17.7.1.4.3.1.4.128
SNMPv2-SMI::mib-2.17.7.1.4.3.1.4.128 = Hex-STRING: 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00
[root@tms n1548]# snmpset -c private -v2c switchca-ib .1.3.6.1.2.1.17.7.1.4.3.1.4.128 x "00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00"
SNMPv2-SMI::mib-2.17.7.1.4.3.1.4.128 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00
[root@tms n1548]# snmpget -c public -v2c switchca-ib .1.3.6.1.2.1.17.7.1.4.3.1.4.128
SNMPv2-SMI::mib-2.17.7.1.4.3.1.4.128 = Hex-STRING: 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00

I'm running software version 6.3.1.8.

Any ideas?

↧

8204F port errors

January 15, 2017, 7:10 pm
$
0
0

We are getting FCS and Internal MAC Rx errors on a single port. I have replaced the SFP and fibre cable as well as moving the cable to an alternate port, none of which has stopped the errors which occur randomly every hour or so (currently up to approximately 1200 errors).

I am not seeing any errors on the other end (the connection is a trunk between an 8024F switch and 5548 switch). The issue started around a month ago and has increased in severity to the point where the port is going down for short periods.

Could issues from the 5548 switch cause errors to only show up on the 8024F switch?

↧

PowerConnect 2824 configuration access issues

January 14, 2017, 3:43 pm
$
0
0

I have a Dell PC2824 managed switch.

When first powered up, it runs in unmanaged mode, though the fan and
manage mode lights blink as if it's trying to configure itself.

With a telnet app, connected to a PC via the switch Com port, I see the
following -

-------------------------------------------------------------------------
-----
------ Performing the Power-On Self Test (POST) ------

UART Channel Loopback Test........................PASS
Testing the System SDRAM..........................PASS
Boot1 Checksum Test...............................PASS
Boot2 Checksum Test...............................PASS
Flash Image Validation Test.......................PASS

BOOT Software Version 1.0.0.13 Built  17-Jul-2012  08:47:13
Board Type - PowerConnect 2824
PowerConnect 2824 board based on FireFox 88E6218 ARM946E-S processor
64 MByte SDRAM. I-Cache 8 KB. D-Cache 8 KB. Cache Enabled.

MAC Address   :  d0:67:e5:96:5f:0a.

Autoboot in 2 seconds - press RETURN or Esc. to abort and enter prom.
Preparing to decompress...

FAIL !!! Check image for valid file.

Switching to the second image ...

Preparing to decompress...

FAIL !!! Check image for valid file.

Both images are not valid  ...
Please download a new image.

Downloading code using XMODEM.
-------------------------------------------------------------------------
-----

The CLI screen stays like this for about five minutes, until the download
routine times out, then the switch does a warm boot and repeats the
process.

Unlike other managed switches I have, the POST does not complete. Because
of this, the mode switch will not allow me to change between unmanaged
and managed mode - so it would be impossible to access the Web interface.

Similarly, becuase the POST routine does not complete, I cannot issue CLI
commands (I never get the console> prompt.

There is the prom option within 2 seconds of start-up. This also offers a
download software option.

The prompt text above seems to indicate that the switch FW is bad and
needs reloading.

I have set up a Solarwinds TFTP server on the PC which I am running
Hyperterminal or PuTTY on. Tghis points to a TFTP root folder which does
contain the two latest firmware files -

powerconnect_28xx_boot-10013.rfb
and
powerconnect_28xx-10045.ros

With the TFTP server running, I would expect the PC2824 to collect the
firmware and download/install it - but nothing seems to be happening.

If I try to "push" the FW over TFTP from Hyperterminal, it sees the files
and attempts to upload to the switch, but after 10 attempts which are
reported as "Received a retry request" it times out.

This whole scenario is not covered by ther PC2824 documentation or CLI
commands - all of which assume that either CLI or Web configuration is
working normally.

There are no options in the PC2824 POST menu that allow me to tell the
switch from where it should download via TFTP the config files.

Neither does the documentation explain which of the two files are for
which purpose or in which order they should be reloaded.

Therefore I seem to be stuck in a loop in which I cannot talk to the
switch to enable me to interrogate it to see what config files may already
exist, or to reinstall and re set the switch.

Also, the reset password option under POST boot options as shown in the
CLI documentation is missing from my switch menu.

The manual also refers to a special Dell set up wizard routine for the
first time the switch is configured, but I don't know how to invoke this
on a switch that presumably has already been configured.

Any suggestions as to how to give this switch a first-birthday and get it
working in managed mode again? None of the Dell documentation instructions are usable because there is no CLI prompt, no managed mode state (and thus no Web interface) and no hardware reset button.

I've been working on  this for two days withourt success, so I'd appreciate any pointers that anyone may be able to offer...

Best regards,

Adrian Redmond

Channel 6 Television Denmark

teknikATchannel6DOTdk

↧
Search

Mac based ACE blocking DHCP traffic? (PowerConnect 5548)

January 16, 2017, 7:19 am
$
0
0

Hi all,


we have a PowerConnect 5548 switch here that is only used for IP phones.
To be sure that no other device works at a port of the switch a mac based ACL was created.
It is applied to port gi1/0/1 which is connected to the router with a DHCP server and looks like that:

mac access-list extended mac-voip-devices-acl1
permit 00:08:5d:00:00:00 00:00:00:ff:ff:ff any vlan 21
permit any 00:08:5d:00:00:00 00:00:00:ff:ff:ff vlan 21
permit 00:0e:08:00:00:00 00:00:00:ff:ff:ff any vlan 21
permit any 00:0e:08:00:00:00 00:00:00:ff:ff:ff vlan 21
....
.... some more ACE
....
....
deny any any vlan 21
exit

All the phones with a MAC address of the specified ranges are working fine.
No we got a new IP phone that does not belong to any of these MAC address ranges so I created a new entry. Now it looks like this:

mac access-list extended mac-voip-devices-acl1
permit 00:08:5d:00:00:00 00:00:00:ff:ff:ff any vlan 21
permit any 00:08:5d:00:00:00 00:00:00:ff:ff:ff vlan 21
permit 00:0e:08:00:00:00 00:00:00:ff:ff:ff any vlan 21
permit any 00:0e:08:00:00:00 00:00:00:ff:ff:ff vlan 21
....
.... some more ACE
....
....
permit bc:c3:42:00:00:00 00:00:00:ff:ff:ff any vlan 21
permit any bc:c3:42:00:00:00 00:00:00:ff:ff:ff vlan 21
deny any any vlan 21
exit

Unfortunatly this phone does not get an IP address of the DHCP server when the ACL is applied.
As soon as I remove the ACL from the port the phone gets an IP address and works. When I set a static IP address in the managment interface of the phone it also work.

Could you tell me what I am doing wrong?

Best regards
Marco

↧
↧

Connect 2 X1026 switches together

January 16, 2017, 11:24 am
$
0
0

Hello all,

I have 2 X1026 switches - each has 3 VLANs defined (1-3).

I am trying to connect the 2 together - preferrably just VLAN 2.

I can easily do this on Cisco equipment - but I've tried Trunk ports, General ports, Access ports - PVID of 2, allowing tagged, untagged...you name it.  I cannot get them to pass traffic.

If I connect an endpoint to the one switchport, it can talk to other VLAN2 devices without issue.  Once I connect it to the other switch, and hang the endpoint off that switch - it doesn't work.  

Can someone tell me how to configure the 2 switch ports so VLAN 2 traffic will pass between them?  

Thanks,

E

↧

Dell Enterprise Hardware & Software Updates, January 16-20

January 16, 2017, 1:32 pm
$
0
0
↧

Connect server to N1524 10GB port

January 17, 2017, 9:00 am
$
0
0

Can anyone tell me if its ok to connect a server to a 10GB "uplink" port on a N1524?

Cheers,

Alg

↧

DHCP Relay needed?

January 17, 2017, 11:50 am
$
0
0

Hello everyone!

I am running into a issue with a DHCP request packets being dropped. Would appreciate any feedback! 

2 x Meraki MX 100 running DHCP.

4 x Dell Power Connect 6224 layer 3 stacked and routing.

3 x Dell Power Connect 5524 layer 2 stacked. (Workstation Switches)

When a client machine try's to renew the IP address it fails. Packet capture on Meraki states that source IP is 192.168.99.1. 

VLAN 105 is our workstations/clients. (192.168.105.0/24)

From what I can gather - since the request is coming from the 99.1 address, it is being dropped because it is not coming from the requesting 105.1 addresses.

Here is a rundown of the layer 3 config.

Layer 3 config-

 

!Current Configuration:

2

!System Description "PowerConnect 6224, 3.3.5.5, VxWorks 6.5"

3

!System Software Version 3.3.5.5

4

!Cut-through mode is configured as disabled

5

!

6

configure

7

vlan database

8

vlan 99-105

9

vlan routing 99 1

10

vlan routing 100 2

11

vlan routing 101 3

12

vlan routing 102 4

13

vlan routing 104 5

14

vlan routing 105 6

15

exit

16

sntp unicast client enable

17

sntp server XXXXXXXXXXX

18

clock summer-time recurring USA

19

clock timezone -5 minutes 0 zone "EST"

20

stack

21

member 1 1

22

member 2 1

23

member 3 1

24

member 4 1

25

exit

26

ip address none

27

ip name-server 192.168.100.69

28

ip routing

29

ip route 0.0.0.0 0.0.0.0 192.168.99.1

30

ip helper-address 192.168.99.1

31

interface vlan 99

32

routing

33

ip address 192.168.99.2 255.255.255.0

34

exit

35

interface vlan 100

36

routing

37

ip address 192.168.100.1 255.255.255.0

38

exit

39

interface vlan 101

40

routing

41

ip address 192.168.101.1 255.255.255.0

42

exit

43

interface vlan 102

44

routing

45

ip address 192.168.102.1 255.255.255.0

46

exit

47

interface vlan 104

48

routing

49

ip address 192.168.104.1 255.255.255.0

50

exit

51

interface vlan 105

52

routing

53

ip address 192.168.105.1 255.255.255.0

54

exit

55

username "admin" password XXXXXXXXXXXXXX level 15 encrypted

56

monitor session 1 destination interface 3/g18

57

monitor session 1 source interface 3/g24

58

monitor session 1 source interface 4/g24

59

monitor session 1 mode

60

line console

61

password XXXXXXXXXXXXXXXXXXXXXXX encrypted

62

exit

63

line telnet

64

exec-timeout 120

65

password XXXXXXXXXXXXXXXXXXXXXXX encrypted

66

exit

67

line ssh

68

password XXXXXXXXXXXXXXXXXXXXXXX encrypted

69

exit

70

ip ssh server

71

spanning-tree priority 4096

72

!

73

interface ethernet 1/g1

74

switchport mode trunk

75

switchport trunk allowed vlan add 104

76

exit

77

!

78

interface ethernet 1/g2

79

switchport mode trunk

80

switchport trunk allowed vlan add 104

81

exit

82

!

83

interface ethernet 1/g3

84

switchport mode trunk

85

switchport trunk allowed vlan add 104

86

exit

87

!

88

interface ethernet 1/g4

89

switchport mode trunk

90

switchport trunk allowed vlan add 104

91

exit

92

!

93

interface ethernet 1/g5

94

switchport mode trunk

95

switchport trunk allowed vlan add 104

96

exit

97

!

98

interface ethernet 1/g6

99

switchport access vlan 104

100

exit

101

!

102

interface ethernet 1/g7

103

switchport mode trunk

104

switchport trunk allowed vlan add 104

105

exit

106

!

107

interface ethernet 1/g8

108

switchport mode trunk

109

switchport trunk allowed vlan add 104

110

exit

111

!

112

interface ethernet 1/g9

113

switchport mode trunk

114

switchport trunk allowed vlan add 104

115

exit

116

!

117

interface ethernet 1/g10

118

switchport mode trunk

119

switchport trunk allowed vlan add 104

120

exit

121

!

122

interface ethernet 1/g11

123

switchport mode trunk

124

switchport trunk allowed vlan add 104

125

exit

126

!

127

interface ethernet 1/g12

128

switchport mode trunk

129

switchport trunk allowed vlan add 104

130

exit

131

!

132

interface ethernet 1/g13

133

switchport mode trunk

134

switchport trunk allowed vlan add 104

135

exit

136

!

137

interface ethernet 1/g14

138

switchport mode trunk

139

switchport trunk allowed vlan add 104

140

exit

141

!

142

interface ethernet 1/g15

143

switchport mode trunk

144

switchport trunk allowed vlan add 104

145

exit

146

!

147

interface ethernet 1/g16

148

switchport mode trunk

149

switchport trunk allowed vlan add 104

150

exit

151

!

152

interface ethernet 1/g17

153

switchport mode trunk

154

switchport trunk allowed vlan add 104

155

exit

156

!

157

interface ethernet 1/g18

158

switchport mode trunk

159

switchport trunk allowed vlan add 104

160

exit

161

!

162

interface ethernet 1/g19

163

switchport mode trunk

164

switchport trunk allowed vlan add 104

165

exit

166

!

167

interface ethernet 1/g20

168

switchport mode trunk

169

switchport trunk allowed vlan add 104

170

exit

171

!

172

interface ethernet 1/g21

173

switchport mode trunk

174

switchport trunk allowed vlan add 104

175

exit

176

!

177

interface ethernet 1/g22

178

switchport mode trunk

179

switchport trunk allowed vlan add 104

180

exit

181

!

182

interface ethernet 1/g23

183

switchport mode trunk

184

switchport trunk allowed vlan add 104

185

exit

186

!

187

interface ethernet 1/g24

188

switchport mode trunk

189

switchport trunk allowed vlan add 104

190

exit

191

!

192

interface ethernet 2/g1

193

switchport mode trunk

194

switchport trunk allowed vlan add 104

195

exit

196

!

197

interface ethernet 2/g2

198

switchport mode trunk

199

switchport trunk allowed vlan add 104

200

exit

201

!

202

interface ethernet 2/g3

203

switchport mode trunk

204

switchport trunk allowed vlan add 104

205

exit

206

!

207

interface ethernet 2/g4

208

switchport mode trunk

209

switchport trunk allowed vlan add 104

210

exit

211

!

212

interface ethernet 2/g5

213

switchport mode trunk

214

switchport trunk allowed vlan add 104

215

exit

216

!

217

interface ethernet 2/g6

218

switchport access vlan 104

219

exit

220

!

221

interface ethernet 2/g7

222

switchport mode trunk

223

switchport trunk allowed vlan add 104

224

exit

225

!

226

interface ethernet 2/g8

227

switchport mode trunk

228

switchport trunk allowed vlan add 104

229

exit

230

!

231

interface ethernet 2/g9

232

switchport mode trunk

233

switchport trunk allowed vlan add 104

234

exit

235

!

236

interface ethernet 2/g10

237

switchport mode trunk

238

switchport trunk allowed vlan add 104

239

exit

240

!

241

interface ethernet 2/g11

242

switchport mode trunk

243

switchport trunk allowed vlan add 104

244

exit

245

!

246

interface ethernet 2/g12

247

switchport mode trunk

248

switchport trunk allowed vlan add 104

249

exit

250

!

251

interface ethernet 2/g13

252

switchport mode trunk

253

switchport trunk allowed vlan add 104

254

exit

255

!

256

interface ethernet 2/g14

257

switchport mode trunk

258

switchport trunk allowed vlan add 104

259

exit

260

!

261

interface ethernet 2/g15

262

switchport mode trunk

263

switchport trunk allowed vlan add 104

264

exit

265

!

266

interface ethernet 2/g16

267

switchport mode trunk

268

switchport trunk allowed vlan add 104

269

exit

270

!

271

interface ethernet 2/g17

272

switchport mode trunk

273

switchport trunk allowed vlan add 104

274

exit

275

!

276

interface ethernet 2/g18

277

switchport mode trunk

278

switchport trunk allowed vlan add 104

279

exit

280

!

281

interface ethernet 2/g19

282

switchport mode trunk

283

switchport trunk allowed vlan add 104

284

exit

285

!

286

interface ethernet 2/g20

287

switchport mode trunk

288

switchport trunk allowed vlan add 104

289

exit

290

!

291

interface ethernet 2/g21

292

switchport mode trunk

293

switchport trunk allowed vlan add 104

294

exit

295

!

296

interface ethernet 2/g22

297

switchport mode trunk

298

switchport trunk allowed vlan add 104

299

exit

300

!

301

interface ethernet 2/g23

302

switchport mode trunk

303

switchport trunk allowed vlan add 104

304

exit

305

!

306

interface ethernet 2/g24

307

switchport mode trunk

308

switchport trunk allowed vlan add 104

309

exit

310

!

311

interface ethernet 3/g1

312

switchport mode trunk

313

switchport trunk allowed vlan add 101-102

314

exit

315

!

316

interface ethernet 3/g2

317

switchport mode trunk

318

switchport trunk allowed vlan add 100,102-103

319

exit

320

!

321

interface ethernet 3/g3

322

switchport mode trunk

323

switchport trunk allowed vlan add 100,102-103

324

exit

325

!

326

interface ethernet 3/g4

327

switchport mode trunk

328

switchport trunk allowed vlan add 101-102

329

exit

330

!

331

interface ethernet 3/g5

332

switchport mode trunk

333

switchport trunk allowed vlan add 100,102-103

334

exit

335

!

336

interface ethernet 3/g6

337

switchport mode trunk

338

switchport trunk allowed vlan add 100,102-103

339

exit

340

!

341

interface ethernet 3/g7

342

switchport mode trunk

343

switchport trunk allowed vlan add 101-102

344

exit

345

!

346

interface ethernet 3/g8

347

switchport mode trunk

348

switchport trunk allowed vlan add 100,102-103

349

exit

350

!

351

interface ethernet 3/g9

352

switchport mode trunk

353

switchport trunk allowed vlan add 100,102-103

354

exit

355

!

356

interface ethernet 3/g10

357

switchport access vlan 100

358

exit

359

!

360

interface ethernet 3/g11

361

switchport access vlan 100

362

exit

363

!

364

interface ethernet 3/g12

365

switchport access vlan 100

366

exit

367

!

368

interface ethernet 3/g13

369

switchport access vlan 100

370

exit

371

!

372

interface ethernet 3/g14

373

switchport access vlan 100

374

exit

375

!

376

interface ethernet 3/g15

377

switchport access vlan 102

378

exit

379

!

380

interface ethernet 3/g16

381

switchport access vlan 100

382

exit

383

!

384

interface ethernet 3/g17

385

switchport access vlan 100

386

exit

387

!

388

interface ethernet 3/g18

389

switchport access vlan 100

390

exit

391

!

392

interface ethernet 3/g19

393

switchport access vlan 100

394

exit

395

!

396

interface ethernet 3/g20

397

switchport access vlan 100

398

exit

399

!

400

interface ethernet 3/g21

401

switchport access vlan 100

402

exit

403

!

404

interface ethernet 3/g22

405

channel-group 1 mode auto

406

exit

407

!

408

interface ethernet 3/g23

409

channel-group 2 mode auto

410

exit

411

!

412

interface ethernet 3/g24

413

switchport mode general

414

switchport general pvid 99

415

switchport general allowed vlan add 99

416

switchport general allowed vlan add 103 tagged

417

switchport general allowed vlan remove 1

418

exit

419

!

420

interface ethernet 4/g1

421

switchport mode trunk

422

switchport trunk allowed vlan add 101-102

423

exit

424

!

425

interface ethernet 4/g2

426

switchport mode trunk

427

switchport trunk allowed vlan add 100,102-103

428

exit

429

!

430

interface ethernet 4/g3

431

switchport mode trunk

432

switchport trunk allowed vlan add 100,102-103

433

exit

434

!

435

interface ethernet 4/g4

436

switchport mode trunk

437

switchport trunk allowed vlan add 101-102

438

exit

439

!

440

interface ethernet 4/g5

441

switchport mode trunk

442

switchport trunk allowed vlan add 100,102-103

443

exit

444

!

445

interface ethernet 4/g6

446

switchport mode trunk

447

switchport trunk allowed vlan add 100,102-103

448

exit

449

!

450

interface ethernet 4/g7

451

switchport mode trunk

452

switchport trunk allowed vlan add 101-102

453

exit

454

!

455

interface ethernet 4/g8

456

switchport mode trunk

457

switchport trunk allowed vlan add 100,102-103

458

exit

459

!

460

interface ethernet 4/g9

461

switchport mode trunk

462

switchport trunk allowed vlan add 100,102-103

463

exit

464

!

465

interface ethernet 4/g10

466

switchport access vlan 100

467

exit

468

!

469

interface ethernet 4/g11

470

switchport access vlan 100

471

exit

472

!

473

interface ethernet 4/g12

474

switchport access vlan 100

475

exit

476

!

477

interface ethernet 4/g13

478

switchport access vlan 100

479

exit

480

!

481

interface ethernet 4/g14

482

switchport access vlan 100

483

exit

484

!

485

interface ethernet 4/g15

486

switchport access vlan 102

487

exit

488

!

489

interface ethernet 4/g16

490

switchport access vlan 100

491

exit

492

!

493

interface ethernet 4/g17

494

switchport access vlan 100

495

exit

496

!

497

interface ethernet 4/g18

498

switchport access vlan 100

499

exit

500

!

501

interface ethernet 4/g19

502

switchport access vlan 100

503

exit

504

!

505

interface ethernet 4/g20

506

switchport access vlan 100

507

exit

508

!

509

interface ethernet 4/g21

510

switchport access vlan 100

511

exit

512

!

513

interface ethernet 4/g22

514

channel-group 1 mode auto

515

exit

516

!

517

q

518

 

519

exit

520

!

521

interface ethernet 4/g24

522

switchport mode general

523

switchport general pvid 99

524

switchport general allowed vlan add 99

525

switchport general allowed vlan add 103 tagged

526

switchport general allowed vlan remove 1

527

exit

528

!

529

interface port-channel 1

530

switchport access vlan 105

531

exit

532

 

533

interface port-channel 2

534

switchport access vlan 105

535

exit

536

snmp-server community XXXXX

537

exit

↧
↧

N-Series switches: Interaction between spanning tree and routed virtual interfaces

January 17, 2017, 1:31 pm
$
0
0

I've done close reading of both the User Guide and CLI manual but I'm not clear on the interaction (i.e, "gotchas"), if any, that spanning tree (STP, RSTP, RSTP-PV, etc.) has wiith respect to virtual routed interfaces.  I know other equipment mfrs. (cough, cough ... B****ade) go to some length to describe the issue; i.e., that virtual interfaces are subject to the rules of STP if they are all in the same domain and are thus blocked for the routed protocols if not in the forwarding state.  Would this kind of operation also be true of the N-series?  What about the case of per-VLAN spanning tree?  Since it's per-VLAN would this still apply?  Wouldn't the spanning tree "terminate" at each virtual interface as opposed to grouping them all in one large domain as would be the case with (R)STP?

Virtual routed interfaces, as opposed to port-based routing, is, for me, a murky area with respect to STP and it's variations.  Any in-depth knowledge that one could share would be appreciated.

↧

Dell PowerConnect x1052: Select LAC hashing algorithm.

January 18, 2017, 4:08 am
$
0
0

How I can select hashing function for LAC in x1052? I need to select Layer3 or Layer4 hash.

↧
Search

Compatibility of Dell 1397 WLAN mini-Card with TP-LINK router configuration

January 18, 2017, 2:36 pm
$
0
0

Hello,

I made a fresh dual-boot installation of Windows 7 Ultimate and Ubuntu 16.04. Before this everything worked fine in Ubuntu 14. Ethernet connection with this router works. The current problem is that I can see the strong-singnal WiFi but I cannot connect: Ubuntu keeps asking me the password, and in Windows an error prompt pops up immediately after trying to connect.

I've been with this over a month, and I cannot recall exactly all the steps. After several attempts, I'm thinking that maybe WiFi card is not compatible with the particular router and its configuration, for this main reason:

(1) The router had a configuration (802.11 bgn maybe); I could see other WiFis but not mine (on both Windows and Ubuntu)

(2) After changing router configuration, nothing changed. I found a solution for Ubuntu here: http://askubuntu.com/questions/55868/installing-broadcom-wireless-drivers?page=1&tab=votes#tab-top and worked fine, in Windows tried reinstalling drivers but problem in (1) remained (drivers issues in Windows was attempted several times; in fact Windows at this point can see another wireless networks).

(3) Router configuration was set as in (1) (I'm on a shared house and the new configuration of (2) was very slow for everyone). After this the Good news: finally I was able to see the WiFi on Windows; Bad news: I cannot connect in either OS - On Ubuntu keeps asking me the password and wont connect, on Windows the "Connection failed" prompt comes up.

If both operative systems gave similar errors, does this necessarily means compatibility error between WiFi card and modem? The router is TP-LINK. Could it be possible to configure network settings (on Windows and Ubuntu separately) to match them according to router configurations?

Best regards

↧

Switch can't transfer file to tftp server

December 20, 2016, 12:22 pm
$
0
0

Dell N-3048P switch setup with a management vlan and a default gateway.  Trying to copy the running or startup config, " copy run config tftp://x.x.x.x/filename" and failed.

There's connectivity between the switch and the server (verified with ping source ip from management vlan).  UDP por 69 is opened on the firewall.  I don't see tftp traffic hitting the firwall (counter 0 traffic) when I initiate tftp from the switch.

↧
↧

Powerconnect 6248 cpu OID's

January 19, 2017, 3:02 am
$
0
0

Morning, I want to monitor my dell switches cpu usage using zabbix 3.0 and grafana
since zabbix does not have a great template for powerconnect 6248 I have been making my own items to monitor.
For the CPU I have found the OID SNMPv2-SMI::enterprises.674.10895.5000.2.6132.1.1.1.1.4.4.0 which is a string value that shows the cpu usage at 5s, 1m and 5m but the problem is I can't graph it or display in any way since its a string.

I have tried searching through different OID's but adding the MIB files to a tree that I have downloaded from the dell website just gives me a lot of errors and does not display most of the MIB's

Is there an OID that I have not found that would give me the current cpu usage as an integer ? or is there some other way around this ?

↧

Dell N4032F PortChannel, VLAN Routing Issue

January 19, 2017, 10:18 am
$
0
0

Hello,

I am configuring my first Dell Switch Stack (having come from a Juniper background) and I seem to be having an issue with some VLAN routing on my stack.

My set up is as follows;

Four N4032F Switches in a stack.

Four FX2S Chassis with multiple blades within each with esxi installed.

8 x 10Gbps per FX2S.

2 x 10Gbps link to each switch in the stack per FX2s

8-ports per FX2S in a LACP port-group, trunk with vlan 100 allowed.

ESXi has a mgmt IP configured, on VLAN 100 (vlan specified), and the DG is configured on the stack.

Each FX2S has its own port channel/LAG group.

Chassis one contains esxi 1 & 2

esxi 1 - 192.168.1.1

esxi 2 - 192.168.1.2

chassis 2 contains esxi 3 & 4

esxi 3 - 192.168.1.3

esxi 4 - 192.168.1.4

From the switch cli, I can ping 192.168.1.1, and esxi 192.168.1.2 but no other esxi hosts.

If I change the ip on the working esxi hosts, they still ping.

The port channel, interface, esxi hosts are all configured the same (bar the vpc id etc).

No idea what is happening but it is flummoxing me!

Any ideas what could cause this?!

Many Thanks in advance.

↧

s4810 management interface

January 19, 2017, 2:34 pm
$
0
0

Hi,

I am getting the following error when I try to configure the route to the management network.

This is what I am getting:

* configure

* interface management 0/0

* ip address 10.8.0.14 255.255.255.0

* no shutdown

* exit

* management route 0.0.0.0/0 10.8.0.5

 Address not in the same subnet as management port.

What did I miss?

Thanks

Paras

↧
Viewing all 2954 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>