I have been working on CISCO's SMA390 and the RPC port for the device is not responsive when connected to a core switch.
1. The core switch is for public-facing IP/ CIMC IP of the device.
2. The IP's are configured and using ipmitool command.
3. The port is responding when tried to configure over a private network(laptop to device connection).
I have tried ping command after checking that the IP's are configured and its failing while the gateway is responding.
ipmitool lan print 1
ipmitool lan set 1 ipsrc static
ipmitool lan set 1 ipaddr 10.10.1.5
ipmitool lan set 1 netmask 255.255.255.0
ipmitool lan set 1 defgw ipaddr 10.10.1.1
ipmitool lan set 1 access on
ipmitool raw 0x36 0x52 0x0f
I want the ping and the ssh to be enabled.
I figured out after some more troubleshooting that CISCO x90 devices by default work on 100G bandwidth connection. The default provided on x95 devices is 1000G bandwidth connection. Hence the RPC port didn't respond.
If you face this issue, try
1. using a 100G connection.
2. change the default connection acceptance bandwidth of your device(i.e x90 here).
Related
I'm trying to access remotely a device (in this case a PLC) through a 3G/4G internet connection.
I have a Raspberry PI connect to the internet with a 3G modem and a OpenVPN configured on it.
The eth0 port is connected to the 3G/4G modem and the eth1 port is connected to the PLC.
How do I add the eth1 port to the VPN connection so I can access the PLC trough any computer connected to this VPN?
This images may better explain what I'm tryng to achive:
physical connections
virtual connections
Scenario:
Clients on VLANs X
DHCP server on VLAN Y
WDS server on VLAN Z
We have IP helper-address command on our layer 3 device for DHCP. I would like to avoid using DHCP options and instead add another IP helper-address command to point clients to WDS as well. Is this possible? I know having two IP helper-address commands will direct traffic to both IPs but will this work correctly if the WDS server is not also hosting DHCP services?
in your case, use the ip helpper to specify the dhcp server and WDS server specify using the options dhcp server (use option 66 and 67).
example dhcp server for cisco IOS:
ip dhcp pool NETWORK10.10.10.0/24
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
dns-server 10.10.10.10
option 66 ascii WDS-server.domainname.local
option 67 ascii Boot\x86\wdsnbp.com
lease 0 24
good like
PC1-VLAN1======Switch : Successful pings from the switch
PC1-VLAN2======Switch : *Unsuccessful* pings from the switch
I've got a single switch with a static IP directly connected to PC1 with a static IP, both on the same 192.168.1.0/24 network. The switch has no VLAN's on it except the default VLAN1.
With this setup, I can successfully ping PC1 from the switch (via terminal from another PC connected to the switch using either telnet or console cable).
If I Create a VLAN2 and assign PC1's port to VLAN2, the switch can no longer ping PC1. I would understand if another PC on a different VLAN couldn't ping PC1, but I would think that the switch could ping either.
What am I missing?
Thanks!
On the switch, the IP address that is configured is probably still in Vlan 1, move the IP to Vlan 2
If your switch IP address is 192.168.1.1
conf t
int vlan 1
no ip address
int vlan 2
ip address 192.168.1.1 255.255.255.0
end
Now you should be able to ping PC1 while it's in vlan 2
Does this help?
I’m using Linux 2.6.32 device that establishes a VPN connection. When VPN is up, all packets sent by the device, includes the VPN client src address.
ICMP packets continuously go through the VPN interface and successfully encrypted/decrypted, and after that they are sent to the WLAN via the WLAN interface (as ESP packet with the VPN Interface as src ip).
After disabling the VPN, the VPN interface goes down, ICMP packets are sent directly to the WLAN interface (with the WLAN Interface as src ip) in plaintext un-encrypted.
But when the VPN is established again and the VPN interface is up again, packets are sent at the same way, but the ESP packet encapsulates a WLAN src IP and not the VPN src IP.
ICMP packets go through the VPN interface and then via WLAN interface as ESP packet with the WLAN Interface as src ip and not VPN Interface as src ip.
The only way to have the ESP packets leave with the VPN IP address encapsulated is either:
Wait until the machines "nf_conntrack_icmp_timeout" expires, and restart ping application.
Remove the WLAN interface (ifconfig down) and set it up again (ifconfig up).
Both solutions are not appropriate, as I don’t want to stop the ping and I don’t want to reconfigure the device network interface.
I tried to clear the routing cache by:
echo 1 > /proc/sys/net/ipv4/route/flush
And I also tried to clear the ARP cache by:
ip -s -s neigh flush all
Is there another way to clear all active session, after the VPN is going down?
i'm triying to imagine how to do:
(with Linux Debian based distro)
I have PC with 4 NIC:
eth0 = Internet Access (connect to router WAN)
eth1 = Local lan
eth2 = OUT NIC
eth3 = IN NIC
I need to send all traffic from eth1 (local lan) to eth2, receive the same traffic from eth3 and route to eth0.
The idea is send all eth1 traffic to external device over eth2, the external device inspect the packets and send to PC again on eth3, then my PC Linux route traffic to eth0
Is posible to do that ?
You're running linux on a PC? We need to know the version first off. Second you are looking into IProutes if you want to redirect traffic from one NIC to another.