Monday, May 12, 2014

Huawei Quidway Switch 5300 Series

The S5352C-EI is a case-shaped device with a 1 U high chassis, provided in a
- limited version LI - provides various Layer-2 functions
- standard version SI - supports Layer-2 functions and basic Layer-3 functions
- enhanced version EI - supports all routing protocols and features
- advanced version HI - supports all routing protocols and features and MPLS, hardware OAM.

LS-S5352C-EI Overview

• Power: need to purchase additional power LS5M100PWA00 or LS5M100PWD00
• Non-POE Switch
• Layer 3 Ethernet Switch
• Ports: 48 GE
• Extended Interface Card Slot: 1
• Software: Enhanced Version
• Stackable switch
• Powerful Service Support
• High Reliability
• Security and QoS
Quidway S5300 series gigabit switches are new generation Ethernet gigabit switches that meet the requirements for high-bandwidth access and Ethernet multi-service convergence, providing powerful Ethernet functions for operators and enterprise customers. Based on the new generation high-performance hardware and Huawei Versatile Routing Platform (VRP), the S5300 features large capacity and gigabit interfaces of high density, provides 10G uplinks, meeting the requirements for the 1G and 10G uplink devices of high density. The S5300 can meet the requirements of multiple scenarios such as service convergence on campus networks and Intranets, the access to the IDC at a rate of 1000 Mbit/s, and the access to computers at a rate of 1000 Mbit/s on Intranets.

Monday, May 5, 2014

Extending Grace Period on Win2008 R2

Most of the content I use for webcasts and live events have virtual machines that have been created either by someone on my team or by someone at Microsoft corporate.  The virtual machines are not created with trial versions of the operating system but with fully licensed product.  For obvious reasons they are not activated, so when I first boot up I usually get a message saying the machine has to be activated within a few days.  Sometimes though, the machines have past the activation grace period and will not log on unless they are activated NOW!!  This can be somewhat annoying because most of the time I only need the machines for a demonstration the following week, maybe for the next month or so, and I don’t want to use one of my product keys for such a short term machine life.  So what can I do?  
The first thing I do with machines that are requiring immediate activation is simply turn them off.  I then change my host machine date back to a date closer to when the virtual machines were originally created and boot them up one more time.  Now the virtual machine thinks my date is kosher and is within the activation grace period, and lets me logon.  That’s great but the date is wrong and I need to access the internet with the host as well as do my demos, and having a wrong date causes issues.  Never fear, one of the things we can do with Windows Server 2008 and Windows Server 2008 R2 (actually this works with Windows Vista and Windows 7 as well), is re-arm the machine and extend the activation grace period another 60 days.

So How’s This Done?

Simple… all we need to do is run a script in the windows\system32 folder called slmgr.vbs.  Check the steps below:
  1. Bring up a Command Prompt.
  2. Type slmgr.vbs –rearm, and press ENTER.
  3. Restart the computer.
You computer has now extended the evaluation period 60 days!!!  You can re-arm up to 3 times giving you an activation-free trial period of a total of 240 days!!

How Much Time Is Remaining in the Evaluation Period

You can find out by running the same script this time with different switch:
  1. Type slmgr.vbs -dli, and the current status of the evaluation period is displayed.  (the dli switch means – display license information)
If you want to find out what else you can do with the script type slmgr.vbs –? and you’ll get a full list and explanation of all the switches.

Thursday, March 20, 2014

Solaris 10 - Notes - Daily

#traceroute -v 192.168.1.1
#netstat -an | grep LISTEN
#route -n , route -tu
#prtdiag | head
#prtdiag -v
#prtconf |grep Mem
#vmstat 5 10
#df –k –F ufs
#df –k –F vxfs
#vxdisk -p or list
#/dm/dmtool s m
#/dm/dmtool de - to deteach the mirror
#find /export/store3 -type f \( -name \*.iso \)
#find /export/store3 -type f \( -name \*.iso -o -name \*.jpg \)
#tail -f /var/adm/messages
#smbstatus -b / -s / -v
#cat /etc/release
#showrev -a
#uname -a / -rv
#prstat
#root@vmshcoss01>gzcat "xxx.tar.gz" | tar -xvf -
#root@vmshcoss01>gzip -d "xxx.tar.gz" |tar -xvf -
root@vmshcoss01>tar -xvf xxx.tar
root@vmshcoss01>tar -C /myfolder -zxvf yourfile.tar.gz

Work with console session Solaris

stty rows 40 cols 80
exec /usr/bin/ksh -o emacs
TERM=ansi
export TERM

