RP Address in MULTICAST
I have few doubts about Multicast RP address
We have MPLS ISP backbone network, here two P routers are configured as RP address(IN GLOBAL) and MSDP is running between them.
Now, my doubts are
All the Multicast customer we are giving is under MVPN only, if dense mode no RP concept, if sparse mode MVPN have a separate RP. Then what the use of Global RP and MSDP??
I come across MSDP for inter domain multicasting, do we need to run MSDP with other ISPs?? if so, is it advisable??
Pls clear my above doubts!!
Thanks in advance!!
Hi Sankar,
All the Multicast customer we are giving is under MVPN only, if dense mode no RP concept, if sparse mode MVPN have a separate RP. Then what the use of Global RP and MSDP??
CE multicast (or simply c-multicast) and SP multicast (or simply p-multicast) are totally independent. As you mentioned, even if Customer multicast is sparse mode, the RP should be from VRF. RP from SP global cannot help with VRF multicast (Else you need complex leaking). Global RP is required if the P-multicast is sparse mode, inorder to establish the MDT tunnel. MSDP is required if you provide some inter domain multicast.
I come across MSDP for inter domain multicasting, do we need to run MSDP with other ISPs?? if so, is it advisable??
MSDP can be iether used for Inter domain or with Anycast RP. Basically MSDP is the protocol used to update any active source details to otehr RP in same domain (in case of Anycast) or different domain.
You may have to check if you have inter-as design or anycast to understand the need for MSDP.
HTH,
Nagendra
Similar Messages
-
Does a rtp-address be multicast?
Does a rtp-address be multicast?
I have a program that sends rtp-information between one address an two ports, say 130.237.251.219 port 10000 and 10100...
I can't get my one written program to catch the rtp-packets.
Is it because it's not multicast??
It throws a "SessionManager exception: address is alreday in use"
I write in the adress rtp://130.237.251.219:10000/127
What's wrong???Yes and No.
RTP is an Protocol that can be used with any other underlaying Transport-Protocol. IPX/SPX TCP/IP UDP... (Sun's implementation supports TCP/IP and UDP only.)
If you want to use TCP/IP and you want to transmit RTP via IP-Multicast, you'll have to use an Multicast IP-address. These addresses are any of 224.0.0.0 through 239.255.255.255.
Look at this Link to get further details about Multicast addresses:
http://www.freesoft.org/CIE/RFC/1700/5.htm
One other thing. You can't use the same PC to receive and transmit RTP-packets via Multicast. You can open a port only once a time and every port is available only once on a pc.
So you need at least two pc's to work with Multicast RTP-transmitions. -
Force mapping to a specific MAC address a multicast IP address in ARP cache table with netsh
Hi all,
I would like to know if there is any solution (netsh option, registry entry, whatever...) to force mapping a given MAC address to a multicast IP address (224.x.y.z) in my ARP cache table.
I am doing the following:
netsh.exe interface ip add neighbors "Ethernet" "224.224.xxx.yyy"
"00-80-EE-UU-VV-WW"
But the entry in the ARP table is substitued by the calculated multicast MAC@ corresponding to my multicast IP@ :
netsh.exe interface ip show neighbors "Ethernet"
Interface 12 : Ethernet
Internet Address
Physical Address Type
224.0.0.22
01-00-5e-XX-YY-ZZ
static
224.224.yyy.zzz
01-00-5e-UU-VV-WW
static
(For information, calculation of the Multicast MAC Address is described in RFC1112§6.4 -> The MAC@ equals 01-00-5e + the last 23 digits of the multicast MAC Address)
My problem is that I'm not using an Ethernet network but an AFDX (used on Airbus A380, Boeing 787 Dreamliner, by the NASA...). This network topology is a deterministic Ethernet. The network must know accurately where each network packet is going. Thus...
the multicast MAC@ cannot be accepted and packet destinated to that MAC@ are not going anywhere.
So, I must match accurately my multicast IP@ to my MAC@ (00-80...).
It used to work with Windows XP (which was not doing any "magical" MAC@ substitution on multicast IP@), but since Windows Vista, netsh is doing the substitution described above. Is there any way to disable this substitution or force my IP
to MAC mapping in ARP table? And of course, I'm not using XP anymore ;)... but a tablet with Windows 8.1.
Thanks for any help.
Cheers,
Olivier.Hi,
The article you pointed me to is just an explanation of what I said in my original post : "Multicast MAC Address is described in RFC1112§6.4".
But, as I said in my original post, this is true ONLY for Ethernet network. And I am NOT on an Ethernet network.
So MAC address automatic calculation for my IP address done by Windows/netsh/arp is wrong in my case. The calculation Windows is doing is correct ONLY for Ethernet network. Since I am not on Ethernet, I don't want these calculations, and I'm looking for
a solution to disable them.
So, the underlying question is : "Is Microsoft/netsh/arp able to handle other network's type than Ethernet ?"
Thanks,
Olivier Dupré. -
Multicast mac address isn't learned, igmp-snooping
I have PIM router which connects to the cat 2960 switch and also I have host which connects to another port on the same switch. Host was joined to the IGMP group 224.1.1.1. I see that the router generates igmp-query and the host respons. IGMP-snooping process sees that process and updates appropriate entries:
2960-5#sh ip igmp snooping mrouter
Vlan ports
15 Gi2/0/32(dynamic)
2960-5#sh ip igmp snooping groups
15 224.1.1.1 igmp v2 Gi2/0/32, Gi2/0/33
But when I command "sh mac address-table multicast" I see nothing:
2960#sh mac address-table multicast
Vlan Mac Address Type Ports
What is reason of this problem?There is the following statement from the "CCNP Practical Studies: Switching:
the process of populating the bridge table with multicast MAC addresses is based upon inspection of the destination MAC address, unlike unicast MAC addresses where the source MAC address of unicast frames is examined to generate bridge table entries.
And this book describes other parts of the mac learning process and says that after exchanging IGMP-message MAC-table must be populated by multicast mac-addresses. But later I found some Cisco and Jupiner documentation which says there is two way to perform multicast forwarding - MAC and IP. Default metod is IP multicast forwarding. When this metod is used multicast MAC-addresses isn't learnt and process of packet forwarding uses special forwarding cache which includes list of mapping IP and appropriate interfaces. It all means that this book isn't actual. All modern switchs perform multicast forwarding by IP metod and MAC-addresses don't populate CAM. -
Multicast mac-address Nexus 7k
Hi,
i'm going to use Nexus 7000 in Data Center.
During analysis configuration, I need define mac-address-static configuration for multicast mac address for Firewall Checkpoint cluster.
In "Layer 2 Switching Configuration Guide, Release 4.1.pdf" documentation speak about
"Configuring a Static MAC Address
[..]You cannot configure broadcast or multicast addresses as static MAC addresses[..]"
Have you a suggestion to manage this problem and why is it not possible configure mac address static multicast?
Regards
DinoJoseph - The ClusterXL A/A configuration is a variation of the StoneSoft or Rainfinity clustering technologies that have been used to cluster Solaris and other *NIX flavored servers and firewalls for years. (In fact, StoneSoft filed suit against Check Point in Europe 8 or 9 years ago for patent violations, and lost.) These configurations were very common on Check Point clusters running on Solaris from the late 90's forward - and, as you describe, have unicast IP's with a multicast MAC for the VIP. Even from the days of installing these on the brand new (at the time) 2900 series switches you had to do exactly as you state above - static MAC entries (or in some cases port mirrors) so traffic was directed to both active switch ports. In Active/Passive mode Check Point ClusterXL clusters are almost always "plug and play" today - rarely do the switches need anything beyond speed/duplex settings. The VIP assumes the MAC of the physical NIC it is currently bound to, and therefore there are no issues as far as switch config or proxy ARP entries on the gateways. All of these issues have to do with traffic flowing to the VIP and through the firewall, and the ability of the switch to correctly identify which physical switch port(s) the VIP is currently patched in to. This is one of three types of traffic associated with ClusterXL itself. The second is state synchronization, which is accomplished through a crossover cable and therefore not relevant. Even when using a switch state sync is a typical TCP 18181 connection from a unicast IP/unicast MAC on one gateway to the other through a dedicated interface pair.
The challenge described by CJ is not with the traffic flowing to the VIP, however. It is an entirely separate process - Check Point Clustering Protocol (aka CPHA if filtering in WireShark) is essentially the heart beat traffic. Every interface pair within a Check Point cluster continually communicates with its "partner" interface on the other cluster members. If any packet takes over 100ms or shows more than a 5% loss the gateway is forced in to "probing" mode where it falls back to ICMP to determine the state of the other cluster member. Depending on the CPHA timing settings an active gateway will failover to the passive in as quickly as 500ms or so. ClusterXL will fail over the entire gateway to the standby to avoid complications with asynchronous routing.
Out of the box, CCP is configured to use multicast, but it supports broadcast as well. To change this in real time (no restart required) simply issue the command:
cphaconf set_ccp {broadcast/multicast}
At the Ethernet level, CCP traffic will always have a source MAC of the Magic MAC of 00:00:00:00:xx:yy where XX is the “Cluster ID” – something identical on each cluster member but unique from one cluster to another, and YY is the cluster priority (00, 01, etc.) based on the priority levels set on cluster members within Dashboard on the cluster object. The destination MAC will always be the Ethernet broadcast of ff:ff:ff:ff:ff:ff.
At the IP level the source of CCP will always appear as 0.0.0.0. The destination will always be the network address (ie, x.x.x.0).
Similarly in multicast mode you will see the same traffic at the IP level but at the Ethernet level the destination will now be a IPv4 multicast MAC (ie, 01:00:5e:4e:c2:1e).
In a tcpdump with the –w flag opened in WireShark and a filter applied of just “cpha” (without the quotes) you should see a continual stream of traffic with the same source and destination IPs on all packets (0.0.0.0 and network IP), the destination of either a bcast or mcast MAC and the source MAC alternating between 00:00:00:00:xx:00 and 00:00:00:00:xx:01.
Long story short, the problem CJ is describing is a behavior on the 7K where a packet capture taken on the Check Point interface itself (ie, tcpdump –i eth0 –w capture.cap) ONLY shows CPHA traffic from it’s own source MAC and no packets from it’s partner. A tcpdump on the 7K itself will show traffic from both.
As CJ mentioned, a simple NxOS upgrade will fix the issue per:
This one:CSCtl67036 basically pryer to NX-OS 5.1(3) the nexus will discard packets that have a source of 0.0.0.0. Which in broadcast mode is exactly what the CCP heartbeat is. We bypassed this one.CSCsx47620 is the bug for the for static multicast MAC address feature but it requires 5.2 code on the 7k
(NOTE:Additional RAM may be required for the 5.2 update)
Also note that Check Point gateways do support IGMP multicast groups, given that you have the correct license. It is a feature of SecurePlatform Professional on the higher end gateways or as a relatively inexpensive upgrade on the lower end boxes or open platforms. For lab purposes you can simply type “pro enable” at the CLI (without the quotes). As of the latest build there is no technical limitation (no license check) so you can enable advanced routing features as needed for testing in a lab. For step by step details on configuring IGMP on SPLAT Pro go to the Check Point support site and search for sk32702.
This can be a frustrating issue to troubleshoot, so hopefully this helps someone avoid the headaches I ran in to. -
Enabling VM Guest NLB w/Multicast IGMP on 2012 Hyper-V host w/ converged SCVMM fabric switch
What a mouthful.
As short as possible:
WHAT I'M ATTEMPTING:
I'm trying to build a new NLB cluster for a 2008 R2 SP1 Remote Desktop Services farm. And I'm trying to do it the right way, with multicast igmp, not unicast.
The two guest VMs with NLB install converge fine. VIP gets this:
IP: 192.168.100.157
MAC: 01-00-5e-7f-64-9d
NLB NIC is on the same VLAN & "Converged switch" in VMM as our mgmt/server traffic (That is to say it's on production VLAN, not on a separate vlan)
PROBLEM:
Can't ping 100.157. From VM guest itself, from host, or from Cisco 6509 switch.
Cisco show mac address lookup does not see that MAC anywhere
show ip igmp groups shows not igmp traffic at all. Clearing counters show sno multicast increment.
FURTHERMORE:
Host is setup thusly:
- Dell R810
- 8x1GbE Broadcom 5709c in a Server 2012 LACP/HASH team built via VMM powershell cmdlets
- On the physical switch side, those 8 nics are in a Cisco port-channel, trunked, all VLANs allowed
- Host has no "physical" nics per se, as in a 2008 R2 hyper-v host. Instead Host has these:
Set-VMNetworkAdapter -ManagementOS -Name "Live Migrate" -MinimumBandwidthWeight 35
Set-VMNetworkAdapter -ManagementOS -Name "MGMT" -MinimumBandwidthWeight 25
Set-VMNetworkAdapter -ManagementOS -Name "CSV" -MinimumBandwidthWeight 40
Set-VMNetworkAdapter -ManagementOS -Name "iSCSI #1" -MinimumBandwidthWeight 0
Set-VMNetworkAdapter -ManagementOS -Name "iSCSI #2" -MinimumBandwidthWeight 0
Set-VMNetworkAdapter -ManagementOS -Name "Aux" -MinimumBandwidthWeight 0
Get-VMSwitch outputs this on the converged v-switch:
ComputerName : My-host
Name : My awesome switch
Id : e2377ce3-12b4-4243-9f51-e14a21f91844
Notes :
SwitchType : External
AllowManagementOS : True
NetAdapterInterfaceDescription : Microsoft Network Adapter Multiplexor
Driver
AvailableVMQueues : 0
NumberVmqAllocated : 0
IovEnabled : False
IovVirtualFunctionCount : 0
IovVirtualFunctionsInUse : 0
IovQueuePairCount : 0
IovQueuePairsInUse : 0
AvailableIPSecSA : 0
NumberIPSecSAAllocated : 0
BandwidthPercentage : 0
BandwidthReservationMode : Weight
DefaultFlowMinimumBandwidthAbsolute : 0
DefaultFlowMinimumBandwidthWeight : 1
Extensions : {Microsoft NDIS Capture, Microsoft
Windows Filtering Platform, Microsoft
VMM DHCPv4 Server Switch Extension}
IovSupport : False
IovSupportReasons : {This network adapter does not support
SR-IOV.}
IsDeleted : False
Question:
Aside from a few of my favorite MS MVPs (shout out to
WorkingHardInIt for having this same question), I can't find much documentation on employing 2008 R2 NLB on guest VM within a fabric-oriented, VMM-built 2012 Hyper-Visor converged switch (no network virtualization...yet).
Yes I know all about VMM NLB but 1) I'm trying to wedge NLB in after building these VMs without a service template (NLB is the audible, essentially) and 2) MS NLB is configured in providers & I've created requisite VIP templates.
Even so, I ought to be able to create an NLB cluster without VMM's assistance in this scenario correct? Suboptimal, I know but possible, yes? Essentially I've put to synthetic NICs on each VM, set IPs manually, and assigned them to the same vlan. I can ping
each synthetic NIC, but not the cluster IP.
And yes: these particular vNICs have Mac Address Spoofing enabled.
Cisco:
I have a TAC case open with Cisco, but they can't quite figure it out either. IGMP Snooping enabled across the switch. And they insist that the old static arp entry to resolve this problem is no longer necessary, that Microsoft now complies with relevant
RFCs
Possible SOlution:
Only thing I can think of is flipping MulticastForwarding param below from disabled to enabled. Anybody ever tried it on a converged virtual switch on the Hyper visor? Is my virtual converged switch protecting
me from multicast igmp packets?
PS C:\utilities> Get-NetIPv4Protocol
DefaultHopLimit : 128
NeighborCacheLimit(Entries) : 1024
RouteCacheLimit(Entries) : 128
ReassemblyLimit(Bytes) : 1560173184
IcmpRedirects : Enabled
SourceRoutingBehavior : DontForward
DhcpMediaSense : Enabled
MediaSenseEventLog : Disabled
IGMPLevel : All
IGMPVersion : Version3
MulticastForwarding : Disabled
GroupForwardedFragments : Disabled
RandomizeIdentifiers : Enabled
AddressMaskReply : Disabled
Thanks for any thoughts.
RobertSorry for the poor follow-up Steven. We are using Server 2012 Hyper-V, not VMWare, on the hosts. You can close this but for the benefit of anyone who comes across it:
After working with Cisco, we decided not to implement multicast IGMP. Cisco says you still need to create a static ARP entry on the physical switch, though my cluster IP address & Microsoft NLB 2008 R2 were set up with igmp multicast, not multicast or
unicast. Here was his email:
Yes, we will need the static mapping for the NLB server in this case because the NLB mac address is multicast and the IP address is unicast. I was under the impression that even the server would be using IGMP but that’s not
the case. We won’t need to do the mapping for the nodes though if they use IGMP. To this end, following is the configuration that should make this work.rp 192.168.100.157
0100.5e7f.649d arpa
<u5:p></u5:p>
mac address-table static 0000.0000.649d vlan <> interface <> disable-snooping
ßThis is the switch interface where the NLB server is located<u5:p></u5:p>
interface vlan<>
<u5:p></u5:p>
ip pim sparse-dense-mode <- This is needed for the switch to elicit IGMP joins from the nodes<u5:p></u5:p>
end<u5:p></u5:p>
I don't think it got through to him that there was a virtual Layer 2/3 Hyper-V switch on top of 8 teamed GbE interfaces in LACP/hash. "Where the NLB server is located" = 1)a Cisco port-channel bound to one of six physical hosts; the NLB VM itself could be
on any of those port channels at any given time (We have a six node Hyper-V cluster).
Once I enabled pim I did see activity; but we killed this later as we realized we'd have to implement the same on 40+ managed routers globally
Anyway we further would have had to implement this across managed routers at 40 sites globally according to Cisco.
Robert -
Modem: WRT310N Firmware: 1.0.9.0 Build 4 (Latest)
192.168.1.1 > Security > Firewall > Filter Multicast
If I want to allow Multicast traffic on my network, does this box need a "Check Mark" or does it need to be "Unchecked"
Thank you for your help!
Here is the manual's pdf text:
Filter Multicast Multicasting allows for multiple
transmissions to specific recipients at the same time. If
multicasting is permitted, then the Router will allow IP
multicast packets to be forwarded to the appropriate
computers. Select this feature to filter multicasting. This
feature is not selected by default.
Here is my router's internal help text:
Filter Multicast. Multicasting allows for multiple transmissions to specific recipients at the same time. If multicasting is permitted, then the Router will allow IP multicast packets to be forwarded to the appropriate computers. Select Enabled to filter multicasting, or Disabled to disable this feature.
WRT610N Manual:
Filter Multicast Multicasting allows for multiple
transmissions to specific recipients at the same time. If
multicasting is permitted, then the Router will allow IP
multicast packets to be forwarded to the appropriate
computers. It is selected by default. Deselect this feature
to disable it.
WRT54G2 Manual:
Filter Multicast Multicasting allows for multiple
transmissions to specific recipients at the same time. If
multicasting is permitted, then the Router will allow IP
multicast packets to be forwarded to the appropriate
computers. This feature is selected by default. Deselect
this feature to disable it.So i re-read some of these articles. And this is the most professional article, the most trustworthy in my opinion as it was taken straight from a textbook written by a Cisco author. However what ails me is that it is from 2006 and for a different linksys router.
Filter Multicast (Disabled)— This setting allows multicast traffic to be forwarded to the appropriate destination. Multicast traffic is traffic destined to multiple hosts. This allows the traffic to be sent one time, while allowing multiple registered hosts to receive it, which it more efficient than sending the traffic individually to each host (which is a process known as unicast). A host registers to receive this multicast traffic by virtue of the fact that it is running an application that is configured to listen on the corresponding multicast IP address. Multicast is frequently used for the transmission of multimedia and streaming data. Multicast traffic is frequently filtered when it is either unnecessary (for example, because no applications that utilize multicast are running on the network) or to prevent multicast-based attacks from being initiated (for example, to prevent an attack that uses multicast traffic to saturate a network with bogus traffic, thus effecting a DoS on the network). Although somewhat counterintuitive, you want to disable filtering if you want to permit multicast traffic.
If you read the last few lines carefully,
1) Multicast traffic is frequently filtered when it is either unnecessary (Filter = block)
2) you want to disable filtering if you want to permit multicast traffic (Disable = Uncheck)
So this confirms that the manual is actually correct. If you want to "Enable" I.E. "Allow" Multicast Traffic. You must "Disable" the "Filter"
Basically uncheck the filter to allow
Check the filter to block (just like everything else on that page)
http://www.ciscopress.com/articles/article.asp?p=598649&seqNum=5
So if this does in fact not work, and the opposite is true. Than it is simply a bug/glitch in the firmware and it should be reported to Cisco/Linksys. However, how do we do this? Everytime I contact them, they just want to know my S/N of my router before they talk to me, and since its too old they say sorry cant help you.
*Edit* Here's another confirmation link from cisco on Multicast Technology:
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/IP-Multi.html
Routers are typically configured with filters to prevent multicast traffic in this address range from flowing outside an autonomous system (AS) or any user-defined domain (Again, in this statement Filter = Block)
"Filter Multicast" Enabled (Checked) = Enable the Filtering (Blocking) of Multicast Traffic
"Filter Multicast" Disabled (Unchecked) = Disable the Filtering (Blocking) of Multicast Traffic
Which makes sense. For every other filter on that page, if you "Uncheck" them, such as "Filter Anonymous Internnet Requests" then it "Allows" your network to be pinged. But if you "Check" that box, it prevents your network from being pinged.
Does anyone agree/disagree? -
Use of Bind , Connect with IP Multicasting
i'm trying to get a clear picture of the semantics of using bind, connect with IP multicasting.
ipv4 & ipv6 both are relavent.
it is my understanding -- you must multicast join on each interface you want to receive on.
in my view of the world, ideal semantics would provide :
bind-ing a socket to a specific local IP address, port - that has joined multiple IP multicast addresses
on multiple interfaces would allow multicasts to still be received - but would limit them to
interfaces which matched the bound IP address, and further if more than 1 interface supported
the same IP address, would allow receipt for all the joined interfaces that match the bound
IP address.
this does not appear to be the case; it appears that binding to a local IP address causes
multicast receipt to terminate. binding to 1 of the joined multicast address limits receipt
to the bound multicast address. the semantics seem confusing.
regarding connect :,
imagine multiple sources of a specific IP multicast address; your socket is doing receiving only,
no transmiting. it seems that ideally connect would allow you to limit the receipt of IP multicast
to the source that you connect to; i imagine connecting to the foreign IP address,
not the IP multicast address being transmitted. if semantically i could connect to the IP multicast address
i would still be receiving from all the sources - so no filtering benefit.
my understanding is you can connect to a IP multicast address; but this seems redundant to bind with
the only advandage that you can use send instead of sendto. and further if multiple sources are
transmitting the same IP multicast address you dont get filtering
when i tried using multiple sources transmitting 2048 different IP multicast address, with a receiver
who had multicast joined the same 2048 IP multicast address -- as soon as connect to 1 of the
sources ( foreign IP address) of the IP multicasts i stop receving packets all together. i had hoped
to limit the receipt of the multicasts to just that single source.Generally, you would use bind variables by changing statements that are written like this
select * from emp where empno=6678 and ename='Jones'
so that they're written like
select * from emp where empno=? and ename=?
How you then bind these question marks to the particular values you want depends on the API you're using (ADO? OLE DB directly?, etc). If you have a support contract, there are plenty of examples for any API on metalink.oracle.com
Justin -
I have a switch stack of 2950's and a 3750 with the SMI version of IOS. I am trying to get Ghost multicasting working. Every time I start a multicast session it seems that the multicast packets to port 7777 show up on every port on every switch (I've plugged my laptop with Ethereal into several switches and found this) I thought that by default the 2950's are supposed to have IGMP snooping on and that should prevent flooding. What am I missing?
thanks for your help on this,
MichaelHi Michael, What Multicast IP address are you transmitting to?
As you may know, a multicast IP address and multicast MAC address are not 1-to-1 mapped, and only use 23 out of the 64 bits in a MAC address to map to a given IP address. As the result the group 230.0.0.1 (for example) and 224.0.0.1 will be mapped to the same mac address 0100.5e00.0001. This is a known reserved group, and any traffic for that group will be flooded out all ports, regardless of IGMP snooping. Since the switch uses the mac address table to forward traffic, any packet going to mac address 0100.5e00.0001 will be flooded.
So due to the 23 bit mapping, you need to avoid using the ip address range 224-239.0.0.x, and 224-239.128.0.x, otherwise it may cause flooding or other problems. If this is what you're running into, try using an address such as 2xx.1.1.1 instead.
HTH,
Bobby
*Please rate helpful posts. -
Unregistered Multicast Filtering vs. NDP Protocol for IP V6 Ping SG300
Hi everybody,
we are running several switches of the SG 300 Series all with Firmware sx300_fw-14088.
We are having a setup that uses a lot of Multi Cast so we use the IGMP Feature of the Switch and enable unregistered multicast filtering.
However: if we enable unregistered multicast filtering, we cannot get a Ping V6 to work. We know, that the basis is the NDP protocol to resolve mac addresses to IP v6.
It seems as if the switch thinks that the multicast based NDP protocotol is unregistered multicast.
Any suggestions?
an example configuration configuration is attached to this mail:There are strict rules to map L3 IPv6 Addresses and L3 IPv4 addresses to L2 Mac Addresses. At the end those Mac Addresses are Multicast addresses independent of their roots (IPv6 or IPv4). Of course you are able to keep them separate from each other (00-01-FF vs. 33-33-FF), but both have the I/G-Bit set to 1 and for a Switch those addresses are multicasts.
It might be that you are using the default Multicast properties: Forwarding Method for IPv6 and Forwarding Method for IPv4 equals MAC Group address. Therefore, the Switch should use the Multicast Mac addresses as an IGMP Snooping filter as well. The Multicast Mac Address which is used in ICMP Type 135 (Neighbor Solicitation) of course is not registered via IGMP and will get blocked. This is only a guess, but it should be worth the effort to Switch the forwarding method to IP Group address.
Cheers,
@gar -
Hi,
To do clustering, should all the instances of the servers need to have multicasting
IP address ? ( I mean b/n 224.0.0.1 to 239.*.*.* ??).
thanks in advance,
vijay
More in-line.
Vijay wrote:
> Thanks Tom,
> I have few more questions..
>
> 1. You said, "the admin server should not be a part of cluster". What does it
> mean? According to the docs, what i understood is, which ever server starts first
> becomes the admin server. Is that correct?
>
See the 6.x docs:
http://edocs.bea.com/wls/docs61/cluster/setup.html#675975
5.1 is different, if you're using 5.1 I'm not the one to ask.
>
> 2. Assume my application is nor clustered. Should I make a request to the multicasted
> IP address or to the individual instances of my application?
>
Client URLs refer to the server address, not multicast address.
The multicast address is used internally by a cluster for propagating shared info.
>
> Thanks in advance
> vijay
> Tom Barnes <[email protected]> wrote:
> >
> >vijay wrote:
> >
> >> Hi,
> >>
> >> To do clustering, should all the instances of the servers need to have
> >multicasting
> >> IP address ? ( I mean b/n 224.0.0.1 to 239.*.*.* ??).
> >>
> >
> >Yes. They must each have the same one. In addition, they must each
> >have
> >the same listen port. Note that the admin server should NOT be a member
> >of the cluster. For more info, see the administration docs.
> >
> >
> >>
> >> thanks in advance,
> >> vijay
> >
-
Cannot get AMS5 to multicast a stream from a Vbrick 9000 encoder
I have a vbrick 9000 series encoder transmitting an RTMP stream to Adobe Media Server 5's multicast service. It appears that AMS5 starts the multicast but then stops the multicast. The AMS tool Multicastplayer just says "Waiting for Video..."
How do I configure the 9000 encoder and the AMS5 to allow multicast to work?
Thanks in advance!
vbrick 9000 transmitter configs for multicast
- Transport type: RMPT
- ip address: ams server IP
- Destination Port: 1935
-RTMP Application: multicast
-RTMP Stream: livestreamTest1?fms.mulicast.type=2&fms.multicast.groupspec=G%xxxxxxx&fms.multicast.addre ss=239.135.x.x&3A4444
-RTMP Username: <blank> <-- I don't see where there is a "username". There is no username in the configurator tool.
-RTMP Password: broadcast <-- This matches whas I used in the multicast configurator tool.
Logs from AMS5
Handling pulish request for source stream: livestreamTest1,
query string: fms.multicast.type=2&fms.multicast.groupspec=G%xxxxxxx&fms.multicast.address=239.135.x.x& 3A4444,
client id:xxxxxxxxx,
client ip: 10.199.3.2
Bound multicast context: livestreamTest1-1 to source stream name: livestreamTest1
Registered multicast context: livestreamTest1-1
Multicast connection status: netconnection.connect.success,
multicast context: livestreamTest1-1 Multicast netstream will publish to ip address 239.135.x.x:4444 on interface address: default, multicast context livestreamTest1-1
Multicast connection status: netstream.connect.success,multicast context: livestreamTest1-1
Multicast connection status: netstream.publish.start,multicast context: livestreamTest1-1
Unloaded application instance/_definst_
Handling unpublished request for source stream:livestreamTest1, client id: xxxxxx. Client ip; 10.x.x.x <--- WHERE DOES THIS COME FROM????
Unbound multicast context: livestreamTest1-1 from source
stream name: livestreamTest1
Shutting down multicast context: livestreamTest1-1. Current state: STATE_PUBLISHING
For what it's worth. I can make unicast flash work fine with these settings...
vbrick 9000 transmitter configs for unicast flash
- Transport type: RMPT
- ip address: ams server IP
- Destination Port: 1935
-RTMP Application: live
-RTMP Stream: livestream
-RTMP Username: <blank>
-RTMP Password: <blank>I think multicast is enabled properly.
"ip pim sparse" is enabled on the router with IGMP at layer 2.
On the router I see *,G and S,G entires in the multicast routing table pointing toward the AMS5 server's vlan.
From the windows server with AMS5 on it I can ping the multicast groups of various video speakers.
From the windows server with AMS5 on it I can run an application called "VBDirectory" that uses multicast to discover all vbrick devices. -
When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
edit "applications/multicast/main.asc" ?
HELP ME !!! THANKS!!!
* File: main.asc
* The server-side portion of the multicast sample application.
* This app accepts publish and unpublish requests from FMLE, and republishes
* the live stream from FMLE into a target Flash Group.
// General Constants
// "Constants" representing multicast event types.
var TYPE_FUSION = 1;
var TYPE_IP = 2;
var TYPE_P2P = 3;
// StreamContext Description, Constants and Functions
* Type: StreamContext
* This application tracks the context for live streams published to the server
* that are being republished into a Flash Group. The StreamContext "type" used
* for this is just an Object containing the following members:
* client - The encoding/publishing client.
* streamName - The source Stream name as published by the client.
* type - The multicast event type.
* groupspec - The groupspec identifying the Flash Group and capabilities.
* address - IP multicast address (optional for pure P2P events).
* netConnection - A loopback NetConnection used for the mcastNetStream.
* mcastNetStream - The NetStream used to republish the source Stream into
* the Flash Group.
* netGroup - An (optional) NetGroup handle for the target Group.
* Only present for Fusion or P2P events.
* state - One of the state constants defined immediately below
* this comment.
var STATE_INIT = 0; // Starting state for a StreamContext.
var STATE_CONNECTING = 1; // Establishing loop-back connection.
var STATE_CONNECTED = 2; // Connection established.
var STATE_PUBLISH_PENDING = 3; // Attempting to publish.
var STATE_REPUBLISHING = 4; // Actively republishing to multicast.
var STATE_UNPUBLISHING = 5; // Shutting down multicast republish.
var STATE_UNPUBLISHED = 6; // Unpublished successfully.
var STATE_DISCONNECTING = 7; // Shutting down loopback connection.
var STATE_DISCONNECTED = 8; // Connection shut down. Done.
* Registers a source Stream published by the specified client, along with the
* context for the multicast event, as a StreamContext Object.
* @param client - The Client publishing the stream.
* @param streamName - The source Stream name.
* @param params - The parameters resulting from parsing the source Stream's
* query string.
* @return The new StreamContext Object for the registered Stream.
function registerStream(client, streamName, params)
var streamContext = { "client": client,
"streamName": streamName,
"type": params["fms.multicast.type"],
"groupspec": params["fms.multicast.groupspec"] };
if (params["fms.multicast.interface"])
streamContext["interfaceAddress"] = params["fms.multicast.interface"];
if (params["fms.multicast.address"])
streamContext["address"] = params["fms.multicast.address"],
streamContext.state = STATE_INIT;
updateStreamContextLookups(streamContext);
trace("Registered multicast context for source stream: " + streamName);
return streamContext;
* Updates the indexed lookups installed for the passed StreamContext Object
* with the application.
* @param streamContext - The StreamContext Object to (re)index.
function updateStreamContextLookups(streamContext)
application.streamTable[streamContext.streamName] = streamContext;
if (streamContext.netConnection)
application.netConnTable[streamContext.netConnection] = streamContext;
if (streamContext.mcastNetStream)
application.mcastNetStreamTable[streamContext.mcastNetStream] = streamContext;
if (streamContext.netGroup)
application.netGroupTable[streamContext.netGroup] = streamContext;
* Provides access to the StreamContext Object for a registered source Stream
* by name.
* @param streamName - A registered source Stream name.
* @return The associated StreamContext Object; undefined if the source Stream
* name is not registered.
function getStreamContextForSourceStream(streamName)
return application.streamTable[streamName];
* Provides access to the StreamContext Object for a given server-side
* NetConnection hosting a multicast NetStream.
* @param netConnection - A server-side NetConnection.
* @return The associated StreamContext Object; undefined if the passed
* NetConnection is not indexed to a StreamContext.
function getStreamContextForNetConnection(netConnection)
return application.netConnTable[netConnection];
* Provides access to the StreamContext Object for a given multicast NetStream.
* @param netStream - A multicast NetStream.
* @return The associated StreamContext Object; undefined if the passed
* NetStream is not indexed to a StreamContext.
function getStreamContextForMulticastNetStream(netStream)
return application.mcastNetStreamTable[netStream];
* Provides access to the StreamContext Object for a given NetGroup associated
* with a multicast NetStream.
* @param netGroup - A NetGroup.
* @return The associated StreamContext Object; undefined if the passed
* NetGroup is not indexed to a StreamContext.
function getStreamContextForNetGroup(netGroup)
return application.netGroupTable[netGroup];
* Unregisters the StreamContext from the application.
* @param streamContext - The StreamContext Object to unregister.
function unregisterStreamContext(streamContext)
if (streamContext.netConnection)
delete application.netConnTable[streamContext.netConnection];
if (streamContext.mcastNetStream)
delete application.mcastNetStreamTable[streamContext.mcastNetStream];
if (streamContext.netGroup)
delete application.netGroupTable[streamContext.netGroup];
trace("Unregistered multicast context for source stream: " +
streamContext.streamName);
// Application callback functions
* Initializes global StreamContext lookup tables.
application.onAppStart = function()
application.streamTable = {};
application.netConnTable = {};
application.mcastNetStreamTable = {};
application.netGroupTable = {};
* Handles a publish event for the application by validating the request
* and bridging the published stream into a target Flash Group. Invalid
* publish requests are ignored and the publishing client's connection
* is closed.
* @param client - The publishing client.
* @param stream - The published stream.
application.onPublish = function(client, stream)
//trace("Handling publish request for source stream: " + stream.name);
var params = parseQueryString(stream.publishQueryString);
if (!validateStreamParams(params))
application.disconnect(client);
return;
var prevContext = getStreamContextForSourceStream(stream.name);
if (prevContext)
forceCloseStreamContext(prevContext);
// Register source Stream, and kick off the async process that will
// eventually wire-up the associated multicast NetStream.
var streamContext = registerStream(client, stream.name, params);
openMulticastConnection(streamContext);
* Handles an unpublish event for the application by shutting down
* any associated multicast NetStream.
* @param client - The unpublishing client.
* @param stream - The source stream being unpublished.
application.onUnpublish = function(client, stream)
trace("Handling unpublish request for source stream: " + stream.name);
var streamContext = getStreamContextForSourceStream(stream.name);
if (streamContext && (streamContext.state <= STATE_REPUBLISHING))
destroyStreamContext(streamContext);
// Callback functions for NetConnection and multicast NetStream/NetGroup wiring.
* First step in setting up a republished multicast NetStream; open the loopback
* connection it requires.
* @param streamContext - The StreamContext Object for the publish event.
function openMulticastConnection(streamContext)
var nc = new NetConnection();
nc.onStatus = netConnectionStatusHandler;
streamContext.netConnection = nc;
updateStreamContextLookups(streamContext);
streamContext.state = STATE_CONNECTING;
nc.connect(resetUriProtocol(streamContext.client.uri, "rtmfp"));
* Status event handler for the loopback NetConnection used by the multicast
* NetStream. Advances setup upon successful connection, or triggers or advances
* tear-down as a result of connection loss or an unpublish and clean shutdown.
* @param info - The status info Object.
function netConnectionStatusHandler(info)
var streamContext = getStreamContextForNetConnection(this);
trace("Multicast NetConnection Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."));
if (streamContext)
switch (info.code)
case "NetConnection.Connect.Success":
streamContext.state = STATE_CONNECTED;
// If event type is Fusion or P2p, wire up a NetGroup for neighbor
// bootstrapping and maintenance ahead of (re)publishing the stream.
var type = streamContext.type;
if (type == TYPE_FUSION || type == TYPE_P2P)
initNetGroup(streamContext);
else
initMulticastNetStream(streamContext);
break;
case "NetConnection.Connect.Failed":
case "NetConnection.Connect.Rejected":
case "NetConnection.Connect.AppShutdown":
trace("MULTICAST PUBLISH ERROR: Failed to establish server-side NetConnection for use by multicast NetStream. " +
"Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
streamContext.streamName);
streamContext.state = STATE_DISCONNECTED;
destroyStreamContext(streamContext);
break;
case "NetConnection.Connect.Closed":
if (streamContext.state < STATE_DISCONNECTING)
trace("MULTICAST PUBLISH ERROR: Unexpected server-side NetConnection close. " +
"Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
streamContext.streamName);
streamContext.state = STATE_DISCONNECTED;
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* Initializes the multicast NetGroup following a successful connection of its
* underlying loopback NetConnection. This hook is optional and only runs for
* event types of Fusion and pure P2P.
* @param streamContext - The StreamContext Object for the multicast publish.
function initNetGroup(streamContext)
var ng = null;
try
ng = new NetGroup(streamContext.netConnection, streamContext.groupspec);
catch (e)
trace("MULTICAST PUBLISH ERROR: Failed to construct NetGroup. Error: "
+ e.name + (e.message ? " " + e.message : "") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
ng.onStatus = netGroupStatusHandler;
streamContext.netGroup = ng;
updateStreamContextLookups(streamContext);
* Status event handler for the multicast NetGroup. Advances to initializing the
* multicast NetStream upon successful NetGroup connect. Otherwise, triggers
* shut down.
* @param info - The status info Object.
function netGroupStatusHandler(info)
var streamContext = getStreamContextForNetGroup(this);
trace("Multicast NetGroup Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
if (streamContext)
switch (info.code)
case "NetGroup.Connect.Success":
initMulticastNetStream(streamContext);
break;
case "NetGroup.Connect.Failed":
case "NetGroup.Connect.Rejected":
trace("MULTICAST PUBLISH ERROR: Failed to connect multicast NetGroup. " +
"Status code: " + info.code + ", description: " + info.description +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
break;
case "NetGroup.MulticastStream.UnpublishNotify":
// At this point, multicast publishers will be notified;
// continue shut down.
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* Initializes the multicast NetStream following a successful connection of its
* underlying loopback NetConnection.
* @param streamContext - The StreamContext Object for the multicast publish.
function initMulticastNetStream(streamContext)
var ns = null;
try
ns = new NetStream(streamContext.netConnection, streamContext.groupspec);
catch (e)
trace("MULTICAST PUBLISH ERROR: Failed to construct multicast NetStream. Error: " +
e.name + (e.message ? " " + e.message : "") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
var type = streamContext.type;
if (type == TYPE_FUSION || type == TYPE_IP)
var iAddr = (streamContext.interfaceAddress) ? streamContext.interfaceAddress : null;
try
trace("Multicast NetStream will publish to IP address: " + streamContext.address +
" on interface address: " + ((iAddr) ? iAddr : "default") +
", Source stream: " + streamContext.streamName);
ns.setIPMulticastPublishAddress(streamContext.address, iAddr);
catch (e2)
trace("MULTICAST PUBLISH ERROR: Failed to assign IP multicast address and port for publishing. Address: "
+ streamContext.address + " on interface address: " + ((iAddr) ? iAddr : "default") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
ns.onStatus = netStreamStatusHandler;
streamContext.mcastNetStream = ns;
updateStreamContextLookups(streamContext);
streamContext.state = STATE_PUBLISH_PENDING;
* Status event handler for the multicast NetStream. Advances state upon successful
* connect and publish, or upon successful unpublish. Triggers tear-down if we fail
* to attach to a source Stream to republish.
* @param info - The status info Object.
function netStreamStatusHandler(info)
var streamContext = getStreamContextForMulticastNetStream(this);
trace("Multicast NetStream Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
if (streamContext)
switch (info.code)
case "NetStream.Connect.Success":
if (!this.attach(Stream.get(streamContext.streamName)))
trace("MULTICAST PUBLISH ERROR: Failed to attach multicast NetStream to source. Source stream: " +
streamContext.streamName);
destroyStreamContext(streamContext);
//var stream;
//stream = Stream.get("liveStream");
//return;
}else{
this.publish(streamContext.streamName, "live");
break;
case "NetStream.Publish.Start":
streamContext.state = STATE_REPUBLISHING;
break;
case "NetStream.Unpublish.Success":
streamContext.state = STATE_UNPUBLISHED;
// Wait for unpublish notify event if the context has a NetGroup;
// otherwise continue shut down now.
if (!streamContext.netGroup)
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* The common tear-down hook. Other functions that manage or shut down
* the StreamContext Object delegate to this function upon detecting a fatal
* error or during shut down.
* @param streamContext - The StreamContext Object for the source Stream and
* (potentially wired-up) multicast NetStream.
function destroyStreamContext(streamContext)
// Unregister by Stream name immediately; lookups by NetConnection, NetGroup
// and multicast NetStream remain in place until tear-down is complete.
delete application.streamTable[streamContext.streamName];
switch (streamContext.state)
case STATE_REPUBLISHING:
streamContext.mcastNetStream.attach(false);
streamContext.mcastNetStream.publish(false);
streamContext.state = STATE_UNPUBLISHING;
return;
case STATE_CONNECTING:
case STATE_CONNECTED:
case STATE_PUBLISH_PENDING:
case STATE_UNPUBLISHED:
// Delete status handler callbacks and cleanup in case we arrived here
// as a result of a force close.
if (streamContext.netGroup)
delete streamContext.netGroup.onStatus;
if (streamContext.mcastNetStream)
streamContext.mcastNetStream.attach(false);
delete streamContext.mcastNetStream.onStatus;
streamContext.netConnection.close();
streamContext.state = STATE_DISCONNECTING;
return;
default:
// Fall-through.
// At this point, we either never got to the republishing state or we've
// proceeded through the clean shut down steps above. Everything for this
// StreamContext can go away.
unregisterStreamContext(streamContext);
* Utility function used to force close a StreamContext in the event that we
* start handling a republish of a Source stream before the context for its
* prior incarnation has been torn down.
* @param streamContext - The StreamContext Object for the source Stream.
function forceCloseStreamContext(streamContext)
trace("Force closing previous multicast context for source stream: " + stream.name);
prevContext.state = STATE_UNPUBLISHED;
destroyStreamContext(prevContext);
// Client callback functions
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onPublish.
* @param streamName - The name of the stream being published.
Client.prototype.FCPublish = function(streamName)
this.call("onFCPublish",
null,
{code:"NetStream.Publish.Start", description:streamName});
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onUnpublish.
* @param streamName - The name of the stream being unpublished.
Client.prototype.FCUnpublish = function(streamName)
this.call("onFCUnpublish",
null,
{code:"NetStream.Unpublish.Success", description:streamName});
* If the client invoker's ip matches what was captured for a currently publishing
* stream, assume it's the same client and reset the stream. Otherwise, ignore.
* @param streamName - The name of the stream being released.
Client.prototype.releaseStream = function(streamName)
var streamContext = getStreamContextForSourceStream(streamName);
if (streamContext &&
(streamContext.client.ip == this.ip) &&
(streamContext.state <= STATE_REPUBLISHING))
// Only tear-down an orphaned stream if it's not
// already shutting down (see state check above).
destroyStreamContext(streamContext);
// Helper functions
* Validates that a newly published stream has correct metadata (e.g. query
* string parameters) to republish into a Flash Group. This function also
* writes a message to the application log for any validation failures.
* @param params - The quiery string parameters for the source Stream.
* @return true if valid; otherwise false.
function validateStreamParams(params)
var empty = true;
for (var param in params)
empty = false;
break;
if (empty)
trace("MULTICAST PUBLISH ERROR: Stream query string is empty.");
return false;
if (!params["fms.multicast.type"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.type'.");
return false;
var type = params["fms.multicast.type"];
if (type != 1 && type != 2 && type != 3)
trace("MULTICAST PUBLISH ERROR: 'fms.multicast.type' has invalid value: " + type);
return false;
if (!params["fms.multicast.groupspec"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.groupspec'.");
return false;
// Fusion and IP require an address:port.
if ((type == 1 || type == 2) &&
!params["fms.multicast.address"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.address'.");
return false;
// No obvious validation issues.
return true;
* Parses the supplied query string, and if valid, returns an Object populated
* with the name-value pairs contained in the query string. The simple processing
* here does not preserve multiple name-value pairings having the same name; the
* last value seen wins. Parameters with no value are mapped to "" (empty String)
* in the returned Object.
* @param queryString - A query string portion of a URI, not including the leading
* '?' character.
* @return An Object containing a key-value mapping for each name-value parameter
* defined in the query string; Object is empty if the query string is
* invalid.
function parseQueryString(queryString)
var result = {};
var decoded = "";
try
decoded = decodeURIComponent(queryString);
catch (e) // Invalid URI component; return empty result.
return result;
if (decoded.length)
var params = decoded.split('&');
for (var i in params)
var pair = params[i];
var sepIndex = pair.indexOf('=');
if (sepIndex != -1)
var name = pair.substr(0, sepIndex);
result[name] = pair.substr(sepIndex + 1);
else
result[pair] = "";
return result;
* Utility function used to swap out the protocol (scheme) portion
* of a given URI with an alternate.
* @param uri - The full URI.
* @param desiredProtocol - The replacement protocol.
* @return The URI with its protocol replaced.
function resetUriProtocol(uri, desiredProtocol)
var sepIndex = uri.indexOf("://");
return desiredProtocol + uri.substr(sepIndex);HELP ME !!! THANKS!!!
-
Troubleshoot CRS with 100GE interface
Hi guys,
We have some trouble with 100GE interfaces. Log says it's a far end failure, but anyway I would like to discard this side.
Looking at the output of "show controllers hundredGigE 0/13/0/0 all" I really can't tell everything's Ok.
I would like to understand a few things about this output:
100GBASE-LR4 has 4 lanes, but there are 20 lanes listed in section
"Mapping of Service Interface Lane and RX PCS Lane:"
What does PCS mean?
What might be the root cause of current PCS Lane BIP Error Counters?
Is there anything I would need to check on plim, pse, etc?
Also, any reading material will be appreciated.
Here you have the command output:
show controllers hundredGigE 0/13/0/0 all
Tue Oct 22 16:38:40.597 BsAs
Operational data for interface HundredGigE0/13/0/0:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Phy:
Media type: R fiber over 4 Lane optics (long reach)
Optics:
Vendor: CISCO-FINISAR
Part number: FTLC1181RDNS-C2
Serial number: FIN1636000W
MAC address information:
Operational address: 001d.454d.8412
Burnt-in address: 001d.454d.8412
No unicast addresses in filter
Operating in multicast promiscuous mode
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
MTU: 9200
MRU: 9200
Inter-packet gap: standard (12)
Statistics for interface HundredGigE0/13/0/0 (cached values):
Ingress:
Input total bytes = 1104715
Input good bytes = 1081503
Input total packets = 5803
Input 802.1Q frames = 0
Input pause frames = 0
Input pkts 64 bytes = 6
Input pkts 65-127 bytes = 3377
Input pkts 128-255 bytes = 1706
Input pkts 256-511 bytes = 293
Input pkts 512-1023 bytes = 313
Input pkts 1024-1518 bytes = 108
Input pkts 1519-Max bytes = 0
Input good pkts = 5803
Input unicast pkts = 5790
Input multicast pkts = 10
Input broadcast pkts = 3
Input drop overrun = 0
Input drop abort = 0
Input drop invalid VLAN = 0
Input drop invalid DMAC = 0
Input drop invalid encap = 0
Input drop other = 0
Input error giant = 0
Input error runt = 0
Input error jabbers = 0
Input error fragments = 0
Input error CRC = 0
Input error collisions = 0
Input error symbol = 15579
Input error other = 0
Input MIB giant = 0
Input MIB jabber = 0
Input MIB CRC = 0
Egress:
Output total bytes = 2862870
Output good bytes = 2836906
Output total packets = 6491
Output 802.1Q frames = 0
Output pause frames = 0
Output pkts 64 bytes = 4
Output pkts 65-127 bytes = 3587
Output pkts 128-255 bytes = 1186
Output pkts 256-511 bytes = 244
Output pkts 512-1023 bytes = 16
Output pkts 1024-1518 bytes = 1454
Output pkts 1519-Max bytes = 0
Output good pkts = 6491
Output unicast pkts = 6455
Output multicast pkts = 35
Output broadcast pkts = 1
Output drop underrun = 0
Output drop abort = 0
Output drop other = 0
Output error other = 0
Management information for interface HundredGigE0/13/0/0:
Port number: 0
Bay number: 0
Interface handle: 0x1d80100
Config:
Auto-negotiation: Configuration not supported (Off)
Carrier delay (up): Not configured
Carrier delay (down): Not configured
Speed: Configuration not supported (100Gbps)
Duplex: Configuration not supported (Full Duplex)
Flow Control: Not configured (None)
IPG: Configuration not supported (standard (12))
Loopback: Not configured (None)
MTU: 9192 bytes
Bandwidth: Not configured
BER-SD Threshold: Configuration not supported
BER-SD Report: Configuration not supported
BER-SF Threshold: Configuration not supported
BER-SF Report: Configuration not supported
BER-SF Signal Remote Failure: Configuration not supported
Driver constraints:
Min MTU: 64 bytes
Max MTU: 9600 bytes
Max speed: 100Gbps
Interface type: HundredGigE
Management interface: No
Promiscuous mode: Yes
Default carrier delay up (auto-neg on): 0 ms
Default carrier delay down (auto-neg on): 0 ms
Default carrier delay up (auto-neg off): 0 ms
Default carrier delay down (auto-neg off): 0 ms
Allowed config mask: 0x26b
Cached driver state:
MTU: 9200 bytes
Burnt-in MAC address: 001d.454d.8412
Operational carrier delay:
Carrier delay (up): 0 ms
Carrier delay (down): 0 ms
Not a member of a bundle interface.
Satellite uplink settings:
Not in satellite uplink (ICL) mode.
Port FSM state:
Port is enabled, link is up
Complete FSM state:
Admin up
Client admin up
Client admin tx not disabled
Port enabled
Port tx enabled
Hardware link up
IDB interface state information:
IDB client admin up
IDB client tx admin up
IDB error disable not set
0 Unicast MAC Addresses:
0 Multicast MAC Addresses:
Operational address: 001d.454d.8412
Burnt-in address: 001d.454d.8412
MAC state for beluga 0 port 0
MAC state for barbur 0 and port 0
0 HSRP/VRRP MAC addresses
VLAN Ethertype: 0x8100
QinQ Ethertype: 0x88a8
MTP Ethertype: 0x88e7
4 VLAN UIDB entries
VLAN1 VLAN2 Packet Type Flags UIDB Result Flags
0 0 VLAN 1 VLAN
0 0 ARPA 1 ARPA
0 0 SAP 1 SAP
0 0 1 SNAP
PLIM 1 Port HundredGigE Internal Information:
shmwin pointer: 0x581d4268
shmwin id : 0x3c
shmwin initlization: complete
shmwin mac stats pointer: 0x60106020
shmwin mac stats version: 0x1
shmwin ctx pointer: 0x6010e07c
shmwin ctx version: 0x1
HW initilization: completed
Maximum CFP power class supported: 4
Maximum CFP power consumption supported: 30000 mW
802.3ba PCS
Previous PCS Alarms:
None
Current PCS Status:
PCS is able to support 100GBASE-R
PCS is Block Locked
PCS Rx Link Status is UP
PCS Errored Block Counts: 25
PCS BER (Sync Header Error) Counts: 1
PCS detailed information:
RX Service Interface Lane Sync Header Lock Status:
Lane-0 : Locked Lane-10 : Locked
Lane-1 : Locked Lane-11 : Locked
Lane-2 : Locked Lane-12 : Locked
Lane-3 : Locked Lane-13 : Locked
Lane-4 : Locked Lane-14 : Locked
Lane-5 : Locked Lane-15 : Locked
Lane-6 : Locked Lane-16 : Locked
Lane-7 : Locked Lane-17 : Locked
Lane-8 : Locked Lane-18 : Locked
Lane-9 : Locked Lane-19 : Locked
RX Service Interface Lane Marker Lock Status:
Lane-0 : Locked Lane-10 : Locked
Lane-1 : Locked Lane-11 : Locked
Lane-2 : Locked Lane-12 : Locked
Lane-3 : Locked Lane-13 : Locked
Lane-4 : Locked Lane-14 : Locked
Lane-5 : Locked Lane-15 : Locked
Lane-6 : Locked Lane-16 : Locked
Lane-7 : Locked Lane-17 : Locked
Lane-8 : Locked Lane-18 : Locked
Lane-9 : Locked Lane-19 : Locked
Mapping of Service Interface Lane and RX PCS Lane:
Rx Service Interface Lane 0 = PCS Lane 13
Rx Service Interface Lane 1 = PCS Lane 11
Rx Service Interface Lane 2 = PCS Lane 14
Rx Service Interface Lane 3 = PCS Lane 15
Rx Service Interface Lane 4 = PCS Lane 17
Rx Service Interface Lane 5 = PCS Lane 12
Rx Service Interface Lane 6 = PCS Lane 10
Rx Service Interface Lane 7 = PCS Lane 9
Rx Service Interface Lane 8 = PCS Lane 16
Rx Service Interface Lane 9 = PCS Lane 8
Rx Service Interface Lane 10 = PCS Lane 7
Rx Service Interface Lane 11 = PCS Lane 4
Rx Service Interface Lane 12 = PCS Lane 3
Rx Service Interface Lane 13 = PCS Lane 5
Rx Service Interface Lane 14 = PCS Lane 6
Rx Service Interface Lane 15 = PCS Lane 19
Rx Service Interface Lane 16 = PCS Lane 2
Rx Service Interface Lane 17 = PCS Lane 18
Rx Service Interface Lane 18 = PCS Lane 0
Rx Service Interface Lane 19 = PCS Lane 1
PCS Lane BIP Error Counters:
Lane-0 : 2071 Lane-10 : 0
Lane-1 : 1415 Lane-11 : 0
Lane-2 : 1530 Lane-12 : 0
Lane-3 : 0 Lane-13 : 0
Lane-4 : 0 Lane-14 : 0
Lane-5 : 0 Lane-15 : 0
Lane-6 : 0 Lane-16 : 0
Lane-7 : 0 Lane-17 : 0
Lane-8 : 0 Lane-18 : 1815
Lane-9 : 0 Lane-19 : 1603
Total PCS Lane BIP Error Count : 8434
Total PCS Lane Sync Header Error Count : 520
Total PCS Lane Bad 64/66 Code Count : 9180
Serdes section:
===============
None of 10 RX serial inputs detects loss of signal.
All of 10 Tx clock multiplication units are locked.
All of 10 Rx clock/data recovery units are locked.
None of 10 TX FIFO has underflow/overflow condition.
None of 10 RX FIFO has underflow/overflow condition.
CFP section:
==============
CFP General Information:
Module Identifier: CFP
Ethernet Application Code: 100GBASE-LR4
Module State: Ready
Power Class: 3
Maximum Power Consumption: 23000 mW
CFP Vendor Information:
Vendor Name: CISCO-FINISAR
Vendor PN: FTLC1181RDNS-C2
Vendor SN: FIN1636000W
Vendor OUI: 0x0-0x90-0x65
Lot Code: 00
DATE CODE(YYYY/MM/DD): 2012/09/05
CFP MSA Hardware Version: 1.4
CFP MSA MDIO Version: 1.4
Vendor Hardware Version: 1.4
Vendor Firmware Version: 1.5
CFP UDI Information:
UDI Compliant: Yes
Cisco PID: CFP-100G-LR4
Cisco VID: V01
CFP Cisco Information:
Vendor Name: CISCO-FINISAR
Cisco PN : 10-2549-01 Rev A0
Cisco SN : FIN1636000W
CFP Detail Information:
Number of lanes supported:
Number of network lanes: 4
Number of host lanes : 10
Time required by module:
Maximum high-power-up time : 4 s
Maximum high-power-down time: 1 s
Maximum tx-turn-on time : 1 s
Maximum tx-turn-off time : 150 ms
Module general control:
Soft reset asserted : No
Soft low power asserted : No
Soft tx disable asserted: No
Soft program control 3 asserted: No
Soft program control 2 asserted: No
Soft program control 1 asserted: No
Soft global alarm test asserted: No
Tx disable pin asserted: No
Low power pin asserted : No
Program control 3 pin asserted: Yes
Program control 2 pin asserted: Yes
Program control 1 pin asserted: Yes
Module Analog A/D value:
Power supply voltage : 3.2549 V
Temperature : 33.2496 degC
Network lane A/D value:
Lane 0 Tx power: 1.1091 mW ( 0.4 dBm)
Lane 1 Tx power: 1.1127 mW ( 0.5 dBm)
Lane 2 Tx power: 1.0976 mW ( 0.4 dBm)
Lane 3 Tx power: 1.1271 mW ( 0.5 dBm)
Lane 0 Rx power: 0.0438 mW (-13.6 dBm)
Lane 1 Rx power: 0.1116 mW ( -9.5 dBm)
Lane 2 Rx power: 0.1022 mW ( -9.9 dBm)
Lane 3 Rx power: 0.0915 mW (-10.4 dBm)
Total Tx power : 4.4465 mW ( 6.5 dBm)
Total Rx power : 0.3491 mW ( -4.6 dBm)
No XGXS present
PCS 802.3ba Registers:
========================
Control 1 = 0x0010
Status 1 = 0x0004
Dev ID 0 = 0x0000 Dev ID 1 = 0x0000
Speed Ability = 0x0008
Devices 1 = 0x0004 Devices 2 = 0x0000
Control 2 = 0x0005
Status 2 = 0x0020
PKG ID 0 = 0x0000 PKG ID 1 = 0x0000
Base R Status 1 = 0x1001
Base R Status 2 = 0x8117
BER high order counter = 0x0000
Errored blocks high order counter = 0x8000
Base R test pattern control = 0x0080
Base R test pattern error counter = 0x0000
Multi-lane BASE-R alignment status 1 = 0x10ff
Multi-lane BASE-R alignment status 2 = 0x0fff
Multi-lane BASE-R alignment status 3 = 0x00ff
Multi-lane BASE-R alignment status 4 = 0x0fff
BIP error counter lane 0 = 0x0002
BIP error counter lane 1 = 0x0002
BIP error counter lane 2 = 0x0004
BIP error counter lane 3 = 0x0000
BIP error counter lane 4 = 0x0000
BIP error counter lane 5 = 0x0000
BIP error counter lane 6 = 0x0000
BIP error counter lane 7 = 0x0000
BIP error counter lane 8 = 0x0000
BIP error counter lane 9 = 0x0000
BIP error counter lane 10 = 0x0000
BIP error counter lane 11 = 0x0000
BIP error counter lane 12 = 0x0000
BIP error counter lane 13 = 0x0000
BIP error counter lane 14 = 0x0000
BIP error counter lane 15 = 0x0000
BIP error counter lane 16 = 0x0000
BIP error counter lane 17 = 0x0000
BIP error counter lane 18 = 0x0007
BIP error counter lane 19 = 0x0005
Lane mapping register 0 = 0x000d
Lane mapping register 1 = 0x000b
Lane mapping register 2 = 0x000e
Lane mapping register 3 = 0x000f
Lane mapping register 4 = 0x0011
Lane mapping register 5 = 0x000c
Lane mapping register 6 = 0x000a
Lane mapping register 7 = 0x0009
Lane mapping register 8 = 0x0010
Lane mapping register 9 = 0x0008
Lane mapping register 10 = 0x0007
Lane mapping register 11 = 0x0004
Lane mapping register 12 = 0x0003
Lane mapping register 13 = 0x0005
Lane mapping register 14 = 0x0006
Lane mapping register 15 = 0x0013
Lane mapping register 16 = 0x0002
Lane mapping register 17 = 0x0012
Lane mapping register 18 = 0x0000
Lane mapping register 19 = 0x0001
Serdes registers:
==================
Chip id register: 0x8154
Chip revision id register: 0x4
Digital control 1 register register:
serdes0:0x017a, serdes1:0x017a, serdes2:0x017a, serdes3:0x017a, serdes4:0x017a
serdes5:0x017a, serdes6:0x017a, serdes7:0x017a, serdes8:0x017a, serdes9:0x017a
Digital control 2 register register:
serdes0:0x0305, serdes1:0x0305, serdes2:0x0305, serdes3:0x0305, serdes4:0x0305
serdes5:0x0305, serdes6:0x0305, serdes7:0x0305, serdes8:0x0305, serdes9:0x0305
Digital control 3 register register:
serdes0:0x0d0f, serdes1:0x0d0f, serdes2:0x0d0f, serdes3:0x0d0f, serdes4:0x0d0f
serdes5:0x0d0f, serdes6:0x0d0f, serdes7:0x0d0f, serdes8:0x0d0f, serdes9:0x0d0f
Digital control 5 register register:
serdes0:0x6de0, serdes1:0x6de0, serdes2:0x6de0, serdes3:0x6de0, serdes4:0x6de0
serdes5:0x6de0, serdes6:0x6de0, serdes7:0x6de0, serdes8:0x6de0, serdes9:0x6de0
Digital status 0 register register:
serdes0:0x303b, serdes1:0x303b, serdes2:0x303b, serdes3:0x303b, serdes4:0x303b
serdes5:0x303b, serdes6:0x303b, serdes7:0x303b, serdes8:0x303b, serdes9:0x303b
Line PRBS control register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
Line PRBS status register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
System PRBS control register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
System PRBS status register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
PRBS status 2 register register:
serdes0:0x8008, serdes1:0x8008, serdes2:0x8008, serdes3:0x8008, serdes4:0x8008
serdes5:0x8008, serdes6:0x8008, serdes7:0x8008, serdes8:0x8008, serdes9:0x8008
TX control 1 register register:
serdes0:0x1884, serdes1:0x1884, serdes2:0x1884, serdes3:0x1884, serdes4:0x1884
serdes5:0x1884, serdes6:0x1884, serdes7:0x1884, serdes8:0x1884, serdes9:0x1884
TX control 2 register register:
serdes0:0x00a0, serdes1:0x00a0, serdes2:0x00a0, serdes3:0x00a0, serdes4:0x00a0
serdes5:0x00a0, serdes6:0x00a0, serdes7:0x00a0, serdes8:0x00a0, serdes9:0x00a0
TX control 4 register register:
serdes0:0x3012, serdes1:0x2812, serdes2:0x3012, serdes3:0x3012, serdes4:0x2c12
serdes5:0x2812, serdes6:0x2c12, serdes7:0x2c12, serdes8:0x2c12, serdes9:0x2812
TX control 7 register register:
serdes0:0x1077, serdes1:0x1077, serdes2:0x1077, serdes3:0x1077, serdes4:0x1077
serdes5:0x1077, serdes6:0x1077, serdes7:0x1077, serdes8:0x1077, serdes9:0x1077
TX control 8 register register:
serdes0:0xb800, serdes1:0xb800, serdes2:0xb800, serdes3:0xb800, serdes4:0xb800
serdes5:0xb800, serdes6:0xb800, serdes7:0xb800, serdes8:0xb800, serdes9:0xb800
TX LVDS contrl 1 register register:
serdes0:0x6050, serdes1:0x6050, serdes2:0x6050, serdes3:0x6050, serdes4:0x6050
serdes5:0x6050, serdes6:0x6050, serdes7:0x6050, serdes8:0x6050, serdes9:0x6050
TX LVDS contrl 2 register register:
serdes0:0x3ba1, serdes1:0x3ba9, serdes2:0x3ba9, serdes3:0x3ba1, serdes4:0x3ba1
serdes5:0x3ba9, serdes6:0x3ba9, serdes7:0x3ba9, serdes8:0x3ba9, serdes9:0x3ba9
TX LVDS contrl 3 register register:
serdes0:0x3ba1, serdes1:0x3ba9, serdes2:0x3ba9, serdes3:0x3ba1, serdes4:0x3ba1
serdes5:0x3ba9, serdes6:0x3ba9, serdes7:0x3ba9, serdes8:0x3ba9, serdes9:0x3ba9
RX control 2 register register:
serdes0:0x222c, serdes1:0x2224, serdes2:0x222c, serdes3:0x222c, serdes4:0x222c
serdes5:0x2228, serdes6:0x2228, serdes7:0x2228, serdes8:0x2228, serdes9:0x2228
RX control 3 register register:
serdes0:0x1611, serdes1:0x1611, serdes2:0x1611, serdes3:0x1611, serdes4:0x1611
serdes5:0x1611, serdes6:0x1611, serdes7:0x1611, serdes8:0x1611, serdes9:0x1611
RX control 4 register register:
serdes0:0x40c9, serdes1:0x50c9, serdes2:0x50c9, serdes3:0x40c9, serdes4:0x40c9
serdes5:0x50c9, serdes6:0x50c9, serdes7:0x50c9, serdes8:0x50c9, serdes9:0x50c9
RX control 6 register register:
serdes0:0x081a, serdes1:0x081a, serdes2:0x081a, serdes3:0x081a, serdes4:0x081a
serdes5:0x081a, serdes6:0x081a, serdes7:0x081a, serdes8:0x081a, serdes9:0x081a
RX control 7 register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
RX control 8 register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
RX control 9 register register:
serdes0:0x0000, serdes1:0x0000, serdes2:0x0000, serdes3:0x0000, serdes4:0x0000
serdes5:0x0000, serdes6:0x0000, serdes7:0x0000, serdes8:0x0000, serdes9:0x0000
RX LVDS contrl 1 register register:
serdes0:0x0bfa, serdes1:0x0bba, serdes2:0x0bba, serdes3:0x0bba, serdes4:0x0bba
serdes5:0x0bba, serdes6:0x0bba, serdes7:0x0bba, serdes8:0x0bba, serdes9:0x0bba
CFP Registers:
================
NVR 1 Registers:
(Reg 0x8000=0x0e) (Reg 0x8001=0x95) (Reg 0x8002=0x01) (Reg 0x8003=0x01)
(Reg 0x8004=0x00) (Reg 0x8005=0x00) (Reg 0x8006=0x00) (Reg 0x8007=0x00)
(Reg 0x8008=0x08) (Reg 0x8009=0x4a) (Reg 0x800a=0x11) (Reg 0x800b=0x81)
(Reg 0x800c=0x34) (Reg 0x800d=0x0a) (Reg 0x800e=0x00) (Reg 0x800f=0x00)
(Reg 0x8010=0x01) (Reg 0x8011=0x04) (Reg 0x8012=0xca) (Reg 0x8013=0x45)
(Reg 0x8014=0xcc) (Reg 0x8015=0xb8) (Reg 0x8016=0x08) (Reg 0x8017=0x34)
(Reg 0x8018=0x21) (Reg 0x8019=0x44) (Reg 0x801a=0x40) (Reg 0x801b=0x70)
(Reg 0x801c=0x1c) (Reg 0x801d=0x73) (Reg 0x801e=0x64) (Reg 0x801f=0x46)
(Reg 0x8020=0x00) (Reg 0x8021=0x43) (Reg 0x8022=0x49) (Reg 0x8023=0x53)
(Reg 0x8024=0x43) (Reg 0x8025=0x4f) (Reg 0x8026=0x2d) (Reg 0x8027=0x46)
(Reg 0x8028=0x49) (Reg 0x8029=0x4e) (Reg 0x802a=0x49) (Reg 0x802b=0x53)
(Reg 0x802c=0x41) (Reg 0x802d=0x52) (Reg 0x802e=0x20) (Reg 0x802f=0x20)
(Reg 0x8030=0x20) (Reg 0x8031=0x00) (Reg 0x8032=0x90) (Reg 0x8033=0x65)
(Reg 0x8034=0x46) (Reg 0x8035=0x54) (Reg 0x8036=0x4c) (Reg 0x8037=0x43)
(Reg 0x8038=0x31) (Reg 0x8039=0x31) (Reg 0x803a=0x38) (Reg 0x803b=0x31)
(Reg 0x803c=0x52) (Reg 0x803d=0x44) (Reg 0x803e=0x4e) (Reg 0x803f=0x53)
(Reg 0x8040=0x2d) (Reg 0x8041=0x43) (Reg 0x8042=0x32) (Reg 0x8043=0x20)
(Reg 0x8044=0x46) (Reg 0x8045=0x49) (Reg 0x8046=0x4e) (Reg 0x8047=0x31)
(Reg 0x8048=0x36) (Reg 0x8049=0x33) (Reg 0x804a=0x36) (Reg 0x804b=0x30)
(Reg 0x804c=0x30) (Reg 0x804d=0x30) (Reg 0x804e=0x57) (Reg 0x804f=0x20)
(Reg 0x8050=0x20) (Reg 0x8051=0x20) (Reg 0x8052=0x20) (Reg 0x8053=0x20)
(Reg 0x8054=0x32) (Reg 0x8055=0x30) (Reg 0x8056=0x31) (Reg 0x8057=0x32)
(Reg 0x8058=0x30) (Reg 0x8059=0x39) (Reg 0x805a=0x30) (Reg 0x805b=0x35)
(Reg 0x805c=0x30) (Reg 0x805d=0x30) (Reg 0x805e=0x49) (Reg 0x805f=0x50)
(Reg 0x8060=0x55) (Reg 0x8061=0x49) (Reg 0x8062=0x42) (Reg 0x8063=0x48)
(Reg 0x8064=0x43) (Reg 0x8065=0x52) (Reg 0x8066=0x41) (Reg 0x8067=0x41)
(Reg 0x8068=0x0e) (Reg 0x8069=0x0e) (Reg 0x806a=0x01) (Reg 0x806b=0x04)
(Reg 0x806c=0x01) (Reg 0x806d=0x05) (Reg 0x806e=0x0c) (Reg 0x806f=0x03)
(Reg 0x8070=0x0f) (Reg 0x8071=0x68) (Reg 0x8072=0x04) (Reg 0x8073=0x01)
(Reg 0x8074=0x01) (Reg 0x8075=0x00) (Reg 0x8076=0x96) (Reg 0x8077=0x01)
(Reg 0x8078=0x07) (Reg 0x8079=0x01) (Reg 0x807a=0xf1) (Reg 0x807b=0x00)
(Reg 0x807c=0x00) (Reg 0x807d=0x00) (Reg 0x807e=0x00) (Reg 0x807f=0x17)
NVR 2 Registers:
(Reg 0x8080=0x4a) (Reg 0x8081=0x00) (Reg 0x8082=0x46) (Reg 0x8083=0x00)
(Reg 0x8084=0x00) (Reg 0x8085=0x00) (Reg 0x8086=0xfc) (Reg 0x8087=0x00)
(Reg 0x8088=0x8f) (Reg 0x8089=0x2a) (Reg 0x808a=0x87) (Reg 0x808b=0x5a)
(Reg 0x808c=0x7a) (Reg 0x808d=0x76) (Reg 0x808e=0x72) (Reg 0x808f=0xa6)
(Reg 0x8090=0x00) (Reg 0x8091=0x00) (Reg 0x8092=0x00) (Reg 0x8093=0x00)
(Reg 0x8094=0x00) (Reg 0x8095=0x00) (Reg 0x8096=0x00) (Reg 0x8097=0x00)
(Reg 0x8098=0x00) (Reg 0x8099=0x00) (Reg 0x809a=0x00) (Reg 0x809b=0x00)
(Reg 0x809c=0x00) (Reg 0x809d=0x00) (Reg 0x809e=0x00) (Reg 0x809f=0x00)
(Reg 0x80a0=0x00) (Reg 0x80a1=0x00) (Reg 0x80a2=0x00) (Reg 0x80a3=0x00)
(Reg 0x80a4=0x00) (Reg 0x80a5=0x00) (Reg 0x80a6=0x00) (Reg 0x80a7=0x00)
(Reg 0x80a8=0xea) (Reg 0x80a9=0x60) (Reg 0x80aa=0xe0) (Reg 0x80ab=0x9c)
(Reg 0x80ac=0x44) (Reg 0x80ad=0x5c) (Reg 0x80ae=0x3a) (Reg 0x80af=0x98)
(Reg 0x80b0=0xdb) (Reg 0x80b1=0xaa) (Reg 0x80b2=0x6e) (Reg 0x80b3=0x18)
(Reg 0x80b4=0x0e) (Reg 0x80b5=0x83) (Reg 0x80b6=0x05) (Reg 0x80b7=0xc7)
(Reg 0x80b8=0x39) (Reg 0x80b9=0x00) (Reg 0x80ba=0x37) (Reg 0x80bb=0x00)
(Reg 0x80bc=0x1b) (Reg 0x80bd=0x00) (Reg 0x80be=0x19) (Reg 0x80bf=0x00)
(Reg 0x80c0=0xdb) (Reg 0x80c1=0xaa) (Reg 0x80c2=0x6e) (Reg 0x80c3=0x18)
(Reg 0x80c4=0x03) (Reg 0x80c5=0x67) (Reg 0x80c6=0x01) (Reg 0x80c7=0x5b)
(Reg 0x80c8=0x00) (Reg 0x80c9=0x00) (Reg 0x80ca=0x00) (Reg 0x80cb=0x00)
(Reg 0x80cc=0x00) (Reg 0x80cd=0x00) (Reg 0x80ce=0x00) (Reg 0x80cf=0x00)
(Reg 0x80d0=0x00) (Reg 0x80d1=0x00) (Reg 0x80d2=0x00) (Reg 0x80d3=0x00)
(Reg 0x80d4=0x00) (Reg 0x80d5=0x00) (Reg 0x80d6=0x00) (Reg 0x80d7=0x00)
(Reg 0x80d8=0x00) (Reg 0x80d9=0x00) (Reg 0x80da=0x00) (Reg 0x80db=0x00)
(Reg 0x80dc=0x00) (Reg 0x80dd=0x00) (Reg 0x80de=0x00) (Reg 0x80df=0x00)
(Reg 0x80e0=0x00) (Reg 0x80e1=0x00) (Reg 0x80e2=0x00) (Reg 0x80e3=0x00)
(Reg 0x80e4=0x00) (Reg 0x80e5=0x00) (Reg 0x80e6=0x00) (Reg 0x80e7=0x00)
(Reg 0x80e8=0x00) (Reg 0x80e9=0x00) (Reg 0x80ea=0x00) (Reg 0x80eb=0x00)
(Reg 0x80ec=0x00) (Reg 0x80ed=0x00) (Reg 0x80ee=0x00) (Reg 0x80ef=0x00)
(Reg 0x80f0=0x00) (Reg 0x80f1=0x00) (Reg 0x80f2=0x00) (Reg 0x80f3=0x00)
(Reg 0x80f4=0x00) (Reg 0x80f5=0x00) (Reg 0x80f6=0x00) (Reg 0x80f7=0x00)
(Reg 0x80f8=0x00) (Reg 0x80f9=0x00) (Reg 0x80fa=0x00) (Reg 0x80fb=0x00)
(Reg 0x80fc=0x00) (Reg 0x80fd=0x00) (Reg 0x80fe=0x00) (Reg 0x80ff=0x43)
NVR 3 Registers:
(Reg 0x8100=0x00) (Reg 0x8101=0x00) (Reg 0x8102=0x00) (Reg 0x8103=0x00)
(Reg 0x8104=0x00) (Reg 0x8105=0x00) (Reg 0x8106=0x00) (Reg 0x8107=0x00)
(Reg 0x8108=0x00) (Reg 0x8109=0x00) (Reg 0x810a=0x00) (Reg 0x810b=0x00)
(Reg 0x810c=0x00) (Reg 0x810d=0x00) (Reg 0x810e=0x00) (Reg 0x810f=0x00)
(Reg 0x8110=0x00) (Reg 0x8111=0x00) (Reg 0x8112=0x00) (Reg 0x8113=0x00)
(Reg 0x8114=0x00) (Reg 0x8115=0x00) (Reg 0x8116=0x00) (Reg 0x8117=0x00)
(Reg 0x8118=0x00) (Reg 0x8119=0x00) (Reg 0x811a=0x00) (Reg 0x811b=0x00)
(Reg 0x811c=0x00) (Reg 0x811d=0x00) (Reg 0x811e=0x00) (Reg 0x811f=0x00)
(Reg 0x8120=0x00) (Reg 0x8121=0x00) (Reg 0x8122=0x00) (Reg 0x8123=0x00)
(Reg 0x8124=0x00) (Reg 0x8125=0x00) (Reg 0x8126=0x00) (Reg 0x8127=0x00)
(Reg 0x8128=0x00) (Reg 0x8129=0x00) (Reg 0x812a=0x00) (Reg 0x812b=0x00)
(Reg 0x812c=0x00) (Reg 0x812d=0x00) (Reg 0x812e=0x00) (Reg 0x812f=0x00)
(Reg 0x8130=0x00) (Reg 0x8131=0x00) (Reg 0x8132=0x00) (Reg 0x8133=0x00)
(Reg 0x8134=0x00) (Reg 0x8135=0x00) (Reg 0x8136=0x00) (Reg 0x8137=0x00)
(Reg 0x8138=0x00) (Reg 0x8139=0x00) (Reg 0x813a=0x00) (Reg 0x813b=0x00)
(Reg 0x813c=0x00) (Reg 0x813d=0x00) (Reg 0x813e=0x00) (Reg 0x813f=0x00)
(Reg 0x8140=0x00) (Reg 0x8141=0x00) (Reg 0x8142=0x00) (Reg 0x8143=0x00)
(Reg 0x8144=0x00) (Reg 0x8145=0x00) (Reg 0x8146=0x00) (Reg 0x8147=0x00)
(Reg 0x8148=0x00) (Reg 0x8149=0x00) (Reg 0x814a=0x00) (Reg 0x814b=0x00)
(Reg 0x814c=0x00) (Reg 0x814d=0x00) (Reg 0x814e=0x00) (Reg 0x814f=0x00)
(Reg 0x8150=0x00) (Reg 0x8151=0x00) (Reg 0x8152=0x00) (Reg 0x8153=0x00)
(Reg 0x8154=0x00) (Reg 0x8155=0x00) (Reg 0x8156=0x00) (Reg 0x8157=0x00)
(Reg 0x8158=0x00) (Reg 0x8159=0x00) (Reg 0x815a=0x00) (Reg 0x815b=0x00)
(Reg 0x815c=0x00) (Reg 0x815d=0x00) (Reg 0x815e=0x00) (Reg 0x815f=0x00)
(Reg 0x8160=0x00) (Reg 0x8161=0x00) (Reg 0x8162=0x00) (Reg 0x8163=0x00)
(Reg 0x8164=0x00) (Reg 0x8165=0x00) (Reg 0x8166=0x00) (Reg 0x8167=0x00)
(Reg 0x8168=0x00) (Reg 0x8169=0x00) (Reg 0x816a=0x00) (Reg 0x816b=0x00)
(Reg 0x816c=0x00) (Reg 0x816d=0x00) (Reg 0x816e=0x00) (Reg 0x816f=0x00)
(Reg 0x8170=0x00) (Reg 0x8171=0x00) (Reg 0x8172=0x00) (Reg 0x8173=0x00)
(Reg 0x8174=0x00) (Reg 0x8175=0x00) (Reg 0x8176=0x00) (Reg 0x8177=0x00)
(Reg 0x8178=0x00) (Reg 0x8179=0x00) (Reg 0x817a=0x00) (Reg 0x817b=0x00)
(Reg 0x817c=0x00) (Reg 0x817d=0x00) (Reg 0x817e=0x00) (Reg 0x817f=0x00)
NVR 4 Registers:
(Reg 0x8180=0x00)
Vendor NVR1 Registers
(Reg 0x8400=0x00) (Reg 0x8401=0x00) (Reg 0x8402=0x00) (Reg 0x8403=0x00)
(Reg 0x8404=0x00) (Reg 0x8405=0x00) (Reg 0x8406=0x00) (Reg 0x8407=0x00)
(Reg 0x8408=0x00) (Reg 0x8409=0x00) (Reg 0x840a=0x00) (Reg 0x840b=0x00)
(Reg 0x840c=0x00) (Reg 0x840d=0x00) (Reg 0x840e=0x00) (Reg 0x840f=0x00)
(Reg 0x8410=0x43) (Reg 0x8411=0x49) (Reg 0x8412=0x53) (Reg 0x8413=0x43)
(Reg 0x8414=0x4f) (Reg 0x8415=0x2d) (Reg 0x8416=0x46) (Reg 0x8417=0x49)
(Reg 0x8418=0x4e) (Reg 0x8419=0x49) (Reg 0x841a=0x53) (Reg 0x841b=0x41)
(Reg 0x841c=0x52) (Reg 0x841d=0x20) (Reg 0x841e=0x20) (Reg 0x841f=0x20)
(Reg 0x8420=0x43) (Reg 0x8421=0x46) (Reg 0x8422=0x50) (Reg 0x8423=0x2d)
(Reg 0x8424=0x31) (Reg 0x8425=0x30) (Reg 0x8426=0x30) (Reg 0x8427=0x47)
(Reg 0x8428=0x2d) (Reg 0x8429=0x4c) (Reg 0x842a=0x52) (Reg 0x842b=0x34)
(Reg 0x842c=0x20) (Reg 0x842d=0x20) (Reg 0x842e=0x20) (Reg 0x842f=0x20)
(Reg 0x8430=0x56) (Reg 0x8431=0x30) (Reg 0x8432=0x31) (Reg 0x8433=0x20)
(Reg 0x8434=0x07) (Reg 0x8435=0x46) (Reg 0x8436=0x49) (Reg 0x8437=0x4e)
(Reg 0x8438=0x31) (Reg 0x8439=0x36) (Reg 0x843a=0x33) (Reg 0x843b=0x36)
(Reg 0x843c=0x30) (Reg 0x843d=0x30) (Reg 0x843e=0x30) (Reg 0x843f=0x57)
(Reg 0x8440=0x31) (Reg 0x8441=0x30) (Reg 0x8442=0x2d) (Reg 0x8443=0x32)
(Reg 0x8444=0x35) (Reg 0x8445=0x34) (Reg 0x8446=0x39) (Reg 0x8447=0x2d)
(Reg 0x8448=0x30) (Reg 0x8449=0x31) (Reg 0x844a=0x20) (Reg 0x844b=0x20)
(Reg 0x844c=0x41) (Reg 0x844d=0x30) (Reg 0x844e=0x20) (Reg 0x844f=0x20)
(Reg 0x8450=0x00) (Reg 0x8451=0x00) (Reg 0x8452=0x00) (Reg 0x8453=0x00)
(Reg 0x8454=0x00) (Reg 0x8455=0x00) (Reg 0x8456=0x00) (Reg 0x8457=0x00)
(Reg 0x8458=0x00) (Reg 0x8459=0x00) (Reg 0x845a=0x00) (Reg 0x845b=0x00)
(Reg 0x845c=0x00) (Reg 0x845d=0x00) (Reg 0x845e=0x00) (Reg 0x845f=0x00)
(Reg 0x8460=0x00) (Reg 0x8461=0x00) (Reg 0x8462=0x00) (Reg 0x8463=0x00)
(Reg 0x8464=0x00) (Reg 0x8465=0x00) (Reg 0x8466=0x00) (Reg 0x8467=0x00)
(Reg 0x8468=0x00) (Reg 0x8469=0x00) (Reg 0x846a=0x00) (Reg 0x846b=0x00)
(Reg 0x846c=0x00) (Reg 0x846d=0x00) (Reg 0x846e=0x00) (Reg 0x846f=0x00)
(Reg 0x8470=0x00) (Reg 0x8471=0x00) (Reg 0x8472=0x00) (Reg 0x8473=0x00)
(Reg 0x8474=0x00) (Reg 0x8475=0x00) (Reg 0x8476=0x00) (Reg 0x8477=0x00)
(Reg 0x8478=0x00) (Reg 0x8479=0x00) (Reg 0x847a=0x00) (Reg 0x847b=0x00)
(Reg 0x847c=0x00) (Reg 0x847d=0x00) (Reg 0x847e=0x00) (Reg 0x847f=0xba)
VR 1 Registers:
(Reg 0xa000=0x0000) (Reg 0xa001=0x0000) (Reg 0xa002=0x0000) (Reg 0xa003=0x0000)
(Reg 0xa004=0x0000) (Reg 0xa005=0x0000) (Reg 0xa006=0x0000) (Reg 0xa007=0x0001)
(Reg 0xa008=0x0003) (Reg 0xa009=0x0002) (Reg 0xa00a=0x0001) (Reg 0xa00b=0x0000)
(Reg 0xa00c=0x0000) (Reg 0xa00d=0x0000) (Reg 0xa00e=0x0000) (Reg 0xa00f=0x0000)
(Reg 0xa010=0x000e) (Reg 0xa011=0x0200) (Reg 0xa012=0x0000) (Reg 0xa013=0x0000)
(Reg 0xa014=0x0000) (Reg 0xa015=0x0000) (Reg 0xa016=0x0020) (Reg 0xa017=0x0000)
(Reg 0xa018=0x0000) (Reg 0xa019=0x0000) (Reg 0xa01a=0x0000) (Reg 0xa01b=0x0000)
(Reg 0xa01c=0x0000) (Reg 0xa01d=0x0002) (Reg 0xa01e=0x0000) (Reg 0xa01f=0x0000)
(Reg 0xa020=0x0000) (Reg 0xa021=0x0000) (Reg 0xa022=0x0000) (Reg 0xa023=0x0000)
(Reg 0xa024=0x0000) (Reg 0xa025=0x0000) (Reg 0xa026=0x0000) (Reg 0xa027=0x0000)
(Reg 0xa028=0x0040) (Reg 0xa029=0x8370) (Reg 0xa02a=0x0000) (Reg 0xa02b=0x0990)
(Reg 0xa02c=0x0000) (Reg 0xa02d=0x0000) (Reg 0xa02e=0x0000) (Reg 0xa02f=0x2116)
(Reg 0xa030=0x8019) (Reg 0xa031=0x0000) (Reg 0xa032=0x0000) (Reg 0xa033=0x0000)
(Reg 0xa034=0x0000) (Reg 0xa035=0x0000) (Reg 0xa036=0x0000) (Reg 0xa037=0x0000)
(Reg 0xa038=0x0000) (Reg 0xa039=0x0000) (Reg 0xa03a=0x0000)
NETWORK LANE VR 1 Registers:
(Reg 0xa200=0x0002) (Reg 0xa201=0x0000) (Reg 0xa202=0x0000) (Reg 0xa203=0x0000)
(Reg 0xa204=0x0000) (Reg 0xa205=0x0000) (Reg 0xa206=0x0000) (Reg 0xa207=0x0000)
(Reg 0xa208=0x0000) (Reg 0xa209=0x0000) (Reg 0xa20a=0x0000) (Reg 0xa20b=0x0000)
(Reg 0xa20c=0x0000) (Reg 0xa20d=0x0000) (Reg 0xa20e=0x0000) (Reg 0xa20f=0x0000)
(Reg 0xa210=0x0000) (Reg 0xa211=0x0000) (Reg 0xa212=0x0000) (Reg 0xa213=0x0000)
(Reg 0xa214=0x0000) (Reg 0xa215=0x0000) (Reg 0xa216=0x0000) (Reg 0xa217=0x0000)
(Reg 0xa218=0x0000) (Reg 0xa219=0x0000) (Reg 0xa21a=0x0000) (Reg 0xa21b=0x0000)
(Reg 0xa21c=0x0000) (Reg 0xa21d=0x0000) (Reg 0xa21e=0x0000) (Reg 0xa21f=0x0000)
(Reg 0xa220=0x0000) (Reg 0xa221=0x0000) (Reg 0xa222=0x0002) (Reg 0xa223=0x0002)
(Reg 0xa224=0x0000) (Reg 0xa225=0x0000) (Reg 0xa226=0x0000) (Reg 0xa227=0x0000)
(Reg 0xa228=0x0000) (Reg 0xa229=0x0000) (Reg 0xa22a=0x0000) (Reg 0xa22b=0x0000)
(Reg 0xa22c=0x0000) (Reg 0xa22d=0x0000) (Reg 0xa22e=0x0000) (Reg 0xa22f=0x0000)
(Reg 0xa230=0x0000) (Reg 0xa231=0x0000) (Reg 0xa232=0x0000) (Reg 0xa233=0x0000)
(Reg 0xa234=0x0000) (Reg 0xa235=0x0000) (Reg 0xa236=0x0000) (Reg 0xa237=0x0000)
(Reg 0xa238=0x0000) (Reg 0xa239=0x0000) (Reg 0xa23a=0x0000) (Reg 0xa23b=0x0000)
(Reg 0xa23c=0x0000) (Reg 0xa23d=0x0000) (Reg 0xa23e=0x0000) (Reg 0xa23f=0x0000)
(Reg 0xa240=0x9999) (Reg 0xa241=0x9999) (Reg 0xa242=0x9999) (Reg 0xa243=0x9999)
(Reg 0xa244=0x0000) (Reg 0xa245=0x0000) (Reg 0xa246=0x0000) (Reg 0xa247=0x0000)
(Reg 0xa248=0x0000) (Reg 0xa249=0x0000) (Reg 0xa24a=0x0000) (Reg 0xa24b=0x0000)
(Reg 0xa24c=0x0000) (Reg 0xa24d=0x0000) (Reg 0xa24e=0x0000) (Reg 0xa24f=0x0000)
(Reg 0xa250=0x805c) (Reg 0xa251=0x805c) (Reg 0xa252=0x805c) (Reg 0xa253=0x805c)
(Reg 0xa254=0x0000) (Reg 0xa255=0x0000) (Reg 0xa256=0x0000) (Reg 0xa257=0x0000)
(Reg 0xa258=0x0000) (Reg 0xa259=0x0000) (Reg 0xa25a=0x0000) (Reg 0xa25b=0x0000)
(Reg 0xa25c=0x0000) (Reg 0xa25d=0x0000) (Reg 0xa25e=0x0000) (Reg 0xa25f=0x0000)
(Reg 0xa260=0x0000)
NETWORK LANE VR 2 Registers:
(Reg 0xa280=0x0000) (Reg 0xa281=0x0000) (Reg 0xa282=0x0000) (Reg 0xa283=0x0000)
(Reg 0xa284=0x0000) (Reg 0xa285=0x0000) (Reg 0xa286=0x0000) (Reg 0xa287=0x0000)
(Reg 0xa288=0x0000) (Reg 0xa289=0x0000) (Reg 0xa28a=0x0000) (Reg 0xa28b=0x0000)
(Reg 0xa28c=0x0000) (Reg 0xa28d=0x0000) (Reg 0xa28e=0x0000) (Reg 0xa28f=0x0000)
(Reg 0xa290=0x0000) (Reg 0xa291=0x0000) (Reg 0xa292=0x0000) (Reg 0xa293=0x0000)
(Reg 0xa294=0x0000) (Reg 0xa295=0x0000) (Reg 0xa296=0x0000) (Reg 0xa297=0x0000)
(Reg 0xa298=0x0000) (Reg 0xa299=0x0000) (Reg 0xa29a=0x0000) (Reg 0xa29b=0x0000)
(Reg 0xa29c=0x0000) (Reg 0xa29d=0x0000) (Reg 0xa29e=0x0000) (Reg 0xa29f=0x0000)
(Reg 0xa2a0=0x7eee) (Reg 0xa2a1=0xabe7) (Reg 0xa2a2=0x7f6e) (Reg 0xa2a3=0x85ad)
(Reg 0xa2a4=0x0000) (Reg 0xa2a5=0x0000) (Reg 0xa2a6=0x0000) (Reg 0xa2a7=0x0000)
(Reg 0xa2a8=0x0000) (Reg 0xa2a9=0x0000) (Reg 0xa2aa=0x0000) (Reg 0xa2ab=0x0000)
(Reg 0xa2ac=0x0000) (Reg 0xa2ad=0x0000) (Reg 0xa2ae=0x0000) (Reg 0xa2af=0x0000)
(Reg 0xa2b0=0x2b53) (Reg 0xa2b1=0x2b77) (Reg 0xa2b2=0x2bab) (Reg 0xa2b3=0x2c07)
(Reg 0xa2b4=0x0000) (Reg 0xa2b5=0x0000) (Reg 0xa2b6=0x0000) (Reg 0xa2b7=0x0000)
(Reg 0xa2b8=0x0000) (Reg 0xa2b9=0x0000) (Reg 0xa2ba=0x0000) (Reg 0xa2bb=0x0000)
(Reg 0xa2bc=0x0000) (Reg 0xa2bd=0x0000) (Reg 0xa2be=0x0000) (Reg 0xa2bf=0x0000)
(Reg 0xa2c0=0x3321) (Reg 0xa2c1=0x2d65) (Reg 0xa2c2=0x2f8b) (Reg 0xa2c3=0x2fd1)
(Reg 0xa2c4=0x0000) (Reg 0xa2c5=0x0000) (Reg 0xa2c6=0x0000) (Reg 0xa2c7=0x0000)
(Reg 0xa2c8=0x0000) (Reg 0xa2c9=0x0000) (Reg 0xa2ca=0x0000) (Reg 0xa2cb=0x0000)
(Reg 0xa2cc=0x0000) (Reg 0xa2cd=0x0000) (Reg 0xa2ce=0x0000) (Reg 0xa2cf=0x0000)
(Reg 0xa2d0=0x01b6) (Reg 0xa2d1=0x0431) (Reg 0xa2d2=0x040d) (Reg 0xa2d3=0x0393)
(Reg 0xa2d4=0x0000) (Reg 0xa2d5=0x0000) (Reg 0xa2d6=0x0000) (Reg 0xa2d7=0x0000)
(Reg 0xa2d8=0x0000) (Reg 0xa2d9=0x0000) (Reg 0xa2da=0x0000) (Reg 0xa2db=0x0000)
(Reg 0xa2dc=0x0000) (Reg 0xa2dd=0x0000) (Reg 0xa2de=0x0000) (Reg 0xa2df=0x0000)
(Reg 0xa2e0=0x0000)
HOST LANE VR 1 Registers:
(Reg 0xa400=0x0000) (Reg 0xa401=0x0000) (Reg 0xa402=0x0000) (Reg 0xa403=0x0000)
(Reg 0xa404=0x0000) (Reg 0xa405=0x0000) (Reg 0xa406=0x0000) (Reg 0xa407=0x0000)
(Reg 0xa408=0x0000) (Reg 0xa409=0x0000) (Reg 0xa40a=0x0000) (Reg 0xa40b=0x0000)
(Reg 0xa40c=0x0000) (Reg 0xa40d=0x0000) (Reg 0xa40e=0x0000) (Reg 0xa40f=0x0000)
(Reg 0xa410=0x0000) (Reg 0xa411=0x0000) (Reg 0xa412=0x0000) (Reg 0xa413=0x0000)
(Reg 0xa414=0x0000) (Reg 0xa415=0x0000) (Reg 0xa416=0x0000) (Reg 0xa417=0x0000)
(Reg 0xa418=0x0000) (Reg 0xa419=0x0000) (Reg 0xa41a=0x0000) (Reg 0xa41b=0x0000)
(Reg 0xa41c=0x0000) (Reg 0xa41d=0x0000) (Reg 0xa41e=0x0000) (Reg 0xa41f=0x0000)
(Reg 0xa420=0x0003) (Reg 0xa421=0x0003) (Reg 0xa422=0x0003) (Reg 0xa423=0x0003)
(Reg 0xa424=0x0003) (Reg 0xa425=0x0003) (Reg 0xa426=0x0003) (Reg 0xa427=0x0003)
(Reg 0xa428=0x0003) (Reg 0xa429=0x0003) (Reg 0xa42a=0x0000) (Reg 0xa42b=0x0000)
(Reg 0xa42c=0x0000) (Reg 0xa42d=0x0000) (Reg 0xa42e=0x0000) (Reg 0xa42f=0x0000)
(Reg 0xa430=0x0000) (Reg 0xa431=0x0000) (Reg 0xa432=0x0000) (Reg 0xa433=0x0000)
(Reg 0xa434=0x0000) (Reg 0xa435=0x0000) (Reg 0xa436=0x0000) (Reg 0xa437=0x0000)
(Reg 0xa438=0x0000) (Reg 0xa439=0x0000) (Reg 0xa43a=0x0000) (Reg 0xa43b=0x0000)
(Reg 0xa43c=0x0000) (Reg 0xa43d=0x0000) (Reg 0xa43e=0x0000) (Reg 0xa43f=0x0000)
(Reg 0xa440=0x0007) (Reg 0xa441=0x0007) (Reg 0xa442=0x0007) (Reg 0xa443=0x0007)
(Reg 0xa444=0x0007) (Reg 0xa445=0x0007) (Reg 0xa446=0x0007) (Reg 0xa447=0x0007)
(Reg 0xa448=0x0007) (Reg 0xa449=0x0007) (Reg 0xa44a=0x0000) (Reg 0xa44b=0x0000)
(Reg 0xa44c=0x0000) (Reg 0xa44d=0x0000) (Reg 0xa44e=0x0000) (Reg 0xa44f=0x0000)
(Reg 0xa450=0x0000)
Thanks in advance,
Diego.I found an important issue:
Lane 0 rx power is lower than minimum expected.
http://www.cisco.com/en/US/partner/prod/collateral/modules/ps5455/data_sheet_c78-633027.html
I guess that's the main problem, but anyway, I would like to know more about this type of transceiver and how to troubleshoot it.
Thanks, Diego. -
Unable to see other OC4J nodes in a cluster
I have installed 2 instances of OracleAS on 2 separate machines, both machines ( Lnx-5 and Lnx-6 ) were installed with the J2EE component and WEB component.
During installation, I have selected Lnx-5 as the administration node of the cluster, and I have configured the discovery address using multicast address 225.0.0.33:8001.
There were no installations errors encountered and things seems to work fine.
However, on Lnx-5, it can't "see" Lnx-6 as one of its cluster nodes. On both Lnx-5 and Lnx-6, I see the following when I issued the "opmnctl @cluster status".
---- On Lnx-5 , here is what I got ---------
[root@Lnx-5 conf]# opmnctl @cluster status
Processes in Instance: Lnx5.anydomain.com
--------------------------------------------------------------+---------
ias-component | process-type | pid | status
--------------------------------------------------------------+---------
OC4JGroup:default_group | OC4J:home | 5392 | Alive
ASG | ASG | N/A | Down
HTTP_Server | HTTP_Server | 5391 | Alive
---- On Lnx-6 , here is what I got ---------
[root@Lnx-6 conf]# opmnctl @cluster status
Processes in Instance: Lnx6.anydomain.com
--------------------------------------------------------------+---------
ias-component | process-type | pid | status
--------------------------------------------------------------+---------
OC4JGroup:default_group | OC4J:home | 5392 | Alive
ASG | ASG | N/A | Down
HTTP_Server | HTTP_Server | 5391 | Alive
I suppose I should see both Lnx-5 and Lnx-6 when I issue the commad in either nodes.
I have also verified that both machine are synchronized to the NTP server.
I have also done a tcpdump on both nodes, indeed I can multicast ( 225.0.0.33:8001 ) packets arriving at both nodes..
Really need some help in what would have go wrong, what information should I look for to address this issue.
Thanks in advance!!Ok, for the discovery server configuration, here is the config that I have in the opmn.xml file, both lnx-5 and lnx-6 use exactly the same configuration :
<notification-server interface="ipv4">
<port local="6101" remote="6201" request="6004"/>
<ssl enabled="true" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
<topology>
<discover list="10.1.230.11:6201,10.1.230.12:6201"/>
</topology>
</notification-server>
the ip address of Lnx-5 is 10.1.230.11, and Lnx-6 is 10.1.230.12.
Once this was configured on both Lnx-5, Lnx-6, I keep seeing this error from the Lnx-6's log file :
07/05/16 22:10:18 [pm-process] Process Alive: default_group~home~default_group~1
(1542677438:3859)
07/05/16 22:10:18 [pm-requests] Request 2 Completed. Command: /start
07/05/16 22:13:25 [ons-connect] Connection 9,10.1.230.11,6201 connect (Connectio
n refused)
07/05/16 22:13:26 [ons-connect] Connection a,10.1.230.12,6201 connect (Connectio
n refused)
Well, Once I enabled the debugging, there were some errors reported when opmn is started, the errors are as follows :
Loading Module libopmnohs callback functions
Module libopmnohs: loaded callback function opmnModInitialize
Module libopmnohs: unable to load callback function opmnModSetNumProcs
Module libopmnohs: unable to load callback function opmnModParse
Module libopmnohs: unable to load callback function opmnModDebug
Module libopmnohs: unable to load callback function opmnModDepend
Module libopmnohs: loaded callback function opmnModStart
Module libopmnohs: unable to load callback function opmnModReady
Module libopmnohs: loaded callback function opmnModNotify
Module libopmnohs: loaded callback function opmnModRestart
Module libopmnohs: loaded callback function opmnModStop
Module libopmnohs: loaded callback function opmnModPing
Module libopmnohs: loaded callback function opmnModProcRestore
Module libopmnohs: loaded callback function opmnModProcComp
Module libopmnohs: unable to load callback function opmnModReqComp
Module libopmnohs: unable to load callback function opmnModCall
Module libopmnohs: unable to load callback function opmnModInfo
Module libopmnohs: unable to load callback function opmnModCron
Module libopmnohs: loaded callback function opmnModTerminate
Loading Module libopmnoc4j callback functions
Module libopmnoc4j: loaded callback function opmnModInitialize
Module libopmnoc4j: unable to load callback function opmnModSetNumProcs
Module libopmnoc4j: loaded callback function opmnModParse
Module libopmnoc4j: unable to load callback function opmnModDebug
Module libopmnoc4j: unable to load callback function opmnModDepend
Module libopmnoc4j: loaded callback function opmnModStart
Module libopmnoc4j: unable to load callback function opmnModReady
Module libopmnoc4j: loaded callback function opmnModNotify
Module libopmnoc4j: loaded callback function opmnModRestart
Module libopmnoc4j: loaded callback function opmnModStop
Module libopmnoc4j: loaded callback function opmnModPing
Module libopmnoc4j: loaded callback function opmnModProcRestore
Module libopmnoc4j: loaded callback function opmnModProcComp
Module libopmnoc4j: unable to load callback function opmnModReqComp
Module libopmnoc4j: unable to load callback function opmnModCall
Module libopmnoc4j: unable to load callback function opmnModInfo
Module libopmnoc4j: unable to load callback function opmnModCron
Module libopmnoc4j: loaded callback function opmnModTerminate
Loading Module libopmncustom callback functions
Module libopmncustom: loaded callback function opmnModInitialize
Module libopmncustom: unable to load callback function opmnModSetNumProcs
Module libopmncustom: loaded callback function opmnModParse
Module libopmncustom: loaded callback function opmnModDebug
Module libopmncustom: unable to load callback function opmnModDepend
Module libopmncustom: loaded callback function opmnModStart
Module libopmncustom: loaded callback function opmnModReady
Module libopmncustom: unable to load callback function opmnModNotify
Module libopmncustom: loaded callback function opmnModRestart
Module libopmncustom: loaded callback function opmnModStop
Module libopmncustom: loaded callback function opmnModPing
Module libopmncustom: loaded callback function opmnModProcRestore
Module libopmncustom: loaded callback function opmnModProcComp
Module libopmncustom: loaded callback function opmnModReqComp
Module libopmncustom: unable to load callback function opmnModCall
Module libopmncustom: unable to load callback function opmnModInfo
Module libopmncustom: unable to load callback function opmnModCron
Module libopmncustom: loaded callback function opmnModTerminate
Loading Module libopmniaspt callback functions
Module libopmniaspt: loaded callback function opmnModInitialize
Module libopmniaspt: unable to load callback function opmnModSetNumProcs
Module libopmniaspt: unable to load callback function opmnModParse
Module libopmniaspt: unable to load callback function opmnModDebug
Module libopmniaspt: unable to load callback function opmnModDepend
Module libopmniaspt: loaded callback function opmnModStart
Module libopmniaspt: loaded callback function opmnModReady
Module libopmniaspt: unable to load callback function opmnModNotify
Module libopmniaspt: unable to load callback function opmnModRestart
Module libopmniaspt: loaded callback function opmnModStop
Module libopmniaspt: unable to load callback function opmnModPing
Module libopmniaspt: unable to load callback function opmnModProcRestore
Module libopmniaspt: loaded callback function opmnModProcComp
Module libopmniaspt: unable to load callback function opmnModReqComp
Module libopmniaspt: unable to load callback function opmnModCall
Module libopmniaspt: unable to load callback function opmnModInfo
Module libopmniaspt: unable to load callback function opmnModCron
Module libopmniaspt: loaded callback function opmnModTerminate
Looks pretty bad.. What cuases those errors to happen? Are they related?
Thanks!!
Maybe you are looking for
-
My ipod not recognisable by itunes i have tried everything suggested by app
ok, here is how it started. i wanted album art in my ipod, so i searched the web got all the album art i could and put in each album stored in my itunes. everything was going smoothly when it came to one particular album and from tat time i m having
-
I've asked the question above. I just need to talk to someone who can tell me IF my subscription has actually expired. If it has, on what date. And, if it has why is my credit card continuing to be charged the monthly fee.
-
I tried all resets.
-
Has there been a thunderbolt firewire hub put out on the market yet? I want to try it with Wirecast 4. Wish to connect two firewire cameras
-
Where can I find a bookmarks system file in the Firefox app for Android?
What's the name of the bookmarks file in FF for Android?