The Arista switch interface doesn't go up, it doesn't have any errors and status is "notconnect" when connected to a Cisco server.
We have the following components:
Arista model is DCS-7050QX-32S-F
QSFP module in the server is Intel XL710 40G QSFP+
QSFP Cable to connect is QSFP-H40G-CU3M
Do you guys have any idea what is the issue?
SOLVED:
We changed the interface configuration from "speed force 40gfull" to "speed auto 40gfull" and the link goes up.
Related
So I have an ESP device that is connected to my WiFi network. It runs a web server and now I want to make requests to this webserver from my android app. So I tried a couple of things and none got satisfied.
Things I tried and why not suitable for me.
Setting up mDNS:
Can't use it since android doesn't really do mDNS it fails in the lookup.
Setting a Static IP:
This approach will fail if the routers' gateway is changed. (at least that's what I believe).
(Can anyone elaborate on this ^. AFAIK if you want to make a static IP you need to match the given gateway with your router's gateway, So if I configured esp board for my router, it might not work with someone else's router.)
Setting a WebSocket connection:
To do this also need the hostname which is IP again.
Asking IP from user:
Since this is going to be a product I can't ask the user to provide the IP address in the mobile application. It leads to a lack of user experience.
I still hope that there should be another way of handling this case which I'm not aware of. I'm actually dying to get this done and I need you guys to help me with this.
It sounds like you are over complicating stuff here.
Step 1. Connect esp board to your wifi (i guess you have figured this out)
step 2. check what lan address your board has connected to, for this is usually just use
Serial.print("IP address: ");
Serial.println(WiFi.localIP());
step 3. start your wifiserver at port 80
WiFiServer(80);
step 4. in your android app, or any other platform(i recommend using browser in computer while simply testing if it works or not) type url: local_ip_address_that_you_got_above/mygetrequest?value1=1
step 5. Listen for incoming clients and intercept the get value that you will recieve in the header in fashion of "GET /mygetrequest?value1=1"
step 6. done :)
If you want to skip the process of implementing all of it from scratch you can get full source code of my example server described above at: https://spacerival.com/lounge/2614/arduino-server but i do highly suggest you to implement it on your own and not just copy paste that source code, since you wont learn much at all to be fair
So after trying all day long, I came with a solution. This is a bit of a workaround as I was lost. So What I did was I created a Soft AP with a small web server that returns the LocalIP. So my esp is working on both AP and STA modes right now.
How it works is simple
ESP runs with a small webserver with /getLocalIP endpoint.
ESP opens a SoftAP for the user to connect. The user connects with the
SoftAP.
The user will be asked to enter credentials for the desired
WiFi.
After connecting to the desired WiFi mobile app will request a
for 192.168.4.1/getLocalIP (AP's IP Address).
Since ESP is already connected to the WiFi this endpoint will send the WiFi.localIP() to the app.
So now the app has the LocalIP.
I have a Beaglebone Black(rev c),I am trying to connect it to Windows 8 laptop using putty. I am putting IP address as 192.168.7.2 and port as 22,but when I says open to it,putty window will pop-up and after sometime I will get fatal ERROR saying:
"Network connection time-out"
I am new to this, can someone tell me what am i missing?
Seems to indicate the an SSH server is not running on the BBB. Or possibly for some reason the BBB did not take 192.168.7.2 as an IP. Or perhaps you might need to wait a little bit longer for the SSH server to start up.
Short of this, there is not much to go on. One way to trouble shoot the issue would be to get a serial debug cable, connected and working to the BBB. Then you could dmesg | grep ssh or some such and hopefully get closer to what the actual problem is. Sorry if this is not enough for you to go by, but it is really hard to figure out what is going on without more information.
Other potential problems could be as simple as a USB cable that sometimes works or sometimes doesn't.
It may not be this but have you installed the drivers? See step 2 here: http://beagleboard.org/getting-started. If it's not that or you have already installed those then I am not sure sorry. Perhaps someone else has another suggestion.
Is the BeagleBone connected to your network with an Ethernet cable? It will only use 192.168.7.2 for the network-over-usb when there's only a USB cable connected - if you have Ethernet connected it will use DHCP to get an IP from your router, in which case you can check your router page to see what IP it got.
If you do just have USB connected then a driver issue is the most likely culprit, but you could try to ssh to the hostname beaglebone.local instead of the IP.
This is my first post, so don't judge if I mess something up.
The problem is that I bought a new Desktop PC for my office (a Windows 8 machine with motherboard Z97-HD3 (has integrated Ethernet/LAN card)) and it worked OK for a few weeks, but now, the internet is gone.
When I boot up my PC I get "Network Identifying". After a minute or so, it says that it is connected, but when I open a browser it either says: "This webpage is not available" (more often) or "SSL certificate problem" (rarely). I've been chipping on this problem for a few days and the only steps that I've mustered up to take are these:
1. Is it the cable? Try the Ethernet/LAN cable on a different computer
Tried that. It works on my other laptop. So I conclude that the problem is with the new computer.
2. Is it a software problem or hardware?
2.1. Look at the back of the PC. The Ethernet card lights are on.
2.2. Try pinging localhost. Start > Open command prompt (cmd) > "ping 127.0.0.1". All 4 packages are sent and received with time 1ms
2.3. Maybe there is something wrong with Windows? Tried installing Ubuntu, but the internet doesn't connect as well
Anything else I could do? Or should I conclude that this is a hardware issue and return it to the shop?
First, make sure that you can ping your Gateway (gateways are computers/routers that are between two networks ). You can find out the IP of your gateway by running this in cmd:
ipconfig
There you will see your currently assigned(or static) ipaddress, the subnetwork, as well as the IP of your Gateway. Then try to ping your Gateway.
If you can then you know that all is good with cables and software and the problem is either configuration(you dont have gateway set) or the gateway can't make the connection outside of your local network.
if you can't ping your gateway, then you know something is wrong on your PC.
I've an application that uses GSM commands sent over a serial port to a GSM ModeM.
The application works just fine on Windows XP, 7 etc., but sometimes it does not connect to the serial port on Windows Server 2008.
I tried to check using an application called Tera Term, but when I try and connect it to the port where the ModeM is supposed to be connected to, I get an error saying the COM1 port is not available ( it is the required port ).
This could indicate that the COM port is busy or occupied...and indeed when I try to rename the port, I get a Windows Warning that port is opened by some other application and renaming it can have consequences etc.etc...
How do I find out which, if any, application is using the COM port? I tried Portmon, but it remains greyed out in the Ports/capture area...so I cannot use it to find out what's happening with it?
Could anyone please tell me if there's a problem with the COM port detection in Windows Server 2008? Or if it's a problem with Tera Term/ PortMon that they're not able to detect the COM port?
This issue is baffling..kindly help me on this.
Thanks...
I think you should be able to use Process Monitor to find out which application is opening or accessing the COM1 serial port, or at least figure out what is going on. It has been while since I last had to do this so I don't remember the details of how to go about doing that.
If you decide to do this, I recommend running Process Monitor on a system that you are able to get this to work successfully first. That way you can see what a "normal" system looks like and compare it to what you are getting on the Windows Server 2008 system.
I'm writing a mini OS just for fun. I want to save some key information to one securiry server on the Internet and ever fetch it BEFORE booting my OS.
So my problem is: How to access the Internet only via BIOS? i.e. How to use the TCP protocol in BIOS environment?
PS.
It is obvious that diskless workstations use such a technique. So it is technically possible.
Diskless workstations use PXE which is part of NIC (network card) ROM or a BIOS extension, it's a simple environment that implements TCP/IP stack that can get a executable over TFTP and run it.
There is an open source one that you could modify iPXE to your needs and replace your existing PXE ROM.
I don't think that this is possible. You need to implement a network driver into the BIOS to achiving that. So I would say this is not possible. By the way I never read that someone wrote his/her own BIOS.
If you have an ethernet port on your pc/router buy a Gil.Net router and connect it wirelessly to your home router and then plug in the router