SyBase IQ - query in columns
Sybase Adaptive Server - query in rows

#screen
run the script
ctl + ad
next day
screen -r

#screen -x / -d / -r

#mount -F ufs -o remount,rw /dev/dsk/c1t0d0s0 /
#mount | head 1

#mount -o rw,remount /dev/md/dsk/d10 /
#fsck /dev/md/rdsk/d10

#cfgadm -al | grep -i c3 -  Configuration administration Hot Plug Devices

#shutdown -y -i6 -g0 - reboot
#shutdown -y -i0 -g0 - shutdown

#/etc/init.d/volmgt stop or start
#svcadm restart volfs

#pkgadd -G -d ./VBoxSolarisAdditions.pkg

Solaris 10 Single User mode
1. reboot
2. on GRUB screen - Select "Oracle Solaris 10  8/11 s10x_u10wos_17b x86"
3. Select Line "Kernel /platform/i86pc/multiboot"
4. after the multiboot add followings
"Kernel /platform/i86pc/multiboot -B console=ttya -s"
5. Then Press Enter
6. Press b to boot with that options.

Sometimes even you can login to Single user mode, system can't mount / to /a

Searching for installed OS instances…
/dev/dsk/c1t0d0s0 is under md control, skipping.
/dev/dsk/c1t1d0s0 is under md control, skipping.
No installed OS instance found.
# mount -o ro /dev/dsk/c1t0d0s0 /a
OR
# mount -o rw /dev/dsk/c1t0d0s0 /a

To reset the root user password
#cd /a/etc
#vi  shadow
root:pvclqIvh6tBm6:16152::::::
(delete pvclqIvh6tBm6)
root::16152::::::
wq!

#reboot
After that you can login without typing root password, then
#passwd to change the password.
   
# df -hF ufs
# swap -lh

/etc/nodename - hostname
/etc/hosts = /etc/inet/ipnodes
/etc/netmasks
/etc/defaultrouter
/etc/hostname.e1000g0
/etc/hostname.e1000g0:1

dig msn.com
dig msn.com +short
dig @local.dns.server msn.com
dig msn.com A +noall +answer
dig msn.com MX +noall +answer
dig msn.com NS +noall +answer 
dig msn.com ANY +noall +answer
dig -x 192.168.10.1 +short

