PowerConnect 5316M Basic configuration

We have recently acquired a Blade Center fully populated with PE 1955's, and 2 PowerConnect 5316M modules. I am able to talk/remote into the switch (via DRAC), and have configured it with an IP address/mask and default gateway... now, I can ping it and all is good so far :)

I have the 1st blade configured with ESXi, but cannot for the life of me figure out how to configure the VLAN's in order to have it talk to the rest of the Network

PC5313 config:

interface range ethernet g(1-12)
switchport mode general
exit
vlan database
vlan 4
exit
interface ethernet g1
switchport general pvid 4 
exit
interface ethernet g2
switchport general pvid 4 
exit
interface ethernet g3
switchport general pvid 4 
exit
interface ethernet g4
switchport general pvid 4 
exit
interface ethernet g5
switchport general pvid 4 
exit
interface ethernet g6
switchport general pvid 4 
exit
interface ethernet g7
switchport general pvid 4 
exit
interface ethernet g8
switchport general pvid 4 
exit
interface ethernet g9
switchport general pvid 4 
exit
interface ethernet g10
switchport general pvid 4 
exit
interface ethernet g12
switchport general pvid 4 
exit
interface range ethernet g(1-10,12)
switchport general allowed vlan add 4 untagged
exit
interface vlan 1
ip address 192.168.5.102 255.255.255.0
exit 
ip default-gateway 192.168.5.1
username admin password XXXXXXXXXXXXXX level 15 encrypted

console# sh int stat
 Flow Link Back Mdix
Port Type Duplex Speed Neg ctrl State Pressure Mode
-------- ------------ ------ ----- -------- ---- ----------- -------- -------
g1 1G-Fiber -- -- -- -- Down -- -- 
g2 1G-Fiber -- -- -- -- Down -- -- 
g3 1G-Fiber -- -- -- -- Down -- -- 
g4 1G-Fiber -- -- -- -- Down -- -- 
g5 1G-Fiber -- -- -- -- Down -- -- 
g6 1G-Fiber -- -- -- -- Down -- -- 
g7 1G-Fiber -- -- -- -- Down -- -- 
g8 1G-Fiber -- -- -- -- Down -- -- 
g9 1G-Fiber -- -- -- -- Down -- -- 
g10 1G-Fiber -- -- -- -- Down -- -- 
g11 1G-Copper Full 100 Enabled Off Up Disabled On 
g12 1G-Copper Full 100 Enabled Off Up Disabled Off 
g13 1G-Copper -- -- -- -- Down -- -- 
g14 1G-Copper -- -- -- -- Down -- -- 
g15 1G-Copper -- -- -- -- Down -- -- 
g16 1G-Copper -- -- -- -- Down -- -- 

 Flow Link 
Ch Type Duplex Speed Neg control State 
-------- ------- ------ ----- -------- ------- ----------- 
ch1 -- -- -- -- -- Not Present 
ch2 -- -- -- -- -- Not Present 
ch3 -- -- -- -- -- Not Present 
ch4 -- -- -- -- -- Not Present 
ch5 -- -- -- -- -- Not Present 
ch6 -- -- -- -- -- Not Present 
ch7 -- -- -- -- -- Not Present 
ch8 -- -- -- -- -- Not Present 
console#

ESXi server configured with 192.168.5.105/24

Thank you for your help

Luc

Responses(4)

A

Anonymous

5 Practitioner

•

274.2K Posts

0

March 5th, 2012 09:00

I see you have all your ports set to general mode. If these ports have VLAN unaware devices attached, workstations, servers, etc, they should be set to access mode. I would try that out and see if we can get some communication.

Let us know the outcome.

Thanks.

LPL33

3 Posts

0

March 7th, 2012 01:00

Hey Daniel,

Thanks for the answer... So, I have removed all the unnecessary configuration, and have it set for basic config:

SW1# sh run

interface vlan 1

ip address 192.168.5.102 255.255.255.0

exit

hostname SW1

username admin password xxxxxxxxxxx level 15 encrypted

snmp-server community xxxxxxx rw

SW1#

Now I can see the rest of the network (LAN) and all is fine and dandy.

I have one ESXi configured on the 1st blade (192.168.5.106), and pings to it drop like flies:

SW1# ping 192.168.5.106 count 10

Pinging 192.168.5.106 with 56 bytes of data: