VMware Cloud Community
FunkyD
Contributor
Contributor

cannot ssh onto second service console

Hi,

I created a second service console on another network. I can ping it but I can't ssh. Below is my console and switch config.

I have tried restarting networking and ssh but to no avail. I can ssh from the sc on 192.168.110.238 to 192.168.111.231.

If I ssh from a machine on 192.168.111.0 I get "connected refused".

The only thing I haven't done is reboot the server which I need to avoid as it is a major hassle.

Name Port Group IP Address Netmask Broadcast Enabled DHCP

vswif0 Service Console 192.168.111.230 255.255.255.0 192.168.111.255 true false

vswif1 Service Console 2 192.168.110.238 255.255.255.0 192.168.110.255 true false

vswif2 Service Console 3 192.168.111.231 255.255.255.0 192.168.111.255 true false

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 64 5 64 1500 vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

VM Network 900 0 vmnic0

Service Console 2 300 1 vmnic0

Service Console 900 1 vmnic0

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch1 64 8 64 1500 vmnic3

PortGroup Name VLAN ID Used Ports Uplinks

Production 200 0 vmnic3

Disaster Recovery 700 5 vmnic3

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch2 64 4 64 1500 vmnic2

PortGroup Name VLAN ID Used Ports Uplinks

External 0 1 vmnic2

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch3 64 4 64 1500 vmnic4

PortGroup Name VLAN ID Used Ports Uplinks

Test 901 1 vmnic4

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

192.168.110.0 * 255.255.255.0 U 0 0 0 vswif1

192.168.111.0 * 255.255.255.0 U 0 0 0 vswif1

192.168.111.0 * 255.255.255.0 U 0 0 0 vswif0

169.254.0.0 * 255.255.0.0 U 0 0 0 vswif0

default 192.168.111.253 0.0.0.0.0 UG 0 0 vswif0

Many thanks Smiley Happy

0 Kudos
1 Reply
jkearsey55
Contributor
Contributor

I think this is normal behaviour. From what I recall (correct me if I am wrong) the second service console IP is strictly for redundancy (reduce host isolation probability) and is pingable, but not manageable via SSH. You can only have one service console per port group.

Perhaps someone else can confirm this.

0 Kudos