Solaris 10 DNS client & servers configuration files and log locations:
root@vmshcom01> svcs -l svc:/network/dns/server:default
root@vmshcom01> svcs -l svc:/network/dns/client:default
/etc/nsswitch.conf
/etc/resolv.conf
/etc/netconfig
/etc/hosts
/etc/named.conf - BIND Configuration
/var/named/bind-log - DNS server log
/var/adm/messages - system messages
/var/svc/log/network-dns-client:default.log - SMF DNS client log (search for ERRORS and
/var/svc/log/network-dns-client:default.log - SMF DNS server log (search for ERRORS and
/var/svc/manifest/network/dns/client.xml - DNS Client Manifest Configuration
/var/svc/manifest/network/dns/server.xml - DNS Server Manifest Configuration

Solaris 10 DNS Client & servers Tools:

/usr/sbin/dig - DNS lookup utility, replaces nslookup future release of Solaris.
/usr/sbin/nslookup - DNS lookup utility, now marked obsolete and will be removed in a future release of Solaris
/usr/sbin/rndc - name server control utility
named-checkconf - named configuration file syntax checking tool
named-checkzone - zone file validity checking tool
/usr/sbin/svcs - Report SMF service status
/usr/sbin/svcadm - Manage SMF services.
/usr/sbin/svcprop - Verify SMF configuration properties

 


   

Friday, January 31, 2014

Try - Pink

Oh oh

Ever wonder about what he's doing?
How it all turned to lies?
Sometimes I think that it's better to never ask why

Where there is desire
There is gonna be a flame
Where there is a flame
Someone's bound to get burned
But just because it burns
Doesn't mean you're gonna die
You've gotta get up and try, and try, and try
Gotta get up and try, and try, and try
You gotta get up and try, and try, and try

Eh, eh, eh

Funny how the heart can be deceiving
More than just a couple times
Why do we fall in love so easy?
Even when it's not right

Where there is desire
There is gonna be a flame
Where there is a flame
Someone's bound to get burned
But just because it burns
Doesn't mean you're gonna die
You've gotta get up and try, and try, and try
Gotta get up and try, and try, and try
You gotta get up and try, and try, and try

Ever worry that it might be ruined
And does it make you wanna cry?
When you're out there doing what you're doing
Are you just getting by?
Tell me are you just getting by, by, by?

Where there is desire
There is gonna be a flame
Where there is a flame
Someone's bound to get burned
But just because it burns
Doesn't mean you're gonna die
You've gotta get up and try, and try, and try
Gotta get up and try, and try, and try
You gotta get up and try, and try, and try
Gotta get up and try, and try, and try
Gotta get up and try, and try, and try
You gotta get up and try, and try, and try
Gotta get up and try, and try, and try

You gotta get up and try, and try, and try
Gotta get up and try, and try, and try...

Memory Kill - Franco Reyes

I'm here
Watch me on display
I'm soul scratched severed inlay
I fear
Wonder if you'd say
Go get going ok ok ok.....?

Adhere to whatever you may
I'm tongue tied twisted hearsay
It's a severe paralysis
Wallowing insane
Hopeless hoping in vain!

Here's a letter to your pride
Our souls and hearts divide
How can this be?
We're beckoned to a lie
Leave uncompromised
How can this be?
Kill that memory

Cold and pale black memory
Of you and me standing still
Kill kill kill

Here's a letter to your pride
Our souls and hearts divide
How can this be?
We're flailing to decide
Desperate to deny
How can this be?
Kill that memory
Kill kill

Wednesday, December 18, 2013

South-bound vs North-bound Interfaces used for Network Management


Most people involved in the Network Management get confused with two terms frequently used to describe the interconnections between the network and the network managers as well as the interconnections between various management systems (OSS).
The terms that get people confused are:
  • South Bound Interfaces (SBI)
  • North Bound Interfaces (NBI)
The analogy used to name these interfaces is that of a compass, and can be explained with the below figure:

About South Bound Interfaces (SBI)
The South Bound Interfaces (SBIs) allow Network Management Systems to connect to the Network Elements (NEs) and manage them. Although SNMP is the most common one, actually there are a lot of other options available and sometimes these are used together with SNMP in order to perform actions that are not available for whatever reason from SNMP.

In particular, integration of Network Elements (NE) to Network Management Systems (NMS) is provided by the following interfaces:
  • SNMP
  • CLI
  • FTP / SFTP
  • Telnet / SSH
Read below an overview of the above interfaces, that can be used as a quick reference when comparing and analyzing Network Management Systems.
SNMP overview
SNMP is a TCP/IP-based network management protocol working at the application layer and using the UDP protocol at the transmission layer.
The SNMP interface typically supports the SNMPv1 /v2c standard and sometimes the v3 standard, and is used to connect to (and manage) elements implementing SNMP agents.
CLI overview
The Command Line Interface (CLI) is an interactive user interface toward an Network Element. With CLI, users respond to a visual prompt by typing in a command on a specified line, receive a response back from the system, and then enter another command, and so forth.
FTP/SFTP overview
FTP and SFTP are typically used for backing up Network Element data and upgrading NE software. FTP / SFTP are TCP/IP-based network management protocols working at the application layer and are dependent on the UDP protocol.
File Transfer Protocol (FTP) is a set of standard protocols for transferring files on networks. FTP transfers passwords and file contents in plain text. SSH FTP (SFTP) uses the SSH protocol to provide secure file transfer and processing. With SFTP, passwords and data are encrypted during transmission.
Telnet and SSH overview
Telnet and SSH are basic types of interfaces used for the remote login and management of the NEs. Telnet / SSH sometimes allow Network Managers to perform specific management functions not available through SNMP.
Telnet is a TCP/IP-based network management protocol working at the application layer. Users can login in to an NE and use CLI to run commands usually related with NE configuration and maintenance. Using the TCP protocol at the transmission layer, the Telnet protocol provides services for network communication. The Telnet protocol transmits communication data in plain text, which is not secure.
Secure Shell (SSH) is also a TCP/IP-based network management protocol working at the application layer. SSH makes use of the TCP protocol at the transmission layer for transmitting data encrypted at the application layer.
About North Bound Interfaces (NBI)
The North Bound Interfaces (NBIs) can comply with ITU-T or TMF series of standards and are used to enable  Alarm / Performance / Inventory / Provisioning / Configuration / Security related info of Network Elements to be forwarded to higher level management system than the NMS, typically referred to as OSS systems.
In particular, northbound integration is provided through the following interfaces:
· XML
· FTP
· SNMP
· SYSLOG · TACACS · LDAP
· CORBA is also another option, available from legacy management systems.
North Bound Interfaces typical usage
Not all interfaces are suited for all management features. It is common to use a particular interface for a specific function, e.g. to use SNMP to forward alarms to North Bound OSS systems. The below table presents this in detail: