Continuing from the previous NTP post, our GNS3 topology hasn't changed except for UbtSvr:
I created a working syslog-ng server on UbtSvr2 long before I did the NTP post so, to make sure I don't miss a step or forget to mention something I did to get it working, I've gone ahead and created a brand new Ubuntu server in VirtualBox named UbtSvr3. The default route 192.0.0.0/8 and ip address on UbtSvr3 is the same as UbtSvr2 in the previous NTP post. Nothing else has changed.
Setting up an Ubuntu NTP Server in preparation for creating a syslog-ng server.
I’m working on creating a syslog-ng server on UbtSvr2 to capture events from routers in my GNS3 environment. The first step is having correct time on all devices; this isn’t important for syslog to function but its nice to associate syslog events with the current date and time – which my devices don’t have:
Problem:
R1 has both a successor and a Feasible successor for R3 L3 (3.3.3.0/27) and R2 L2 (2.2.2.0/24)
But, when looking at the EIGRP Topology Table for R2 and R3, there isn't a Feasible successor for R3 L3 (3.3.3.0) nor for R2 L2 (2.2.2.0) - what's the deal?!
It's probably due to the feasibility condition
CME Router: 3825 w/CME installed
Phones: 2x7960G & 1 7970G – all are registered & using SCCP
TFTP Server: Win2008 running SolarWinds TFTP Server. Connectivity throughout.
I have several ringtones I want to feed to my IP Phones but was having trouble getting the phones to:
1. Recognize that the ringtones were available
2. Getting the phones to find the files
VirtualBox ver: 4.2.10
Virtual Machine (VM): Windows 7 pro, guest additions installed
Requirements: Ability to run a command prompt and VirtualBox as administrator (the usual problem with accessing VBoxManage).
Scenario:
I have a Win7Pro Virtual Machine (VM) with a 20 GB dynamically allocated storage disk (VDI) which only has about 2 GB of space left. I need to install a program on the VM which requires 2.5 GB of disk space. In short, I cannot install this program unless I increase the disk size.
So, in this post I’m going to increase the same disk (disk 0 or drive C) from 20 GB to 30 GB. This will give me the space I need with room to grow.
I did this a while ago when I was preparing a lot of config files (.txt) for use on my routers & switches. I needed to find interface numbers and replace them with interfaces that I had available or was using (i.e. s0/0/0 with s0/0, etc.). As I don’t use this feature very often, it is a prime candidate for a blog post.
PART 2:
Now that SRV is set up and running WinRadius we can configure DLS1 & DLS2 to use RADIUS on SRV for login authentication (telnet).
The configurations are straight forward and if you’d like to know more I’d suggest searching Cisco’s site.
Some of the key information we needed to take note of in Part 1 was the following:
Radius IP: 10.1.50.1
Radius Password (a.k.a NAS Secret): WinRadius
Radius auth-port: 2812
Radius acct-port: 2813
Our User: User1
& Password: CCnP
